Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Comparison (Score 2, Insightful) 48

by ColourlessGreenIdeas (#22051138) Attached to: Roadmap To the OOXML Process
This fails to deal with the main problem.

Most criticisms of OOXML deal with the fact that it is a hastily implemented pile of incomprehensible rubbish that no-one in the world will ever implement correctly and that Microsoft is allowed to change at will without consultation. However, this actually utterly misses the point of the problem of OOXML, and the reason why MS is so opposed to ODF.

The issue is that ODF forbids you from embracing and extending while OOXML allows you to. This means that if you've got an ODF document and an ODF reader, you can read the document. This is not true for OOXML as anyone (MS) is allowed to put random rubbish in the middle of the document, that a different application might not understand.

MS criticises ODF for missing features, but never make clear that this 'problem' cannot be fixed by adding features; they are in fact criticising ODF for standardising what constitutes a valid ODF document.

"Life sucks, but it's better than the alternative." -- Peter da Silva

Working...