Menu
▾
▴
#71 Errors in TCG, 4th edition
Here are some minor errors in Docbook XSL TCG, fourth edition.
1. http://www.sagehill.net/docbookxsl/OnlineResources.html (page 5)
The address to the SF account registration page is https://sourceforge.net/account/registration/
(as of 2008-07-12).
2. http://www.sagehill.net/docbookxsl/ToolsSetup.html#Validation (page 14)
"For example, xsltproc includes a program called xmllint...".
This is not correct: xmllint is not part of xsltproc; it comes with the libxml2 library.
3. http://www.sagehill.net/docbookxsl/InstallingAProcessor.html (pages 24, 25, 26)
Replace "xalan25.jar" with "xalan27.jar".
4. http://www.sagehill.net/docbookxsl/SpecialChars.html#MissingChars (page 331)
"Most XSLT processors do not do full validation, but they do load the entities defined in the DTD."
http://www.sagehill.net/docbookxsl/ToolsSetup.html#Validation (page 13)
"Most XSL processors won't automatically take the time to validate your document while it is converting it to HTML or XSL-FO".
Both these sentences are a little misleading: the XML parser does the validation and loading of entities.
5. http://www.sagehill.net/docbookxsl/OtherOutputForms.html#XhtmlXsltproc (page 409)
"The head element includes an XHTML namespace declaration"
Wrong: it is the "html" element that has the namespace declaration.
Logged In: YES
user_id=193218
Originator: NO
Thanks for this feedback. I'll fix the book source and add them to the book's Errata sheet.
I'm not clear about what you mean by item 4, though. The XML parser used by xslt processors does not apply the DTD rules to the XML content. It will flag non-well-formed input, but it won't flag invalid input. Can you clarify what you mean?
Logged In: YES
user_id=582041
Originator: YES
Regarding item 4:
It's not a big deal, I just think that it may be a good idea to be clear about the separate responsibilites of XML parsers and XSLT processors. It is a bit misleading to say that "most XSLT processors do not do full validation", when they in fact don't do any validation at all.
Logged In: YES
user_id=582041
Originator: YES
Some additional comments on TCG, 4th edition.
6. http://www.sagehill.net/docbookxsl/WriteCatalog.html#ResolveDtdLoc (page 50)
The "Relative SYSTEM identifiers may not work" section should be updated with information on the systemSuffix element (http://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html#s.systemsuffix).
7. http://www.sagehill.net/docbookxsl/WriteCatalog.html#MapURLtoFile (page 51)
The <system> entry in Example 5.3 looks odd (and out of place). The attribute values are what you would expect on a <rewriteSystem> entry.
8. http://www.sagehill.net/docbookxsl/Imagemaps.html (pages 303-305) and
http://www.sagehill.net/docbookxsl/AnnotateListing.html#CalloutsGraphics (page 449)
Here, it should be mentioned that "mediaobjectco" has been removed in DocBook 5.0.
10. http://www.sagehill.net/docbookxsl/DraftMode.html (page 465)
"The pathname for the image file draft.png is contained in the draft.watermark.image parameter, which by default is set to a web address, so you might want to set it to a local file. Or you could use an XML catalog entry to redirect the parameter's URL value to a local file."
The last sentence is not correct. A catalog cannot be used to rewrite the draft.watermark.image location. A parameter value is just a string; it is not the type of resource identifier that can be resolved in a catalog.