and elements ..." (73) 3rd from last line; calcuateArea should be calculateArea (73) Paragraph below 'Parameters' heading; "You can pass templates with..." should be "You can pass parameters with..." {74-75} p.74 - template, pp.74-75 - template; In both cases the opening and closing element names should be preceded with the "xsl" prefix. {77} Xalan; My version of xalan (1.0.1) needs single quotes around the parameter values as well, just like Oracle's. (Quick check of http://xml.apache.org tells me that newer versions do not require them though) {83} pseudocode example; The line of pseudocode that reads lastOfString = replaceString( ... ) should read lastOfString = replaceSubstring( ... ) {86} code immediately below 'Implementation' heading; For the xsl:param tag with name attribute "operator", the value for the 'select' attribute should read: select="'='" Otherwise, when running the example (for-loop.xsl) against an XML file with a single empty element, Xalan gives this error: ---begin error--- (Location of error unknown)XSLT Error (javax.xml.transform.TransformerConfigurationException): javax.xml.transform.TransformerException: java.lang.RuntimeException: Programmer's assertion in getNextStepPos: unknown stepType: -1 ---end error--- My environment: RedHat 7.1 Sun JDK 1.3.1_01 Xalan2 Java 2.2.D11 Note the same problem exists with the "operator" parameter for other examples on page 86 and page 87. {86} 1st paragraph (bulleted), second sentence; The second sentence which outlines the options for the operator variable says that not equal is "<> (coded as <>)". However, the following stylesheet listing (starting on page 87) uses "!=" for not equals. (87) bottom source sample; When using the sample "Chapter4\for-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: the third line should be (or at least, that did the trick for me): {104} 2nd code example; in 2nd code example on the page: .. .... @id is defined as an attribute of the child node "term" in the DTD preceeding, yet this Xpath refers to attribute of "glentry". one fix would be: .. ..... {120} 2nd paragraph from bottom; I think normalizeSpace() should read normalize-space(). (Also in the index.) {137} The last xsl fragment at the bottom of the page; The code now reads: It should read: In other words, the xpath specification should have only the first "/". [141] Code under section "A Brute-Force Approach"; The intermediate stylesheet sorts the address elements by last-name and first-name. The idea of the example however, is to sort the address elements by zip. It appears therefore, that the zip order and address order may still be out of step. The answer would be for the intermediate stylesheet to sort the address elements by zip (and then optionally also last-name and first-name). (146) complete stylesheet; The complete stylesheet on page 146 does not correspond to the example file, Chapter6/namegrouper3.xsl. {150} Code example, line 14; / missing from end of element (150) entire page; The stylesheet on pages 150-152 omits the ending slash in _most_ empty tags. For example: , should read: (154) paragraph under heading "Generating output to initialize a variable"; This paragraph refers to the variable runningTotal when it should, I think, refer to the variable orderTotal. (197) 2nd paragraph; The files Compare_es.java and Compare_es.class are missing from the examples files. (202) 4th paragraph; 2nd and 3rd sentences should be changed as follows: Original: --------- If this particular element has a required="true" attribute, the XML data contains . 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 , and the value of this element is an empty string, then the font is changed to bold and red. {examples} Chapter5/crossref4.xsl; The example does not use the 'targetLanguage' variable. The problem also shows itself in the generated HTML - dictionary4.html. {examples} Chapter5/crossref3.xsl; line 60 should be: Presently the line uses "name" rather than "href". [243] Under 'Optional Attributes' in the paragraph describing 'select'; This concerns the default behavior of the 'select' attribute. The last sentence reads, "Without this attribute, all element children of the current node are selected." The default is all child nodes, not just child elements. For example, a correct sentence would be, "Without this attribute, all child nodes of the current node are selected." The W3C specification reads, "In the absence of a select attribute, the xsl:apply-templates instruction processes all of the children of the current node, including text nodes." (http://www.w3.org/TR/ 9780596000530#section-Applying-Template-Rules) (298) example; I've been trying to use the info you give in your book "XSLT" (on pages 298 and 307) regarding and 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.... 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) href="gannt.css" type="text/css" {337} "Boolean Operators" Tidwell says that the operator "!=" "tests whether two expressions are not equal." This, it appears, is not strictly correct; or at least it should be made clear that "A != B" is not equivalent to "not(A = B) [338] 2nd paragraph; String comparisons Original : "For less-than and greater-than comparisons, the character codes are compared." This is incorrect. Both strings are converted to numbers (with the "number()" function) and then compared. Note : This correct rule is stated in the 4th paragraph on the same page. Implication : You can't compare strings characterwise unless you use a sorted, temporary node-set. Example : "A" >= "A" is actually false, as is "B" >= "A" as these are converted to NaN >= NaN, with is false by IEEE 754 [394] Bottom, flowing onto top of 395; I'd like to confirm the report for 394 in "Unconfirmed" -- the output is the result of running the stylesheet on itself (not on the XML example offered prior to the stylesheet listing). {394} last paragraph; I don't belive the output for the example for the name() function is correct. The example gives us an XML file and a XSL stylesheet but I don't think the output is from running the stylesheet on the XML file. I think the output that's printed is the output of running the stylesheet on the STYLESHEET. This is very confusing for someone trying to learn how to write and use stylesheets. [440] Bottom of the page; The description of output-escaping on page 440-1 is backwards. When 'disable-output- escaping="yes", the actual character will be written, not the escape value. The description of output-escaping on pages 319 and 321, which accompanies the and elements, is correct. The following is from the latest spec at www.w3.org: 16.4 Disabling Output Escaping Normally, the xml output method escapes & and < (and possibly other characters) when outputting text nodes. This ensures that the output is well-formed XML. However, it is sometimes convenient to be able to produce output that is almost, but not quite well-formed XML; for example, the output may include ill-formed sections which are intended to be transformed into well-formed XML by a subsequent non-XML aware process. For this reason, XSLT provides a mechanism for disabling output escaping. An xsl:value-of or xsl:text element may have a disable-output-escaping attribute; the allowed values are yes or no; the default is no; if the value is yes, then a text node generated by instantiating the xsl:value-of or xsl:text element should be output without any escaping. For example, < should generate the single character <. [440] last sentence in first question's answer; The statement "This element is replaced with..." should really be "This element generates..." This wording matches the wording of the answer to the next question on the same page, and also, the misleading use of the phrase "is replaced by" probably resulted from the over-use of cutting and pasting by the preparer of the text since this example is similar to the "replace-substring" example earlier in the book.

Glossary Listing: -

should be closed with

tag. The
element can be a child of the element or a element, but not the

Glossary Listing: -

should be closed with

tag. The element can be a child of the element or a element, but not the

tag. The
element can be a child of the element or a element, but not the