Michael O'Henly wrote:
> Can you help me fill in the blanks?
>
I will try.
> QUESTION: I'm making up the filenames on the Linux side. Is that OK? Do they
> have to be lower case?
>
I think that it's not necessary. But it's case sensitive, so the name you write
in the file have to been the name you use.
> QUESTION: What do I do with this? It doesn't contain any POST resources
> so I can't "unmacify" it. Do I need it on the Linux side?
>
????
> This produces Fontmap, fonts.dir, fonts.scale, and type1inst.log. It tells me
> that it can't identify the foundry. I manually edit fonts.scale and
> fonts.dir, replacing "unknown" with the name of the foundry (in lower case).
>
I think that you have to add your file to the fonts.dir.
>
> I become the root user and add the path to this directory in the
> /etc/X11/fs/config catalogue. I restart the fontserver.
>
> /etc/rc.d/init.d/xfs restart
>
> Now -- according to everything I've read -- my X applications should be
> able to see this new font family. They don't.
>
> I've tried xfontsel and from within various applications. I've rebooted
> the system, checked permissions, etc.
>
> QUESTION: Where am I going wrong?
>
I don't know, why don't you try kfontinst?
>
> QUESTION: What are the practical side-effects of adding a large number
> of fonts to X? Does it slow things down, consume memory, or anything
> else?
>
I have read that is worst when you use a lot of fonts because you use more
memory, but I need a confirmation.
>
> QUESTION: Are you aware of any "font managment" packages for Linux that
> help to organize large collections of fonts?
>
Kfontinst.
Best regards, feel free to write me directly, I want to do the same, and
probably I would have the same problems.
Leo
--
Leopold Palomo Avellaneda
Linux User 152692
Catalonia
