Fonts & Encodings
by Yannis Haralambous

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated February 11, 2008.


UNCONFIRMED  errors and comments from readers: 

[all] Throughout entire book;
In all code listings, negative numbers are incomplete. Only the minus sign is present--values are 
missing.


{28} small paragraph between the CCITT code tables;
Here "LF" is carriage return, ...

should be changed to

Here "CR" is carriage return, ...


[50-51] bottom and next page;
In the book on pages 50 and 51 there are several instances of ``iso--'' which should be ``iso-8859-1'' or 
(in one case) ``iso-8859-15''


(87) line -17 ;
The code point range given as

0x1D400-0x0x1D7FF

should read

0x1D400-0x1D7FF


(169) first line (sample XML document);
book shows

encoding="UTF-"

but should be

encoding="UTF-8"


(188) 5th paragraph, 5th sentence;
"it opens like any other file" should be "it opens like any other directory" because the behavior 
described is that of a directory (a.k.a. folder) in the Finder, not a file.


(190) 1st full paragraph in list item # 1;
"only a handful of Macintoshes" should be "only a handful of fonts"


{229-230} passim;
These two pages contain complex instructions on installing fonts under X-window. This information may 
well work and may once have been necessary, but it is obsolete on a modern Linux system and will probably 
frighten off potential Linux users for life! All that is needed is to place the new font in the same 
directory as the existing ones, or in /.fonts in a user's home directory, and the OS does the rest.


(244) first table;
The \fontseries entry for ultra-bold should be ``ub'' not ``ul''


{262} code example;
There seems to be general problem regarding code examples:
whenever a number follows a minus sign, the number disappers

<right dim="-"/>
should be:
<right dim="-19.657"/>


(647)
%!PS-Adobe-.0
should read:
%!PS-Adobe-3.0


(652)
/FontBBox [- - 1006 747] def
should be
/FounBBox [-<number> -<number> 1006 747] def


(667)
30 63 vstem 413 63 vstem - 50 hstem 634 50 hstem
should be:
30 63 vstem 413 63 vstem -9 50 hstem 634 50 hstem


(670) code example (rmoveto, rcurveto)


(672) code example (callothersubr)


(676)
KPX F comma -
should be
KPX F comma -<number>


(679)
/FontBBox {{- - - -} ...

/BlueValues[[ - - - - - - - - ]...


(680) code example (callsubr)


(690)
/FontBbox [ - - 1023 900 ] def


(691)
/BlueValues [ - 0 800 806 550 575 ] def


(698)
<FontBBox value="- - 1195 940"/>


(699) code example (hhcurveto)


{702} 2nd paragraph;
It appears that the hintmasks related to Figure C-17(a) reverse the vertical and horizontal hints. The 
first 3 bits are for horizontal stems, and the 2nd 3 bits are for vertical stems. Since the hint 
replacement is for the vertical hints, that means the 2nd set of 3 bits should be changed, not the first 
3. I calculate the masks to be 11111000 and 11110100.


(716)
<xMin value="-"/>
<yMin value="-"/>


(717)
<descent value="-"/>


(726)
<underlinePosition value="-"/>


(728)
<pt x="44" y="-" on="1"/>


(729)
<pt x="780" y="-" on="1"/>


(744)
<pair l="A" r="S" v="-"/>


(748)
<record yMax="7" yMin="-" ...


(749)
<descent value="-"/>


(756, 757)
<MinCoord value="-"/>