Errata

This occurs throughout the book. For example, the following command:

java org.apache.xalan.9780596000530.Process -in greeting.xml -xsl fo-greeting.xsl
-out greeting.fo

which appears in section 2.5.2, if copied and pasted to a terminal window, will be executed as two lines,
producing unexpected results.

Such commands should be formatted with a continuation character (backslash) at the end of each continued
line. E.g.,

java org.apache.xalan.9780596000530.Process -in greeting.xml -xsl fo-greeting.xsl
-out greeting.fo

I recommend also mentioning this continuation character convention in the preface under "Conventions Used
in This Book".

Page http://www.oreilly.com/catalog/9780596000530/chapter/ch05.html:

<h1>
<xsl:text>Glossary Listing: </xsl:text>
<xsl:value-of select="glentry[1]/term"/>
<xsl:text> - </xsl:text>
<xsl:value-of select="glentry[last()]/term"/>
</h2>

<h1> should be closed with </h1>, not </h2>.

The DOMit servlet no longer works.

http://www.ibm.com/developerworks/features/xmlvalidatorform.html

When clicking on "Create the DOM tree button", gives "The page you requested cannot be displayed."

Typo:
"For more details on how to install and configure the XML tools to work with the
brower"

"brower" should be "browser"

Ik the last text paragraph on page 25 of XSLT, i found the following sentence (between brackets):
'If more than one element matches....'

This sentence is slightly misplaced, i believe. In the given example the 'greeting' element is the root
node of the xml document. But, as the document node can only have one child, as documented earlier in the
book. I think placing the bracketed sentence here would confuse readers. Giving the readers a warning that
in this example there can't be more than one 'greeting' element is better.

I believe that the last "z" in this text:

<?xml version="1.0"?>
<x>
<y>
<z/>
</y>
</z>

should be an "x":

<?xml version="1.0"?>
<x>
<y>
<z/>
</y>
</x>

"This template does nothing." Why tell me this? Does it just consume the comment() and processing-
instruction() items? Why not say so?

This is one example of several I could raise with respect to chapter 2. I have written HTML, XHTML, and
manuals for years. I came to the book with some familiarity with XML, both as a means of data
representation and as a mechanism for producing documents. What good does it do to tell me "this template
processes the root and any of its children" and then show me a match string of "*|/" without giving me a
clue what *|/ DOES/REPRESENTS?

I read this closely enough to note that the sequence of attributes in the radialGradient element was
changed. Even if you ARE going to keep giving us multi-line examples in which only a handful of characters
are actually the point of the example, but without somehow pointing them out (italics, bold, numbered
callout, ...) why not SAY that the sequence of the attributes was reversed because (perhaps?) it was
processed on a last-in-first-out basis -- and that of course the sequence does not matter?

It would seem that FOP project has made some changes that mean version 0.20.4 of FOP
requires subtle changes to the sytle sheet as presented in the book, and as in the
download, or the next stage, the creation of the PDF file, will fail.

I'm far from certain that this is a perfect fix, but:

Change: <fo:conditional-page-master-reference master-name="main" odd-or-even="any"/>
To: <fo:conditional-page-master-reference master-name="main" master-reference="main"
odd-or-even="any"/>

and
Change:<fo:page-sequence master-name="standard">
To: <fo:page-sequence master-reference="standard">

The Stylesheet is then:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format">

<xsl:output method="xml"/>

<xsl:template match="/">
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
<fo:layout-master-set>
<fo:simple-page-master margin-right="75pt" margin-left="75pt"
page-height="11in" page-width="8.5in"
margin-bottom="25pt" margin-top="25pt" master-name="main">
<fo:region-before extent="25pt"/>
<fo:region-body margin-top="50pt" margin-bottom="50pt"/>
<fo:region-after extent="25pt"/>
</fo:simple-page-master>
<fo:page-sequence-master master-name="standard">
<fo:repeatable-page-master-alternatives>
<fo:conditional-page-master-reference master-name="main" master-
reference="main" odd-or-even="any"/>
</fo:repeatable-page-master-alternatives>
</fo:page-sequence-master>
</fo:layout-master-set>

