Slashdot Mirror
ODF Offers MS Word Plugin to MA
Goalie_Ca writes "Groklaw just posted that the OpenDocument Foundation is offering Massachusetts a plugin that could 'allow Microsoft Office to easily open, render, and save to ODF files, and also allow translation of documents between Microsoft's binary (.doc, .xls, .ppt) or XML formats and ODF ... The testing has been extensive and thorough. As far as we can tell there isn't a problem, even with Accessibility add ons, which as you know is a major concern for Massachusetts.'"
Microsoft will make sure this plugin won't work well for a long time ;)
Sure there isn't the same victory for OSS in having them switch to OpenOffice as some would like, it instead shows that OSS can adapt as needed and allow the state to continue to use the same front end app and not have to deal with the cost and hassle of retraining countless workers with a new system.
At the same time though... this does conceivably give more power to Redmond as there is now less incentive for MA to leave the Windows/Office platform.
Help Brendan pay off his student loans
Microsoft can't/won't provide interoperability tools, but the ODF (an organization with far more money, right?) is able to do it.
I love it.
It was a joke! When you give me that look it was a joke.
Embrace and Extend...
As far as we can tell there isn't a problem, even with Accessibility add ons, which as you know is a major concern for Massachusetts.
I've met plenty of people from Massachusetts. I can imagine the Accessibility add-ons would be crucial there.
No one posts a link?
wtf is the point of posting something like this without a link?
wtf good is a plugin if no one can get it...
eesh
Microsoft built Word/Office with Plug-in support, did they not? In fact, they built their OS with every intention that other companies would offer services on their platform.
This foundation has decided to do so.
Kudos to them. They just proved that there is none of that so-called vendor lock-in.
Sure, it takes effort, but if you can be bothered to do it, it pays off.
Can you feel it? It's the tide of inevitibility.
Why? The Catch 22 has been solved (we need MS vs. can't convert while using MS). And it's the bean counters that ultimately sway government decisions.
1) Plugin will be installed on gov pc's
2) Documents will be handled in ODF
3) Gov bean counters will be suggesting to managers everywhere they can save $XXXX if they use OpenOffice instead of MS Office
The world is made by those who show up for the job.
Seriously. I don't use MSOffice all that much, but have to constantly exchange .doc, .xls, etc. formats all the time with other people. For the most part, OO.o saves in these formats and opens in Office fine, as intended. Sometimes it doesn't though. If I could save in ODF format and include a plugin with the document itself, I would think that would be far more helpful in getting people to at least look at open source, rather than just pointing them to OO.o and saying "Install this".
Office 97? Office XP? Office 2002? Office 2000? Office 2007? Forward-portable to future versions? I'm quite sure this is a good thing, but at the same time I'm quite sure it wont work well for many many MS Office users...
Very smart move. It allows the office workers to continue as if nothing had changed, for the moment. But when M$ comes knocking and tries to sell them an upgrade to Office200x, the answer will be "if we have to upgrade anyways, as you have just elaborately shown, then we'll upgrade to OpenOffice, thank you".
Especially if the new Office they release with Vista changes the interface considerably, and requires re-training anyways.
Of course, the next Office update will break the plugin. It'll be a cold day in hell before M$ can let this stand unchallenged.
Assorted stuff I do sometimes: Lemuria.org
Currently my office runs on M$ Office 2k3. We could easily switch to OpenOffice save one luser who creates every one of his spreadsheets using M$ specific formatting that throws the OO conversion tool for a loop. I would switch the rest of us but we all have to be able to access his documents as he is the shop manager and he gets cranky when people don't read his crap. Had I been here when the network was set up in the first place this would be a M$ free shop as Linux has all of the tools these lusers need in a default workstation install. So I am going to sit here patiently waiting to move everyone to Linux immediately after we can get ODF translations for all of his crap. At least I can move the website to a Slack server soon (after I weed out the useless ASP code). IIS is killing me
I am Microsoft Certified, which is why I use Linux.
No animals were harmed in the making of this sig.
Well, there was that one puppy, but he is all better now.
Hi,
I work in a fairly technical group, but many of my colleagues are quite ignorant about the problems of using proprietary standards (e.g., office) in their day-to-day life. When Firefox was released, I put up the copy of the New York times ad in the lounge and people noticed. I wondered if there is a similar blurb for ODF (or OpenOffice). Now seems to be the ideal time to make people aware of the choice and alternatives.
Is there a nice one-page (non-technical) write-up that clearly states why open standards (ODF) is better than closed standards controlled by evil monopolies (Microsoft's doc format)?
Aravind.
I see less of this but rather Microsoft doing one of two things:
1) Embrace the plugin and create it as a standard feature of MS Office. Make sure this integration solution falls behind the standard and start including special Microsoft initiated ideas. When standards people complain about the new features, yell at them stating that the standard people are holding the product back from its true capabilities that customers keep demanding of Microsoft.
2) Include a warning message when loading or saving documents to special plugins that they may include viruses, have missing features, or that data may be lost. If people complain, Microsoft will state that feature X in Word is not in the standard.
My sweetheart works for a non-profit health agency in Massachusetts. Nearly all of his paperwork is in MS Word. Not that he has any particular feelings for or against MS Word, but because the Massachusetts Department of Public Health requires this.
Nearly every grant application, mandated report, etc. must be in MS Word "doc" format. Not plain text, not HTML, not SGML or XML or anything else, MS Word "doc" format. If it's not in MS Word "doc" format the state won't accept it and your grant application won't be received, your mandated reports not accepted, etc.
Sure other levels of state government are talking about adopting ODF, but that is just theory, until the state converts all of it's huge library of forms and applications, the paperwork that it all runs on, to something other then MS Word "doc", this is all theory. For that there will need to be a huge transition, and this sort of plugin is what can make it possible.
In the meantime all of the elaborate integration many of us take for granted, and that there are islands of in the state, and pockets of in state contractors, affiliated agencies, and the huge range of state-government dependent organizations, will be able to continue using MS Word in their established workflows.
Back to my sweetheart's agency, they do have a considerable investment in MS Word. Not just in licenses, they know MS Word. Their staff aren't computer geeks, indeed most of them only tolerate the crappy PCs they have now (running Windows 98) because they have to. But at least their fingers are trained to the keystrokes, they know the menu options, the more ambitious can even do a mail merge, lay out a flyer, etc.
Yes readers of /. think nothing of staring at an unfamiliar screen and working out how to do something with it; for a case manager trying to find a spot in a detox program for a 65 year old homeless woman who wants to get clean that is just not a hassle they want. Therefore anything that eases adopting open formats is a huge benefit, and critical to the process being painless and positive.
While many would like to hurt MS more of us really just want a level field and files that can be properly read a hundred years from now. Let applications and vendors come & go, lets at least have some durable file formats.
I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
On the topic of Office 2007's user interface, the recent promotional movie published on the Microsoft web site seems like they're trying especially hard in this next release to be different for the sake of being different. So hard that some of their innovative ideas may prove better in concept than implementation. Here were some of my thoughts on this 12 minute video.
Not only does this plugin allow MS Office users to use ODF, it does it with their existing MS Office licenses. Microsoft's OpenXML would have required an Office upgrade in order to achieve interoperability. And if they had implemented ODF in the upcoming Office release, this plugin probably wouldn't have been written, so again, you'd have needed to buy an Office upgrade to play.
Now there's interoperability with no revenue stream for Microsoft. Nice going, MS.
Posted from my Android phone. Oh, I can change this? There, that's better...
You own the DVD. You do not own the copyright on the DVD. Therefore CSS is a system for protecting a copyright that you do not own.
If you don't know where you are going, you will wind up somewhere else.