|
|
|
| Authored by: stegu on Wednesday, August 15 2012 @ 04:50 AM EDT |
> I wonder if OOXML fully supports all of Microsoft's current features ...
It doesn't. They extended and subverted their own "standard" right
from the start so that anyone else's standard OOXML files would be incompatible
with the sort-of OOXML files from MS Office, and switching to the (allegedly)
standards-compliant OOXML mode in Office 2012 will most probably invoke an
onslaught of compatibility warnings that try to discourage users from ever using
that format for anything. MS only does lip service here - their business depends
on *not* using a standard, but many procurement contracts require them to at
least formally support a standards-compliant file format. MS effectively
extinguished the standard long before it ever became relevant for actual use.
Another issue is that OOXML is still a broken standard. There are so many
remaining errors and internal inconsistencies in the specification that it is
impossible to implement it to spec. Maybe this recent effort forces Microsoft to
maintain and update the specification, but I doubt it. From the look of it, they
have very bad internal documentation and depend on old and smelly source code
that they have been using for all versions of Office since 1995, with minimal
maintenance and no refactorization. MS can be described as a dinosaur, and by
that analogy their source code is the fossil record of a bygone era.
[ Reply to This | Parent | # ]
|
- Broken by design - Authored by: Anonymous on Wednesday, August 15 2012 @ 11:52 AM EDT
- since 1995 - Authored by: Anonymous on Wednesday, August 15 2012 @ 05:19 PM EDT
|
|
|
|
