font display name

[Haines Brown]

I'm changing from LaTeX to XeLaTeX, and one thing needed is to known
font "display names". I've installed the arphic faults for Chinese, but
these names don't work (when displaying the document with xpdf):

I have this preamble:

\documentclass[12pt]{article}
\usepackage{xltxtra}
\usepackage{xeCJK}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\begin{document}

This works for Vietnamese:

\section{Tiếng Việt}...

But none of the following works for simplified Chinese, I tried
everything, but could not find information on the display names for the
arphic gbsn CN:

\section{Han} % worked just once
无为

\section{Chinese Simplified}
无为

\newfontlanguage{Chinese~Simplified}{ZHS}
无为

\section{SimSun}
无为

\section{gbsn}
无为

\section{CJKfamily{gbns}}
无为

How does one find the display name?

Haines Brown?

[Thad Floryan]

On 4/22/2012 1:14 PM, Haines Brown wrote:
> I'm changing from LaTeX to XeLaTeX, and one thing needed is to known
> font "display names". I've installed the arphic faults for Chinese, but
> these names don't work (when displaying the document with xpdf):

> [...]

> But none of the following works for simplified Chinese, I tried
> everything, but could not find information on the display names for the
> arphic gbsn CN:
>
> \section{Han} % worked just once
> 无为
>
> \section{Chinese Simplified}
> 无为

> [...]

> How does one find the display name?

If you paste one set of those identical 2 symbols onto this page:

<http://translate.google.com/>

and select Chinese to English, those symbols translate to the
English word "Inaction" which suggests something isn't copacetic.
in your setup.

[Haines Brown]

Foryan, my problem not a traslation, but the font display name. The wu
wei characters are indeed often translated as "inaction", but better
would be to translate it as "unintended action". An action that responds
to the world's possibilities instead of a telos. It is a standard
concept in Daoism.

My problem is, that while I can print simplified chinese characters in
LaTeX, I need the font display name for XeLaTeX. I have the Arphic fonts
installed; what are their display nanes? How does one find the display
names for such fonts as Vietnamese, Ethiopic, or for that matter, for CM
sans?

I usually use xdvi to view .dvi output files, but XeLaTeX does not
generate a .dvi but a .pdf. Is the problem with xpdf? I really prefer
a .ps output because I seem to have more control over priting than with
a .pdf.

Haines Brown

[John F. Morse]

Haines,

Have you tried the alt.binaries.fonts group? There are some
knowledgeable people there.

Also alt.binaries.font and alt.binaries.fonts.flood are active.


--
John

When a person has -- whether they knew it or not -- already
rejected the Truth, by what means do they discern a lie?

[Kees Theunissen]

'xfontsel' might be helpful. It's part of the x11-utils package.
From the manpage:

XFONTSEL(1)

XFONTSEL(1)

NAME
xfontsel - point and click selection of X11 font names

SYNTAX
xfontsel [-toolkitoption ...] [-pattern fontname] [-print]
[-sample text] [-sample16 text16] [-sampleUCS textUCS] [-scaled]

DESCRIPTION
The xfontsel application provides a simple way to display
the fonts known to your X server, examine samples of each, and retrieve
the X Logical
Font Description ("XLFD") full name for a font.

[snip]


Regards,

Kees.

--
Kees Theunissen.

[J G Miller]

On Sunday, April 22nd, 2012, at 16:14:39 -0400, Haines Brown wrote:

> I'm changing from LaTeX to XeLaTeX, and one thing needed is to known
> font "display names". I've installed the arphic faults for Chinese, but
> these names don't work (when displaying the document with xpdf)

A possible stab in the dark as to the problem ...

As xpdf is an older application, it uses the old X11 font interface.

Your non standard fonts may not be available under that scheme,
but only under the newer Xft scheme.

I would therefore suggest you try using evince (which is compiled with
libXft) rather than xpdf.

To see the fonts and their names in the Xft scheme, fire up gnome-specimen,
doing first

apt-get update
apt-get install gnome-specimen

if necessary.

Under Xft, see the directory /etc/fonts for configuration and if
necessary for adding your own fonts in /usr/local or wherever,
add the full directory name to the file /etc/fonts/local.conf.

But if you have added extra fonts from the Debian packages,
these should all be made available under the /etc/fonts/conf.d
symbolic link scheme to the actual configuration file in /etc/fonts/conf.available

