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 |
|
index
symbols |
1. The index is missing a reference to the '$' symbol which is a serious impediment to a person new to XSLT trying to decipher real-world examples such as found in DocBook style sheets.
2. Similarly, an index reference to the '{}' symbols is missing.
These were also missing in the first edition (which I have), and, I assume, the second edition as well.
Nevertheless, from my brief look at the XSLT Reference pages, the third edition is much improved over the first edition.
|
Tom B. |
Jul 01, 2010 |
| Printed |
Page 9
Example 2-1 |
The content of MyApp.xaml is incorrect, as it specifies a NavigationWindow object, rather than an
Application object. (At the least, with the RTM version of the Windows SDK and .NET 3.0, this will not
compile.)
The correct content should be something like the following:
<Application xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
StartupUri="Page1.xaml"
/>
|
Anonymous |
|
| Printed |
Page 12
7th paragraph (project file example) |
The project file presented appears to be written so as to allow the compilation of the sample
application outlined on the preceding pages (i.e., "MyApp.xaml" and "Page1.xaml"). However, the
"TargetType" specification is a list of all possible target types, rather than being a single supported
type (e.g., "winexe"), and the "WindowsUIAutomation" reference inclusion appears not to exist in the RTM
Windows SDK/.NET 3.0.
A corrected version of this file (which works with the RTM Windows SDK) would be as follows:
<?xml version='1.0' encoding='utf-8'?>
<Project
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<AssemblyName>MyFirstApplication</AssemblyName>
<TargetType>winexe</TargetType>
<OutputPath>.</OutputPath>
</PropertyGroup>
<Import Project="$(MSBuildBinPath)Microsoft.CSharp.targets" />
<Import Project="$(MSBuildBinPath)Microsoft.WinFX.targets" />
<ItemGroup>
<ApplicationDefinition Include="MyApp.xaml" />
<Page Include="Page1.xaml" />
</ItemGroup>
<ItemGroup>
<Reference Include="System">
<Private>false</Private>
</Reference>
<Reference Include="System.Xml">
<Private>false</Private>
</Reference>
<Reference Include="System.Data">
<Private>false</Private>
</Reference>
<Reference Include="WindowsBase">
<Private>false</Private>
</Reference>
<Reference Include="PresentationCore">
<Private>false</Private>
</Reference>
<Reference Include="PresentationFramework">
<Private>false</Private>
</Reference>
<Reference Include="UIAutomationProvider">
<Private>false</Private>
</Reference>
</ItemGroup>
</Project>
|
Anonymous |
|
| Other Digital Version |
21
Note callout |
In the epub version (downloaded 25th April 2010), the callout describing the unusual case where the greater-than sign does need escaping, ends:
"Instead you have to write it as ]]>"
Which is obvious nonsense! The PDF version of the callout ends with the more expected:
"Instead you have to write it as ]]>."
|
chrisridd |
Apr 25, 2010 |
| Printed |
Page 257
top of page - example 16-2 |
Example 16-2
Uses the namespace qualifier xs: in the example, but does not define it. Instead the schema namespace is associated with the qualifier xsd.
|
Anonymous |
Feb 09, 2011 |
| Printed |
Page 469-470
self-evident |
I found some discrepancies betweend XSLT element lists in the following three books. Please advise. Note: Lists below shows differences between the books. If there are no notes next to the element, this implies that all three books categorizes the element the same way.
Three references:
XSLT Pocket Reference by Evan Lenz (O'Reilly); Pages 42-44
XML in a Nutshell, 3rd Edition by Elliotte Rusty harold & W. Scott Means (O'Reilly); Pages 469-470
XSLT Quickly by Bob DuCharme (Manning); Pages 260-267
== TOP LEVEL ELEMENTS ==
xsl:attirbute set
xsl:decimal-format
xsl:import (XSLT Quickly lists as "No Category")
xsl:include
xsl:key
xsl:namespace-alias
xsl:output
xsl:param
xsl:preserve-space
xsl:strip-space
xsl:template
xsl:variable
== Instructions ==
xsl:apply-imports
xsl:apply-templates
xsl:attribute
xsl:call-template
xsl:choose
xsl:copy
xsl:copy-of
xsl:document (XSLT 1.0 Pocket Reference and XML in a Nutshell does not list)
xsl:element
xsl:fallback
xsl:for-each
xsl:if
xsl:message
xsl:number
xsl:processing-instruction
xsl:text
xsl:value-of
xsl:variable
== Special Elements / No Category ==
xsl:otherwise (XML in a Nutshell lists as instruction element)
xsl:param (XSLT Quickly does not list, XML in a Nutshell does not list as an instruction)
xsl:sort (XML in a Nutshell lists as instruction element)
xsl:stylesheet (XML in a Nutshell lists as root element)
xsl:transform (XML in a Nutshell lists as root element)
xsl:when (XML in a Nutshell lists as instruction element)
xsl:with-param (XML in a Nutshell lists as instruction element)
|
Robert Liguori |
Jun 06, 2010 |