Unable to add fonts to X
 

I couldn't find a more appropriate place to ask this question. Please feel
free to point me to such a place if one exists.

----

Using a completely up-to-date 32-bit arch system, I am trying to make some
fonts available to X.

My understanding of the process is:

1. Put the fonts in a directory.
2. Since these are scalable fonts, run mkfontscale in the directory.
3. Run mkfontdir in the directory.
4. run xset +fp <directory name>

So what I did:

0. Created the directory ~/.fonts.
1. Put the fonts in ~/.fonts.

At this point the contents of the directory looks like this (sorry about
the wrapping):

lrwxrwxrwx 1 n7dr users 39 Apr 22 17:08 CourierNewPSMTN7DR.ttf ->
/home/n7dr/fonts/CourierNewPSMTN7DR.ttf
lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.afm ->
/home/n7dr/fonts/N7DR_SFTT1000.afm
lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.pfb ->
/home/n7dr/fonts/N7DR_SFTT1000.pfb

2. Ran mkfontscale in ~/.fonts.

This created the file fonts.scale, which had the following contents:

33
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-adobe-standard
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-ascii-0
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp437
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp850
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp852
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp866
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso10646-1
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-1
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-10
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-13
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-15
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-2
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-3
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-4
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-5
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-8
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-9
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-koi8-e
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-koi8-r
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-koi8-ru
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-koi8-u
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-koi8-uni
CourierNewPSMTN7DR.ttf -monotype-courier new
n7dr-medium-r-normal--0-0-0-0-m-0-microsoft-cp1252
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-adobe-standard
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-ascii-0
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-iso10646-1
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-1
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-15
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-9
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-koi8-r
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-koi8-ru
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-koi8-u
N7DR_SFTT1000.pfb -misc-computer modern
n7dr-medium-r-normal--0-0-0-0-p-0-microsoft-cp1252

3. Ran mkfontdir in ~/.fonts.

This created the file fonts.dir, which was identical to fonts.scale.

4. One piece of documentation I read said that X automatically includes
~/.fonts in its path, but running
xset q
did not include ~/.fonts in the directory list.

So I ran:
xset +fp /home/n7dr/.fonts

But now we come to the problem. This command returns:

