Novell Releases OO–OOXML Translator
Tookis writes in with news that Novell has released an Office Open XML (OOXML) translator for OpenOffice.org. The article argues that, though this move may represent a nail in the coffin of the franchise known as Microsoft Office, and therefore a Good Thing, what is truly needed is a fully supported Evolution on Windows.
I think the article is confusing larger memory usage with greater efficiency.
what is truly needed is a fully supported Evolution on Windows.
How about an (ABI compatable) Exchange-equivilant for linux?
There are shills on slashdot. Apparently, I'm one of them.
I believe the yearly revenue for Microsoft Office is about 15 billion which is about one third of the total revenue Microsoft makes every year. Correct me if I'm off. Over the past five years or so Microsoft's stock has been essentially stagnant. And Microsoft has had to make huge cuts over many of the preceding quarters to hit their street expectations and keep the stock from tanking.
Even a modest hit to the Microsoft Office revenue due to the upgrade treadmill from the format lock-in would have a massive effect on the company. Over the years Microsoft used their rapidly growing stock to keep salaries down and attract people with the lure of huge gains from their option grants. If office software revenue starts falling and Microsoft exec options start turning worthless I think you will start to see dramatic cuts at the company - the multi-billion dollar Xbox fiasco, the Zune mess, and many of the other let's throw money at new markets to try to get the stock moving attempts that Ballmer and others have tried since the stock peaked back around 2000.
I have to imagine that Microsoft will fight this move to open office formats with a fury never seen before. This isn't just extra billions that Microsoft won't miss, it is the multi-million dollar retirement money for a whole lot of execs up in Redmond under direct assault by a bunch of dirty hippies.
It's really comforting to know that there are such men as this -- such utter, bigbrained geniuses who deign to drop us mortals a few crumbs of the great bread of awesome.
Sarcasm aside: I am sick to death of people going, "I want this for my computer, therefore everybody else wants it too, and therefore the only rational course is what I say." Have you considered asking the users what they wanted? Instead of assuming that "the users" want "full-featured desktop apps", do you think it might be worthwhile to check with them if that's true? Maybe they're already using gmail and love it. Maybe they don't even know about Google Calendar. Maybe they haven't ever heard of Zimbra.
Why should I, as J. Random Developer, bust my hump porting Evolution to Windows (which I couldn't do anyway as I know zip about Windows programming) just because this clown says what's good for him is good for everyone else?
"Honey, it's not working out; I think we should make our relationship open-source."
So what is needed is Evolution for Windows eh? Kind of like this? I don't have Windows around anywhere to try it out, but it looks like it runs fine. I expect it still has a few kinks to be worked out, but it is certainly up and running, so not only is a port in progress, it looks like it is even usable already.
Craft Beer Programming T-shirts
I was hoping for a "final solution", if you will, to the XML problem.
1. Naive programmers implement patented microsoft CLR/C#
2. Novell buys liability nightmare language/runtime implementation
3. Novell does patent deal with Microsoft
4. Novell releases patented information for Office translator
5. Microsoft starts raising legitimate lawsuits against both Novel (mono) and everyone else (using Novell precedent of signing patent protection agreement)
6. . . .
7. Loss!!!
Wake up, little Suse. . .
I'm surprised that Novell wants to kill Microsoft. I thought they were friends. I am not surprised that all Novell did is use XML as it was intended?
Nail in the coffin? Pretty bold thing to say about Microsoft Office. OpenOffice is a great, free product, but IMO it's no replacement for Office in a never-look-back sense. Yes, they should keep putting pressure on MS regarding open formats, but I'm not about to switch from Office 2007 after my [wonderful] experience with it so far.
Techies love to complain about things like the ribbon, but everyone I see actually use it loves it.
MS Office isn't going anywhere. Neither is OpenOffice. And apparently neither is the Drama Llama.
Turning coffee into code.
//Microsoft made a new format (instead of using ODF) because they thought they could do it better, not because they wanted to lock people into using Office 2007.//
That is not correct. Microsoft's supposedly "open" format in fact avoids "open" as much as it can. For example, where OpenDocument uses SVG for graphics, which is itself a W3C open format that any vendor may use, in the Microsoft format Office Open XML (OOXML) they could have used SVG, but no, they could have used CGM, but no, what did they use? WMF. That is right, a buggy Microsoft proprietary graphics format, the one with the security hole, WMF. WMF relies on the Microsoft GUI API to render properly, as WMF has embedded metadata meant for calls to the Microsoft GUI API.
That is not the only thing in OOXML like that. If there is an open format for anything, Microsoft avoids it. Microsoft's OOXML is as packed as can be on dependencies that the underlying platform on which any application runs is a Windows platform.
Microsoft wanted to lock people in all right. It will be impossible to achieve perfect fidelity with OOXML on any platform other than a Windows platform.
If you have documents saved in OOXML format, you will be locked in to Windows platforms.
I fail to see how this can be considered "a nail in the coffin"? Not even the article really talked about what Novell releasing this would do, and why. Am I missing something?
Oh fuck no.. How about a fully supported version for Linux first?
If they could fix some bugs, it wouldn't be such a steaming pile of shit.
The stranglehold is in the calendaring AFAIK.
Insert
Do you remember the classic IE vs netscape battles back in the 90's?
Microsoft came out with a fast release and quick delivery iterations.
Yes, they had an advantage by forcing it upon every windows 9X user, but their original release was pitiful, and netscape had an opportunity to deliver a superior product and win the browser majority.
What did they do?
Netscape spent their time working in multiple directions without releasing a core product.
In the end, the mozilla project came out with the superior browser, but since it took so long to deliver, it fights with opera and safari for 10% of the browser market.
Do I see history repeating itself here in the desktop office app battles?
The reason I use Evolution on my Linux desktops is because it lets me talk to Exchange servers. Thunderbird and KMail are both great if all you need is a GUI mail client that talks POP and IMAP. Evolution does those pretty well too.
But Evolution can also (sort of) speak to Exchange servers (through Outlook Web Access), which is supposed to make it possible to do things like manipulating Exchange calendars, managing Exchange tasks, and using Exchange global address lists. Unfortunately, it's still not all there yet. And from what I've seen lately, it's getting worse. There are some major connector regressions in the 2.8.x release of Evolution that make me regret upgrading to Fedora Core 6 every day. And no one seems to be interested in doing anything about it, the bugs have been open for weeks -- even months.
Outlook is a killer application for business desktop users, and I say "killer" because not having an equivalent for Linux will KILL Linux desktop adoption. Hell, even cell phones work better with Exchange than Evolution does right now.
Evolution may be trying to clone Outlook, but it's not great as a standalone e-mail program. There is nothing really wrong with Thunderbird. For a calendar, try Palm Desktop. There is a little program to sync it to iPod.
... this could make Linux desktops (KDE, GNOME, etc.) suitable for SOHO use. I work independently, but I need 100% compatibility with Word and PowerPoint to collaborate with colleagues and funding agencies who are still dedicated to MS Office. I can save money and headaches over CrossOver.
.doc filtering will be perfect. (.xls filtering in Gnumeric has been pretty good.)
In particular, I'm hoping that there will emerge a GNOME alternative to Impress, and that AbiWord
This will do squat for putting any nails in anything.
/ 02/openoffice-support-for-the-openxml-formats.aspx
Microsoft wanted this. Infact, Microsoft helped Novel do this: http://www.novell.com/ctoblog/?p=43
And the Microsoft Open XML developers were more than helpful to advertise this: http://blogs.msdn.com/brian_jones/archive/2007/03
This is a GOOD THING for everyone. OpenOffice.org users get interopability with MS Office. MS Office meets many government required interopability and open XML format requirements. Win-win.
Let's keep the absurd commentary out of the summary and in the modded down comments, please?
http://brandonbloom.name
Since there seems to be no way around this entire IP mess, I shall go with the flow for now and ask - is it (legally) safe to include this in any Linux OSS project?
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
The reason why OOXML uses WMF and relies on quirks of old versions of Word (and of WordPerfect etc) and all this other stuff is because OOXML has to be able to store every piece of data that the word *.doc file format stores. Because Word has used WMF ever since Microsoft invented WMF (which was long before SVG came along), Word will continue to use WMF.
After reading the article and comments, it appears the compatibility is only good for Novell's version of Open Office. It is not available for the "standard" Open Office.
OOXML has to be able to store every piece of data that the word *.doc file format stores
Not true; Office 2007 could have a WMF -> SVG converter in it. Storing graphics as SVG would then just be part of saving into an XML format.
Throughout it's existence, Novell has never been a credible threat to Microsoft over a reasonable lenth of time. Their agreement with Microsoft further reinforces the suspicion that Novell might not be realy competing, rather they might be collaborating with Microsoft to further extend the monopoly situation and exclude genuine choice, and freedom of software. Some concerns:
1. Does Novell's translator work well with OO.org, or Novell's version of Open Office only?
2. Like Mono's port of VB, is the usage of the translator covered by the patent deal between MS and Novell?
3. Why did Novell abandon the Netware range of products?
This does not appear to be a nail in the coffin of Office, it seems to be an extended lease of life for a dying format and bloatware from the 800lb gorilla.
-
If you keep throwing chairs, one day you'll break windows....
1- How well does it work ? In my experience, translators and export filters are never that great. So even a translator is not enough, it has to be a GOOD translator.
.doc is not very good at maintaining layout across platforms / versions / even PCs... is OpenDoc any better ?
2- More generally, how well does OpenDoc travel from one program to another, and from one platform to another ? We all know
The Cloud - because you don't care if your apps and data are up in the air.
Really? So often you can not have correct conversion of WMF to SVG. I don't know why but probably WMF (or EMF to be more precise) can do things that SVG cannot. Now, would you do it if you were Microsoft and did this move did broke lots of current documents of your customers because you couldn't keep the figures the same way they are? Would you as a customer buy Office 2007 if you knew that there is a 1% probability that some of your Office 2003 documents could not be read correctly?
We don't need Evolution for windows, we need something other than the pile of crap that Evolution is.
Disclaimer: I use Evolution.
If only it was that easy. The real problem is that Word must without fail remain 100.0% compatible with every previous version, down to the pixel. The feature sets of WMF and SVG are not identical, and a converter with true 100% compatibility is not something anyone is going to whip up in a few days. It may not even be feasible. And after conversion, even if the document looks the same, the structure will be different. The way you edit it will change. The saved undo history will probably have to be thrown away. The interaction with other Word features like Track Changes might be different. etc etc...
People expect their documents to always look and work *exactly* the same, even though they do incredibly boneheaded things that end up relying on every feature and bug Word has ever had. For just one example, a relative of mine who will remain nameless typed out all his Word documents using tabs in place of carriage returns. That's right: between every paragraph, instead of pressing enter, he pressed tab to fill up lines until he got far enough down the page to start another paragraph. He centered text using this method too. Not a single carriage return in the entire document. What do you think that document will look like after *any* conversion at all? The precise to-the-pixel word-wrap decisions made by Word define everything about how that document looks. But if this person upgrades their Word and their documents are messed up, are they going to say "Boy I'm a dumbass, thanks Microsoft for showing me the error of my ways, I'll just retype all my documents now"? I think you know the answer.
This is why the OOXML spec is 6000 pages of hacks like 'autoSpaceLikeWord95' or 'lineWrapLikeWord6'. Not just to be obtuse; not as a grand conspiracy to hinder interoperability and shut out Open Office; not because Microsoft is incompetent. Because people demand uncompromising perfect backwards compatibility, and that's the only way to truly deliver it.
Firebug. It will make your jaw hit the floor.
I had to modify manifest.xml and get rid of application/octet-stream to install this oxt file without those unsupported media type errors. (it was on Windows...)
Although with those errors, it seems to be installed just fine, though.
Right. It all makes sense... except for the fact that if the goal is 100 % compatibility, then there is no point in actually creating a new format, or in particular building it on top of XML and marketing as an "open" format.
Now they are creating a new format that will undoubtedly create new bugs and incompatibility problems, however hard they try to avoid them. If they wanted to, they could reach even better compatibility by using the same old binary format, with minor extensions for new features. But that would mean their marketing would have no answer to calls for open standard formats, and they cannot have that.
Nowhere in the 6000 spec do they claim that every application needs to implement 100% of the spec. Office 2007 does and that makes it compatible with old version binary documents. Open Office .org can implement a small part with all SVG-type additions they want - that is what new formats are about.
A few weeks ago Sun released a plugin for Word that allows it to read and wright .odf (i.e. OpenOffice.org) documents.
It's free.
That should be easy to fix. It is quite obvious that memory usage can be decreased simply by changing it to 5OXML
Dude, there has never been this pixel perfect rendition between different Word versions, not even on Windows, let alone if you also include the Mac versions. I absolutely don't buy your argument as a valid reason for all the renderAsWord1OnMacintosh1984 attributes
OOXML uses WMF and relies on quirks of old versions of Word ... Word has used WMF ever since Microsoft invented WMF (which was long before SVG came along), Word will continue to use WMF.
So, Word is using all the quirks and legacy formats that it has been using, except now it's "open" because it's got XML wrapped around it. It's not that easy - you can't have it both ways.
My Karma: ran over your Dogma
StrawberryFrog
So you wouldn't disagree that it is impossible to write an implementation
on a non-Windows platform, and you'd agree that it would be right for
Governments to avoid OOXML as a lock-in format?
Please. Office isn't going anywhere. As long as there are Microsoft-loving managers, MS Office will be overwhelmingly dominant. Frankly-- and bear in mind that I hate MS-- Office is a far sight better than OpenOffice.org, which I've always found to be bloated and amateurish.
This whole "OOH OFFICE IS GOIN' DOOOOOOOOWN" mentality strikes me as wishful thinking.
With spending like this, exactly what are "conservatives" conserving?
..is an evolution plugin that connects to Microsoft Exchange server Outlook Web Access through a proxy.
My job requires me to program on Linux, and I also prefer using Linux full time as ITservices here has draconian policies here for Windows users (Everyone is a restricted user and they cannot even change their own wallpaper). On my linux box, I have root access, my own wallpaper and mp3 player. There are so few linux boxen here that ITS let me have root access. They aren't well versed enough, and they don't want the extra hassles.
I don't get to choose what Mail server my employer uses. I can choose my client though. IT services refuses to support POP or SMTP as they have had to deal with Viruses before.I work on a Dual Boot FC6/WinXp box, and am forced to forced to boot into WinXp just to manage my email. Outlook Web Access does not work that great with Firefox, and does not provide for a way to pull email off the server and store them locally. Our web access is through an authenticated Proxy and the evolution plugin cannot deal with that (yet). What do the other folks out there with linux boxen and M$ mail servers deal with this?
Perhaps people find MS Office better to use than OpenOffice.org. Just a thought....
as the seeds of a new tyranny enabled by patents on the CLR and supporting libraries.
That's a good point. Some dudes at sun with a bunch of schlubs in their underwear at home can
figure out the various office formats and save their docs to them. Why can't MS work that out
> OpenOffice.org users get interopability with MS Office.
l
The problem is, this translator is "lossy", meaning that any translation will lose information *both ways*:
http://odf-converter.sourceforge.net/features.htm
Also, being a translator instead of an exporter means that a double save will have to happen which has it's own set of issues.
> Win-win.
Actually, it's win-lose since it's the appearance of openness without actual openness, so MS Office devotes will be able to claim that no change in status quo is required (after all competition exists so there's no vendor lockin) but no-one will trust ODF translations into OOXML since they will look bad. Another side effect is that people will move away from DOC which has better support universally (through years of reverse engineering) in favour of OOXML (which has poorer universal support) since "XML is the future". Not good.
But if you're going to support OOXML in OpenOffice despite this last comment, a better approach would be an OOXML *exporter*. The key difference between an exporter and a translator is that an exporter has access to a lot more information about the document (the internal application representation of document) and so the exporter can be more accurate than the translator (which could in theory rebuild those data structures, but in practice won't unless OpenOffice and MS Office are refactored so that the creation of the internal data structures from the file system is available through a library) and an exporter will be faster (no double-save, no external tool, no recreation of even minimal internal data structures).
Just to drive the nail in even further, distros like Ubuntu and Fedora should offer it in the updates almost immediately, or even in the updater for OOo, as to show how fast OSS can really be.
Kernel Krunch - Part of a Complete OS
It's fascinating how slashdot still prefers opinions to facts.
.docx file (the Windows Vista Product Guide failed, with nothing happening or displayed.
I downloaded the odfconverter-1.0.0-2.oxt file and tried to install into OpenOffice.org 2.1.0 for Windows (as downloaded from openoffice.org web site, not the Novell version).
I had to use Tools -> Extension manager (not Package manager), and when installing, had several pop-ups stating "This media-type is not supported: application/octet-stream". OKing these showed the odfconverter installed into "My extensions". And "Microsoft Word 2007 Document (.docx)" was added to the list of files in File -> Open.
But trying to open a
Anyone want to try the other options of Linux, OO.o 2.0.4, Novel OO.o 2.0.4 and report back?
Andrew Yeomans
n. The right to sell a company's products in a particular area using the company's name
From Cambridge Advanced Learner's Dictionary.
Office is not a franchise, it is a product, like any other piece of software. Please stop using words you don't understand, it lowers the tone of the entire site and leads to otherwise utterly redundant posts like this one.
It's official. Most of you are morons.
figure out the various office formats and save their docs to them. Why can't MS work that out What kind of an animal is a 'schlub'? And why is it's preferred habitat the underwear of dudes@Sun.com? Perhaps the whole problem could be solved by breeding some more shlubs and setting them free in the underwear of dudes@Microsoft.com?
Only to idiots, are orders laws.
-- Henning von Tresckow
Microsoft will simply add a ODF exporter as well... It's still the best office productivity software out there. The feature set and development capabilities cannot be ignored.
Apart from the good news of an OOXML translator for OpenOffice.org, that was a terrible article!
It seems the author is a noob who is only just putting his toe in the water with a first install of OOo. After anouncing the news of the translator, he then starts rambling on about Evolution on windows, whatever.
Who said it was the goal of the open-source community to crush Microsoft??! While it may be true that many in open-source folk don't like Microsoft, I think it would be more accurate to say that the goal of open-source is to produce good free software that is based on open standards that anyone can use, improve and learn from. It's about freedom, not Microsoft bashing.
Sure, Evolution on Windows might be great for some people - but that's another story, can't we just be happy with the good news (about the translator) for the moment?
Ross Kendall Web Consultant and Developer (UK) - Drupal and Open Source Solutions
And if you believe that, and believe it's a good idea to further lock yourself in to the products of a user-hostile company, MS has several other bridges to sell you. There's never been a better time to move away from binary, ephemeral, inscrutable formats for our documents. Word can't even open these memory dump docs consistently across versions/platforms.
The fact that MS either hasn't grasped this (highly unlikely, given the level of people they have working there), or actually chooses to lock in its customers with OOXML, tells me, as a customer, all I need to know.
Life needs more saving throws.
Acronym Is Too Short, Needs More OOs
What we really need is an Object Oriented OpenOffice.org Office Open XML translator (OOOOoOOXML).
Perscriptio in manibus tabellariorum est.
For a released product, i sure can't find it anywhere.
Currently I use MSOffice 2003 on WinXP SP2.
(I also run Slackware 11.0 under coLinux).
This has always worked fine for me, I'm used to it and many of my documents are saved in this format.
A converter between two competing XML document format changes absolutely nothing for me or anybody I know, at all.
If you really want pixel/layout perfect compatability between all machines running all weird and wonderful OSs, then you realistically have to store you data in plain text with monospaced font, HTML or PDF.
Office documents contain too much stuff instrinsic to the program used to create them.
For example, you can include COM-based VB macros, OLE embedded objects (such as equation editor), and other miscallaneous items in MS Word documents, getting them to work correctly on different OSs correctly would be a nightmare.
If the OpenOffice suite did absolutely everything that MS Office did (including in particular Excel with its myriad features, a real must), than I would just write all my new documents/spreadsheets with that and be done with it, leaving my existing documents as they are.
The goal is mostly stationary as the real useful improvements in Office since 2000 (except Access, and perhaps Excel 2003), are frankly negligible (Word 2000 added nested tables, that is the only useful difference I have noticed between Word 2003 and Word 1997).
Outlook in my opinion is rubbish so I try to avoid it wherever possible (what is wrong with webmail).
Also, why do people seem to need an integrated calendar, email client and word processor?
Calendar: Calendar program/piece-of-paper-on-wall.
Word processor: Whatever you like/have.
Email: Whatever, (webmail is least hassle by far).
What would really be useful is if MS Office would run properly and smoothly without huge amounts of messing about with WINE or paying for Cedega, under Linux. That is more important than whether I can convert (lossily), between the two formats at the moment.
That and games are mostly what are stopping me leaving MS Windows.
One day I'll reserve the order and run windows as a VM under Linux...
There is no psychiatrist in the world like a puppy licking your face - Ben Williams
I agree with you completely, and raise 2 cents.
Try the same version on the same OS.
I work in the publishing business, and you kan never rely on a word document looking the same on any two computers. Things like OS language, printer margins, the phase of the moon, and even more obscure factors will ensure that it never happens.
OpenOffice is, despite its other shortcomings, a lot better in this respect.
When a customer wants to deliver a "ready for press" document we demand PDF. Even then you run into problems with font substitutions, missing fonts, ligatures that the production machine can't handle, and so on.
The only sure way to get a pixel perfect replication is... a bitmap. And even then you depend on the production machine's ripping process not mangling it, wich often happens if you try to achieve exactly THAT shade of gray by rasterizing manually in Photoshop (tested on a Xerox DocuTech 6135, 6180, and DocuColor 2040). Have fun
Are you a grammar Nazi? I'm trying to improve my English; please correct my errors!