Big issues in OpenOffice.org 2.0

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 18:06, 12 November 2005 (edit)
Sardisson (Talk | contribs)
m (→Opening the <tt>.sversionrc</tt> file)
← Previous diff		 Current revision (22:27, 27 July 2006) (edit) (undo)
Sardisson (Talk | contribs)
(→Using Start OpenOffice.org as the launcher for OpenOffice.org/X11 2.0)
 
(2 intermediate revisions not shown.)
Line 17: Line 17:
==I can't open any files with Scandanavian or non-Roman characters in their filenames== ==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 OpenOffice.org 2.0.app "launcher" does not properly encode filenames before handing them off to the actual X11 binaries. Try opening the files from within OpenOffice.org/X11's '''Open''' dialogue. You might also wish to use Start OpenOffice.org as your launcher instead of OpenOffice.org 2.0.app.+These may be two separate issues; it is too early to tell. The new OpenOffice.org 2.0.app "launcher" does not properly encode filenames before handing them off to the actual X11 binaries.
 + 
 +* Try opening the files from within OpenOffice.org/X11's '''Open''' dialogue.
 +* You might also wish to use Start OpenOffice.org as your launcher instead of OpenOffice.org 2.0.app; it is able to correctly encode these filenames.
 +* If all else fails, try renaming the file.
===Using Start OpenOffice.org as the launcher for OpenOffice.org/X11 2.0=== ===Using Start OpenOffice.org as the launcher for OpenOffice.org/X11 2.0===
-Unfortunately, the late Terry Teague's [http://www.geocities.com/terry_teague/openoffice.html Start OpenOffice.org] application does not include built-in support for the new OpenOffice.org 2.0. However, it is not ''too'' difficult to configure Start OpenOffice.org to launch the new version, but it may require a tiny bit of Terminal usage.+Unfortunately, the late Terry Teague's [http://www.geocities.com/terry_teague/openoffice.html Start OpenOffice.org] application does not include built-in support for the new OpenOffice.org 2.0. Since Start OpenOffice.org 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 OpenOffice.org.
 + 
 +Luckily it is not ''too'' difficult to configure Start OpenOffice.org to launch the new version, but it may require a tiny bit of Terminal usage.
====Opening the <tt>.sversionrc</tt> file==== ====Opening the <tt>.sversionrc</tt> file====
Line 47: Line 53:
** You can drag and drop documents onto its icon to open them ** You can drag and drop documents onto its icon to open them
** You will need to manually assign Start OpenOffice.org to the new OpenDocument filetypes (see [[Setting the Default Application]]) in order to be able to open them via double-clicking ** You will need to manually assign Start OpenOffice.org to the new OpenDocument filetypes (see [[Setting the Default Application]]) in order to be able to open them via double-clicking
 +
 +[[Category:Tips and Hints]][[Category:OpenOffice.org]]

Current revision

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

Contents

OpenOffice.org 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/OpenOffice.org 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 OpenOffice.org, 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/OpenOffice.org 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 OpenOffice.org 2.0.app "launcher" does not properly encode filenames before handing them off to the actual X11 binaries.

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

Using Start OpenOffice.org as the launcher for OpenOffice.org/X11 2.0

Unfortunately, the late Terry Teague's Start OpenOffice.org application does not include built-in support for the new OpenOffice.org 2.0. Since Start OpenOffice.org 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 OpenOffice.org.

Luckily it is not too difficult to configure Start OpenOffice.org 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 OpenOffice.org 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 OpenOffice.org 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 OpenOffice.org 1.1.2 is not necessary if you do not have 1.1.2 installed): 
[Versions]
OpenOffice.org 1.1.2=file:///Applications/OpenOffice.org1.1.2/
OpenOffice.org 2.0=file:///Applications/OpenOffice.org2.0.app/Contents/openoffice.org/
  • Save the file (there should be no warnings this time)

Launch and Configure Start OpenOffice.org

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