Linked by Thom Holwerda on Mon 4th Dec 2006 22:26 UTC
Permalink for comment 188100
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 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2005-11-11
//features available in their product of choice because ODF can't currently support them//
Which features are these?
Remember, Microsoft were a participant of the ODF committee. If there is any Microsoft-only feature within an office format and interoperation protocols that ODF cannot "connect" to, then it is that way only because Microsoft refused to open up the interface to let ODF interoperate with that.
Microsoft had two options that would have achieved interoperability: (1) support interoperability by adopting ODF and the other attendant features such as SVG, ogg & SIML, or (2) open up their own formats to allow competing products to be written (even as open source), including all of the attendant features such as ActiveX, wmv, wma, OLE, binary blobs from legacy MS Office formats, exchange connector, etc, etc, etc.
Microsoft have done neither of these. People should abandon Microsofts offerings for this reason.
Edited 2006-12-05 02:15