xset: bad font path element (#37), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax

But:
a. the directory obviously exists, and it has permissions rwx for the user.
b. The directory contains the file fonts.dir
c. The syntax looks OK.

So what is xset complaining about?

(I suspect that the problem lies in the *contents* of fonts.dir, since if I
create a dummy version of the file, I don't receive the error. But since
the file was automatically created, I don't know what might be wrong, nor
how to correct it. Maybe my suspicion is wrong, though.)

Doc

--
Web: http://www.sff.net/people/N7DR

Unable to add fonts to X
 

On Tue, Apr 24, 2012 at 5:34 AM, D. R. Evans <doc.evans@gmail.com> wrote:
> I couldn't find a more appropriate place to ask this question. Please feel
> free to point me to such a place if one exists.
>
> ----
>
> Using a completely up-to-date 32-bit arch system, I am trying to make some
> fonts available to X.
>
> My understanding of the process is:
>
> 1. Put the fonts in a directory.
> 2. Since these are scalable fonts, run mkfontscale in the directory.
> 3. Run mkfontdir in the directory.
> 4. run xset +fp <directory name>
>
> So what I did:
>
> 0. Created the directory ~/.fonts.
> 1. Put the fonts in ~/.fonts.
>
> At this point the contents of the directory looks like this (sorry about
> the wrapping):
>
> lrwxrwxrwx *1 n7dr users * 39 Apr 22 17:08 CourierNewPSMTN7DR.ttf ->
> /home/n7dr/fonts/CourierNewPSMTN7DR.ttf
> lrwxrwxrwx *1 n7dr users * 34 Apr 22 17:08 N7DR_SFTT1000.afm ->
> /home/n7dr/fonts/N7DR_SFTT1000.afm
> lrwxrwxrwx *1 n7dr users * 34 Apr 22 17:08 N7DR_SFTT1000.pfb ->
> /home/n7dr/fonts/N7DR_SFTT1000.pfb
>
> 2. Ran mkfontscale in ~/.fonts.
>
> This created the file fonts.scale, which had the following contents:
>
> 33
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-adobe-standard
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ascii-0
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp437
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp850
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp852
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp866
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso10646-1
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-1
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-10
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-13
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-15
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-2
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-3
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-4
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-5
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-8
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-9
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-e
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-r
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-ru
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-u
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-uni
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-microsoft-cp1252
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-adobe-standard
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-ascii-0
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso10646-1
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-1
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-15
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-9
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-koi8-r
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-koi8-ru
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-koi8-u
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-microsoft-cp1252
>
> 3. Ran mkfontdir in ~/.fonts.
>
> This created the file fonts.dir, which was identical to fonts.scale.
>
> 4. One piece of documentation I read said that X automatically includes
> ~/.fonts in its path, but running
> *xset q
> did not include ~/.fonts in the directory list.
>
> So I ran:
> *xset +fp /home/n7dr/.fonts
>
> But now we come to the problem. This command returns:
>
> xset: *bad font path element (#37), possible causes are:
> * *Directory does not exist or has wrong permissions
> * *Directory missing fonts.dir
> * *Incorrect font server address or syntax
>
> But:
> a. the directory obviously exists, and it has permissions rwx for the user.
> b. The directory contains the file fonts.dir
> c. The syntax looks OK.
>
> So what is xset complaining about?
>
> (I suspect that the problem lies in the *contents* of fonts.dir, since if I
> create a dummy version of the file, I don't receive the error. But since
> the file was automatically created, I don't know what might be wrong, nor
> how to correct it. Maybe my suspicion is wrong, though.)
>
> *Doc
>
> --
> Web: *http://www.sff.net/people/N7DR
>

There are no dot in /home/n7dr/fonts/ path. Should be /home/n7dr/.fonts/

--
Kirill Churin
Jabber: reflexing@reflexing.ru

Unable to add fonts to X
 

Add path to /etc/X11/xorg.conf ?
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection

and exec mkfontdir;mkfontscale in ~/.fonts dir, finally exec fc-cache -fv

On Tue, Apr 24, 2012 at 5:49 PM, Kirill Churin <reflexing@reflexing.ru>wrote:

> On Tue, Apr 24, 2012 at 5:34 AM, D. R. Evans <doc.evans@gmail.com> wrote:
> > I couldn't find a more appropriate place to ask this question. Please
> feel
> > free to point me to such a place if one exists.
> >
> > ----
> >
> > Using a completely up-to-date 32-bit arch system, I am trying to make
> some
> > fonts available to X.
> >
> > My understanding of the process is:
> >
> > 1. Put the fonts in a directory.
> > 2. Since these are scalable fonts, run mkfontscale in the directory.
> > 3. Run mkfontdir in the directory.
> > 4. run xset +fp <directory name>
> >
> > So what I did:
> >
> > 0. Created the directory ~/.fonts.
> > 1. Put the fonts in ~/.fonts.
> >
> > At this point the contents of the directory looks like this (sorry about
> > the wrapping):
> >
> > lrwxrwxrwx 1 n7dr users 39 Apr 22 17:08 CourierNewPSMTN7DR.ttf ->
> > /home/n7dr/fonts/CourierNewPSMTN7DR.ttf
> > lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.afm ->
> > /home/n7dr/fonts/N7DR_SFTT1000.afm
> > lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.pfb ->
> > /home/n7dr/fonts/N7DR_SFTT1000.pfb
> >
> > 2. Ran mkfontscale in ~/.fonts.
> >
> > This created the file fonts.scale, which had the following contents:
> >
> > 33
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-adobe-standard
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ascii-0
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp437
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp850
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp852
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp866
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso10646-1
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-1
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-10
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-13
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-15
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-2
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-3
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-4
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-5
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-8
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-9
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-e
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-r
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-ru
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-u
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-uni
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-microsoft-cp1252
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-adobe-standard
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-ascii-0
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso10646-1
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-1
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-15
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-9
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-koi8-r
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-koi8-ru
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-koi8-u
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-microsoft-cp1252
> >
> > 3. Ran mkfontdir in ~/.fonts.
> >
> > This created the file fonts.dir, which was identical to fonts.scale.
> >
> > 4. One piece of documentation I read said that X automatically includes
> > ~/.fonts in its path, but running
> > xset q
> > did not include ~/.fonts in the directory list.
> >
> > So I ran:
> > xset +fp /home/n7dr/.fonts
> >
> > But now we come to the problem. This command returns:
> >
> > xset: bad font path element (#37), possible causes are:
> > Directory does not exist or has wrong permissions
> > Directory missing fonts.dir
> > Incorrect font server address or syntax
> >
> > But:
> > a. the directory obviously exists, and it has permissions rwx for the
> user.
> > b. The directory contains the file fonts.dir
> > c. The syntax looks OK.
> >
> > So what is xset complaining about?
> >
> > (I suspect that the problem lies in the *contents* of fonts.dir, since
> if I
> > create a dummy version of the file, I don't receive the error. But since
> > the file was automatically created, I don't know what might be wrong, nor
> > how to correct it. Maybe my suspicion is wrong, though.)
> >
> > Doc
> >
> > --
> > Web: http://www.sff.net/people/N7DR
> >
>
> There are no dot in /home/n7dr/fonts/ path. Should be /home/n7dr/.fonts/
>
> --
> Kirill Churin
> Jabber: reflexing@reflexing.ru
>

Unable to add fonts to X
 

Kirill Churin said the following at 04/24/2012 03:49 AM :

>> So I ran:
>> xset +fp /home/n7dr/.fonts
>>
>> But now we come to the problem. This command returns:
>>
>> xset: bad font path element (#37), possible causes are:
>> Directory does not exist or has wrong permissions
>> Directory missing fonts.dir
>> Incorrect font server address or syntax
>>
>> But:
>> a. the directory obviously exists, and it has permissions rwx for the user.
>> b. The directory contains the file fonts.dir
>> c. The syntax looks OK.
>>
>> So what is xset complaining about?
>>

>>
>
> There are no dot in /home/n7dr/fonts/ path. Should be /home/n7dr/.fonts/
>

I don't understand. The command was:

>> So I ran:
>> xset +fp /home/n7dr/.fonts

so it did contain the correct path.

Doc

--
Web: http://www.sff.net/people/N7DR

Unable to add fonts to X
 

Jianjun Mao said the following at 04/24/2012 04:03 AM :
> Add path to /etc/X11/xorg.conf ?

There is no such file.

There is a directory /etc/X11/xorg.conf.d, but it doesn't contain an
xorg.conf either.

(FWIW, I don't think that xorg.conf has been used for a couple of years in
most distributions; I don't know about arch, but its absence strongly
suggests that it isn't used in that distribution either, since X is working
fine without it.)

Doc

--
Web: http://www.sff.net/people/N7DR

Unable to add fonts to X
 

That's right... There's no xorg.conf in Ubuntu, either. But in arch, using
X -configure to create the configuration file makes everything simpler? Of
course this works fine in my laptop.

On Tue, Apr 24, 2012 at 10:31 PM, D. R. Evans <doc.evans@gmail.com> wrote:

> Jianjun Mao said the following at 04/24/2012 04:03 AM :
> > Add path to /etc/X11/xorg.conf ?
>
> There is no such file.
>
> There is a directory /etc/X11/xorg.conf.d, but it doesn't contain an
> xorg.conf either.
>
> (FWIW, I don't think that xorg.conf has been used for a couple of years in
> most distributions; I don't know about arch, but its absence strongly
> suggests that it isn't used in that distribution either, since X is working
> fine without it.)
>
> Doc
>
> --
> Web: http://www.sff.net/people/N7DR
>
>

Unable to add fonts to X
 

Jianjun Mao said the following at 04/24/2012 08:43 AM :
> That's right... There's no xorg.conf in Ubuntu, either. But in arch, using
> X -configure to create the configuration file makes everything simpler? Of
> course this works fine in my laptop.
>

I tried X -configure and received this response:

----

X.Org X Server 1.12.1
Release Date: 2012-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.3.1-1-ARCH i686
Current Operating System: Linux shack 3.3.2-1-ARCH #1 SMP PREEMPT Sat Apr
14 10:08:43 UTC 2012 i686
Kernel command line:
root=/dev/disk/by-uuid/04611735-3010-419b-8755-dd7dfe4b371b ro
Build Date: 14 April 2012 07:32:51AM

Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 24 17:08:58 2012
List of video drivers:
openchrome
vesa
(++) Using config file: "/root/xorg.conf.new"
(==) Using config directory: "/etc/X11/xorg.conf.d"
Number of created screens does not match number of detected devices.
Configuration failed.
Server terminated with error (2). Closing log file.

----

Perhaps the fact that I have to use VNC-over-ssh to reach the system in
question is causing a problem? In any case, no file xorg.conf is being
created when I execute "X -configure".

I can access and use these fonts just fine in applications (such as the
xfce desktop settings), so it's very frustrating that making them directly
accessible to X is for some reason proving so difficult :-(

Doc

--
Web: http://www.sff.net/people/N7DR

X.Org X Server 1.12.1
Release Date: 2012-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.3.1-1-ARCH i686
Current Operating System: Linux shack 3.3.2-1-ARCH #1 SMP PREEMPT Sat Apr 14 10:08:43 UTC 2012 i686
Kernel command line: root=/dev/disk/by-uuid/04611735-3010-419b-8755-dd7dfe4b371b ro
Build Date: 14 April 2012 07:32:51AM

Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 24 17:08:58 2012
List of video drivers:
openchrome
vesa
(++) Using config file: "/root/xorg.conf.new"
(==) Using config directory: "/etc/X11/xorg.conf.d"
Number of created screens does not match number of detected devices.
Configuration failed.
Server terminated with error (2). Closing log file.

Unable to add fonts to X
 

Any more thoughts as to how I can add these fonts? Or at least diagnose why
I receive error #37 when I try to add them?

Or where there is an X-specific mailing reflector where I can ask this
question?

I can't progress with my project until these fonts are working under X :-(

Doc

----

D. R. Evans said the following at 04/23/2012 05:34 PM :
> I couldn't find a more appropriate place to ask this question. Please feel
> free to point me to such a place if one exists.
>
> ----
>
> Using a completely up-to-date 32-bit arch system, I am trying to make some
> fonts available to X.
>
> My understanding of the process is:
>
> 1. Put the fonts in a directory.
> 2. Since these are scalable fonts, run mkfontscale in the directory.
> 3. Run mkfontdir in the directory.
> 4. run xset +fp <directory name>
>
> So what I did:
>
> 0. Created the directory ~/.fonts.
> 1. Put the fonts in ~/.fonts.
>
> At this point the contents of the directory looks like this (sorry about
> the wrapping):
>
> lrwxrwxrwx 1 n7dr users 39 Apr 22 17:08 CourierNewPSMTN7DR.ttf ->
> /home/n7dr/fonts/CourierNewPSMTN7DR.ttf
> lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.afm ->
> /home/n7dr/fonts/N7DR_SFTT1000.afm
> lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.pfb ->
> /home/n7dr/fonts/N7DR_SFTT1000.pfb
>
> 2. Ran mkfontscale in ~/.fonts.
>
> This created the file fonts.scale, which had the following contents:
>
> 33
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-adobe-standard
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ascii-0
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp437
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp850
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp852
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp866
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso10646-1
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-1
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-10
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-13
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-15
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-2
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-3
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-4
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-5
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-8
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-9
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-e
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-r
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-ru
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-u
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-koi8-uni
> CourierNewPSMTN7DR.ttf -monotype-courier new
> n7dr-medium-r-normal--0-0-0-0-m-0-microsoft-cp1252
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-adobe-standard
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-ascii-0
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso10646-1
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-1
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-15
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-9
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-koi8-r
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-koi8-ru
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-koi8-u
> N7DR_SFTT1000.pfb -misc-computer modern
> n7dr-medium-r-normal--0-0-0-0-p-0-microsoft-cp1252
>
> 3. Ran mkfontdir in ~/.fonts.
>
> This created the file fonts.dir, which was identical to fonts.scale.
>
> 4. One piece of documentation I read said that X automatically includes
> ~/.fonts in its path, but running
> xset q
> did not include ~/.fonts in the directory list.
>
> So I ran:
> xset +fp /home/n7dr/.fonts
>
> But now we come to the problem. This command returns:
>
> xset: bad font path element (#37), possible causes are:
> Directory does not exist or has wrong permissions
> Directory missing fonts.dir
> Incorrect font server address or syntax
>
> But:
> a. the directory obviously exists, and it has permissions rwx for the user.
> b. The directory contains the file fonts.dir
> c. The syntax looks OK.
>
> So what is xset complaining about?
>
> (I suspect that the problem lies in the *contents* of fonts.dir, since if I
> create a dummy version of the file, I don't receive the error. But since
> the file was automatically created, I don't know what might be wrong, nor
> how to correct it. Maybe my suspicion is wrong, though.)
>
> Doc
>


--
Web: http://www.sff.net/people/N7DR

Unable to add fonts to X
 

Hi.
Try one of this :

1) create link to font folder inside /etc/X11/fontpath.d , restart X
2) copy/link font folder to /usr/share/fonts , restart X
3) copy font folder to ~/.fonts then do fc-cache -rv and check output for line like
'/home/n7dr/.fonts/n7dr: caching, new cache contents: 33 fonts, 0 dirs'

and as usually

4) avoid topposting ;)

Option 3 should work immediately, without restarting X...

Regards,
Slawek
--
________
_/ __/ __/ Fnord.
\__ \__ \_________________________________________________ ______________
/___/___/ Sławomir Szczyrba steev(AT)hot.pl


Dnia Wed, 25 Apr 2012 08:56:33 -0600
"D. R. Evans" <doc.evans@gmail.com> napisał(a):

> Any more thoughts as to how I can add these fonts? Or at least diagnose why
> I receive error #37 when I try to add them?
>
> Or where there is an X-specific mailing reflector where I can ask this
> question?
>
> I can't progress with my project until these fonts are working under X :-(
>
> Doc
>
> ----
>
> D. R. Evans said the following at 04/23/2012 05:34 PM :
> > I couldn't find a more appropriate place to ask this question. Please feel
> > free to point me to such a place if one exists.
> >
> > ----
> >
> > Using a completely up-to-date 32-bit arch system, I am trying to make some
> > fonts available to X.
> >
> > My understanding of the process is:
> >
> > 1. Put the fonts in a directory.
> > 2. Since these are scalable fonts, run mkfontscale in the directory.
> > 3. Run mkfontdir in the directory.
> > 4. run xset +fp <directory name>
> >
> > So what I did:
> >
> > 0. Created the directory ~/.fonts.
> > 1. Put the fonts in ~/.fonts.
> >
> > At this point the contents of the directory looks like this (sorry about
> > the wrapping):
> >
> > lrwxrwxrwx 1 n7dr users 39 Apr 22 17:08 CourierNewPSMTN7DR.ttf ->
> > /home/n7dr/fonts/CourierNewPSMTN7DR.ttf
> > lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.afm ->
> > /home/n7dr/fonts/N7DR_SFTT1000.afm
> > lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.pfb ->
> > /home/n7dr/fonts/N7DR_SFTT1000.pfb
> >
> > 2. Ran mkfontscale in ~/.fonts.
> >
> > This created the file fonts.scale, which had the following contents:
> >
> > 33
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-adobe-standard
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ascii-0
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp437
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp850
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp852
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-ibm-cp866
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso10646-1
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-1
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-10
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-13
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-15
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-2
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-3
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-4
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-5
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-8
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-iso8859-9
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-e
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-r
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-ru
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-u
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-koi8-uni
> > CourierNewPSMTN7DR.ttf -monotype-courier new
> > n7dr-medium-r-normal--0-0-0-0-m-0-microsoft-cp1252
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-adobe-standard
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-ascii-0
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso10646-1
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-1
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-15
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-iso8859-9
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-koi8-r
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-koi8-ru
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-koi8-u
> > N7DR_SFTT1000.pfb -misc-computer modern
> > n7dr-medium-r-normal--0-0-0-0-p-0-microsoft-cp1252
> >
> > 3. Ran mkfontdir in ~/.fonts.
> >
> > This created the file fonts.dir, which was identical to fonts.scale.
> >
> > 4. One piece of documentation I read said that X automatically includes
> > ~/.fonts in its path, but running
> > xset q
> > did not include ~/.fonts in the directory list.
> >
> > So I ran:
> > xset +fp /home/n7dr/.fonts
> >
> > But now we come to the problem. This command returns:
> >
> > xset: bad font path element (#37), possible causes are:
> > Directory does not exist or has wrong permissions
> > Directory missing fonts.dir
> > Incorrect font server address or syntax
> >
> > But:
> > a. the directory obviously exists, and it has permissions rwx for the user.
> > b. The directory contains the file fonts.dir
> > c. The syntax looks OK.
> >
> > So what is xset complaining about?
> >
> > (I suspect that the problem lies in the *contents* of fonts.dir, since if I
> > create a dummy version of the file, I don't receive the error. But since
> > the file was automatically created, I don't know what might be wrong, nor
> > how to correct it. Maybe my suspicion is wrong, though.)
> >
> > Doc
> >
>
>

Unable to add fonts to X
 

Sławomir Szczyrba said the following at 04/25/2012 09:23 AM :
> Hi. Try one of this :
>
> 1) create link to font folder inside /etc/X11/fontpath.d , restart X

There is no extant /etc/X11/fontpath.d. So what I did:

0) create /etc/X11/fontpath.d (as root)