<fo:page-sequence master-reference="standard">
<fo:flow flow-name="xsl-region-body">
<xsl:apply-templates select="greeting"/>
</fo:flow>
</fo:page-sequence>
</fo:root>
</xsl:template>

<xsl:template match="greeting">
<fo:block line-height="76pt" font-size="72pt" text-align="center">
<xsl:value-of select="."/>
</fo:block>
</xsl:template>

</xsl:stylesheet>

is:
<xsl:apply-templates select="lines/line/">

should be:
<xsl:apply-templates select="lines/line"/>

is:
/sonnet/writers::*
should be:
/sonnet/writers:*

"As the XSLT processor cycles through all the <xsl:section> and <xsl:panel> elements ..." should read "...
all the <section> and <panel> elements ..."

calcuateArea

should be calculateArea

"You can pass templates with..." should be "You can pass parameters with..."

When using the sample "Chapter4for-loop.xsl" I got a parse error from my 9780596000530 engine
(msxml v4 sp1). The error was due to an error in the piece of code on page 87:

<xsl:param name="i" select="1"/>
<xsl:param name="increment" select="1"/>
<xsl:param name="operator" select="="/>
<xsl:param name="testValue" select="1"/>
<xsl:param name="iteration" select="1"/>

the third line should be (or at least, that did the trick for me):

<xsl:param name="operator" select="'='"/>

The complete stylesheet on page 146 does not correspond to the example file, Chapter6/namegrouper3.xsl.

The stylesheet on pages 150-152 omits the ending slash in _most_ empty tags. For
example:

<xsl:strip-space elements="*">,

should read:

<xsl:strip-space elements="*"/>

This paragraph refers to the variable runningTotal when it should, I think, refer to
the variable orderTotal.

The files Compare_es.java and Compare_es.class are missing from the examples files.

2nd and 3rd sentences should be changed as follows:

Original:
---------
If this particular element has a required="true" attribute, the XML data contains <requiredFieldsMissing/
>. The value of this element is an empty string, the font is changed to bold and red.

Corrected:
----------
If this particular element has a required="true" attribute, and the XML data contains
<requiredFieldsMissing/>, and the value of this element is an empty string, then the font is changed to
bold and red.

I've been trying to use the info you give in your book "XSLT"
(on pages 298 and 307) regarding <xsl:output> and <xsl:processing-instruction>
and each separately seems to work. I can either generate a DOCTYPE
in my xml output or I can generate a stylesheet reference in my output.
HOWEVER, when I try and do both, the DOCTYPE generated contains
"root-not-available" rather than the actual desired value of "svg".
Again, the "svg" comes out nicely if I dont also try to generate the stylesheet
reference (via xsl:processing-instruction).

So, how do *you* generate an xml document with a specified
DOCTYPE and that also references an external css stylesheet?

Here is an example of the "bad" output I get....
<?xml version='1.0' ?>
<!DOCTYPE root-not-available PUBLIC "-//W3C//DTD SVG 1.0//EN"
"http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
<?xml-stylesheet href="gannt.css" type="text/css"?>
<svg width="100%" height="100%">
</svg>

How do I generate this in XSLT just the same except that "root-not-available" says
"svg" ???

here is my XSLT...
(try separately commenting out the xsl:output and/or xsl:processing-instruction tags)

<?xml version='1.0'?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"
doctype-public="-//W3C//DTD SVG 1.0//EN"
doctype-system="http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd"
/>

<xsl:template match="/">
<xsl:processing-instruction name="xml-stylesheet">href="gannt.css"
type="text/css"</xsl:processing-instruction>
<svg width="100%" height="100%">
</svg>
</xsl:template>
</xsl:stylesheet>