Issue 23589 - italic fonts not displaying
Summary: italic fonts not displaying
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: gsl
Classification: Code
Component: www (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christof.pintaske
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-16 05:01 UTC by tads
Modified: 2004-01-27 17:22 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description tads 2003-12-16 05:01:19 UTC
I am having problems with italic fonts displaying properly on a new Debian
install.  I am using Oo.o 1.1-2 from a deb via a net install (not sure of the
build number; how do I check?).  This is a new install of Debian 3 with 2.4.22
kernel.  I am using KDE 3.1

Most fonts display as normal/regular text (with perhaps a small base shift) when
they should appear italicized.  However, a few fonts (e.g., Bitstream Vera
Serif) do display italics properly.  But for most, italics appear as normal text
though the italics button is highlighted when the cursor is in text that should
appear italic.  Bold and underline work properly.  If I create a doc with what
should be italic text, save it, and open it in MS Word on another machine, it
displays correctly.  Unfortunately, I cannot try printing from the linux machine.

On my previous setup with this hardware (Debian Potato--2.2.19 kernel,
windowmaker, and Oo.o 1.0) I did not have this problem.

Not sure if it is a bug or my ignorance, but I cannot figure it out.  Thanks!
Comment 1 philipp.lohmann 2003-12-16 10:41:26 UTC
The problem is most likely that you don't have a corresponding italic font for
the normal font. This e.g. the case for Bitstream Vera Sans.
Comment 2 christof.pintaske 2003-12-16 16:29:39 UTC
yep, please make sure that you have installed the according italic fonts. Have a
look at the file user/psprint/pspfontcache . There you'll find all the fonts
OpenOffice.org is aware of. 
Comment 3 tads 2003-12-16 17:47:29 UTC
Thanks!  I have found a kludge to get around the problem.  You are right that
(at least part of) the problem has to do with font availability.

First, since this was installed with a debian package manager, I am not sure how
to determine the home directory for the install.  I was unable to find
user/psprint/pspfontcache under any directories.  I checked /usr, /usr/local,
/usr/share, /usr/lib, /usr/share/openoffice, and
/usr/share/openoffice.org-debian-files (among others).  How can I find the
install directory?  Maybe that is not really an openoffice question.

What has worked (sort of) is to copy important TT fonts from another machine to
/usr/share/fonts/truetype/ttf-xxx/ directories (where xxx is the name of the
font).  This was the organization of the Bistream Vera Sans font that displayed
correclty before.  As I have played with this some I have noticed that some
fonts appear only as italics (e.g. Courier); Courier 10 Pitch appears only as
normal.  Since I don't have this problem with displays in other programs, I am
reluctant to change things too much (I know just enough to be dangerous).

For gsfonts, the italic fonts appear to be present in the directory along with
the normal and bold fonts, but they still don't display properly in Oo.o.  But,
when I export a file (that has italic text) to pdf, and open with acrobat reader
or KGhostView, the italics appear correctly.

Things are working well enough that I can atleast get some work done.  Thanks
again, for your help.
Comment 4 christof.pintaske 2004-01-05 18:06:48 UTC
cp->tads: you can find the pspfontcache file by starting this command in a shell:
    find / -name pspfontcache
please note that this might be annoyingly slow if you are working in a local
area network. 
Comment 5 christof.pintaske 2004-01-19 12:58:15 UTC
cannot reproduce, no idea how to work on that without further information 
Comment 6 christof.pintaske 2004-01-27 17:22:03 UTC
closing as works for me