I upgraded ( Well, backed up my stuff, including fonts, blew it all away, then installed 8.2, and dumped the fonts in ). The fonts are all type1 from www.apostrophiclabs.com. Very cool and nice fonts. Under 8.0, in staroffice, they all worked. I could even get them in SodiPodi. Now, it is a ROYAL mess. I can see them, I can use them in some programs. But whereas in 8.0, using Staroffice 6, I could use all my fonts, under 8.2, Staroffice seems to think that some fonts are now ugly white-boxes. The drop down list shows no more previews for these fonts, and when you type, you get the little annoying boxes. It sounds like an encoding problem, but I am at my wits end! -Daniel -- The Meek shall inherit the Earth, for the Brave are among the Stars!
* Daniel Joyce
I upgraded ( Well, backed up my stuff, including fonts, blew it all away, then installed 8.2, and dumped the fonts in ).
[...]
It sounds like an encoding problem, but I am at my wits end!
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.
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
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...
===
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
They're opentype fonts, and it appears that Heidorn Hill and the other trouble causing fonts are two-byte fonts. But they worked under 8.0... :P KDE, which uses the Freetype2 libs, has no problems with them. I'm suspecting it's a problem with Freetype/X as this has been mentioned on the OO website... I can try dumping them into the local dir though... -Daniel
-----Original Message-----
From: Daniel Joyce
I upgraded ( Well, backed up my stuff, including fonts, blew it all away, then installed 8.2, and dumped the fonts in ).
The fonts are all type1 from www.apostrophiclabs.com. Very cool and nice fonts. Under 8.0, in staroffice, they all worked. I could even get them in SodiPodi.
Now, it is a ROYAL mess.
I can see them, I can use them in some programs. But whereas in 8.0, using Staroffice 6, I could use all my fonts, under 8.2, Staroffice seems to think that some fonts are now ugly white-boxes. The drop down list shows no more previews for these fonts, and when you type, you get the little annoying boxes.
It sounds like an encoding problem, but I am at my wits end!
-Daniel
I too had this problem once and found that it was a permissions problems with the fonts. I would check there first. Ken
participants (4)
-
BandiPat -
Daniel Joyce -
Ken Schneider -
Mads Martin Joergensen