So if your language font is mentioned in /etc/fonts/conf.available but
not enabled in conf.available, then you need to make the symbolic link manually
for some reason.

Apologies if this is all irrelevant to your problem ...

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> A possible stab in the dark as to the problem ...
>
> As xpdf is an older application, it uses the old X11 font interface.
>
> Your non standard fonts may not be available under that scheme,
> but only under the newer Xft scheme.
>
> I would therefore suggest you try using evince (which is compiled with
> libXft) rather than xpdf.

Tried, but no go. However, rather than blank, it provides rectangles, so
at least it knows characters are there.

> To see the fonts and their names in the Xft scheme, fire up
> gnome-specimen

The gnome-speciman displays the latin font names, and it sees I have the
Chinese AR fonts installed, but displays them not as Chinese, but as
english ("The quick brown fox..."). The names provided for these fonts,
such as "AR PL KaitiM GB Regular" don't seem to be their "display name",
for it does not work.

> Under Xft, see the directory /etc/fonts for configuration and if
> necessary for adding your own fonts in /usr/local or wherever,
> add the full directory name to the file /etc/fonts/local.conf.

Yes, the local.conf has the arphic chinese fonts.

> But if you have added extra fonts from the Debian packages, these
> should all be made available under the /etc/fonts/conf.d symbolic link
> scheme to the actual configuration file in /etc/fonts/conf.available

? The "conf.d" file is not a symlink to conf.available.

> So if your language font is mentioned in /etc/fonts/conf.available but
> not enabled in conf.available, then you need to make the symbolic link
> manually for some reason.

You kind of loose me here. My chinese fonts are mentioned in conf.avail,
but not sure what you mean they should also be enabled there. Not sure
exactly what symlink should be there.

Haines Brown

[Haines Brown]

"John F. Morse" <jo...@example.invalid> writes:

> Haines,
>
> Have you tried the alt.binaries.fonts group? There are some
> knowledgeable people there.
>
> Also alt.binaries.font and alt.binaries.fonts.flood are active.

Much appreciated. Will give it a try.

Haines

[J G Miller]

On Monday, April 23rd, 2012 17:54:13 -0400, Haines Brown wrote:

> The gnome-speciman displays the latin font names, and it sees I have the
> Chinese AR fonts installed, but displays them not as Chinese, but as
> english ("The quick brown fox...").

Because it is displaying the characters specified in the
Preview Text text box.

If you do not want it to display the characters "The quick brown fox"
then change the text to something in Chinese or whatever characters.

> The names provided for these fonts, such as "AR PL KaitiM GB Regular"
> don't seem to be their "display name", for it does not work.

What is "it" and in which manner does "it" fail to work?

> Yes, the local.conf has the arphic chinese fonts.

If the arphic Chinese fonts are not in the standard directories
listed in the /etc/fonts/font.conf eg

<!-- Font directory list -->

<dir>/usr/share/fonts</dir>
<dir>/usr/X11R6/lib/X11/fonts</dir>
<dir>/usr/local/share/fonts</dir>
<dir>~/.fonts</dir>

<!--

you need to add them to
the directory list in /etc/fonts/local.conf eg

<!--
Font directory list
-->

<dir>/usr/local/X11R6/lib/X11/fonts</dir>
<dir>/usr/local/X11R6/share/xfce/fonts</dir>

<!--

If they were installed from standard Debian packages,
then they should have gone in the standard font location
/usr/share/fonts and nothing needs to be added.

> My chinese fonts are mentioned in conf.avail,

For a number of system applications which can
have optional features which need to be turned on
and off in an easy manner, Debian uses the following scheme
(used in eg apache2 and fonts).

The feature configuration file goes in a directory
{something}-available

There is also a directory conf.d which is the actual
directory used by the sofware application to read its
configuration files. But this does not contain any files.
It just contains symbolic links to the actual configuration
files in {something}-available according to the system
administrator whether or not to turn on that particular feature.

So in /etc/fonts/conf.available you have lots of configuration
files for different fonts and properties. But each one of
this is only *activated* for use, if there is a symbolic link
in the conf.d directory to it, eg

in /etc/fonts/conf.available there is the file

10-antialias.conf

But this configuration for features of anti-aliasing are only
used if in /etc/fonts/conf.d there is the symbolic link

10-antialias.conf -> ../conf.avail/10-antialias.conf

So if there is a configuration file for your arphic Chinese
fonts or whatever else in /etc/fonts/conf.available and
there is no link in /etc/fonts/conf.d to it, then the
features offered by the configuration file will never be
used.

Which is why I suggested that you check for the presence
of both the configuration file in /etc/conf.avail and
the presence of a symbolic link in /etc/conf.d to that file
if it exists in /etc/conf.avail.

Is that a clear enough explanation of what I was trying
to convey and clearly failed?


And what you should do is the following to ensure that all
fonts present in the directories listed in /etc/fonts/font.conf
and /etc/fonts/local.conf are available in the Xft system,
as root

fc-cache -fsv

You can then get a list of all fonts available in the Xft system
with

fc-list | sort

If you want to try out a font, then use a program such as
urxvt (terminal emulator) which has been linked with Xft eg

urxvt -font "xft:GenoaItalic"

urxvt -font "xft:

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> If you do not want it to display the characters "The quick brown fox"
> then change the text to something in Chinese or whatever characters.

Aha! Obvious. Should have read the manual. Thanks.

>> The names provided for these fonts, such as "AR PL KaitiM GB Regular"
>> don't seem to be their "display name", for it does not work.

I've managed to resolve this problem. $ fc-list provides the name I need
for XeLaTeX.

>> Yes, the local.conf has the arphic chinese fonts.
>
> If the arphic Chinese fonts are not in the standard directories
> listed in the /etc/fonts/font.conf eg

I find that the fonts are listed and accessible.

> Is that a clear enough explanation of what I was trying
> to convey and clearly failed?

Yes it is, but the fog was at my end.

> You can then get a list of all fonts available in the Xft system
> with
>
> fc-list | sort
>
> If you want to try out a font, then use a program such as
> urxvt (terminal emulator) which has been linked with Xft eg
>
> urxvt -font "xft:GenoaItalic"
>
> urxvt -font "xft:

Thank you, this is a big help. The urxvt term does not seem to support
multiple sessions, and one session is tied up permanently. So I had to
use rxvt-unicode instead for above commands. This worked, but for some
reason the spacing between characters was to big. But a minor issue.

My problem at this point is that in XeLaTeX, when I do:

\setCJKmainfont{AR PL KaitiM GB}

it sets the body Chinese font successfully, but when I do

\newfontfamily\sungtiGB{AR PL SungtiL GB}
{\sungtiGB This is Sung}

The Chinese characters remain in main font instead of changing to the
\newfontfamily font.

This, of course, this is a XeLaTeX rather than debian issue.

Haines Brown

[J G Miller]

On Thursday, April 26th, 2012, at 13:17:53h -0400, Haines Brown wrote:

> Yes it is, but the fog was at my end.

That is why it is important to turn on the fog lights so
that others can know whether or not the message is
getting through the mist ;)

> The urxvt term does not seem to support multiple sessions, and one
> session is tied up permanently. So I had to use rxvt-unicode instead
> for above commands.

urxvt is rxvt-unicode, so I do not understand what you mean by this.

From the manual page ...

NAME
*rxvt-unicode* (ouR XVT, unicode) - (a VT102 emulator for the
X window system)

SYNOPSIS
*urxvt* [options] [-e command [ args ]]

> This worked, but for some reason the spacing between characters was to big.
> But a minor issue.

Perhaps because urxvt needs some fine tuning? It would be good
if you could send in a report to the urxvt authors, or submit the
information as a Debian bug since you are presumably using urxvt
from the Debian package.

> My problem at this point is that in XeLaTeX, when I do:
>
> \setCJKmainfont{AR PL KaitiM GB}
>
> it sets the body Chinese font successfully, but when I do
>
> \newfontfamily\sungtiGB{AR PL SungtiL GB}
> {\sungtiGB This is Sung}
>
> The Chinese characters remain in main font instead of changing to the
> \newfontfamily font.

Stupid suggestion -- if you do not do \setCJKmainfont{AR PL KaitiM GB}
and just do \newfontfamily\sungtiGB{AR PL SungtiL GB}, do you see
characters in the newfont family or do they remain in the Latin font
that is used for everything else?

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> On Thursday, April 26th, 2012, at 13:17:53h -0400, Haines Brown wrote:

>> The urxvt term does not seem to support multiple sessions, and one
>> session is tied up permanently. So I had to use rxvt-unicode instead
>> for above commands.
>
> urxvt is rxvt-unicode, so I do not understand what you mean by this.

My bad. I run mutt permantly with a urxvt terminal. If I run urxvt from
another terminal, the new urxvt terminal opens beneath mutt on on the
workspace dedicated to mutt.

>> My problem at this point is that in XeLaTeX, when I do:
>>
>> \setCJKmainfont{AR PL KaitiM GB}
>>
>> it sets the body Chinese font successfully, but when I do
>>
>> \newfontfamily\sungtiGB{AR PL SungtiL GB}
>> {\sungtiGB This is Sung}
>>
>> The Chinese characters remain in main font instead of changing to the
>> \newfontfamily font.
>
> Stupid suggestion -- if you do not do \setCJKmainfont{AR PL KaitiM GB}
> and just do \newfontfamily\sungtiGB{AR PL SungtiL GB}, do you see
> characters in the newfont family or do they remain in the Latin font
> that is used for everything else?

No, when the \setCJKmainfont{} is removed, the \newfontfamily\...{}
command does not access the new font, and xpdf display of the .pdf file
shows no chinese characters at all. That is, as implied by the initial
problem, \newfontfamily command is not accessing the Arphic fonts.

Haine Brown

[J G Miller]

On Thursday, 26 Apr 2012 17:40:48 -0400, Haines Brown wrote:

> No, when the \setCJKmainfont{} is removed, the \newfontfamily\...{}
> command does not access the new font, and xpdf display of the .pdf file
> shows no chinese characters at all.

Okay that does provide some information, so may I be permitted a followup --
what happens if you do

\setCJKmainfont{AR PL SungtiL GB}

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

The document is displayed in the SungtiL, and the \newfontfamily command
has no offect. This is why I was so puzzled, for it did not seem a
problem of accessing fonts, but of XeLaTeX syntax.

I have trouble understanding manuals, but I finally managed to get this
to work.

In a document with just one default Chinese font, I define it:

\usepackage{xltxtra}
\usepackage{xeCJK}

\setCJKmainfont{AR PL SungtiL GB}

and then simply paste chinese characters in the text or call their
unicode, such as ^^^^8708.

My problem was that I confused this with selecting different Chinese
font families. For that I dont need to set the main Chinese font, but
in preface put:

\usepackage{xltxtra}
\usepackage{xeCJK}
\setCJKfamilyfont{Sung}{AR PL SungtiL GB}
\setCJKfamilyfont{Kaiti}{AR PL KaitiM GB}
\setCJKfamilyfont{UMing}{AR PL UMing CN}

and in body:

Kaiti: {\CJKfamily{Kaiti} ^^^^8708}
Sung: {\CJKfamily{Sung} ^^^^8708}
Ming: {\CJKfamily{UMing} ^^^^8708}

Not sure how legitimate all this is.

Haines Brown

[J G Miller]

On Friday, April 27th, 2012, at 09:37:20h -0400, Haines Brown wrote:

> J G Miller <mil...@yoyo.ORG> writes:
>>
>> Okay that does provide some information, so may I be permitted a
>> followup -- what happens if you do
>>
>> \setCJKmainfont{AR PL SungtiL GB}
>
> The document is displayed in the SungtiL, and the \newfontfamily command
> has no offect.

Thanks for reporting back on this -- it reveals an important point --
if
\setCJKmainfont

is used to define a main font, then following(?) invocations of \newfontfamily
are ignored.

If you would indulge me on one more point then ...

If I understand correctly you put the \newfontfamily definition after
\setCJKmainfont in the document.

Does it make any difference if you do things in the following order

1) define your newfontfamily first
2) then invoke \setCJKmainfont
3) then try to use \newfontfamily

It may not work at all and that the \setCJKmainfont results in any
use of \newfontfamily being ignored, but it could be possible that having
the definition of \newfontfamily after the \setCJKmainfont causes it to
be lost and then not available to the subsequent \newfontfamily invocation.

> For that I dont need to set the main Chinese font, but
> in preface put:
>
> \usepackage{xltxtra}
> \usepackage{xeCJK}
> \setCJKfamilyfont{Sung}{AR PL SungtiL GB}
> \setCJKfamilyfont{Kaiti}{AR PL KaitiM GB}
> \setCJKfamilyfont{UMing}{AR PL UMing CN}

Well that could be a better way of doing it rather than defining defining a
default main with \setCJKmainfont and invoking each CJKfamilyfont as needed.

It could be that the macro for \setCJKmainfont causes all subsequent
\fontfamily definitions to be lost or the actual \fontfamily invocation
to be ignored, which is why I suggest doing the test above.

> Not sure how legitimate all this is.

How legitimate which is? Just getting TeX or LaTeX or whatever to
produce what you want is difficult enough (but worth it of course)
and you need a real TeX GURU (not me) to pronounce on the legitimacy
or official way it should be done ;)

Anyways, it is good to hear that you are making some progress
in getting the output you want to produce.

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> If you would indulge me on one more point then ...

You do understand that I got things working, but your are asking me to
perform a little experiment.

> If I understand correctly you put the \newfontfamily definition after
> \setCJKmainfont in the document.

In my previous message you will note that there is no \newfontfamily
command at all. I do have a document that has that command as well as
\setCJKfamilyfont commands, and so I'll run the experiment on it.

> Does it make any difference if you do things in the following order
>
> 1) define your newfontfamily first
> 2) then invoke \setCJKmainfont
> 3) then try to use \newfontfamily

You loose me. In my present document that works, briefly it is:

\documentclass[12pt]{article}
\usepackage{xltxtra}

\setmainfont[Mapping=tex-text]{Linux Libertine O}

\newfontfamily{\punknova}{punknova-regular.otf}

\usepackage{xeCJK}
\setCJKfamilyfont{Sung}{AR PL SungtiL GB}

\begin{document}

This is punk: {\punknova Punknova}

This is Sung: {\CJKfamily{Sung} ^^^^8708}

\end{document}

So this order may be what you are asking for. In any case it works. I'll
try a different order if you like?

> It may not work at all and that the \setCJKmainfont results in any
> use of \newfontfamily being ignored,

No, the above example works ok.

> but it could be possible that having the definition of \newfontfamily
> after the \setCJKmainfont causes it to be lost and then not available
> to the subsequent \newfontfamily invocation.

I put the \newfontfamily for punknova just before \begin{document}
and after \setCJKmainfont, and everything still works.

> Anyways, it is good to hear that you are making some progress in
> getting the output you want to produce.

Unfortunately, now comes a detail I had not mentioned. I ran # fc-cache
on some directories, and now have a rich # fc-list. However, I'm lost.

For example, punknova font does not show up in fc-list, but nevertheless
I can display it with the .otf extension. So XeTeX does not rely on the
fontconfig? Why do I have to specify the .otf extension for it?

I can use Junicode, but it is not in fc-list and I must invoke it with

\newfontfamily{\junicode}{Junicode-Regular.ttf}

I have /storage/fonts/bitstream/lombardc.atm, lombardc.ofm,
lombardc.pfb. Any way to display it?

Is there a better way to know what's accessible to LaTeX? The #
gocharmap utility does not see junicode or punknova.

Haines

[J G Miller]

On Friday, April 27th, 2012, at 17:58:39h -0400, Haines Brown wrote:

> You loose me.

Seems *I misunderstood* your previous message when you wrote

My problem at this point is that in XeLaTeX, when I do:

\setCJKmainfont{AR PL KaitiM GB}

it sets the body Chinese font successfully, but when I do

\newfontfamily\sungtiGB{AR PL SungtiL GB}
{\sungtiGB This is Sung}

I thought you meant that you had a document with

\setCJKmainfont{AR PL KaitiM GB}

*followed by*

\newfontfamily\sungtiGB{AR PL SungtiL GB}
{\sungtiGB This is Sung}

and that the font was remaining as KiaitiM and not
changing to SungtiGB

Hence why I was asking if you moved the definition of
\newfont family if that made any difference.

> For example, punknova font does not show up in fc-list, but nevertheless
> I can display it with the .otf extension. So XeTeX does not rely on the
> fontconfig? Why do I have to specify the .otf extension for it?

You were running fc-cache to update the font database for Xft applications
eg evince, the PDF viewer. If you do ldd {XeTeX binary} | egrep xft
does it show anything? If XeTeX displays stuff then it may use xft,
but for actually creating the document with TeX I expect it uses the TeX
font handling system.

