Microsoft Votes to Add ODF to ANSI Standards List

RzUpAnmsCwrds writes "In a puzzling move, Microsoft today voted to support the addition of the OpenDocument file formats to the American National Standards List. OpenDocument is used by many free-software office suites, including OpenOffice.org. Microsoft is still pushing its own Office Open XML format, which it hopes will also become an ANSI standard. Is Microsoft serious about supporting ODF, or is this a merely a PR stunt to make Office Open XML look more like a legitimate standard?"

Comments

Re:My Name Is Bill

[Falladir]

rtf is not an open format. From a popular commentary:

In earlier versions of this document, I listed RTF (Rich Text Format) as a more standards based way of exchanging word-processor documents. I have been corrected on that point innumerable times. RTF is little better than MS-Word format itself. It is a little better, but it shares all of the problems as MS-Word. Although RTF was advertised as a document exchange format, it never lived up to that. It appears to have varying features, and the various version of RTF that Microsoft products create have elements which only Microsoft Products can read. Note that this is not because MS-Word is a better product, but because Microsoft keeps elements of what it considers to be RTF secret.

Consumers may not care what format their stuff is in, but when they get a replay saying "sorry, I can't seem to open that .doc, could you save it as .odt?" they'll care whether their word-processor can do it.

Re:My Name Is Bill

[spun]

Come on, if .rtf and .txt could store the files that Word could create, people would never have used .doc. What a poorly thought out response, equating .rtf and .txt with formats that can actually, you know, store all the formatting you applied to your documents.

Not necessarily.

[khasim]

However, it's going to be harder and harder, as OpenOffice will implement a way to read and write MS's XML format, since it HAS to be documented if MS intends to satisfy government customers.

As can be seen with their current "standard", they can just cite "behave the same way as MS Word version X.y.z on OS a" and claim that it is "documented".

Since Microsoft is the only ones who REALLY know how that behaviour was implemented, they'll be the only one who can write a compleat implementation.

Just as the situation is today. Look at the "reviews" of OpenOffice.org by various "journalists". You'll see them complaining that the formating on a document was "messed up" when they went
from MS Word
to OpenOffice.org
back to MS Word.

Now, if there are a dozen word processors out there and they all implement the ODF standard and none of them (except MS Word) trashes the formatting when bouncing a document between the other 11 ...

THAT is what businesses and governments want. The ability to see the same document the same way no matter WHO edited it on WHAT operating system using WHICH word processor.

If Microsoft fails at that it will be because Microsoft failed on their own.

Re:My Name Is Bill

[edwdig]

RTF is simply a version of .doc that's largely ASCII text. It's main purpose was to be a format that was easier for tools to parse. Windows Help files used to be based off it. You can still drop whatever random objects into it.

Microsoft hasn't stood in the way of ODF at all???

[mpapet]

Really???

Then what the hell happened in Massachusetts wanted to switch to ODF?? Here's a long-winded citation: http://searchenterpriselinux.techtarget.com/origin alContent/0,289142,sid39_gci1144104,00.html

No, they'll do what they already do with everything that's not a .doc (or whatever extension is next) make it _really_ hard to use anything but .whatever.

Re:Red herring

[prockcore]

IE, Firefox, and Opera all support DesignMode extensively. Safari is the odd man out, failing to support 90% of the execCommands, and failing to even return the proper return value.

IE, Firefox, and Opera all support XSLTProcessor. Safari is the odd man out, failing to support it at all.

It's disingenuous to say that FF, Opera and Safari are all pretty much equivilent and IE is the one with all the weird exceptions. In fact, it's more accurate to say Safari is the weird browser. Safari's javascript is at least 4 years behind all the others. Didn't even support Ajax until Safari2.

Re:Why would it be puzzling?

[1110110001]

Windows had threading for years before POSIX did. Keep your fork().

1003.1c-1994 (real-time extensions and threads). Thus it had to be in Windows 3.0 or 3.1 because for years is at least two years and NT came out in 1993, which is too late.

And fork() is not that bad if done right.

Funny how MS gets an instant bad wrap

[mgiuca]

Isn't it funny how, when Microsoft does something puzzlingly in support of what we've all been asking for all this time, rather than being congratulated, the Slashdot crowd immediately starts trying to guess what their devious secret strategy is here to achieve world domination?

Possible reason for this: They have been around for thirty years, and in all that time, they have ALWAYS had a devious secret strategy to achieve world domination!

On with the speculation!

Obviously they're just doing this to make themselves look better when it comes time to vote for OOXML!