[SOLVED] Slackware 14.0 64-bit Problem with Ghostview (gv) and Fonts
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Slackware 14.0 64-bit Problem with Ghostview (gv) and Fonts
I'm getting strange (at least to me) error messages using
Code:
gv filename.ps
Any PostScript file I've attempted this with spits out
Quote:
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-efont-biwidth-medium-r-normal--16-*-*-*-*-*-iso10646-1,-gnu-unifont-medium-r-normal--16-*-*-*-*-*-iso10646-1,-adobe-helvetica-medium-r-normal--14-*-*-*-*-*-*-*,-jis-fixed-medium-r-*--16-*-*-*-*-*-jisx0208.1983-0,-*-*-medium-r-*--16-*-*-*-*-*-*-*,*" to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Huh?
Something I've missed somewhere?
I do have the Adobe Type Library installed (in /usr/local/share/fonts/Adobe) -- it's all PostScript -- along with other local font directories in /usr/local/share/fonts/[names] with the local.conf file in /etc/fonts (been working for years, those).
Is there a fonts.dir, fonts.scale & font.alias? If not, it doesn't see the fonts. cd to the directory and as root do
mkfontdir
mkfontscale
From the mkfontdir man page
Quote:
The file "fonts.alias", which can be put in any directory of the font-path, is used to map new names to existing fonts, and should be edited by hand. The format is two white-space separated columns, the first containing aliases and the second containing font-name patterns. Lines beginning with "!" are comment lines and are ignored.
I don't think even the encodings in /usr/share/X11/fonts/encodings are read without the encodings.dir file, e.g. from my Xorg.0.log
FreeType: couldn't find encoding 'iso8859-13' for '/usr/share/fonts/sazanami/mincho/sazanami-mincho.ttf'
iso8859-13 is:
/usr/share/X11/fonts/encodings/iso8859-13.enc.gz
It is possible for encodings.dir to list the contents of multiple directories:
# cd /usr/share/X11/fonts/encodings
# mkfontdir -n -e /usr/share/X11/fonts/encodings -e /usr/share/X11/fonts/encodings/large
Of course, it's Fedora and it's from 2010 (so there's no /usr/share/X11/fonts/encodings directory in Slackware 14, but there are /usr/share/fonts/encodings and /usr/share/fonts/encodings/large, seemingly with the same content).
Subsequently, there is this post (referring to the above one):
Quote:
Roderick Johnstone 2010-10-26 11:24:28 EDT
Edward: Very many thanks.
The problem was in one of our local font directories. Your mkfontdir command in bug #634039 fixed it nicely.
Closing this report.
So, maybe that worked OK in 2010 but I'm reluctant to touch the font directories (might no hurt, but, boy do I not want to screw things up not knowing what I'm doing).
I'm going to keep digging -- it certainly is strange that the identical errors occur in Slackware 14 that were appearing years ago, eh?
Not really strange that the same error happened in the past, with similar consequences.
If you find a solution (in this case, running mkfontdir like I already suggested) check for it or do it. Otherwise, ignore the past. Have you fonts.dir wuith a line for each of your fonts?
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Both fonts.dir and fonts.scale contain 593 indexes for the font files found in /usr/share/ghostscript/fonts (which is actually a symbolic link to /usr/share/fonts/Type1).
I have a 13.37 box (gv, ghostscript and ghostscript-fonts are the same versions on 13.37 and 14.0 and I'm doing compares to find any differences. None have turned up as yet.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
OK, finally got a little bit schmarter; a Google search for "Missing charsets in String to FontSet conversion" turned up the answer at http://www-01.ibm.com/support/docvie...id=swg21146408 -- it's the locale, stupid.
You know those warnings about UTF-8 in /etc/profile.d/lang.sh? Well, they're true -- you're going to get the messages from gv with a UTF-8 locale but if you put it back to LANG=en_US you don't.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.