Re: [Groff] Re: Resource forks in OSX

[Alejandro López-Valencia]

Werner LEMBERG wrote:
>> [The DESC file] will be overwritten when installing a latter CVS
>> snapshot; why can't we have a shadow site-fonts directory where we
>> can place our own font and download files, perhaps even custom DESC
>> files?  Perhaps easier than the idea of emulating kpathsea.
>
> Just set GROFF_FONT_PATH!

Works nicely, thanks. Don't I say? This happens when you play by ear and
start getting a little deaf...

> A single site-fonts directory is simply not enough IMHO.  While the
> number of default fonts for groff is usually quite small, they should
> be organized somehow.  Putting TeX's CM and EC fonts together with
> PostScript fonts into the same directory is simply bad.  Thus
> emulating kpathsea is for the benefit of organization, not to provide
> a user's font directory (which is already handled nicely by both
> troff's -F option and the GROFF_FONT_PATH environment variable).
>
> Exactly the same arguments hold for a single site-macros directory,
> so a kpathsea-like library will really be a win.

I agree with you completely. Yet, I believe my idea is still valid and
that it complements a kpathsea style directory sarch.

For example, for site-wide installations, a site-fonts directory is
ideal to keep house style font, logos and such. And for individual users
who use a unix desktop and may prefer to have all their local fonts in
one system-wide place (e.g., I always have more than one account to work
with and separate tasks per account, when I have administrative control
of the machine).