Errata

Fonts & Encodings

Errata for Fonts & Encodings

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page all
Throughout entire book

In all code listings, negative numbers are incomplete. Only the minus sign is present--values are
missing.

Anonymous   
Printed Page Appendix A
various: heading => header

Anonymous   
PDF Page n/a
n/a

No title or author information in the PDF eBook. The book just says "untitled" by "Unknown Author" on any eBook readers that have a library feature.

Anonymous  Mar 23, 2010 
Printed Page vi
Final bullet point

The thanks to Scott Horne, the translator, mentions that he translated the third stanza of Gaudeamus Igitur from Latin to archaic English for use in the dedication. However, the dedication on page v gives the Latin text. What happened to the English translation?

Kristofer Nelson  Apr 08, 2012 
Printed Page vi
Final bullet point

I have found the English translation of Gaudeamus Igitur. It is on the last line of the colophon on page 1017.

Kristofer Nelson  Apr 08, 2012 
Printed Page 12
5th paragraph

Dates seem wrong, says point unit invented in 1699, refined in 1664. Probably a typo for 1764 - I don't think Fournier was born yet in 1664.

Anonymous   
Printed Page 12
5th paragraph

dates seem wrong, says point unit invented in 1699, refined in 1664.

probably a typo for 1764, i don't think Fournier was born yet in 1664 ;-)

Anonymous  Jun 22, 2008 
Printed Page 18
Figure 0-6

B. TeX et [omega] fonts => B. TeX and [omega] fonts

Anonymous   
Printed Page 28
small paragraph between the CCITT code tables

Here "LF" is carriage return, ...

should be changed to

Here "CR" is carriage return, ...

Anonymous   
Printed Page 29
first para under ASCII

June 17, 1963 is a few months before the assassination of President Kennedy, not a few months after.

Probably delete the whole clause.

Anonymous  Sep 25, 2009 
Printed Page 31
2nd paragraph

JIS C-6220 => JIS C 6220

Anonymous   
Printed Page 32
line -5

with 2^12 = 4,096 bits => with 12 bits (2^12 = 4,096 patterns)

Anonymous   
PDF Page 34
Figure 1-2

the index of the cells in Figure 1-2 "seems" wrong:

the rows' index should be for the lower nib,
and the columns' index should be for the higher nib.

so,

for rows' index, they should read:
-0,
-1,
-2,
...
-F

for the columns' index, they should read:
0-, 1-, 2-, ..., f-


Anonymous  Oct 24, 2008 
Printed Page 36
line -6

'1a, '2o', etc. => '1a', '2o', etc.

Anonymous   
Printed Page 45
3rd paragraph

xE1 => 0xE1

Anonymous   
Printed Page 45
end of the 3rd paragraph

.. => ....

Anonymous   
Printed Page 47
last paragraph

xA1, xBC, F5 => 0xA1, 0xBC, 0xF5

Anonymous   
Printed Page 48
3rd paragraph

'a (0xBE) => 'a' (0xBE)

Anonymous   
Printed Page 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''

Anonymous   
Printed Page 51
3rd paragraph

"Transfer-coding: chunked" in the example HTTP header should be "Transfer-Encoding: chunked".

Kristofer Nelson  Mar 25, 2012 
Printed Page 51
2nd paragraph, last sentence

"The 'transfer coding' that we use is chunk"

chunk should be chunked.

Also, chunked allows blocks of varying length, with the length of each block being sent before the block. The wording "blocks of a fixed length" sounds like all blocks must be the same size.

Kristofer Nelson  Mar 25, 2012 
Printed Page 51
2nd paragraph, first sentence

"called content-coding whose values may be ..."

"content-coding" should be "content-encoding"

Kristofer Nelson  Mar 25, 2012 
Printed Page 59
footnote

'a' 'o' => 'a', 'o'

Anonymous   
Printed Page 62
last pargraph

for "CES") => (or "CES")

Anonymous   
Printed Page 67
2nd paragraph

