| 1 |
While making it easier for those who want all of their fonts included in |
| 2 |
the x11 server-side font list is not an unreasonable goal, forcing them |
| 3 |
to be is unreasonable. |
| 4 |
|
| 5 |
As someone who has run X11 regularly for over 20 years now, I absolutely |
| 6 |
do not want any type1 or SFNT fonts in my x server font path. Any app I |
| 7 |
use these days with such fonts supports client-side fonts. For the apps |
| 8 |
which require server-side fonts, the bfd fonts suit best. |
| 9 |
|
| 10 |
Putting all of /usr/share/fonts into the fontpath will only slow the X11 |
| 11 |
startup. |
| 12 |
|
| 13 |
I'd suggest either an eselect(1) driven applet to let one choose which |
| 14 |
directories to add to a single .d conf file, or perhaps a non-gentoo- |
| 15 |
specific gui app to do so. Either of those would provide exactly the |
| 16 |
right sort of configuation assistance for users who are not comfortable |
| 17 |
editing their configs in text editors. |
| 18 |
|
| 19 |
Or, if you are feeling ambitious, write an X-Font-Server which uses |
| 20 |
libfontconfig to find fonts, generates and keeps a cache of fc-pattern |
| 21 |
to/from xlfd mappings, and serves said fonts to X servers. |
| 22 |
|
| 23 |
-JimC |
| 24 |
-- |
| 25 |
James Cloos <cloos@×××××××.com> OpenPGP: 1024D/ED7DAEA6 |
Archives