KOffice Developers Reply to Yates
danimo writes "In response to his letter to the Massachusetts administration, the KOffice team has written an open letter to Microsoft manager Alan Yates. It clarifies some false claims that Yates made, such as KOffice, StarOffice and OpenOffice.org being one codebase and that OpenDocument was thus never a real standard. Massachusetts has meanwhile adopted OpenDocument."
Microsoft spreads Fear Uncertainty and Doubt, what a shocker!
Bavarian Purity Law of Rice Krispie Squares: Rice Krispies, Marshmallows, Butter, Vanilla.
Why even bother with word processors these days when LaTeX is more than capable of the vast majority of document typesetting needs? It does take a bit longer to learn that Word, but everyone I know who has learned it has become far more efficient and can produce documents that are far more professional.
Cyric Zndovzny at your service.
I wish my organization would switch to some kind of inexpensive standard. We are starting to feel pressure from problems caused by running different versions of Word, or upgrading from OS9 to OSX and wishing they could take their license with them (without running in classic mode), or some people don't think it's worth the money to switch from AppleWorks (which sucks, by the way) to Word, and then we have to try to read documents in ClarisWorks (which also sucks) format in Word and vice-versa, and we are getting SICK OF IT! And I only work in an elementary school!
I cried real tears when Li Mu Bai died.
So he's not just "trying to save only [his] own face," but is actually pointing out that there are multiple implementations and that OpenDocument really is a standard.
Of course, it wouldn't even be a problem if they were the same codebase, because since they're Free Software they can all share the same code. Certainly, Microsoft could support OpenDocument easily just by copying the same code into Office, right?
...oh, wait.
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
They say it's "illegal" to standardize on OpenDocument and back that up with the (false) claim that the tools that support it are from a single codebase.
All so they can convince the Mass. gov't to use their own single codebase "standard."
The reason is simple. Typesetters/formatters are great for generating splendid output. But most people never produce a hardcopy (or any "final" output) for 90% of their documents. Instead, their documents are workplaces for organizing ideas, bascially pseudo-database records in a filing system stored in their "My Documents" folder.
In short, the vast majority of word processor use is for manipulating, organizing, and retrieving text-based data in a format rapidly parsable by human eyes as part of a workflow or thought process.
For such things, LaTeX, troff, or any other text formatter... sucks. In fact, it isn't even appropriate for the task.
But you're right, if you just want nicely structured, rendered output in hardcopy or PDF, you can't beat 'em.
STOP . AMERICA . NOW
Martin Kotulla
SoftMaker Software GmbH
SoftMaker Office for Windows|Linux|Android