Plugins for Microsoft Office for OpenOffice Documents?
DeBaas asks: "We are all in favour of getting Open Standards in place so that we can happily use Open/Star/K Office or whatever without the nagging problem: The Microsoft Office users cannot read our files correctly.
Much of the focus is on providing filters to be able to make and read Microsoft Office files. However, should it not be the other way around, as well? Would it be feasible to make an open source project providing a plugin to MS office so that it can read and write in our preferred open format. Sort of a 'save as open document standard'. Is there a legal problem?, a technical problem? (is it already possible?) I would love it if I could send documents in OpenOffice knowing the other site can actually use and see it the way I meant to, even with MicroSoft Office."
This seems like a good idea initially, but if people can continue using MS Office to communicate with users of OpenOffice.org and StarOffice, then what encouragement do they have to use the free/less expensive alternatives? I think that, while this might encourage a standard document format, it has the negative effect of encouraging MS Office use.
I hate to say this, but I think in this case the wise choice is to use MS's tactics against itself.
A solution to the problem with music today
Not even remotely feasible. Probably technically possible, but utterly pointless. Now you not only have to have Word 2k5 installed, but you need to download some plugin from somewhere in order to read a .doc file you found on the net.
Hint: "Oh, this file is corrupted. *DELETE*" is the first thing that will occur to any normal windows user upon trying to read your "open .doc" file.
It's only worthwhile to make outputting perfectly M$-compliant word documents. Otherwise your interoperability = zero.
--that's one of the better "can't see the forest for the trees" bingo epiphanies I have read here on slashdot. Outstanding., Ya, it might slow down adoption for these other companies, but so what? Eventually they'll want to move on,more hardware and new software, by then they'll think "hey, might as well use the open stuff, makes mucho sense and cents to do so".
Most individuals don't buy Office -- the people they work for buy it. So, the price is irrelevant to most individual users. They'd use quill pens if that's what the boss wanted, so Microsoft's tactics mean zip to them.
Of course, MS is trying to protect their market position with Office by manipulating file formats. Why would you expect them to do anything different? MacDonald's manipulates its products and recipes to protect its market position, too.
I suspect that only people who choose their software for ideological reasons will make an effort to do a standards end-run around Office.
The real solution here, as elsewhere, is for open source to give consumers something innovative that makes Office obsolete.
-- Slashdot: When Public Access TV Says "No"
HTML is not a WYSIWYG language, it shouldn't be
HTML+CSS with paged media, on the other hand, comes very close, at least as close as RTF.
And RTF doesn't render many things reliable from one application to another.
Neither does .doc. It may screw up layout between computers with different fonts, different versions of a font, or different versions of Microsoft Word software. If you want to preserve the exact look of a page while sacrificing editability, use PDF. If you want to preserve editability, use something like LaTeX, DocBook, or HTML+CSS.
RTF doesn't appear to have the capability to generate complicated table structures I need.
Then use HTML+CSS instead. Heck, HTML export programs used to do layout with tables.
Will I retire or break 10K?