Linked by Thom Holwerda on Tue 4th Sep 2007 21:40 UTC, submitted by archiesteel
Features, Office Microsoft has failed in its attempt to have its Office Open XML document format fast-tracked straight to the status of an international standard by the International Organization for Standardization. The proposal must now be revised to take into account the negative comments made during the voting process. Microsoft expects that a second vote early next year will result in approval, it said Tuesday. That is by no means certain, however, given the objections raised by some national standards bodies.
Thread beginning with comment 268718
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Miguel de Icaza's take
by lemur2 on Wed 5th Sep 2007 04:48 UTC in reply to "RE[4]: Miguel de Icaza's take"
lemur2
Member since:
2007-02-17

Think "email attachments". Think "sharepoint". Think "double-click in the file manager". You need to be able to associate your Office applications directly with a file format in order for these work-flow actions to work. Therefore, you need your Office application to be able to directly open and save the format.

So it's Microsoft's fault if no one other than them implements the formats? If I'm using Lotus, should I blame IBM if their tools are optimized for ODF, but I want to use Office instead?


You got that utterly backwards. If you have an ODF file and your Windows system has MS Office installed as the Office suite and Microsoft's ODF converters, then you cannot click on ODF email attachments, you cannot use ODF files in sharepoint and you cannot double-click on ODF files in a file manager and have your Office suite application open the file. Essentially, you cannot associate ODF files with MS Office if the only capability you have is Microsoft's ODF converters. This is because Microsoft's ODF converters cannot be set as a "save as" format, and you cannot just open ODF files via the converter (ie. you have to "import" ODF files).

Yes, this is indeed Microsoft's fault. Entirely. It is deliberate. It is Microsoft that mandates that the workings of CleverAge ODF support for MS Office is via converters.

Sun's ODF plugins do not have this restriction.

Reply Parent Bookmark Score: 4

RE[6]: Miguel de Icaza's take
by n4cer on Wed 5th Sep 2007 06:07 in reply to "RE[5]: Miguel de Icaza's take"
n4cer Member since:
2005-07-06

You got that utterly backwards. If you have an ODF file and your Windows system has MS Office installed as the Office suite and Microsoft's ODF converters, then you cannot click on ODF email attachments, you cannot use ODF files in sharepoint and you cannot double-click on ODF files in a file manager and have your Office suite application open the file.


Then change the file associations. It's easy to do. Just because you have Office installed, you don't have to use it to open ODF files. Install an ODF editor and associate it with ODF files.

Yes, this is indeed Microsoft's fault. Entirely. It is deliberate. It is Microsoft that mandates that the workings of CleverAge ODF support for MS Office is via converters. Sun's ODF plugins do not have this restriction.


Then what's the issue. Use Sun's plugins or use CleverAge's source to build the support (which Sun does IIRC).

Reply Parent Bookmark Score: 2