is a free, multi-platform office suite. It includes key desktop applications, such as a word processor, spreadsheet, presentation manager, drawing program, and database module. is an Open Source project and available on all major platforms, including Linux, Mac OS X and Windows. At present, you can choose from more than 100 different language options. avoids the risk of vendor lock-in because it uses a standardised, XML-based file format that makes interoperability easy and your documents future-proof. is compatible with Microsoft Office. The latest version imports .docx files and continues to be able to read and write all the other Office formats.


“ is released under the LGPL licence. This means you may use it for any purpose—domestic, commercial, educational, public administration. You may install it on as many computers as you like. You may make copies and give them away to family, friends, students, employees—anyone you like.”

Submitting Bug Reports

“Simple end users are really critical in the process of making the code better. It’s important for end users to understand how important they are in the process.” developer Florian Reuter discusses some of the issues and explains how you can take part.

Bug reports

Florian Reuter is a software engineer for Sun Microsystems and a contributor to the project. His particular interest is in the ongoing development of’s import and export filters for the .doc, .rtf and Word ML formats.

What follows is an exerpt from an interview Florian recently gave to Mad Penguin’s Christian Einfeld, highlighting the importance of end users submitting bug reports to help in the development of

MP: You said earlier that you were helped out by end user bug reports. Many end users don’t really understand how they fit into your world as a developer. They don’t understand that there are developers out there who really do read their bug reports. What message do you have for simple end users about bug reports?

FR: If you have a Word document in .doc or .rtf or Word ML, and you use the current filter, and something goes wrong, even something not very noticeable, please submit the document as a bug document to, so that we can get a critical mass of documents that we can look at.

When we do the investigation of the file formats, we do it in the following way. We look at the basic engineering approach. We look at what happens, and we make an assumption. Then you have to see if your assumption is correct or not. The more documents we have, the more we can test whether our assumption is correct. The real value to me as a developer is having a huge amount of documents available so that I can check my hypothesis to see if it’s correct.

MP: Let’s break that down a bit. How does an end user help you out. What are the mechanical steps for submitting a bug document?

FR: Go to the website. Register as a user. You just have to pick up a user name. Enter your email address. Click on issue. Click on submit a new issue. Select the WW8 filter. Attach the file, and submit the bug. If possible, please also provide a description with what is wrong with the document.

MP: How is an end user going to know that there is something wrong with the document so that they need to do a bug report?

FR: That’s easy. If you document doesn’t look right, just go ahead and submit it as a bug. Let us worry if it is a bug or not. Don’t assume that you have made a mistake. It could be a bug.

If you use Windows, you can download a free Word viewer which will let you see what the document looks like. So you can download the viewer, view the document in Word, compare it to what looks like, and if it doesn’t look right, then submit it as a bug.

MP: Give us a little more detail about the value of bug reports. You mentioned something earlier about having lots of tables, and how that was helpful. Could you elaborate on that a little more?

FR: You need to have a critical mass of documents to either prove or disprove your current hypothesis as to how the Microsoft layout formatting works. As a developer, you see the differences at the edges of performance. can import >90% of the documents correctly in 2.0. It is in the remaining 10% or 1% that some kind of magic happens, and you’re not sure what it is. You can only figure out what magic is making that work by looking at lots of samples. It’s only by seeing patterns in that small margin that you can get an idea of what makes the magic happen.

You need to have users making unexpected use of the application to figure out what is going on. As a developer, it’s hard to imagine all the different ways that something might be used. In computer science, having lots of samples helps us refine our hypotheses as to how to best import files from Microsoft Word. Real world samples make a big difference for us. It’s that way in most fields of science. You need to have a critical mass of data to test your theory.

So simple end users are really critical in the process of making the code better. It’s important for end users to understand how important they are in the process. That’s one reason why I enjoy working with the community. They help me do my job better. So thanks!

This work is distributed under a Creative Commons Attribution NonCommercial NoDerivs 2.5 license.

Office 2007 to gain native ODF support early next year

“Users will be able to set ODF as their default file formats under Office 2007, and Microsoft plans to continue support of the OOXML-ODF translator for those using older versions of Office.” Jacqui Cheng details Microsoft’s recent announcement to make Office 2007 compatible with
Personally, I remain sceptical about Microsoft delivering on these promises. But genuine interoperability has to start from somewhere…

