Xerox Paris, a document system Support & Software User Guide
Chapter 4
140
The Paris Spooler Technical Manual
Q:
When I select the ‘Font’ file type in the Add Pack Files dialog, it shows me
all the fonts, but when I select and try to pack it, I cannot. Why?
A:
The fonts you see appearing in the view are actually taken from the fonts.ini
file, which is stored in an internal list in Paris. The Resource Manager reads and
displays the fonts from this list.
In order for everything to be in sync, the logical names of .lpf fonts (such as line
printer 9 regular) in fonts.ini reflects or corresponds to the actual physical files on
disc (in this case, LI09.lpf or similar name). Hence, if a user deletes the physical
file, the reference is still in the fonts.ini file, and Paris will still build a list that
contains the logical name. However, there is no corresponding physical file on disk
in the Paris fonts directory.
Therefore, another way of putting this question would be “I have 10 physical .lpfs
in my Paris fonts directory, but more than that appears in the font view in the add
dialog” … the answer is that some physical files have been deleted in the Paris
fonts directory.
displays the fonts from this list.
In order for everything to be in sync, the logical names of .lpf fonts (such as line
printer 9 regular) in fonts.ini reflects or corresponds to the actual physical files on
disc (in this case, LI09.lpf or similar name). Hence, if a user deletes the physical
file, the reference is still in the fonts.ini file, and Paris will still build a list that
contains the logical name. However, there is no corresponding physical file on disk
in the Paris fonts directory.
Therefore, another way of putting this question would be “I have 10 physical .lpfs
in my Paris fonts directory, but more than that appears in the font view in the add
dialog” … the answer is that some physical files have been deleted in the Paris
fonts directory.
Q:
I’m trying to unpack a .pak file, but the Resource Manager keeps coming up
with the message ‘Not a valid pack file’. Why?
A:
The only answer is that the .pak file has been corrupted, or the file extension
of a normal file has been deliberately changed to .pak, a highly improbable
occurrence.
occurrence.