XML in a Nutshell, 2nd Edition
by Elliotte Rusty Harold, W. Scott Means 

The following corrections were made to the 10/03 reprint of "XML in a Nutshell, 2nd Edition":

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



(12)  3rd paragraph;
Nonetheless, t is a well-formed XML document.

NOW READS:
Nonetheless, it is a well-formed XML document.


(17): In the first line of Example 2-5,
http://www.w3.org/1999/xlink/namespace/ 

NOW READS:
http://www.w3.org/1999/xlink



p. 39: The example declaration of the name element was missing a
closing right parenthesis.

NOW READS:
<!ELEMENT name ( last_name
                  | (first_name, ( (middle_name+, last_name) | (last_name?)))
                   ) >


{84}: In Example 5-4, the omicrons were swapped in the first text
line. The omicron should have come in the first syllable and the omicron
with tonos in the second syllable.

NOW READS:
&sigma;&omicron;&phi;&omicron_with_tonos;&final_sigma;



<85>: Language codes section, 2nd paragraph: The complete list of IANA language codes has moved from previous URL of
ftp://ftp.isi.edu/in-notes/iana/assignments/languages/tags

NOW READS:
ftp://ftp.isi.edu/in-notes/iana/assignments/languages/ 



p. 151:IN PRINT: At the end of the 2nd paragraph, the sentence 
"For example, suppose you wanted to write a name template that changed 
the input name elements to empty elements with first_name, middle_initial,
and last_name attributes like this:" 

NOW READS: 
"For example, suppose you wanted to write a name template that changed the 
input name elements to empty elements with first, initial, and last attributes
like this:"


(152)  last paragraph, before example 8-15;
The sentence previously read:
[...] but the name elements in example 8-13 aren't in no namespace.

NOW READS:
[...] but the name elements in example 8-14 aren't in no namespace.


Reported as pg. 154, actually on pg. 161, Sixth paragraph the sentence:
"The node() wildcard matches not only all
element types but also text nodes, processing instructions nodes,..."

NOW READS:
"The node() wildcard matches not only all element types but
also the root node, text nodes, processing instructions nodes, ..."..



p. 168: The select statement in the last code fragment incorrectly calculated the century.

Code fragment NOW READS:
<xsl:template match="person">
   <century>
     <xsl:value-of select="((@born - (@born mod 100)) div 100) + 1"/>th
   </century>
</xsl:template>



{199} The code fragment at the bottom of the page NOW READS:

xpointer(start-point(string-range(//title, "Wizard")))



(221) IN PRINT:  2nd paragraph;
The sentence: "If the text were traditional Chinese, then... the before 
on the lefthand side, and the after on the righthand side." 

NOW READS:
"If the text were traditional Chinese, then the start would be on top, 
the end on bottom, the before on the righthand side, and the after on the
lefthand side.


(288)  line 20;
Text-based processing can be preformed ...

NOW READS:
Text-based processing can be performed ...



p. 300: In Table 18-1, in the second column, third row,
"Unsigned  type"  

NOW READS:
"nodeType"


(341)  Table 20-1;
&apos; "

NOW READS:
&apos; '



P. 350: In in the table in the middle of the page, in the "ENTITY,
ENTITIES" row,  "separated by spaces"

NOW READS:
"separated by white space"


P. 424: In the heading for the floor function, "floor(3e)" 

NOW READS:
"floor()"


p. 518: In the second heading,  "The SAXExceptions Class" 

NOW READS:
"The SAXException Class"