Skip to main content

An example of how MS Word is superior to Open Office Writer

There's been considerable debate of late over the use of Open Office in preference to Microsoft's Office suite. The general argument is that Open Office is 'good enough' for most work, and that documents are interchangeable for the most part. I'm about to provide two screen shots showing that for my work (and the work of a lot of other engineers) Open Office is inferior to supporting engineering, and in particular system engineering.

The issues I'm about to write about cropped up when I opened a large MS Word document in Open Office Writer under SuSE Linux. I then rebooted my notebook under Windows and created the much smaller sample document that captured two of the problems I found on the Linux side. To keep from having to boot back and forth, I installed the Windows version of Open Office, and found it had the same issues as the Linux version did.

This first image shows the example document opened in MS Word.

Note the comment block to the right. Also notice the graphic at the bottom of the page. Now, the same document opened in Open Office Writer under Windows.

There are a number of differences to note between the two. First, the comment block on the right of the document is missing in Open Office. The graphic at the bottom of the page is not rendered correctly (it's too wide, and the bullet character is not properly rendered). The graphic in the example document is a stripped down version of a more complex drawing. The original so overwhelmed Open Office Writer that Writer displayed it as large blocks of black-on-black, with the text showing up as gibberish.

Open Office Writer might be suitable for basic editing or document preparation. But for large complex documents with complex embedded graphics, or using collaborative features such as the comment block, Open Office is a poor choice at best. The comment block is an incredibly useful collaborative feature used extensively on many engineering projects, especially during a system engineering review process. It keeps track of multiple reviewer comments. After being introduced to it, I can't imagine not having it available any more.

Many critics of Microsoft Office like to point out that Office users don't use most of the features available under Office. And I'll be the first to admit I probably don't use most of the features. But it is surprising how poorly Open Office Writer supports the features I do find important and useful in Microsoft Word. Folks considering Open Office need to be very careful about switching. You may not like Microsoft, but moving over from Word to Writer can leave you in a precarious situation, especially with partners who will not leave Office, and who use the latest Office releases and features.


  1. You know, "comment blocks" and especially "track changes" seem to be one of the most common features I use regularly that have these compatability issues.

    I think the root of the problem stems from the fact that home users and business users tend to care about drastically different software features. As an unrelated example, "Spotlight" in MacOS 10.4 is a totally useless gizmo on my personal PowerBook. However, I find myself using it all the time on my work machine.

    I also tend to find that people who advocate OpenOffice as an MS Office replacement tend to spend more time on advocacy, and assuming eveyone only has "basic home-user-style needs", than on actually seeing that issues do indeed exist. What OpenOffice really needs is to refocus itself in terms of what it sees as its user base. Most of the people who advocate it right now don't seem to realize that all these compatability issues do exist. Of course our day-to-day featureset is totally different from theirs.

    Then again, if Microsoft actually did get off their Windows "high horse" and released MS Office for Linux (and didn't half-ass it), chances are that they'd sell more copies than we'd like to believe. (and more techies would probably migrate over)

  2. Normal use of Comment blocks and Track changes will completely bring MSWord to a halt in serious documents over 100 pages. I'm sorry but such documents exist. And yes, one can split a big document into a number of smaller files. But this is not a viable option if the publishing date is nearing.


    printing will _hang Word completely_. The kludge to save the file as HTML or RTF output does not improve matters since these formats not show you the comment balloons etc. etc.
    This is costing my two secretaries, VP and myself tons of time. We would have been
    better off starting in raw ASCII or: OpenOffice. Sure the latter application is not as neat as MSWord, on the whole. But the fonts look better and documents are any case more scalable to projects of realistic (non-home usage) business sizes.

  3. I deal with "serious documents" well over 100 pages myself (ranging from 150 to 300+). Since I can't compare our Windows environments, I'll outline mine briefly. I'm running Windows XP SP2 with the latest patches, and I'm running Microsoft Office Standard 2003 with their latest updates. I've run on Dell (I can't remember the model number), and two generations of Gateways (M680 and M685). In the case of the Dell and the M680 the CPUs were Pentium M's running at 2.13 GHz. My latest gateway is a Core Duo T2500 (2GHz). In all cases I had 1GB of RAM on the machines, and anywhere from 80GB to 100GB of hard disk. The latest has been a SATA 100GB drive.

    I keep only a minimal software load on the machines. I don't download anything executable unless it's needed and from a trusted source. It all goes through the virus scanner and/or other validation regardless. I keep the disks defragged. I run ZoneAlarm, Symantec Antvirus, and Firefox to keep the crud out. Where-ever possible I run behind an additional firewall, whether at home or in the office. This paranoia has kept my machines fast and capable. When I ran the above test I was running it on the older M680 (Pentium M) under Windows XP and Suse 10.0 with OpenOffice 2.0.2. In fact I installed Oo 2.0.2 on both sides just to see if Oo had the same issues all around. It did.

    Using the same H/W platform and running the two operating systems, I found for my use Oo 2.0.2 was considerably inferior to Microsoft Office (Writer vs. Word) for the tasks and the documents I had in hand at the time.

  4. I agree with comment bubbles, this is a feature and one that I think needs to be added to OpenOffice.

    I do want to point out that the Word doc format is closed. People have to reverse engineer it. I HATE seeing people bash Open Office and Abiword (and other's) for their rendering of Word documents. Microsoft won't tell us how the doc format works, therefor of course we can't render them correctly all of the time. This is Microsoft's fault, not OpenOffices.


Post a Comment

All comments are checked. Comment SPAM will be blocked and deleted.

Popular posts from this blog

cat-in-a-box channels greta garbo

So I'm sitting at my computer, when I start to notice a racket in back. I ignore it for a while until I hear a load "thump!", as if something had been dropped on the floor, followed by a lot of loud rattling. I turn around and see Lucy in the box just having a grand old time, rolling around and rattling that box a good one. I grab the GX1 and snap a few shots before she notices me and the camera, then leaps out and back into her chair (which used to be my chair before she decided it was her chair).

Just like caring for Katie my black Lab taught me about dogs, caring for Lucy is teaching me about cats. She finds me fascinating, as I do her. And she expresses great affection and love toward me without coaxing. I try to return the affection and love, but she is a cat, and she takes a bat at me on occasion, although I think that's just her being playful. She always has her claws in when she does that.

She sits next to me during the evening in her chair while I sit in mi…

vm networking problem fixed

Over the weekend I upgraded to Windows 8.1, then discovered that networking for the virtual machines wouldn't work. Then I tried something incredibly simple and fixed the problem.

Checking the system I noticed that three VMware Windows services weren't running; VMnetDHCP, VMUSBArbService, and VMwareNatService. VMware Player allows you to install, remove, or fix an existing installation. I chose to try fixing the installation, and that fixed the problem. The services were re-installed/restarted, and the virtual machines had networking again.

Once network connectivity was established there was exactly one updated file for Ubuntu 13.10, a data file. This underscores how solid and finished the release was this time. Every other version of every other Linux installation I've ever dealt with has always been succeeded by boatloads of updates after the initial installation. But not this time.

Everything is working properly on my notebook. All's right with the world.

sony's pivotal mirrorless move

I'm a died-in-the-wool technologist, even when it comes to photography. I have always been fascinated with the technology that goes into manufacturing any camera, from the lenses (optics) through the mechanical construction, the electronics involved, and especially the chemistry of the film and the sophistication of the digital sensor. It's amazing that the camera can do all it's asked of it, regardless of manufacturer.

Of all the types of cameras that I've really taken an interest in, contemporary mirrorless (again, regardless of manufacturer) are the most interesting because of the challenging problems the scientists and engineers have had to solve in order to build a compact but highly functional camera. In particular I've followed the sensor advances over the years and watched image quality climb (especially with μ4:3rds) to exceed film and rival one another such that there's very little difference any more as you move from the smaller sensors such as 4:3r…