Documente Academic
Documente Profesional
Documente Cultură
INTRODUCTION
The DLL will interact with the event log and the registry, under
certain conditions. The registry is always queried at the start of
the conversion to verify if the copyright holder has agreed to have
their font converted. The event log is used if an error occurs and if
the "Log events" entry in the registry is not zero. The required
entries in the registry is described in "t1instal.ini". Use
regini.exe to load these settings.
IsType1A
This function determines if a file is a valid Printer Font
Metrics files (pfm), and returns the face name of the font. This
function will only return TRUE if there is a valid PFB file in
the same directory or in the parent directory.
ConvertTypefaceA
This function takes the name of a PFM, a PFB and a TTF file as
parameters, that are used in the conversion.
Remove the comments from the t1instal.ini file and use regini utility
to place new keys in registry for use.
regini t1instal.ini
----------------------------------------------------------------------
-------------------------------------------------
The message logging mechanism in the Type 1 Installer.
Messages are recorded/displayed based on the severity of an error and based on the
state of the "log events" key in the registry. There are three types of messages:
- Errors : A problem that cased the conversion to abort.
- Warnings : A non-fatal problem that the converter resolved.
- Information : Information that may be useful to trace the execution of the
conversion, such as the name of the font and the vendor.
If an error occurs then a pop-up is presented to the user with the appropriate
message. Note that this will always happened, regardless of the "log events" key.
These strings are defined in the string table in the dll's resource file
(t1instal.rc).
The "log events" key is used for PSS and for debugging . It should not be used by
the users. It should only be turned on when attempting to determine the cause of a
failed conversion. This key causes all messages to be stored such that they are
accessible by the Event Viewer. These strings are defined in the dll's message file
(t1msg.mc). Note that warnings are being displayed in pop-up dialogs, in addition
to errors, when "log events" is non zero.
The motivation for this approach is that PSS may need to be able to remotely
resolve a problem that a customer has when converting a type 1 font. PSS will be
able to do this by instructing the user to turn on the "log events" feature and get
immediate feed-back when an error or a warning pops up a message. A computer that
is connected to a network can be accessed directly through the Event Viewer by the
PSS engineer.