Re: OpenOffice.org 1.1.2 on XQuartz
Re: OpenOffice.org 1.1.2 on XQuartz
- Subject: Re: OpenOffice.org 1.1.2 on XQuartz
- From: Eric Hoch <email@hidden>
- Date: Fri, 22 Oct 2010 13:03:25 +0200
Hi René,
Am Fri, 22 Oct 2010 11:30:53 +0200 schrieb René J.V. Bertin:
> Hello,
>
>
> OpenOffice 1.1.2 (X11) does not work properly with XQuartz 2.5.3 on my
> new MBP13" running OS X 10.6.4: almost none of my (truetype and PS)
> fonts are rendered, or they are almost all rendered in the local
> background colour. OOo1.1.2 being a PPC application, I can understand
> this when it's run locally, but the exact same thing happens when I
> run it on my Powermac (runs OS X 10.4.11 with Apple's X11) and display
> on my MBP. Given that OpenOffice has its own font database, I consider
> that fonts should display remotely if they display locally... or am I
> missing something?
Well OpenOffice.org 1.1.2 is a very old release and the X11 version
of OOo isn't supported any longer since the arriving of the first
aqua native version 3.0 and the subsequent releases up to 3.2.1 and
the soon to come 3.3.0.
In addition 1.1.2 was more or less the first true release for the
mac since 1.0 and 1.1.0 were still marked as beta or release
candidates.
In order to display the fonts in 1.1.2 you had to convert them and
import them into OpenOffice.org. The tool to use was, when I
remember it correctly, called psprint and needed to be run from an
xterm. You'll find psprint inside the OpenOffice.org Application
bundle. You can access the application bundle by simply using the
cd command eg. cd Applications/OpenOffice.org/ I don't remember the
exact location but using "find . -name "*psprint*" inside the
application folder should do the trick or you use the spotlight
search inside the folder via finder but this may only work on
10.6.4.
Once psprint is up and running you will find a button called "Add
fonts" or similar which opens a dialogue that lets you choose the
folder in which the fonts you wish to use are stored. Be aware that
psprint doesn't support subfolder, meaning all the fonts you wish
to use need to be on the first level.
I also remember that only specific true type and ps fonts could be
used and that those were mostly the windows version and not the mac
versions. So you had to convert the "mac only" fonts to windows
fonts. Sadly I don't remember which command line tool we used for
this task but I remember that we either included the tool itself or
the command that run the version shipped with the Mac OS X
underlying BSD userland into our starter application starting with
the 2.0 version of OOo. In later versions of the starter
application we added a dialogue that allowed the user to either
convert the fonts out of the default Mac OS X fonts folders or
choose a folder of his choice.
Even if you don't want to update to a 2.0 version or even a native
3.x version you may download the latest 2.4.x release (find it here
<ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/2.4.3rc2/>
and simply modify the launching script to match the path of the
1.1.x version. I once did so for a friend and it took me no longer
than two minutes to do so.
> When run on the MPB, behaviour is correct also when I display on the
> Powermac (deadkeys function too, there) or when I use Apple's X11 to
> have a local :1.0 display (deadkeys do not work).
I don't get it. First you write that OpenOffice.org 1.1.2 does not
work properly on your MBP and now you say it does work on the MBP.
Please be more specific what does and what does not work.
> Is this a bug I should report?
For XQuartz yes, for OpenOffice.org there is no longer any support
or bugfixing for the 1.1.x code being it on Mac, Windows or Linux.
There was a discussion once if we should release a 1.1.6 for the
Mac but there were not enough volunteers for this task and as of
today I supposed there are close to none and Oracle only engages in
the native version of OOo.
You may be able, if you know the tag for the cvs checkout, which I
don't, to checkout the sources for the to be 1.1.6 and build it on
your own but you would have to fix all occurring build breaks on
your own.
Btw, is there a specific reason to stick with 1.1.2?
Eric
--
## de.OpenOffice.org - Office für MacOS X, Linux, Solaris & Windows
## Openoffice.org - ich steck mit drin!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden