Big issues in 2.0

From NeoWiki

Jump to: navigation, search

This page is intended to collect causes and, if possible, quick fixes for 2.0 builds.

Contents is suddenly taking a large amount of extra diskspace

This is because the included fondu application has converted your Mac fonts for use with the OOo code. This can eat over 100 MB of your disk. You can find these fonts at /Applications/ 2.0/Contents/openoffice.org2.0/share/truetype .

You can delete fonts from this directory, but remember that you will not be able to use them in OOo anymore. (You can delete all the fonts with a .bdf extension without any loss of functionality, as they are not used by OOo but are still created by the fondu process.)

After running, my NeoOffice installation crashes and brings down my entire system

Your OOo 2.0 installation most likely converted a large number of fonts, one or more of which may be corrupted and causing NeoOffice to crash spectacularly.

The solution seems to be to go to /Applications/ 2.0/Contents/openoffice.org2.0/share/truetype and delete any fonts larger than 1 MB.

See also the report in this forum thread.

I can't open any files with Scandanavian or non-Roman characters in their filenames

These may be two separate issues; it is too early to tell. The new "launcher" does not properly encode filenames before handing them off to the actual X11 binaries.

  • Try opening the files from within's Open dialogue.
  • You might also wish to use Start as your launcher instead of; it is able to correctly encode these filenames.
  • If all else fails, try renaming the file.

Using Start as the launcher for 2.0

Unfortunately, the late Terry Teague's Start application does not include built-in support for the new 2.0. Since Start includes many advanced setup features, as well as menu items that provide easy access to the Printer Admin function and each application, and the ability to open files with non-Roman characters in their names on all versions of Mac OS X, many users my prefer to continue using it to launch

Luckily it is not too difficult to configure Start to launch the new version, but it may require a tiny bit of Terminal usage.

Opening the .sversionrc file

  • Open the hidden .sversionrc file at the root of your home directory (this file will only exist if you've previously used 1.x.x)
    1. Open Terminal (in /Applications/Utilities)
    2. At the prompt, type open -a TextEdit .sversionrc and hit return.
  • If you've not previously used 1.x.x
    1. Open TextEdit and create a new document
    2. Choose Make Plain Text from the Format menu
    3. Save the (empty) file; navigate to your home folder, uncheck "Hide Extension", enter .sversionrc as the filename, and click Save. When the dialogue warns you about saving a "dot" file, choose the Use “.” button.

Edit the .sversionrc file and save

  • Your file should look like this (the entry for 1.1.2 is not necessary if you do not have 1.1.2 installed):
[Versions] 1.1.2=file:///Applications/OpenOffice.org1.1.2/ 2.0=file:///Applications/
  • Save the file (there should be no warnings this time)

Launch and Configure Start

  • Launch Start
    • If you've not run Start before, it may ask you to locate X11 (in /Applications/Utilities)
    • If you have already used Start with 1.1.2, it will launch X11 and 1.1.2
  • In the Start Preferences, make sure " 2.0RC3" is selected as your preferred version and click OK.
  • Quit Start
    • When restarting Start, it will now lauch 2.0
    • You can drag and drop documents onto its icon to open them
    • You will need to manually assign Start to the new OpenDocument filetypes (see Setting the Default Application) in order to be able to open them via double-clicking
Personal tools