First look at 3.0 beta

First look at 3.0 beta

Summary: Since I'm testing the viability of running Ubuntu on a number of platforms, and paving the way to shift from Internet Explorer to Firefox 3.0, I might as well take a look at the viability of abandoning Microsoft Office and making the leap to


Since I'm testing the viability of running Ubuntu on a number of platforms, and paving the way to shift from Internet Explorer to Firefox 3.0, I might as well take a look at the viability of abandoning Microsoft Office and making the leap to

Check out the gallery.

Now, I'm a firm believer that the (OO.o) suite offers far more functionality than the average user needs or wants. However, an area of prime concern to me is backward compatibility with Microsoft Office. This is important to me for two reasons:

  • I have a massive archive of old Word, Excel and PowerPoint files that I need to be able to have access to. Not only do I need to be able to open these documents, but the reproduction (both on-screen and print) needs to be faithful.
  • I exchange Word, Excel and PowerPoint files on a regular basis with others. Most of the people and companies I work with use Microsoft Office (although some do use OO.o) so my solution needs to be compatible.

With that in mind I downloaded 3.0 Beta and loaded it into a VMware test machine for experimentation. [See gallery for a close-up view.]

Here are some thoughts from the download and install process:

  • The complete download is only 144MB.
  • Installation was quick and painless, taking only a few minutes (less than five).
  • No restart required.
  • OO.o doesn't seem to junk up the system much (compared to Microsoft Office 2007).

Once I had the application suite installed, I decided to have a look around.

  • The first time loading any of the applications seems slow, much slower than the Microsoft Office 2007 equivalent. Subsequent launches are much faster (until you reboot).
  • File loading times don't seem that different to those the Microsoft Office 2007 equivalent.
  • Once loaded, applications feel nice and responsive, same as the Microsoft Office 2007 equivalent.
  • Occasionally I noticed odd screen artifacts when using menus or resizing windows. Not sure what's behind this.

OK, but what about compatibility?

Word document compatibility

For this test I created three Word documents in .docx Word 2007 format:

  • A simple one page document containing text and simple formatting
  • A 217 page document containing text and simple formatting
  • A two page document containing drop caps, SmartArt and Shapes Writer beta handled the first two documents just fine with hardly any format differences (nothing that mattered at any rate).

The third document was a different matter. The formatting on the drop cap was wrong, the SmartArt didn't show up and the Word Shape was rendered incorrectly.

First look at 3.0 beta Document displayed in Word 2007

First look at 3.0 beta Document displayed in Writer 3.0 beta

I then tool the three documents as displayed in Writer and saved them in the Word 97/2000/XP .doc format and tried opening these in Word 2007. All three files worked fine in Word 2007, although the two page document containing drop caps, SmartArt and Shapes was no longer formatted correctly.

Conclusion: Since I don't do much with drop caps, SmartArt and Shapes, I think I could live with Writer instead of Word.

Page 2 -->

Excel document compatibility

Next I created a test Excel document in Excel 2007 .xslx format that contained several examples of formulae (sum, average, count number, min and max), and a couple of charts (I use Excel charts a lot).

First look at 3.0 beta Document displayed in Excel 2007

The file opened in Calc beta and all the formulae seemed to work fine, but the charts were as good. They were accurate in terms of the information, but they were a stylistic nightmare.

First look at 3.0 beta Document displayed in Calc 3.0 beta

Saving the file in Calc into Excel 97/2000/XP .xls format just mangled the charts further when the output was opened in Excel 2007.

First look at 3.0 beta Document saved into .xls format in Calc 3.0 beta and opened in Excel 2007

Conclusion: The way Calc handles charts for me is, at present, a deal-breaker. Maybe things will get better as the beta program progresses.

PowerPoint document compatibility

I created a couple of sample PowerPoint document in PowerPoint 2007 .pptx format based on built-in templates.

So, how did Impress beta handle these files? Well, to put it bluntly, the output was an unmitigated disaster.

First look at 3.0 beta Document #1 displayed in PowerPoint 2007

First look at 3.0 beta Document #2 displayed in PowerPoint 2007

First look at 3.0 beta Document #1 displayed in Calc 3.0 beta

First look at 3.0 beta Document #2 displayed in Calc 3.0 beta

