02.07.2013 Views

A/UX® Programmer's Reference Sections

A/UX® Programmer's Reference Sections

A/UX® Programmer's Reference Sections

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

afm(4) afm(4)<br />

XHeight nwnber<br />

Ascender nwnber<br />

Descender nwnber<br />

Top of lowercase x.<br />

Top of lowercase d.<br />

Bottom of lowercase p.<br />

The individual character metrics are surrounded with the lines<br />

StartCharMetrics and EndCharMetrics and consist of a<br />

list of keys and values separated by semicolons. The characters<br />

are sorted (numeric ascending) by character code. Unencoded<br />

characters follow all of the encoded ones and are distinguished by<br />

having character code -1. Each character gets one line of description.<br />

Standard keys are:<br />

Cnwnber<br />

wx width-x<br />

w width-x width-y<br />

Nname<br />

B llx lIy urx ury<br />

decimal value of default POSTSCRIPT<br />

character code (-1 if unencoded).<br />

Character width in x (y is 0).<br />

Character width vector.<br />

PoSTSCRIPT character name.<br />

The character bounding box.<br />

L successor ligature A ligature sequence. The current character<br />

may join with the character<br />

named successor to form the character<br />

named ligature. Note that characters<br />

may have more than one such entry.<br />

Most western language fonts have wx entries rather than w ones.<br />

Note that keys are one letter for brevity. Here too, the set is extensible,<br />

with unknown entries ignored. (This leaves room for addition<br />

of new infonnation, for example.) A future revision of this<br />

format will have a specification for kerning information.<br />

FILES<br />

/usr/lib/ps/*. afm AFM files in the TRANSCRIPT distribution.<br />

SEE ALSO<br />

awk(1), sed(1).<br />

3 February, 1990<br />

RevisionC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!