The ODF-Converter translates OpenXML documents (.DOCX) to Open Document Format (.Open Document Format) (and conversely) for Open XML processing applications. You will find below the list of unsupported features which may be due to standard compatibility issues, or to the translator itself (see rendering issues as discussed in the
blog)...
Page Comments
David A. Wheeler submitted a comment to the OASIS ODF TC outlining his concerns with this publication. He suggests that a few minor changes to ODF could greatly improve compatibility - interop issues. He also figures out that OpenOffice - ODF has more features than MSOffice - MOOXML. Wha the doesn't ge is that it is these new and innovative features that continue to increase the difficulties of implementing ODF in real world business process workgroups!
David also ignores the fact that the TC jus tvoted down the Novell "LIt Enhancement Proposal" which was specifically designed to address the compatibility - interop issues outlined in this odf-converter blog! Given a choice, the ODF TC members chose the new and innovative features of the interop breaking Sun-KOffice "List Enhancement Proposal".
The List Enhancement Proposal discussion was so contentious and focused on personal destruction as to represent a total break down of the ODF concensus process. There is no way that either the Foundation or Novell will ever contribute another compatibility - interop enhancement proposal given the personal assault and determined oppostion of Sun to compatibility - interoperability initiatives.
The hard lesson the Foundation learned is that if you oppose Sun, you'll get booted out of OASIS!
The lesson Novell learned is that they are better off working through Ecma 376 to resolve these issues that the public demands be addressed.
Notice the last line in David's comment, "In any case, the MUCH, MUCH longer list of problems with Microsoft XML format isn't our problem."
During the contentious List Enhancement Proposal and the compatibility - interop related Metadata RDF/XML discussions, ODF members frequently use terms like, "not our problem, out of scope, out of bounds, outside our charter, and not supported by OpenOffice" to dismiss any and all efforts at compatibiltiy and interop with MSOffice application specific legacy documents and business processes. I've personally witnessed this for four and a half years now, and it's time for the ODF TC to come clean with the public. Enough is enough.
Here's David's comment to the ODF TC:
[office] Would someone examine list for "missing" ODF capabilities?
1 message
David A. Wheeler
<dwheeler@dwheeler.com>
Fri, May 25, 2007 at 12:28 PM
Reply-To:
dwheeler@dwheeler.com
To:
office@lists.oasis-open.org
Before we wrap up the latest revision of OpenDocument,
could someone look through this "features" file to see what (if
anything) should be added to ODF, and if so how?:
http://odf-converter.sourcefor
I
think several of the items are actually NOT problems in ODF, but
misunderstandings of the authors. Also, in many cases the authors seem
to confuse the OpenDocument specification with OpenOffice.org (which as
we all know is just one of several products that IMPLEMENT
OpenDocument) - and so are just feature requests for OpenOffice.org.
But I think there are probably a few gems in here -- i.e., items that
simply need the addition of an attribute that would really aid users.
Be sure to check the "Undocumented features" section of the webpage
too. I would do this, but I've been focusing on formulas and nothing
in this document relates to formulas - it's only about comparing
OpenDocument to Microsoft XML's DOCX.
Adding such capabilities, where we haven't already, would simplify people's transition to OpenDocument.
By
the way, an interesting statistic: When printed, this webpage has about
SIX PRINTED PAGES of capabilities that OpenDocument can do, but
Microsoft XML cannot. In contrast, it only has about TWO printed pages
of stuff that Microsoft XML, but (it claims) that OpenDocument cannot.
And while I can't speak to the Microsoft XML list, it appears to me
that many of the "ODF can't do this" material is really just "does it
differently" or "OpenOffice.org doesn't do this" instead of actual
OpenDocument limitations. For example, they say ODF can't "start page
numbering with something other than 1" but in fact I do that routinely.
And some of the Microsoft XML limitations of DOCX are nasty! For
example: Microsoft XML tables can only hold up to 63 columns, it cannot
prevent table splitting, table headings can't be multiple rows (and
thus fail to be duplicated on new pages), it doesn't support rotating
text by 90 or 270 degrees, controlling the number of widow/orphan lines
isn't available, justified paragraphs can't change the last line
alignment (so justified paragraphs are often impractical to use), and
so on. At least, that's what this analysis seems to say.
That
suggests that Microsoft XML format is MUCH more limited, and unable to
represent many real-world documents, compared to OpenDocument. Which
shouldn't be surprising, since OpenDocument development included a
large number of different organizations who actively worked together to
create a format that EVERYONE could represent their documents in.
Also, note that the referenced page only compares Microsoft XML and
OpenDocument. Microsoft XML appears to have problems representing
.doc/.xls files as well, though whether this is a problem with the
format or their tool I don't know. E.G.:
http://www.robweir.com/blog
In any case, the MUCH, MUCH longer list of problems with Microsoft XML format isn't our problem.
Thanks.
--- David A. Wheeler
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.