Conclusion: Impress totally fails to impress me.

Closing thoughts

It's early days for OO.o 3.0 Beta and things could get a lot better between now and release, but what I'm seeing now doesn't give me much hope that I'll be able to replace Microsoft Office 2007 with OO.o 3.0.


<< Home >>

Topics: Collaboration, Microsoft, Software

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • OLD NEWS: Don't expect OpenOffice to develop more perfect compatibility

    I gave up on OpenOffice a long long time ago and I'm not surprised that the compatibility is still pitiful. OpenOffice's Presentation could never handle PowerPoint files properly. OpenOffice's Writer could handle simple documents, but could never accurately and perfectly handle complicated Word documents. So you should expect the same much-less-than-faithful results when you use the final version 3.0 of OpenOffice.

    NeoOffice for Mac is much closer (but still not perfect) to Word compatibility and NeoOffice is a fork off of OpenOffice 2.2.1. OpenOffice never seemed to get any better since then.

    However, OpenOffice is good enough if you don't ever intend to exchange documents.
    • Completely different experience.

      Having never had Windows, obviously, I use OO all the way back to when it was StarOffice 5.1. I will give you the StarOffice, it was pretty terrible, but in the past few years, I have had no trouble with reading/writing 2003 files (what I default to when sending to others). PPTs always worked fine.

      One niggle, occasionally, a font replacement scheme is needed (easy to do) when you get a document with "New Zaph Sans Times New Quantum Berry Italic" that some person installed on their local computer and then used. Course, same problem happens when using strange custom settings on one MS machine and another even using Office.


      P.S. Office 2003 just couldn't open many W95 files, hence the server I set up as stated in my post below.
      • Perhaps

        your documents had no complexity to them. <br><br>
        This "push" by the people that many functions are unecessary anyway doesn't hold up with those I work around. I'm talking even clerical people. They need to be able to faithfully share complex documents of all kinds, without issue. It's not possible.
        • Complex documents

          You should never use a word processor to produce "complex" documents. That's what page layout programs and PDF is for. Word itself can't faithfully render truly complex documents across versions, as others have pointed out.

          Seriously, anyone who thinks that Word is suitable for producing "complex" documents is someone who has never tried to produce a "complex" document with it and tried to get several thousand Word users to open up that document and see exactly the same thing. Word will never work for that. In fact, Microsoft doesn't even have a product that is good for producing complex documents that render reliably across different systems. It tried, but failed miserably, with Publisher.
          • "Should" never produce complex documents?

            Pardon me: it is not up to you to decide whether others "should" produce complex documents. If Word has trouble rendering consistently (and boy, does it!) over versions, and even, in my experience, between installations on not-so-different machines, that is a problem with [b]Word{/b], not with the author. Even WordPerfect has problems dealing with some Word documents, and it, frankly, does better than Word does sometimes.

            OpenOffice will not be adequate for people who use Office for more than fairly plain letters and memos until it can render at least as well as Word.

            People: a word processor and the rest of an office suite are [b]TOOLS[/b]. Disliking one tool is not sufficient reason to use a different one that won't do the job. OOo has to satisfy the needs of a [i]very[/i] large fraction of users of MS Office before it will be a viable substitute for business users ("very large" being over something like 98%).

            The question isn't whether you or I like MS: it's whether the tools will do the job. If I want complex documents, that is one of the criteria for choosing my tools. Otherwise I would be throwing out the concept of screws because they can't be installed with a hammer.
          • Precisely why XML is NOT "standard"

            Microsoft used underhanded tactics for coercing the ISO to declare 00 XML a "standard" when it is clearly no such thing as long as Microsoft refuses to COMPLETELY release ALL the specs for it (the rule/criteria for a standard). But ISO caved in. It is NOT by any stretch a "standard" - it is clearly proprietary and MS intends to keep it that way, while getting it NAMED a "standard." Norway was among those nations filing protests with the ISO for its ignoring all technical evaluations (which declared MS's offering NOT eligible as a standard) and instead caving into political pressure. (ISO is now being referred to as "I Sold Out") It's an absolutely appalling situation.

            Microsoft deliberately designed in "traps" for other office programs and is deliberately withholding key parts of the specifications so that no one else can have complete compatibility with it. This is in blatant defiance of ISO's rules.

            It is not Open Office's fault - their documents work wonderfully - it's only when they try to interface with Microsoft's deliberately squirrelly and not fully released so-called "standards" that trouble is created for us, the users and customers.

            I think Microsoft should be legally forced to COMPLETELY release ALL specifications for the protocol since they were so insistent on having it declared a standard. They should have to abide by the same rules as everyone else.
          • Could Not Have Said It Better Myself

          • Interesting!

            In all three cases it was the MS xml "standard" that was checked using OpenOffice. And the result was easily foreseeable...
            In case of the "old" MS formats the results are generally decent.
            BTW, have you ever tried to open an Office 2007 document with an earlier version? NO? So, you should try, then, you would come to a discovery that it is impossible!
          • Right, but in practice...

            UserLand, in generic terms you are right. Neither Word nor OOo are meant to replace InDesign or QuarkXpress. However, there are many degrees of complexity in documents, and many things that could be done with them later. Most professional documents these days, even with a fairly large degree of complexity, don't end up in an industrial scheme to be professionally worked by a bureau and perhaps printed on a massive scale on couch? paper. More often than not, the end result is a PDF to be distributed on-line that doesn't contain any real exotic formatting, and Word's features are enough to produce the "complexity" needed in 99% of cases. Even ancient Word 6.0 for Windows 3.1 would do for perhaps 90%.

            Moreover, the reverse is also true: InDesign is not meant for word processing, and even if you do use it, you need to have first a raw master document made in Word (or OOo) to be reworked on later. In my experience, the degree of complexity that OOo chokes with includes "mid-complexity" things such as simple nested tables, separate section definitions, text boxes or fixed-position pictures - that is, things that are not exactly "basic," but are not otherworldly esoteric features either.

            I am a professional technical translator and software localizer (English to Brazilian Portuguese), and my work mostly involves delivering the final product, rarely just raw text. Sometimes I get a PDF to start with, sometimes printed material, sometimes CHM or HLP files that need to be reworked into something sequentially printable (i.e., an old-fashioned manual, that some clients and regulatory entities require here in Brazil, where I live), sometimes even JPEG or TIFF scans. In other words, I rarely have direct access to the original master document in English, and mostly have to rebuild its structure as closely as possible. Word does this job well, while OOo has proven grossly inadequate for that, especially because my clients need to have the master files for further rework on their own, if necessary.

            One thing I do use OOo for, however, is to directly open PDF files and save them as DOC or RTF for further rework. Word doesn't do that, OOo does. In some cases, when I get a PDF as input, this simplifies my work enormously.
          • Right, but in practice...

            1. Oo is FREE.
            2. Oo is compact -- both the software and the documents, which means in the long run it will be a big time saver.

            3. Some of the problems reported below can be avoided by avoiding round-tripping -- Import into Oo; and thereafter circulate not MS Office documents, but PDFs.

            4. Oo has some features that beat the pants off MS Office, like:
            (a) Functionality of expensive add-ins like EndNote for researchers
            (b) A much better Math Engine than the Equation Editor that comes with MS Office
            (c) No need to buy a PDF Creator!
            (d) ruby text (pronunciation keys) in the default version

            4. MS Office has created impenetrable undocumented objects and features like Pivot Tables in Excel that don't translate into Oo -- I challenge even Microsoft to create a Oo translator for Pivot tables. And such incapability actually helps them -- by creating barriers for changeover.

            5. Unfair! Unfair! We expect the Earth and more from FREE Oo but no one thinks to ask Microsoft to provide purchasers of their ever-more-expensive software a simple "save as Oo" option that works just as well in Oo as Oo manages MS Office documents.
            And we expect that we translate MS Office to Oo to MS Office!
            Rajesh H
          • Built in PDF

            You might want to look at the new version of WordPerfect. It's not free but it handles PDF files and other formats --- including Microsoft's latest pretty well.
            Of course, I've only had the new version for a week or two and I'm sure there are limits but at a $159 upgrade price, I'm glad i got it.
          • Exactly!

            This whole thing is completely one sided.
            MS makes compatability difficult or impossible by design, then any that would come along to offer up choice in the marketplace are called fatally flawed because they can not undo what MS has done.

            Pitiful, and the lemmings continue to reach ever deeper into their wallets, while running head long at the cliff and zealously defending their plight even as they fall to their demise.
          • Perhaps I should not have used "documents"

            I tend to use that term as a general one for all office applications and their output. <br><br>
            I was not limiting what I said to Word exclusively. <br><br>
            As i said to Tripell, i seriously don't think MSO 2007 and are comparable. Perhaps MS Works and open office would be closer to a comparison in many ways. <br><br>
            MSO has become a system with many apps and the next release will have real web capabilities that are a hassle now. It is highly programmable with minimal code and can be used as part of a larger set of tools. <br><br>
            I don't think this "complexity" leaves out the average worker however. <br><br>
            Sharepoint's marketshare has quietly passed 100 million licenses. It's becoming commonplace for MOSS to be implemented in some fashion. To give all workers access to backend data via Office, in the format they need, when they need it, is a Huge business advantage. <br><br>
          • Publisher

            Absolutely correct, Publisher cross-version compatibility doesn't exist.
        • Inlcudes Macros in Word and Excel.

          We have very complex quote templates for feature specificications, performance estimators and quote documents. Most are prompt based (click inside), cross referenced to line items in the xls. They work very well since OO 2.0 (before that, not so much). I am not sure how complicated the PPT are, however, inbedded spreadsheets are no problem.

          Your point may be valid, we aren't using xls sheets as CAD programs, nor are we an accounting firm, etc, but it works really really well for what we need.

          Something that I have asked before, what specifically, is the list of features Word has that OO doesn't?

          • I think compares better to MS Works.

            In terms of functionality and cost. <br><br>
            We are using Sharepoint and Infopath forms with Office. The ability to create custom application with either VBA or VSTO is a huge plus. The VSTO capabilities for Office/exchange and sharepoint in Visual Studio 9 are phenomenel in my experience. <br>
            MSO had changed. It's not just an Office suite anymore. <br><br>
            Thus i think the MS Works - comparisons are the only that make sense at this point in time.
          • Sharepoint, etc.

            I was talking about word processors. OO as a word processor stacks up quite well against Office 2003. (Don't know about 2007, have never seen it). That said, what does sharepoint have to do with word processing.

            Bringing in a free add on to a windows server function that integrates with Office is not really relevant. When sharepoint server is included with Office 2007 for the desktop, it is relevant.

            There are many solutions for hosted and managed document management that have existed for many years. My company uses them, independent of the client machine. We share, collaberate, integrate, merge, etc from probably over 150 countries worldwide on our document host platform.

            The only interesting or new thing I think is the integration of the IM client with calendaring from the sharepoint server. For one customer I work with, this is the only function they use, and it is only local to one location because IT won't open the firwewall ports.

            Anyway, sharepoint has nothing to do with Office, it has to do with Windows server, except, that it integrates with server.

            So, what you say is fine, you have an entire Windows ecosystem, doing lots of development, however, that is not really specific to Word, and as said, comparing OO to your complete IT infrastructure is not really valid.

            Assume no internet connection, no Windows server backend, no sharepoint, what does Word 2007 do that OO can't, or why is 2007 so superior?

          • It is included.

            form free with server product. <br><br>
            MSO has a Sharepoint designer as an application now, so it's very relevant i think. <br><br>
            It's similar in some ways to the Groove client for Office. <br><br>
            You see, MSO has much more breadth and depth than <br><br>
            As for word head to head with WP, there is no comparison in my mind. Word 2007, as are all MSO 2007 applications, is a revolutionary change and not merely an evolutionary one. I've used MSO 2007 for over a year now and can say with every app, the amount of work, keystrokes and clicks included, has been reduced by 50% or more in most cases, to achieve the same or better result than in Office 2003, or <br><br>
            Try out Office 2007, you'll love it.
          • Just to add...

            OO 2.4 plays MS created PPT fairly well; I just haven't figured out how to get the background sound to survive the first frame.
    • Open Office trashed my docs

      I was using OO for school. I switched back to MS Office when I nearly got a failing grade after the OO docuements I saved as Word docs were corrupted. I later found that other docs, which were originally in Word format were also corrupted to the point Word would not open them.