Re: Installing an X fonts package to a new FontPath.
On Tue, 14 Sep 1999, Branden Robinson wrote:
>> We can consider about the case of gsfonts-x11. Ghostscript's type1
>> fonts can be shared by ghostscript and X11. (I really like this type
>> of sharings.) There seems to be no way for gsfonts-x11 to meet your
>> proposal.
> I don't see why not. You could ship a bunch of symlinks from
> /usr/X11R6/lib/X11/fonts/Type1/* to wherever gsfonts-x11 keeps them.
I was just browsing the archives, and noticed your recent request for more
feedback. Coincidentally, I was just thinking about this today. :)
I'd actually prefer to see the Type1 and Truetype fonts in a
/usr/share/fonts, and symlinked into /usr/X11R6/. Both of these formats
are broadly useful to a variety of software, and by no means exclusive to
X. They're architecture independent as well, so /usr/share seems like a
good place. This idea also helps aesthetically in providing a symmetric
place to install local fonts. (a must, IMHO, given the poor quality of
available DFSG-free display fonts)
I suppose this moves things up a level policy-wise, but I think it's the
best thing to do. The FHS doesn't seem to specify anything on the subject.
> BTW, if Type1 fonts like this are truly sharable, I don't see much point
> in naming the package "gsfonts-x11", but maybe that's just me. If I get
> started ranting on people's illogical and inconsistent package names,
> I'll never stop. And we've all seen how gracefully dpkg handles package
> renames (not).
See, my proposal gets rid of the need for such packages! =)
> I'll clarify the proposal that symlinks are acceptable as long as
> /usr/X11R6/lib/fonts/ is not otherwise cluttered with directories.
You mean /usr/X11R6/lib/X11/fonts/ ?
Down at the wishlist level, I'd like to see some way to break font
collections into directories. Things quickly get unwieldy and it would be
nice to have an obvious indication of what fonts came from where.
Cheers,
-ralph
--
Ralph_Giles@sfu.ca
please cc me on replys, I'm not subscribed to the list
Reply to: