[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Font setup in "startkde".
From:       James Richard Tyrer <tyrerj () acm ! org>
Date:       2004-08-31 16:34:18
Message-ID: 4134A88A.8050103 () acm ! org
[Download RAW message or body]

Craig Drummond wrote:
>> Is it necessary to add the KDE font directories to the X fontpath?
> 
> 
> In the case of $HOME/.fonts - Yes, so that non-kde / fontconfig apps can see 
> the fonts. OpenOffice (AFAIK) needs the fonts to be in X's font path before 
> it can see them - it also read the fonts.dir files (IIRC)
> 
Yes, that is correct OO still uses the old X FontPath.  However, since: 
"$HOME/.fonts" is a standard system directory, shouldn't we presume that
it has been properly configured (already)?  Shouldn't it be in: "XF86Config" 
already?  If it is using the old X FontPath, is it using the "encodings.dir" 
file as well?
> 
>> Then there is the GS_LIB code:
>> 
> --------
>> # Get Ghostscript to look into user's KDE fonts dir for additional Fontmap
>> if test -n "$GS_LIB" ; then
>>      GS_LIB=$usr_fdir:$GS_LIB
>>      export GS_LIB
>> else
>>      GS_LIB=$usr_fdir
>>      export GS_LIB
>> fi
>> 
>> --------
>> 
>> This has more issues which should be apparent to anyone that has read the 
>> GhostScript documentation.
> 
> This sounds familiar - you have discussed this before.

I have found a simpler way to work around the bug in Bash and found additional
problems.  Including that the "startkde" script was erasing some of my
"encodings.dir" files.

> I added these lines as the KDE font installer does create Fontmap files - 
> therefore GS_LIB is the correct one to use. The trouble with using 
> GS_FONTPATH is that it doesn't recurse into sub-directories.
> 
AFAIK, there is no recursion with GS_LIB because GhostScript doesn't use
FontConfig.  You can put all of the entries in the "Fontmap" file in the
directory that is the root of that directory tree, but that isn't the normal way
to do it and utilities that create "Fontmap" files do NOT do that.

But you make a good point.  If we assume that KDE users will install fonts with
the KDE Font Installer, then why do we need all of this junk in "startkde"?

>> Clearly, it would be necessary to check for all of these directories in 
>> GS_LIB.
> 
> 
> *necessary* ? It would be nice maybe, but seeing as it works fine for me - 
> and it would seem most other users - I don't think its *necessary* But feel 
> free to make the changes.

In general, it is proper programing practice not to add redundant entries to a 
path in the environment.

<SNIP>

>> So, this is really something of a mess.
> 
> 
> Again - in your own bug report (http://bugs.kde.org/show_bug.cgi?id=59367) 
> about this, I did state that you can modify the foomatic-rip script to get 
> ghostscript to look into $HOME/.fonts for a Fontmap file. This solves the 
> issue for me.

It is the script code in "startkde" that I am stating is a mess.

--
JRT
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]