Just 150 years to go. Just do it.
OOXML is a sensitive subject, but if issues are not raised out in the open, we are destined to be locked down in another digital dark age. Although one man has attempted to implement rudimentary OOXML support in Gnumeric, it is estimated that it would take 150 man years to implement OOXML as it stands at moment (incomplete).
…we’re now looking at 150 man years to do the job for a competitive PPA.
”In fact, not even Microsoft Office 2007 implements something which complies with the existing specification.“There is no source code available for reuse (Microsoft Office is purely closed-source and proprietary) and there is no proper reuse of existing standards (e.g. for dates) inside OOXML. Also remember that Microsoft admitted that it is not committed to sticking to its own specification (OOXML), which makes it a moving target. In fact, not even Microsoft Office 2007 implements something which complies with the existing specification. It’s merely a derivative which ensures no compatibility through a ‘golden’ reference (a written document, spread across over 6,000 pages). There are serious patent issues to consider, but sadly enough, no-one seems to notice.
I fail to see why Gnumeric has very, very basic support for OOXML
while ODF support (the ISO standard) does not have any support yet. That’s just what I was told yesterday. Are non-standards given precedence over international and open standards, which are suddenly/temporarily worth neglecting? [Correction: ODF support is coming shortly. See comments below.] The following assessment seems unrealistic.
Among the many other topics discussed at Ontario LinuxFest was a completely objective comparison of Microsoft’s OOXML document standard and OpenOffice.org’s ODF document standard by Gnumeric maintainer Jody Goldberg, who has had to wade through both in depth. His summary is that OOXML is not the spawn of Satan, and ODF is not the epitome of perfection. Both have their strengths and weaknesses, and he sees no reason why we could not go forward with both standards in use.
See the aforementioned remarks about the complexity involved in implementing OOXML, which carries a patent burden and will probably be ignored by Microsoft, which will ‘extend’ things its own way in order to ensure obsolescence (forced upgrades) and poor compatibility with other applications (technical sabotage). █