On Sunday 14 September 2003 06:14 pm, Daniel Joyce wrote:
Did you remember to run:
# SuSEconfig --module fonts
After you dumped them?
-- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J.
I've tried them all. For example, Heidorn Hill used to work fine in Open/Star Office. Now it gives the dreaded Squares of Doom.
And running that command has seemingly messed up some other fonts as well.
Grrr!
Folks, we're supposed to make this easier, not harder!
-Daniel ===============
Daniel, Did you have both the .pfb and .afm files of all the fonts? Font handling is actually getting better, a bit more precise and Ghostscript a bit more finicky, but it's certainly finding the good & bad. Not all fonts are good fonts, as you are finding out. This is one of the problems with all the low quality truetype fonts everyone tries to use that don't work. If you install the fonts using the Control Center, you can have it generate .afm (ghostscript) files as well, but that still won't turn a bad font into a good one. It may make it work where it didn't before though. Always be sure to run the command that Mads mentioned or /sbin/fonts-config --force to build all the scales etc. needed for screen display and font setup. The best thing usually to do for SO/OO is to add the fonts into their main directories. I believe SO is /opt/staroffice6.0/share/fonts and the new OO1.1 is /usr/local/OpenOffice.org1.1.0/share/fonts. They will use the fonts and not be quite as particular about the quality. You won't have them available to the sytem then, but that will allow you to test which fonts work and which ones don't to remove them from the system. Lee -- --- KMail v1.5.3-3 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...