OpenOffice .odt Opened Up - Part 1: Overview
,----[ Quote ]
| The office:document may contain any of the document elements listed
| below.
|
| * office:document-attrs
| * office:document-common-attrs
| * office:meta
| * office:settings
| * office:scripts
| * office:font-face-decls
| * office:styles
| * office:automatic-styles
| * office:master-styles
| * office:body
`----
http://3monkeyweb.com/3monkeys/2007/01/12/openoffice-odt-opened-up-part-1/
There are some visual examples in this article. See below for contrasts.
Related:
How to hire Guillaume Portes
,----[ Quote ]
| This is a running criticism I have of Microsoft's Office Open XML
| (OOXML). It has been narrowly crafted to accommodate a single
| vendor's applications. Its extreme length (over 6,000 pages)
| stems from it having detailed every detail of MS Office in an
| inextensible, inflexible manner. This is not a specification;
| this is a DNA sequence. For example, take this part of the
| OOXML "Standard":
|
| 2.15.3.6 autoSpaceLikeWord95 (Emulate Word 95 Full-Width
| Character Spacing)
|
| This element specifies that applications shall emulate the
| behavior of a previously existing word processing application
| (Microsoft Word 95) when determining the spacing between full-width
| East Asian characters in a document's content.
|
| [...]
|
| 2.15.3.26 footnoteLayoutLikeWW8 (Emulate Word 6.x/95/97
| Footnote Placement)
|
| This element specifies that applications shall emulate the
| behavior of a previously existing word processing application
| (Microsoft Word 6.x/95/97) when determining the placement of
| the contents of footnotes relative to the page on which the
| footnote reference occurs. This emulation typically involves
| some and/or all of the footnote being inappropriately placed
| on the page following the footnote reference.
`----
http://www.robweir.com/blog/2006/01/how-to-hire-guillaume-portes.html
Is Open XML a one way specification for most people?
,----[ Quote ]
| Who will implement Open XML correctly and fully? Maybe Microsoft.
| Why? Since it is essentially a dump into XML of all the data
| needed for all the functionality of their Office products and
| since those products are proprietary, only they will understand
| any nuances that go beyond the spec. The spec may illuminate
| some of the mistakes that have been made and are now being
| written into a so called standard for all to have to implement,
| but I'm guessing there might be a few other shades of meaning
| that will not be clear. Fully and correctly implementing Open
| XML will require the cloning of a large portion of Microsoft's
| product. Best of luck doing that, especially since they have
| over a decade head start. Also, since they have avoided using
| industry standards like SVG and MathML, you'll have to
| reimplement Microsoft's flavor of many things. You had
| better start now. So therefore I conclude that while Microsoft
| may end up supporting most of Open XML (and we'll have to
| see the final products to see how much and how correctly),
| other products will likely only end up supporting a subset.
`----
http://sutor.com/newsite/blog-open/?p=1145
|
|
