Linked by Thom Holwerda on Sat 6th May 2006 22:05 UTC
Permalink for comment 121744
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/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2006-01-11
I disagree with your assessment. Without perfect format compatibility, switching away from Office can be too risky; You're at a comparative disadvantage because transactions with the outside world go less smoothly.
So, you want perfect format compatibility so that using, say, OpenOffice doesn't put you at a disadvantage. But it's tough for OO devs to get Office format handling just right. And as long as MS keeps its format obscured and doesn't have ODF support, OO has to dance to MS's tune.
The beauty of this plugin is, it gives OO an opening to turn the tables. The way things currently are, a person has to download and install a couple hundred megs of extra, unfamiliar software to read ODF. I cannot reasonably expect this out of just anybody I send an email attachment to. But if the plugin is considerably smaller than OO, I'd definitely feel better about sending people .odf files and telling them how to open them.
IOW, ODF evangelism becomes a more realistic option. Perfect compatibility is attainable, and on ODF rather than on MS format. And by extension, switching away from Office becomes more realistic. A win for ODF is a win for OO.