1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
% This is ASEX encoding. (file ASEX.enc)
%
% Adobe Standard Encoding Extended.
%
% Creator: Pierre A. MacKay mackay@cs.washington.edu
% Creation Date: Thu Aug 31 08:56:22 PDT 1993
%
% This is an input coding file for creation of a "raw font".
% It can, for esample be used with Radical Eye Software's
% afm2tfm. Use with the -p flag. This same encoding can also be
% used with ps2pk to create a complete set of bitmapped
% simplex characters.
%
% The {\em sole} purpose of this file is to ensure that all {\em simplex}
% characters in the font are made available in the raw TFM. Therefore
% there are no ligatures or any other refinements. The raw TFM
% file contains no ligatures or kernings---nothing but character
% metrics. We retain Adobe Standard encoding for all mapped
% characters in the AFM file, and extend the list by adding
% the unmapped simple characters into the empty code positions
% from O 200 to O 240. It is assumed that the output coding used
% for the TeX tfm will be different from this ( -t flag in afm2tfm ).
%
% The extended part of this encoding is consistent with the general
% run of text fonts from Adobe, BitStream, DTC, Linotype, Monotype,
% URW and probably others as well. For SuperFont characters, see below.
% In a library of over 300 text fonts, I have found no variants. The only
% variant in display fonts is the occasional absence of lowercase.
%
% Jan Michael Rynnings has pointed out that a few very carefully designed
% fonts, e. g. Adobe Garamond and Adobe Caslon, may treat all the accented
% characters as simplex glyphs (must make for a large pfa file), and that
% this input encoding would not recognize such refinements. True---but
% such fonts will be a tiny minority, and can be dealt with by
% special encoding files. A couple of tests indicate that it makes
% no perceptible difference whether you use composites formed from
% the CC recipes in the AFM file or call the characters out directly
% from the PFA file. There seems no reason, therefore, to fill the
% raw font with characters that are clearly identified as composites
% in the AFM file.
%
% Usage:
% afm2tfm <FontName>.afm -p ASEX.enc -t <output>.enc -v <vplname> <rawname>
%
/ASEXEncoding [ % now 256 chars follow
%
% The following will replace the characters from 0 to 32 in the raw encoding
% if you have access to a SuperFont. There is reason to hope that this
% set will be as stable as the unmapped set in current text fonts
% If you don't have a SuperFont, and have to create any of these as a
% composite, precede the name with a dot, as is done here for
% Scedilla and scedilla. The change in name keeps afm2tfm from thinking
% that the character already exists when it comes to evaluate the output
% (-t flag) encoding.
%
% 0x00
/Aogonek /Eogonek /Iogonek /Kafii9170 /Lafii9170 /Lcaron /Nafii9170 /Rafii9170
/Safii9170 /.Scedilla /Tafii9170 /Uogonek /.notdef /.notdef /.notdef /.notdef
% 0x10
/aogonek /eogonek /iogonek /kafii9170 /lafii9170 /lcaron /nafii9170 /rafii9170
/safii9170 /.scedilla /tafii9170 /uogonek /.notdef /.notdef /.notdef /.notdef
% 0x20 % Keep the space, for use as \boundarychar (Give it zero width in vpl)
/space /exclam /quotedbl /numbersign
/dollar /percent /ampersand /quoteright
/parenleft /parenright /asterisk /plus /comma /hyphen /period /slash
% 0x30
/zero /one /two /three /four /five /six /seven
/eight /nine /colon /semicolon /less /equal /greater /question
% 0x40
/at /A /B /C /D /E /F /G /H /I /J /K /L /M /N /O
% 0x50
/P /Q /R /S /T /U /V /W
/X /Y /Z /bracketleft /backslash /bracketright /asciicircum /underscore
% 0x60
/quoteleft /a /b /c /d /e /f /g /h /i /j /k /l /m /n /o
% 0x70
/p /q /r /s /t /u /v /w
/x /y /z /braceleft /bar /braceright /asciitilde /.notdef
%
% This is the Extension to Adobe Standard Encoding
%
% In as many of the next 32 positions as necessary, include
% all the unmapped simple (non-composite) characters. The
% inclusion of Ccedilla and ccedilla is problematic. These are
% composites in some schemes, simple in others. Best to
% assume they are simplex. Characters are entered in alphabetical order
% by name. If you need to create your own composite for Ccedilla
% ccedilla or Eth, precede the name with a dot as indicated above.
%
% 0x80
/Ccedilla /Eth /Thorn /brokenbar /ccedilla /copyright /degree /divide
/eth /logicalnot /minus /mu /multiply /onehalf /onequarter /onesuperior
% 0x90
/plusminus /registered /thorn /threequarters
/threesuperior /trademark /twosuperior /.notdef
/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
%
% From here on the order is again Adobe Standard Encoding
%
% 0xA0
/.notdef /exclamdown /cent /sterling /fraction /yen /florin /section
/currency /quotesingle /quotedblleft /guillemotleft
/guilsinglleft /guilsinglright /fi /fl
% 0xB0
/.notdef /endash /dagger /daggerdbl /periodcentered /.notdef /paragraph /bullet
/quotesinglbase /quotedblbase /quotedblright /guillemotright
/ellipsis /perthousand /.notdef /questiondown
% 0xC0
/.notdef /grave /acute /circumflex /tilde /macron /breve /dotaccent
/dieresis /.notdef /ring /cedilla /.notdef /hungarumlaut /ogonek /caron
% 0xD0
/emdash /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
% 0xE0
/.notdef /AE /.notdef /ordfeminine /.notdef /.notdef /.notdef /.notdef
/Lslash /Oslash /OE /ordmasculine /.notdef /.notdef /.notdef /.notdef
% 0xF0
/.notdef /ae /.notdef /.notdef /.notdef /dotlessi /.notdef /.notdef
/lslash /oslash /oe /germandbls /.notdef /.notdef /.notdef /.notdef
] def
|