Bug#218833: openoffice.org: Type 1 fonts do not display correctly on-screen (all programs)
On Sun, Nov 02, 2003 at 04:05:39PM -0600, Scott Thatcher wrote:
> OpenOffice.org does not seem to display Type 1 fonts correctly
> on-screen, instead substituting another font for the requested font.
> For example, the Type 1 font Palatino is replaced by Times New Roman on
> the screen, and Zapf Chancery is replaced by Comic Sans-Serif. When I
> print to a file, the postscript renders correctly using gv, and the
> document prints correctly (although I haven't tried this with a
> non-standard type 1 font).
Michael Meeks said about this to me:
10:08 < michael_> haggai: if the font has a printer icon by it then: yes, it
uses another font to render to screen, and it uses the adobe font metrics to
space the glyphs
10:08 < michael_> haggai: and when it prints it outputs the real font.
10:08 < michael_> haggai: so I think that is feature-not-bug
> I really appreciate the work you've done to make a Debian package of
> OpenOffice, but I do worry that you've removed the ability of OpenOffice
> to use load fonts (using spadmin) separately from the rest of the system.
> I have run into system-wide font problems several times in various
> contexts, and in the past OpenOffice's ability to just read the font
> directly has been a big help.
With the resources we have, we only have two choices for this sort of thing:
Include the patches as they are or do not include them. We did not really
have any choice about spadmin. Ximian disable spadmin completely; I did
modify their patches to make it possible to create printer queues, but I do
not have enough free time to write and test extra features into them such
as supporting both OOo and spadmin.
If the bug is fixable by making small tweaks, we may be able to do this.
Otherwise we can only bin the whole of the Ximian fontconfig support and
wait until it appears in the official OOo 2.0, which would be a pity since
it simplifies font configuration for most user installs. But we'll have to
do that if these problems can't be solved soon.
Now, back to your setup. I don't actually have font files for the fonts you
listed, so I cannot get them to display on screen, and the screen
substitutions that you mentioned occur for me too. Are you saying that you
are getting substitutions for a font that you actually have, i.e. you have a
Type 1 font file for 'Palatino' and therefore expect this to be displayed?
Or are you saying that you think the substitution mechanism is not working
properly and another font should be displayed instead? What would having
'spadmin' allow you to do that the current mechansim does not?
Thanks,
Chris
Reply to: