Xerox Paris, a document system Support & Software 用户指南
Chapter 4
138
The Paris Spooler Technical Manual
FAQ
S A N D
T
R O U B L E S H O O T I N G
Q:
I selected an environment with a .ttf font in it, but this font never shows up in
the tree dialog, neither does it get packed using the Add Selected Files and
Required Resources option. What's going on?
Required Resources option. What's going on?
A:
The true type fonts are handled differently.
1.
As soon as the Resource Manager starts up, a true type font table is built.
2.
The Resource Manager scans the /windows/fonts/ directory and for each
physical .ttf file it picks up, it figures out the corresponding logical name.
Thus, for a file called ‘arial.ttf’, the generated logical name would be
something like ‘Arial Regular 10’.
Normally, when you choose an environment with an ‘Arial Regular 10’
font (the logical name) to pack, the Resource Manager figures out the
actual file name (in this case, arial.ttf) by looking it up in the table for the
corresponding logical name.
Assume that you select an old environment, possibly brought over from
another machine, and further assume that this environment contains a
‘Garamond Regular’ font that was present in that machine.
If this font is absent in your font directory, when the Resource Manager
starts up, it will not have an entry for the logical and physical names for
the ‘Garamond Regular’ font. Hence, when the Resource Manager
encounters a font called ‘Garamond Regular’, it will look up the true type
font table to find if such a font exists. Naturally it does not, so the font is
neither displayed nor packed.
physical .ttf file it picks up, it figures out the corresponding logical name.
Thus, for a file called ‘arial.ttf’, the generated logical name would be
something like ‘Arial Regular 10’.
Normally, when you choose an environment with an ‘Arial Regular 10’
font (the logical name) to pack, the Resource Manager figures out the
actual file name (in this case, arial.ttf) by looking it up in the table for the
corresponding logical name.
Assume that you select an old environment, possibly brought over from
another machine, and further assume that this environment contains a
‘Garamond Regular’ font that was present in that machine.
If this font is absent in your font directory, when the Resource Manager
starts up, it will not have an entry for the logical and physical names for
the ‘Garamond Regular’ font. Hence, when the Resource Manager
encounters a font called ‘Garamond Regular’, it will look up the true type
font table to find if such a font exists. Naturally it does not, so the font is
neither displayed nor packed.
!
NOTE:
This is the only satisfactory way of handling true type fonts. The other
option of looking at font entries in the Windows registry is not sufficient, as not all
fonts in the Windows font directory have entries in the registry. If the font is to
appear in the registry, then it should be properly installed.
Only by scanning all the .ttf font files in the Windows font directory and reading
their internals for the corresponding logical names would result in the most
accurate .ttf font table as this reflects all the current true type fonts in the system.
fonts in the Windows font directory have entries in the registry. If the font is to
appear in the registry, then it should be properly installed.
Only by scanning all the .ttf font files in the Windows font directory and reading
their internals for the corresponding logical names would result in the most
accurate .ttf font table as this reflects all the current true type fonts in the system.