1) inside /etc/X11/fontpath.d:
ln -s /home/n7dr/.fonts home-n7dr-.fonts (as root)

Restarted X (actually, rebooted)

> 2) copy/link font folder to /usr/share/fonts , restart X

2) Inside /usr/share/fonts:
ln -s /home/n7dr/.fonts home-n7dr-.fonts (as root)

Restarted X (actually, rebooted)

> 3) copy font folder to ~/.fonts then do fc-cache -rv and check output
> for line like '/home/n7dr/.fonts/n7dr: caching, new cache contents: 33
> fonts, 0 dirs'

A bit unsure about this, since the font folder *is* ~/.fonts, so I think I
just skip the step "copy font folder to ~/.fonts".

So I executed "fc-cache -rv" (as root) and the line you suggest actually says:
/home/n7dr/.fonts: caching, new cache contents: 2 fonts, 0 dirs

So there are two differences:

1. It says "/home/n7dr/.fonts", not "/home/n7dr/.fonts/n7dr" (perhaps that
was a typo on your part, since there is no directory /home/n7dr/.font/n7dr)

2. It says "2 fonts" not "33 fonts"

Executing xlsfonts (as ordinary user) still does not list the fonts as
available to me.

I did not at any point change the contents of /home/n7dr/.fonts, so it
still looks like this:

total 16
drwxr-xr-x 2 n7dr users 4096 Apr 23 17:12 .
drwx------ 34 n7dr users 4096 Apr 25 12:14 ..
lrwxrwxrwx 1 n7dr users 39 Apr 22 17:08 CourierNewPSMTN7DR.ttf ->
/home/n7dr/fonts/CourierNewPSMTN7DR.ttf
-rwxrwxrwx 1 n7dr users 2896 Apr 23 17:13 fonts.dir
-rwxrwxrwx 1 n7dr users 2896 Apr 23 17:12 fonts.scale
lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.afm ->
/home/n7dr/fonts/N7DR_SFTT1000.afm
lrwxrwxrwx 1 n7dr users 34 Apr 22 17:08 N7DR_SFTT1000.pfb ->
/home/n7dr/fonts/N7DR_SFTT1000.pfb

Sorry about the wrapping in that output; Thunderbird no longer seems to
support changing the wrap column for anindividual e-mail :-(

Doc

--
Web: http://www.sff.net/people/N7DR