Users of Microsoft Office may also want to consider the Sun ODF Plugin for Microsoft Office as an alternative solution.

Norway mandates open formats

“In a move to ensure equal access to public information for Norwegian citizens, the government has decided to make the freely accessible document standards HTML, PDF, and ODF obligatory.” Justin Fielding reports on Norway joining countries such as the Netherlands, Belgium, Malaysia, Finland, France, Japan and Germany in a drive to make government documents more accessible. 1.1.5 1.1.5 is a free, multi-platform office suite. It includes key desktop applications, such as a word processor, spreadsheet, presentation manager, and drawing program.

Installing 1.1.5 on Windows NT/2000/XPSP1/XPSP2 1.1.5 is not difficult to install. However, there are a couple of steps to the installation procedure which differ from what you might expect.
Once you have obtained the software, installation takes place in two distinct phases. The first is performed with administrator rights, placing the installation resource onto your system. The second is then performed for each user individually, providing them with an environment that they can configure to reflect their personal preferences.

Obtaining the Software (Administrator) 1.1.5 works best with Java installed on your system. Hence, you should begin by downloading the latest version of the Java Runtime Environment and installing it onto your system.

Download by confirming your choices and saving the file onto the Desktop. Extract the folder OOo_1.1.5_Win32Intel_install from inside the archive onto the desktop by using the built-in functionality of Windows XP or a free utility such as FreeZip. You are now ready to install

Copying the Installation Resource (Administrator)

From the Start menu, choose Run and browse to open Setup inside the OOo_1.1.5_Win32Intel_install folder on your Desktop.

Append -net to the string in the Open field:

"C:\Documents and Settings\Administrator\Desktop\
OOo_1.1.5_Win32Intel_install\setup.exe" -net

Click OK to start the installation script and follow the on-screen instructions. When prompted, chose to perform a Standard Installation. In the Java Setup dialogue, select the Java Runtime Environment.

Click Complete to finish the first phase of your installation.

Setting Up the Environment (User)

Find the OpenOffice.org1.1.5 folder inside the Program Files folder on your C: drive.

Double-click Setup inside the OpenOffice.org1.1.5 folder to begin setting up the user environment.

Click Next to start the installation script and follow the on-screen instructions. When prompted, chose to perform a Workstation Installation.

Select the file types Microsoft Word Documents, Microsoft Excel Spreadsheets and Microsoft PowerPoint Presentations. If you prefer to use alternative software, deselect the option to use Writer/Web as the Default HTML editor.

Click Complete to finish the second phase of your installation.

Adjusting the Menu Fonts (User)

In 1.1.5, you can easily adjust the menu fonts to blend in with your system wide settings. This example uses Tahoma, which is the default on Windows:

Open and go to Tools > Options.
In the Options box, expand the section and select Fonts.

Select Apply Replacement Table and enter AndaleSans UI into the Font field.

Enter Tahoma into the Replace field and confirm your choices with the green tick button to the right.

In the replacement table, select Always and Screen for AndaleSans UI.

Click OK to apply your changes.

Creating a Desktop Icon

If you would like to use a desktop icon to launch 1.1.5, follow these simple steps:

Find the Program folder inside the OpenOffice.org1.1.5 folder inside the Program Files folder on your C: drive.

Right-click soffice inside the Program folder and from the context menu select Create Shortcut.

Choose to have the shortcut placed on the desktop. Otherwise move the resulting file from the Program folder to the desktop.

Rename Shortcut to soffice to and you’re done.

Adding New Dictionaries Using the AutoPilot 1.1.5 makes it easy to install additional language modules. Follow these simple steps:

Open and go to File > AutoPilot > Install New Dictionaries.

Select the language in which you would like to interact with the installation wizard and click Start DicOOo.

If you are logged into your system as an administrator and wish to install the language modules system wide, chose Administrator Setup. Otherwise select Current User Setup. Click Next to proceed. Please note that installation of Thesaurus dictionaries can only take place if you select Administrator Setup.

Follow the on-screen instructions and make your selections from the available Spelling Checker, Hyphenation and Thesaurus dictionaries.

The installation wizard now informs you about the overall size of the required downloads. Click Next to proceed.

After the installation is complete, click Finish to exit the wizard. Close

When next you start, the newly installed dictionaries will be available to you as language modules under Tools > Options > Language Settings > Writing Aids.