CGFont .atc file builder for PPage etc.
=======================================

MkAtc V1.0 Copyright Adrian Aylward 1991

You may freely copy, use, and modify this program.  The source is included
in the distribution.

This program builds a character encoding table file (.atc) in the format
used by Professional Page for its CG fonts.  It uses the PostScript style
encoding file.  You can use it to change the character set used by PPage,
to access special characters and typographic symbols.

Command line interface
======================

usage:

    mkatc -options atcfile

options:

        -e encodingfile
                The character set encoding file.  Default
                "PSFonts:encoding.ps".

        -c charcodesfile
                The file listing the available CG font character codes.
                Default "CGFonts:cgcharset".

        -lnnn   LoChar (default 32).  Character codes below this value
                are ignored.

        -hnnn   HiChar (default 255).  Character codes above this value
                are ignored.

        -unnn   Unique id.

        -r      Read the .atc file, only.  Do not update it.

        -v      Verify the encoding table to the standard output.

        -V      Verify encoding table, using an alternative format.

The "atcfile" argument is the name of the .atc file to be created.

When creating a new .atc file the unique id must be given as an option.  (Its
value can be determined by looking in the corresponding .dat file, or by
referring to an old version.  When updating an old file the old value will
be used by default.

for example:

    mkatc cgfonts:Times.atc

    mkatc -e psfonts:ppage_encoding.ps cgfonts:Times.atc

    mkatc -rv cgfonts:Times.atc

After changing the .atc file you should purge any entries refering to it
from the font cache, to ensurethat you get the new characters next time
you run PPage.  The easy way to do this is to type:

    rm cgcache:Times*

Caveat
======

The .atc file format and the character codes were determined by reverse
engineering.  So I can't guarantee their accurary.  However they appear to
work OK.

Versions
========

    V1.0  04-May-91

The original.