This file contains a sample Postscript type 3 font (TIMESEXT.PS) which
takes the basic Times-Roman font and creates a new font with new ASCII
mapping to allow better compatibility with Pagestream.  Other required
files for Pagestream also included.

If you are only interested in using the font, simply copy the enclosed
files into your Pagestream font folder.  You will need to go to the font
manager and select the 'update' button in order for Pagestream to know the
font has been added.



WARNING!  FOR EXPERTS ONLY, PLEASE!
------------------------------------
If you are interested in how this works, and how you might do this with
your own fonts, please read on.  A little basic knowledge of Postscript is
required, and a fairly good knowledge of Pagestream is assumed.

First, please note that the re-encoded font does not replace the original
font.  Both are still available.  However, regardless of if the original font
is a type 1 font or a type 3 font, the new font will be a type 3 font.
And yes, you can re-encode resident printer fonts in a Postscript printer
and/or native Ultrascript fonts.  I've even used these re-encoded fonts
with Linotron typesetting equipment with no problem.

Note that although this example uses Times-Roman, almost any font could be
used as long as the necessary characters are defined.  To simply change the
original font being used, you would need to edit the last line of the font
file, which looks like:

(|_Times-Roman) RecodeFont

You would need to remove "Times-Roman" and insert the Postscript font name
of the desired font.  To do this, you need to know the name Postscript uses
internally for the font.  Please note that the Postscript font name may not
be exactly the same as the name used by an application program like
Pagestream.  Postscript font names do not contain spaces, so the words of
the font name are typically either run together or separated by dashes.

For example, "Times Roman" is "Times-Roman" and "Palatino Bold Italic" is
"Palatino-BoldItalic"

For most fonts, this may be all you need to do, aside from creating the
necessary support files for Pagestream (that is discussed a bit later).
However, if you want to change the character mapping in a different way
than what the sample font does, some more work is needed.

To change the character mapping, you need to know the postscript names for
the characters involved.  (Also, the sample font only remaps the characters
in the range of 128-255.  If you need to remap characters 127 and/or below,
you are on your own, although the sample font may serve as a starting
point.)

Most Postscript fonts should be accompanied by an Adobe Font Metrics file.
This is a text file that contains information about the font, such as the
font name, which characters are defined and their names, and other
information such as the relative width and height of each character.  These
files usually have a filename extension of .AFM.

The sample font uses the existing mapping for characters 0-127, and remaps
characters 128-255.  If you wanted, for example, to change the mapping for
character 173, you would find the line with this character and change the
character name on that line to what you want.  Shown below is the section
of the sample font file which contains the mapping for character 173.

   /logicalnot     % 170
   /onehalf
   /onequarter
   /exclamdown     % <--- THIS IS IT!  CHARACTER 173
   /guillemotleft
   /guillemotright
   /atilde
   /otilde
   /Oslash
   /oslash
   /oe             % 180

As we can see, character 173 is currently mapped to "exclamdown", which is
which is the name of the Postscript subroutine within the font which draws
an upside down exclamation point.  To change it to, for example, an "*"
character, you'd change that line to:

   /asterisk       % <--- THIS IS IT!  CHARACTER 173

If in doubt about what characters are available, you have two choices.  If
the font comes with an .AFM (Adobe Font Metrics) file, you can look in
there.  Otherwise, you can simply try it and see.  If a particular
character is not available in a particular font, you can substitute another
character name.  The sample font uses the space character for this purpose.

Once you finish making any changes to create a new font, you need to create
support files for Pagestream to recognize it.  The best starting point is
to copy the appropriate files from the original font that is being
re-encoded, and give them new names.

Once you've done that, you must use the Pagestream font editor to give the
files all the same NEW font ID number, and you should change the font name
indicated as well.  Once you have done this correctly, the new font should
be usable.

Where did I learn all this?  The font remapping stuff came mostly from a
book named "Real World Postscript" If you are interested in Postscript
programming, I suggest you look it up.

That's about all for now.  I realize things might get a bit
under-described there at the end, but to be honest, I didn't originally
intend to take this quite this far.  If anyone has specific questions
about how this works, please leave EMAIL to MIKE-FULTON.


           Mike