[twg-tds] scripts, enc/lig/map

Karl Berry karl at freefriends.org
Thu Feb 19 02:24:47 CET 2004

Here's revised text for the scripts and enc/lig/map directories, and
mention of .inf.  Full DVI attached.

Further comments?  I'll send to tex-implementors once we're happy here.


for platform-independent executable files, such as Perl, Python, and
shell scripts, and Java class files.  Subdirectories under
\path|scripts| should be by package names.  The intent is not for all
such directories to be added to a user's command search path, but to
benefit helper scripts in the normal executable directory.  Examples:


The TDS also reserves the names \path|enc|, \path|lig|, and \path|map|
for font encoding, ligature, and mapping files, respectively.  All of
these directories are structured the same way, with \replaceable{syntax}
subdirectories, and then \replaceable{package} subsubdirectories.  Each
of these file types is intended to be searched along a single
recursively-searched path.  The names of the actual files must be unique
within their subtree, as usual.  Examples:

The Fontname collection and Dvips package have more examples of the
\path|enc| and \path|map| types.  The \path|afm2pl| program uses
\path|lig| files.

\path|pfm| files are included in the \path|type1| directory, instead of
being given their own directory, for two reasons: 1)~a \path|.pfm| file
is always an adjunct to a given \path|.pfb| file; 2)~they must be
installed from the same directory for Windows programs other than \TeX{}
to use them.

\path|inf| files are included in the \path|afm| directory, since
an \path|inf| and \path|afm| file can be used to generate a \path|pfm|.
(Unfortunately, Adobe Type Manager and perhaps other software requires
that the \path|pfb| be in the same directory as \path|afm| and
\path|inf| for installation.)

More information about the twg-tds mailing list