(Quote from Window n, => (Quote from Window n),

Anonymous   
Printed Page 69
Figure 2-2

Allocated Codepoints => Allocated codepoints

Anonymous   
Printed Page 81
ideographic abbrevations

groups of 4 to 6 katakana => groups of 2 to 6 katakana
# 2 katakana: "kiro" (0x3314), "doru" (0x3326), etc.

Anonymous   
Printed Page 82
penultimate paragraph

"actually made of ** characters" -- should ** be something else?

Anonymous   
Printed Page 84
It looks like there's a figure 2.6 for Plane 14 which has been truncated

Anonymous   
Printed Page 84
bottom of page (Figure 2-6)

Figure 2-6 at the bottom of page 84 is complete (it ends at the jagged line below E2x); only its caption is missing. The missing caption is "Figure 2-6: The roadmap of Unicode's Supplementary Special-Purpose Plane (SSP): (1) language tags, (2) supplementary variation selectors."

Kristofer Nelson  Apr 06, 2012 
Printed Page 87
line -17

The code point range given as

0x1D400-0x0x1D7FF

should read

0x1D400-0x1D7FF

Anonymous   
Printed Page 89
Ol Chiki

These glyphs are not Ol Chiki but Cirth.

Anonymous   
Printed Page 90
Avestan

The 3d century CE => the 3rd century CE

Anonymous   
Printed Page 91
Samaritan

These glyphs are not Samaritan but South Arabian.

Anonymous   
Printed Page 96
last line

Latin- Supplement => Latin-1 supplement

Anonymous   
Printed Page 97
5th paragraph

Canadian_aboriginal => Canadian_Aboriginal
Old_italic => Old_Italic
Tai_le => Tai_Le
Linear_b => Linear_B

Anonymous   
Printed Page 98
Line -8

The Breton 'c'h' is a trigraph, not a digraph.

Kristofer Nelson  Apr 08, 2012 
Printed Page 100
Nl (number, letter), penultimate line

'sampi #5' should be sampi '#5'.

(#5 is the encoding for sampi in Beta code, which is used to represent Greek characters in ASCII.)

Kristofer Nelson  Apr 07, 2012 
Printed Page 101
Pi (punctuation, initial quote) and Pf (punctuation, final quote)

The quote characters in Pi are not quoted, whereas quote characters are quoted elsewhere (such as Pf below, the apostrophe on page 30, and the general punctuation block on pages 77-78).

Also, the double quote in Pf is hard to read because of the surrounding quotes. The apostrophe on page 77 and the double quotes on pate 78 have some space between the surrounding quotes that the double quote in Pf lacks.

Kristofer Nelson  Apr 08, 2012 
Printed Page 102
last paragraph

under Unix, it is NL; => under Unix, it is LF;
it is a pair of bytes, CR NL. => it is a pair of bytes, CR LF.

Anonymous   
Printed Page 106
3rd paragraph

<control->..<control-D> => <control-0009>..<control-000D>
<control-> => <control-0085>

Anonymous   
Printed Page 107
4th paragraph

"other, surrogate" characters => "other, surrogate" characters Cs

Anonymous   
Printed Page 107
Line 2

0x??FFE and 0x??FFF should be 0x??FFFE and 0x??FFFF.

Kristofer Nelson  Apr 08, 2012 
Printed Page 108
penultimate paragraph

0x1D400-0x0x1D7FF => 0x1D400-0x1D7F

Anonymous   
Printed Page 109
penultimate paragraph

the "hyphen" property => the "terminal punctuation" property

Anonymous   
Printed Page 113
3rd paragraph

03C3 => 0x03C3
03C2 => 0x03C2

Anonymous   
PDF Page 118
1st-3rd paragraph

The author's account of Unicode's 'Combining Grapheme Joiner' character (CGJ, or 'U+0x034F', as I like to call it) is flawed. He suggests that it can be used to combine characters (including base characters) together in such a way that a subsequent adjacent combining character will modify the cluster collectively; the author gives the example of combining '5' and '0' with CGJ to make the combining enclosing circle character produce &#12991; (U+32BF, for those of you with fonts by lazy foundries.)

But this isn't how the CGJ works, as anyone with a Unicode-capable text editor can verify instantly.

More damningly, the FAQ on unicode.org states the following, in direct contradiction to the author of this otherwise-excellent book:

--
Q: Is it possible to apply a diacritic or combining enclosing mark to a sequence of more than one (non-combining) character?

A: No... CGJ (U+034F COMBINING GRAPHEME JOINER) [will not] ?glue? characters together in a way that the scope of any following combining character would be affected.
---
http://unicode.org/faq/char_combmark.html#19

Elizabeth Marston  Sep 05, 2011 
Printed Page 120
errant formatting commands (setlength extrarowheight0dd) appear at the bottom of the page.

Anonymous   
Printed Page 123
8th line from bottom

<<thus we see that the canonical decomposition of ' '>>

the character is blank where it should be unicode character 0100 (A with macron)

Anonymous   
Printed Page 123
8th line from bottom

<<thus we see that the canonical decomposition of ' '>>

the character is blank where it should be unicode character 0100 (A with macron)

Anonymous  May 20, 2008 
Printed Page 131
Line -10

The last line of the second paragraph under Normalization Forms says to see page 4 in reference to the hangul syllables. However, page 4 does not mention hangul at all.

Kristofer Nelson  Apr 15, 2012 
Printed Page 146
Line -6

The final reversal of the third example has an extra E at the beginning (right side) of the string.

Kristofer Nelson  Apr 15, 2012 
Printed Page 157
Line -4

I_{h} and I_{v} should be V_{h} and V_{v}.

Kristofer Nelson  Apr 15, 2012 
Printed Page 169
first line (sample XML document)

book shows

encoding="UTF-"

but should be

encoding="UTF-8"

Anonymous   
Printed Page 169
start of bottom example: missing number from id attribute

Anonymous   
Printed Page 184
Line -6

"What is even more interesting is that recode refers to surface, which is roughly the equivalent of Unicode's serialization mechanisms (see page 62"

Page 62 does not mention Unicode?s serialization mechanisms. It seems that "serialization" means "transfer encoding syntax", which is in list item 5 on page 63. But the description of TES does not use the word "serialization"; it uses the word "transcriptions".

Kristofer Nelson  Apr 15, 2012 
Printed Page 184
Line -2

"quoted-printable (page 48)" should be "quoted-printable (page 49)".

Kristofer Nelson  Apr 15, 2012 
Printed Page 185
UCS-2LE: change 0x10ffff to 0xffff

Anonymous   
Printed Page 185
Lines 4 and 6

On line 4, "h1, x2, x4" should be "x1, x2, x4". h1 converts to HTML 1.1, not to hexadecimal.

On line 6, "o1, x2, x4" should be "o1, o2, o4", and "hexadecimal"should be "octal".

Kristofer Nelson  Apr 15, 2012 
Printed Page 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.

Anonymous   
Printed Page 190
1st full paragraph in list item # 1

"only a handful of Macintoshes" should be "only a handful of fonts"

Anonymous   
Printed Page 199
Table, second row, first column

"Optima gras" should be "Optima bold".

Kristofer Nelson  Apr 22, 2012 
Printed Page 207, 208
Screenshots near bottom of page 207 and top of page 208

In the images that begin "What is more readible," "readible" should be "readable".

Also, is the bottom line of the image on page 207 supposed to be antialiased? With the antialiasing its two lines look almost identical, but it seems like its bottom line should look the same as the bottom line in the image on page 208.

Kristofer Nelson  Apr 22, 2012 
Printed Page 211
Text describes two fonts as very similar to Linotype Palatino but the diagram shows 5.

Anonymous   
Printed Page 216
Figure 7-7

The description of Figure 7-7 in the text (pp. 215-6) does not match the image. The text states that the Multiple Master instance is bold 435, width 350, optical size 68, but the image shows italic 446, width 350, optical size 34. Figure 7-6 has the same settings as Figure 7-7.

Kristofer Nelson  Jun 06, 2012 
Printed Page 223
example font name: probably missing some numbers

Anonymous   
Printed Page 225
Item 3.

The XLFD font name in item 3, -b&h-lucidatypewriter-... has "n" in the spacing field. The description of spacing on page 224 (item 11) lists the valid values as "p", "m", and "c", as does X Logical Font Description Conventions [185, 3.1.2.10 on page 7]. Is "n" correct, or should this be "m"?

Kristofer Nelson  Jun 06, 2012 
Printed Page 227
examples missing numbers in font names

Anonymous   
Printed Page 229
examples missing numbers in font names

Anonymous   
Printed Page 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.

Anonymous   
Printed Page 231
example near bottom of page missing numbers in font name

Anonymous   
Printed Page 240
Footnote 3, line 2

The footnote mark at the end of the first sentence, after the word "lion", should be 4, not 5.

Kristofer Nelson  Jun 06, 2012 
Printed Page 244
first table

The fontseries entry for ultra-bold should be ``ub'' not ``ul''

Anonymous   
Printed Page 261-2
First and third lines of the DVX code on paeg 261, and line 7 of the text on page 262

In the DVX file, the font's internal number is 14, but in the text, it is described as having the internal number 18.

Kristofer Nelson  Jun 06, 2012 
Printed Page 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"/>

Anonymous   
Printed Page 278, 283
various

On p278, first paragraph: "We shall return to fontinst later in this book (page 518), when we discuss ways to adapt fonts to meet the user's needs." The page reference appears to be in error, as page 518 is actually the section on TrueType instructions.

Similarly, on p283, first paragraph: "Later (page 520) we shall see how to correct these small errors..." Again, page 520 contains nothing related to this topic.

And p283, second bullet point (2/3 down page): "This problem can be solved with an ad hoc configuration of fontinst; we shall see the procedure on page 520." Same issue.

Should these references instead be pointing towards the section on customizing TeX fonts which begins on page 285?

Alexander Taylor  Mar 28, 2015 
Printed Page 279
Last code snippet

last code snippet contains 3 incorrect font names
(TimesNewRoman___ instead of Centaur)

Anonymous  Mar 14, 2011 
Printed Page 298
Line -12

In the last line of the penultimate paragraph ("That solves the problem..."), there is a double quote after the first dal-parenthesis string. It should be a single quote.

Kristofer Nelson  Jun 06, 2012 
Printed Page 298
TeX code at bottom of page

Should there be a \setslot command after \setleftboundary{percent}? There is a seemingly unmatched \endsetslot command at the top of page 299.

Kristofer Nelson  Jun 06, 2012 
Printed Page 305
First two lines of TeX code

Is "oxxx" the proper name, or should it be "ohorn", "uni01a1", or something else?

Kristofer Nelson  Jun 06, 2012 
Printed Page 319
Line 7

The relative values for the size attribute should be between +1 and +6 or between -1 and -6. +7 and -7 would always put the absolute font size out of range.

Kristofer Nelson  Jun 06, 2012 
Printed Page 321
Line 8

Arial is not the same font as Helvetica. It would be better to say that Arial is similar to Helvetica.

Kristofer Nelson  Jun 06, 2012 
Printed Page 327-328
More missing numbers in the examples

Anonymous   
Printed Page 327
Example is Charcoal,Omega,Heisei but the penultimate paragraph implies order Omega,Charcoal,Heisei

Anonymous   
Printed Page 331
Example is missing various digits in the widths: line

Anonymous   
Printed Page 344
Footnote 14, line 6

There is an extra closing parenthesis.

Kristofer Nelson  Jun 06, 2012 
Printed Page 354, 355
Lines -6 and -4 on page 354, SVG example on page 355

The URLs in the SVG example do not match the URLs in the text.

Kristofer Nelson  Jun 10, 2012 
Printed Page 355
SVG example

In the altGlyphDef example, all the references to "glyphref" should be "glyphRef".

Kristofer Nelson  Jun 10, 2012 
Printed Page 356
Text implies missing-glyph is mandatory but the example at the end of the page omits it.

Anonymous   
Printed Page 356
5th paragraph

the sentence is written as:
font-face, which contairs the global informations
instead of <<contains>>, I suppose

Best Regards

Anonymous  May 20, 2008 
Printed Page 363
Glyph for Q on this page is unreadable.

Anonymous   
Printed Page 371
5th paragraph (not including type samples)

This paragraph introduces Frederic Goudy's Italian Old Style in a manner which implies that a sample of the typeface is shown. However, no sample of this typeface appears. Should there not be one?

Alexander Taylor  Mar 28, 2015 
Printed Page 372--374
throughout

"Stanley Morrison" should be "Stanley Morison" on all three pages. (On the other hand, it is written correctly on p402.)

Alexander Taylor  Mar 28, 2015 
Printed Page 378
Line 1

"Benner's" should probably be "Berner's".

Kristofer Nelson  Jun 16, 2012 
Printed Page 381
2nd paragraph

The comma in 'Thus it was he who designed the first garaldes, which Blanchard called "germanized Garamonds"' appears to be an error and should be removed.

i.e. 'Thus it was he who designed the first garaldes which Blanchard called "germanized Garamonds"...'

The inclusion of the comma causes the sentence to claim (a) that Kis designed the first garalde typefaces in general, which he clearly did not; and (b) that garaldes in general have been described as "germanized Garamonds", also false.

The intended meaning is evidently that Kis designed the first garaldes that could be described as germanized Garamonds. Deleting the comma will restore this meaning.

Alexander Taylor  Mar 28, 2015 
Printed Page 395
Line 2

"Dwiggings" should be "Dwiggins".

Kristofer Nelson  Jun 16, 2012 
Printed Page 426
2nd paragraph from bottom

c/d&#8804;00.97 or c/d&#8805;1.03
Should read: e/f&#8804;00.97 or e/f&#8805;1.03

Anonymous  Nov 30, 2010 
Printed Page 427
Exaggerated serif condition 3

"g/h > 0.19" should be "g/H > 0.19".

Kristofer Nelson  Jun 17, 2012 
Printed Page 428
Bullet point 6: medium

"75" should be "7.5".

Kristofer Nelson  Jun 18, 2012 
Printed Page 434
Line -3

"We say that the serifs are simple..." should be "We say that the serifs are single...". Panose does not use the word "simple" to describe serifs.

Kristofer Nelson  Jun 18, 2012 
Printed Page 446
1st paragraph

typo at the end of the paragraph: "..., and ofter poorly at that." -> often

Anonymous  May 17, 2011 
Printed Page 449
The example is 'MacOS Roman' but the text talks about 'MacRoman'

Anonymous   
Printed Page 482
1st Python example, 3rd line

should read:
g.Distance( -30, -30, 1 )

Anonymous  Nov 30, 2010 
Printed Page 482
2nd Python example, 4th line

should read:
g.Distance( -10, -10, 1 )

Anonymous  Nov 30, 2010 
PDF Page 482
1st line

`GetContourNumbers()' is a misprint for `GetContoursNumber()'

Anonymous  Jan 31, 2013 
Printed Page 567

Figure 14-4: "OpenType window". Should read: "Classes window"

Anonymous  Nov 30, 2010 
Printed Page 633
1st paragraph

There seems to be a reference problem, the text references section 9 twice. The text reads "We have already explained [...] in Sections 9 and 9."

Anonymous  May 17, 2011 
Printed Page 634
Bottom / entirety of B.4

It appears that much of the text in B.4, the section on OVF, was copied from B.2, the section on OFM, but not updated correctly. For example, they both start out with the the phrase "The OFM format was defined by John Plaice and the author..." even those B.4 is supposed to be explaining the OVF format not OFM as B.2 does. For example, the last sentence in each section is verbatim identical as well.

This is in the September 2007 printing.

Anonymous   
Printed Page 647

%!PS-Adobe-.0
should read:
%!PS-Adobe-3.0

Anonymous   
Printed Page 648
"(note: just one 't')" is not relevant in English, as 'atend' is obviously 'at-end' and not 'wait' (attend)

Anonymous   
Printed Page 652

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

Anonymous   
Printed Page 652
3rd paragraph

/FontBBox [- - 1006 747] def

should be

/FontBBox [-37 -249 1006 747] def

which I retrieved from the file cmr10.ps which can be found at https://ctan.org/texarchive/fonts/cm/ps-type3

Patrick Xarles Hayes  Mar 18, 2018 
Printed Page 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

Anonymous   
Printed Page 670
code example (rmoveto, rcurveto)

Anonymous   
Printed Page 672
code example (callothersubr)

Anonymous   
Printed Page 676

KPX F comma -
should be
KPX F comma -<number>

Anonymous   
Printed Page 679

/FontBBox {{- - - -} ...

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

Anonymous   
Printed Page 679
2nd paragraph

The book has

/FontBBox {{- - - -} {- - - - }
{- - - -} {- - - - }
{1052 1155 1291 1429} {693 816 1103 1183 }
{866 892 925 925} {798 850 854 871 }} def

which should probably be

/FontBBox {{-95 -108 -70 -91} {-67 -142 -87 -84 }
{-250 -250 -273 -273} {-250 -250 -278 -260 }
{1052 1155 1291 1429} {693 816 1103 1183 }
{866 892 925 925} {798 850 854 871 }} def

though the actual /FontBBox in Adobe Kepler MM is

/FontBBox{{-95 -108 -70 -91 -67 -142 -87 -84 }{-250 -250 -273 -273 -250 -250 -278 -260 }{1052 1155 1291 1429 693 816 1103 1183 }{866 892 925 925 798 850 854 871 }}def

which is a procedure of four procedures rather than eight....

Patrick Xarles Hayes  Mar 18, 2018 
Printed Page 680
code example (callsubr)

Anonymous   
Printed Page 690

/FontBbox [ - - 1023 900 ] def

Anonymous   
Printed Page 691

/BlueValues [ - 0 800 806 550 575 ] def

Anonymous   
Printed Page 698

<FontBBox value="- - 1195 940"/>

Anonymous   
Printed Page 699
code example (hhcurveto)

Anonymous   
Printed Page 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.

Anonymous   
Printed Page 716

<xMin value="-"/>
<yMin value="-"/>

Anonymous   
Printed Page 717

<descent value="-"/>

Anonymous   
Printed Page 726

<underlinePosition value="-"/>

Anonymous   
Printed Page 728

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

Anonymous   
Printed Page 729

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

Anonymous   
Printed Page 744

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

Anonymous   
Printed Page 744
example missing digits in the v attributes

Anonymous   
Printed Page 748

<record yMax="7" yMin="-" ...

Anonymous   
Printed Page 749

<descent value="-"/>

Anonymous   
Printed Page 751
end of D.9: D.11 is not the following section

Anonymous   
Printed Page 756, 757

<MinCoord value="-"/>

Anonymous   
Printed Page 786
4th paragraph, 2nd line

the Flemish 'ij'
should read: the Dutch 'ij'

Anonymous  Nov 30, 2010 
Printed, PDF Page 792
line 10

<Input index="1" value="e"> should be
<Input index="1" value="t">

Anonymous  May 09, 2012 
Printed Page 874
Last bullet point

In "growPriority et shrinkPriority", "et" should be "and".

Kristofer Nelson  Sep 27, 2013 
Printed Page 883
1st line

"that the first and second"
should read: ""second and third"

Anonymous  Nov 30, 2010 
Printed Page 883
1st list entry in section E.2.1

"et" should read "and"

Anonymous  Nov 30, 2010 
Printed Page 948

(948) 'special version TeX' => 'special version of TeX'

Anonymous   
Printed Page 972
[49], [50], and [51]

The URL for Inside Macintosh: More Macintosh Toolbox has changed to http://developer.apple.com/legacy/mac/library/documentation/mac/pdf/MoreMacintoshToolbox.pdf .

Kristofer Nelson  Apr 21, 2012 
Printed Page 977
[151]

2e edition should be 2nd edition.

Kristofer Nelson  Apr 06, 2012 
Printed Page 987
[336]

2e edition should be 2nd edition.

Kristofer Nelson  Apr 06, 2012 
Printed Page 987
[321]

2e edition should be 2nd edition

Kristofer Nelson  Apr 06, 2012 
Printed Page 987
[327]

The 'okina (the ' character) in Hawai'i is incorrect. It should look like a single opening quotation mark (U+2018 or &lsquo;) instead of a single closing quotation mark or apostrophe (U+2019 or &rsquo;). Technically it should be represented by U+02BB (modifier letter turned comma), but U+2018 is identical in appearance. In other words, the 'okina should be shaped like a 6, not like a 9.

(Some sources, including the Unicode character details, use the ` character to represent the 'okina (or `okina) in ASCII, but this is of arguable correctness.)

Kristofer Nelson  Apr 06, 2012 
Printed Page 988
[343]

3e edition should be 3rd edition.

Kristofer Nelson  Apr 06, 2012 
Printed Page 995
3rd column

The index entry for Icelandic eth is under D, not E.

Kristofer Nelson  Sep 27, 2013 
Printed Page 996, 1008
3rd column of page 996, 1st column of page 1008

The eszett is listed under "eszett", but not under "ss".

Kristofer Nelson  Jun 10, 2012 
Printed Page 997
2nd column

Several index entries beginning with "font-" are misplaced. They appear in the second column, between "font" and "FontAgent", instead of near to the rest of the "font-" entries in the third column. "Font/DA Mover" could similarly be moved between "fontconv" and "FONTDEV (DVI)"..

Kristofer Nelson  Jun 10, 2012 
Printed Page 997
3rd column

"@font-face (CSS)" is not in the index. It is mentioned on page 327 and 328.

Kristofer Nelson  Jun 10, 2012 
Printed Page 999
hyphen

The index entry for hyphen does not mention page 109.

It also makes no mention of the soft hyphen on page 36, either directly or by "see also soft hyphen".

Kristofer Nelson  Apr 08, 2012 
Printed Page 1005
3rd column

"J.F." is listed between "pound sign" and "pre-chain".

Kristofer Nelson  Jun 10, 2012 
Printed Page 1008
soft hyphen

The index entry for soft hyphen does not mention page 103.

Kristofer Nelson  Apr 08, 2012 
Printed Page 1014
Dwiggings, William Addison

"Dwiggings" should be "Dwiggins".

Kristofer Nelson  Jun 16, 2012 
Printed Page 1017
Colophon line 2

"[Omega] system" is incorrectly formatted. The ~ that should represent a non-breaking space in TeX is instead printed as an accent above the first s in system, and there is no space between [Omega] and system.

Kristofer Nelson  Apr 08, 2012