Linked by Thom Holwerda on Mon 4th Dec 2006 22:26 UTC
Permalink for comment 188828
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
More News »
Sponsored Links



Member since:
2005-07-06
Care to list these "features" you refer?
2. ODF codifies a format that excludes the MS Office features that OO.o lacks. So any one (e.g. a misguided govt entity) that mandates that all documentation be ODF is makes the extra MS features unusable, allowing OO.o to better compete.
Which one? ODF only uses the existing nomenclature like XHTML, SGML, SVG and MathML. Do you insinuate MS Office does not support these? What really stop a multi billionaire company to support them given their large amount of resource?
If a format depends on a particular feature from an Office application, that is unacceptable and must be avoid for the sake of my own data.