Errata

Learning XML

Errata for Learning XML

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 5
Example 1-2

&Invisibletimes; is deprecated by now,
and modern browsers won't render this example properly
(tested in Chrome and Internet Explorer)

 Stefanie Scherzinger  Aug 28, 2015 
Printed Page 22
HTML at bottom of page

The HTML generated by the XSLT script is missing the img element. It should be between the subj and blockquote lines.

 Lithis  Nov 12, 2011 
Printed Page 52
Figure 2-2

The XML declaration in Figure 2-2 is invalid. It should read ?<?xml version="1.0"encoding="utf8"?>?.

 Lithis  Nov 12, 2011 
Printed Page 53
Listing in Example 2-1

The entity declaration cannot be resolved by some tools (e.g. xmllint).

Instead of
<!ENTITY smile "<graphic file="smile.eps"/>">
(nested double quotes),
use single quotes for the nested quotes:
<!ENTITY smile "<graphic file='smile.eps'/>">

This should be fixed in the book as well as the sample code that comes with the book.

 Stefanie Scherzinger  Oct 08, 2015 
Printed Page 59
Last line

The thorn character is backwards. It should be ?.

 Lithis  Nov 17, 2011 
PDF Page 65
Figure 2-14

O'Reilly sent out an update notifying customers that this image had been fixed (it was blank), but in the updated file it is still blank.

 John Adams
John Adams
 		 Mar 06, 2011 
Printed Page 65
Figure 2-14 - A document tree

The figure is missing - only a blank box appears on the page.

 Dave Chisholm  Apr 04, 2011 
Printed Page 65
top half of page

The box for example 2-14 was blank. I downloaded the zip file with examples, but the folder for chapter 2 contained only 2_1 and 2_2, so I haven't got the content of this example (2-14. A document tree).

 Bas van der Mije  May 26, 2014 
Printed Page 67
Figure 2-17

There is no arrow from the character box to the numbered box.

 Lithis  Nov 12, 2011 
Printed Page 69
Last line

The typo on page 59 above, "The thorn character is backwards. It should be ?.", should have been on page 69.

(Also, extended characters such as thorn do not appear correctly on this web page. The thorn's bowl should point to the right like b and p, not to the left like d and q.)

 Lithis  Nov 20, 2011 
Printed Page 86
Figure 3-2

The letter 'n' is missing in the second inline element.

 Lithis  Nov 20, 2011 
Printed Page 128
Example 4-4

The comment "<!-- Inline elements -->" should be above the inline.group entity definition on page 129.

 Lithis  Dec 03, 2011 
Printed Page 134
Table 4-1, last line on the page

The second xs:IDREF should be xs:IDREFS.

 Lithis  Dec 03, 2011 
Printed Page 192
Last paragraph

If each size is 1.2 times larger than the previous one, xx-large would be 3 times larger than xx-small, not 3.6 times larger (though the current version of CSS2 no longer recommends a fixed ratio between sizes; see note 2 in section 15.7 of the CSS2 TR).

 Lithis  Dec 31, 2011 
Printed Page 199
entire page

The Examples downloads do not contain ANY of the CSS Stylesheets -- at least for Chapter 5. May I get these please?

Or, alternatively, please send the PDF file -- I have purchased the book, paying full retail at Powell's technical bookstore in Portland.

Thank you!

 Neil Bauman  Jun 15, 2009 
Printed Page 211
Table 6-3, Pattern .//para

The description of .//para says ?The double slash (//) is shorthand for /descendant-or-self::node()//.? However, section 2.5 of the XPath Recommendation says ?// is short for /descendant-or-self::node()/.? Note that the book has an extra slash at the end.

 Lithis  Jan 16, 2012 
Printed Page 212
Table 6-4

There's another reader comment that claims the match listed for id('q1')/parent::* is incorrect, but I think it's correct, based on testing a similar situation here: http://www.zvon.org:9001/saxon/cgi-bin/XLab/XML/extras.html.

However, I think the match listed for id('q2')/.. is incorrect. Again based on the site above, it seems the match should be the second quotation element, not the document element.

 Anonymous  Jun 12, 2008 
Printed Page 212
Table 6-4, Path id('q1')/parent::*

As far as I can tell, id('q1')/parent::* should match the document element, not the first quotation element. The next path, id('q2')/.., looks correct to me.

(If the book is correct, an explanation of why it is correct would clear matters up, as several people have expressed confusion as to which match, if either, is incorrect.)

 Lithis  Feb 10, 2012 
Printed Page 215
Table 6.7, Operator <=

There is an extra space before the <= in "expr <= expr".

 Lithis  Feb 10, 2012 
Printed Page 215
Table 6-9, Function name(node set)

The phrase "node set" in the Returns column should be italicized.

 Lithis  Feb 10, 2012 
Printed Page 215, 216
Table 6-9

In Table 6-9, "node set" is spelled without a hyphen. In Table 6-11, it is spelled with a hyphen. (Table 6-13 spells similar multi-word identifiers with a hyphen.)

 Lithis  Feb 10, 2012 
Printed Page 248
Second code block

The third line of the second code block, "<xsl:number count="chapter" format "1. ">, should be "<xsl:number count="chapter" format="1. "/>. The format attribute is missing an equals sign and the element is missing its closing slash.

 Lithis  Feb 11, 2012 
Printed Page 257
Example 7-5

The HTML is missing the head element. Example 7-4 includes an empty head tag between the html and body opening tags.

(Also, 31-6-00 is not a valid date.)

 Lithis  Feb 11, 2012 
Printed Page 274
1st paragraph

An em is not the width of a lowercase letter "m". The CSS chapter has the correct definition of an em on page 185.

 Lithis  Feb 11, 2012 
Printed Page 309
Figure 8-10

The table header is labeled "table-head". It should be labeled "table-header".

 Kristofer Nelson  Feb 17, 2012 
Printed Page 323
Second to last paragraph

The explanation of encoding pi into UTF-8 does not mention that the first zero of the binary representation is the third bit (the first zero) of the first byte of the encoded byte string. Note that there are 12 bits in the binary representation of 0x03C0 but only eleven x's in the relevant UTF-8 byte string in table 9-2. The explanation could be improved to explain this discrepancy.

Also, I have never seen a Unicode code point formatted like 0+x03C0. It should be U+03C0. Likewise, the hyphens in the UCS character numbers in Table 6-2 should be pluses.

 Kristofer Nelson  Feb 17, 2012 
Printed Page 329
Second code example

The "</if>" tag should be a "</xsl:when>" tag.

 Kristofer Nelson  Feb 17, 2012 
PDF Page 334
2nd full paragraph, 2nd-to-last line

"... used to built document trees...."

"built" should be "build".

 Kyle Dippery  Apr 08, 2009 
Printed Page 375
Last sentence of the XHTML Status

The URL for the working drafts of XHTML 2.0 is missing. It should be http://www.w3.org/TR/xhtml2/ .

 Kristofer Nelson  Mar 22, 2012 
Printed Page 381
DOM in both left and right columns

DOM appears twice in the glossary, and the first one is sorted as "document object model" instead of "DOM".

 Kristofer Nelson  Mar 22, 2012 
Printed Page 384
PCDATA

PCDATA is sorted incorrectly. It should be after parser, to be consistent with the other abbreviations in the glossary.

 Kristofer Nelson  Mar 22, 2012 
Printed Page 386
XHTML

Exntensible should be Extensible.

 Kristofer Nelson  Mar 22, 2012