> I have /storage/fonts/bitstream/lombardc.atm, lombardc.ofm,
> lombardc.pfb. Any way to display it?

The general purpose font manipulating and viewing program is fontforge, which
can handle pfb fonts such as

/usr/share/texmf-texlive/fonts/type1/urw/palatino/uplb8a.pfb

so install it and try using that on lombardc.pfb

> Is there a better way to know what's accessible to LaTeX?

The fonts installed understalled /usr/share/texmf-texlive ;)

Also look at /etc/texmf/texmf.cnf which contains variables pointing to
directories containing fonts which TeX can use. Maybe XeTeX also has
a cofiguration file pointing to extra font directories?

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> Hence why I was asking if you moved the definition of
> \newfont family if that made any difference.

No.

>
>> For example, punknova font does not show up in fc-list, but nevertheless
>> I can display it with the .otf extension. So XeTeX does not rely on the
>> fontconfig? Why do I have to specify the .otf extension for it?
>
> You were running fc-cache to update the font database for Xft applications
> eg evince, the PDF viewer. If you do ldd {XeTeX binary} | egrep xft
> does it show anything? If XeTeX displays stuff then it may use xft,
> but for actually creating the document with TeX I expect it uses the TeX
> font handling system.

$ ldd {XeTeX binary} | egrep xft
ldd: ./{XeTeX: No such file or directory
ldd: ./binary}: No such file or directory

So does this mean that XeTeX is not using xft? Yet I believe can use all
fonts returned by $ fc-list.

>> I have /storage/fonts/bitstream/lombardc.atm, lombardc.ofm,
>> lombardc.pfb. Any way to display it?
>
> The general purpose font manipulating and viewing program is
> fontforge, which can handle pfb fonts such as
>
> /usr/share/texmf-texlive/fonts/type1/urw/palatino/uplb8a.pfb
>
> so install it and try using that on lombardc.pfb

It was already installed. Are you suggesting that I use it to convert
the .pfb to an .otf, and then call it with something like
\newfontfamily{\lombardic}{lomgardc.otf}? Sorry to be so dense about
these matters.

>> Is there a better way to know what's accessible to LaTeX?
>
> The fonts installed understalled /usr/share/texmf-texlive ;)
>
> Also look at /etc/texmf/texmf.cnf which contains variables pointing to
> directories containing fonts which TeX can use. Maybe XeTeX also has
> a cofiguration file pointing to extra font directories?

Yes, but XeTeX can access and print fonts such as punknova-regular and
Caligula. They don't seem to be mentioned in texfm.cnf.

Haines

[J G Miller]

On Friday, April 27th, 2012, at 22:27:37h -0400, Haines Brown asked:

> $ ldd {XeTeX binary} | egrep xft
> ldd: ./{XeTeX: No such file or directory
> ldd: ./binary}: No such file or directory
>
> So does this mean that XeTeX is not using xft?

No! It means that you did not replace the string {XeTeX binary}
with the actual path to the XeTeX binary on you system,
perhap something like /usr/bin/xetex

> It was already installed.

So use it to look at the font characters to see what
they are like -- which is what I thought you were
wanting to do but did not know what program to use
to do so.

> Are you suggesting that I use it to convert
> the .pfb to an .otf

As you say you already have the font in .otf format,
there is not need to do that.

> and then call it with something like
> \newfontfamily{\lombardic}{lomgardc.otf}?

Is that how you invoke other fonts in .otf format?

Remember also that the font has to be located in one of the
directories specied in the texmf.conf file.

> Yes, but XeTeX can access and print fonts such as punknova-regular and
> Caligula. They don't seem to be mentioned in texfm.cnf.

It is not the individual fonts which need to be mentioned but
that the font file needs to be located in the one of the
directories specified in the texmf.conf file.

I am afraid to say that I never did get around to working
on adding additional fonts to the TeX fonts directory.

As always other things have got in the way, but maybe your
prompt will get me to look at the issue some time in the
near future.

There is a chapter on how to do this in "TeX Unbound"
if you want to read up on all the details of how TeX
uses fonts and what formats are supported.

Since you seem to be wanting to do quite complicated things
with TeX, having a copy to hand would probably be a help for you.

<http://www.amazon.COM/TeX-Unbound-LaTeX-Strategies-Graphics/dp/019509686X>