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.
| Version |
Location |
Description |
Submitted By |
| Printed |
Page 28
|
This is regarding creating an XHTML file. In the book it says: "1) Fire up your favorite text editor."
So, I am using Microsoft Works Word Processor, the version that comes with Windows XP, Security Pack 2.
I have typed in the XHTML code exactly the way it appears in the book, and I have saved it as an HTML file.
But when I open the file with my browser, it shows the code, exactly as I typed it into my text editor. I've tried with both Safari for Windows, and Firefox, both current versions of the browsers.
So I copied and pasted the code into Notepad. There's no way to save it as HTML, but according to the book that's ok. But when I open the notepad file with my browser, it's the same thing. It just shows the code exactly as I entered it.
So I took my file to Validome.com, as suggested in the book. The results were "Fatal Error: Could not validate this document, because it does not include a DOCTYPE Declaration." So I followed the link to the list of valid declarations, copied and pasted the declaration they have on their site for XMTML 1.0 strict, saved my file, tried with the browser again. Same thing, it shows the entire code. Took this new version, with the "correct" DOCTYPE declaration, and again, I got the Fatal Error that my document does not have the declaration.
Why? Please help!
|
Isabelle |
| Printed |
Page 28
in reply of Isabelles question |
I don't know if this has been clarified in the meantime. Isabelle writes:
"...and I have saved it as an HTML file."
Intuitively you would "Save as -> HTML" (in Word). - Don't do it!
Instead you have to save the file as a *plain text* file.
(Maybe you will have to give it the ".htm" or ".html" extension manually.)
|
Joergen W. Lang |
| Printed |
Page 51
Caption to Figure 2-15 |
The second sentence reads "First, the page is missing the mandatory <header> section." Shouldn't that be the "<head> section"?
|
James Welch |
| Printed |
Page 60
1st paragraph |
www.domaindirect.com does not exist anymore. It redirects to Hover.com. To check for a domain name in hover.com, you have to select Register a Domain Name and it will check for available names after you input your desired name.
|
Matthew Klein |
| Printed |
Page 65
last paragraph |
reads: As you learned on page 34...
should read: As you learned on page 64...
|
Anonymous |
| Printed |
Page 80
United States |
Greetings
I have really enjoyed the book but ran into serious problems trying to use ftp and Windows Explorer to upload my files. I called Sonic.net about the problem and they told me that it would not work and the error was Microsoft's in not providing the feature.
Is this true? I really expected the example in the manual to work!!!
Thanks,
Les
|
Leslie L Brabetz |
| Printed |
Page 87
6th paragraph |
The story you gave on Nvu's lifespan is wrong. The real one is actually quite confusing to me.
Nvu was discontinued, you got that correct. KompoZer is a separate application from another author. It was based off of Nvu's source code and is still updated. It's under the name KompoZer because the name Nvu was copyrighted. You can download Nvu at www.nvudev.com, or KompoZer (recommended) at www.kompozer.net.
|
Anonymous |
| PDF |
Page 105
Figure 4-15 |
(very small minor glitch)
The caption of figure 4-15 talks about the Lee Park website while the screenshot shows an earlier example (Popsicle workers) which resides in the same tutorial folder.
Therefore it might be a good idea to exchange this with a screenshot that shows one of the resume files (4 or 5).
On the other hand, who is Lee Park, anyway?
We only get to know him in chapter 5. ;)
|
Joergen W. Lang |
| PDF |
Page 105
figure 4-15 |
correction: We know Lee Park from ch. 2.
|
Joergen W. Lang |
| PDF |
Page 105
figure 4-15 |
(this refers to the description of the buttons in the "file" panel)
* the button saying "Disconnect" should actually read: "Connect/Disconnect"
* the button saying "Connect" should actually read: "Refresh"
|
Joergen W. Lang |
| PDF |
Page 106
the very last paragraph (Tip) |
(referring to clicking the "Synchronize" button)
The beginning reads:
"Once you’re comfortable with transferring small batches of files, you can try out the Synchronize button. It works like the Web site publishing feature in Expression Web."
From the description of the button's function this should actually be the "Refreh"-button. Thus the first sentence should read:
"Once you’re comfortable with transferring small batches of files, you can try out the Refresh button."
|
Joergen W. Lang |
| Printed |
Page 120
last paragraph at bottom of page |
The first sentence is missing the closing quotation marks, it currently reads:
Headings are section titles-for example, the word "Headings just above this para-
It should read:
Headings are section titles-for example, the word "Headings" just above this para-
|
Anonymous |
| Printed |
Page 131
Figure 5-13, both screen shots. |
In both screen shots, the third reference to "superscript" should read "subscript".
|
Peter McKie |
| Printed |
Page 131
Figure 5-13 |
In the second screen print, when you are describing Subscript, as in being handy for chemistry, it actually was typed out "Superscript" in the book as in "Superscript is handy for chemistry H20 (with the 2 being in subscript".
|
Katie Greene |
| Printed |
Page 131
Fig. 5-13 |
reads: Superscript is handy for chemistry...
should read: Subscript is handy for chemistry...
|
Anonymous |
| PDF |
Page 141
1st, 2nd and last code example |
(referring to PDF of 2nd ed.)
In the first two code examples on page 141 the mandatory semicolon at the end of a CSS-rule is missing.
h1 { color: blue } should read:
h1 { color: blue; }
selector { property: value } should read:
selector { property: value; }
h1, h2, h3 { color: blue } should read:
h1, h2, h3 { color: blue; }
|
Joergen W. Lang |
| PDF |
Page 141
same as above |
(referring to semicolon usage at the end of a CSS declaration)
Just to clarify the above erratum: Stritly speaking, semicolons are *not* mandatory at the end of the *last* declaration.
Still it is highly recommended (especially to beginners) to use them at any time.
|
Joergen W. Lang |
| PDF |
Page 142 ff.
3rd paragraph from bottom and following pages |
(referring to the section "Applying a Stlye Sheet")
Mentioned is the tutorial file for chapter 2 named 'resume.htm'.
This file does not contain any headings, only 'resume5.htm' does. Thus:
'resume.htm' should read:
'resume5.htm'
to make the style sheet example work.
|
Joergen W. Lang |
| PDF |
Page 143
list item 5, last sentence (in brackets) |
The last sentence of list item #5 reads:
"If you put these two files in different folders, you need to specify the location of the .css file using the file path notation system you’ll learn about on page 171."
On page 171 no information about file paths can be found.
|
Joergen W. Lang |
| PDF |
Page 148
code example on bottom of page |
(referring to the ul {...} rule)
The declaration
color: fuschia; should read:
color: fuchsia;
|
Joergen W. Lang |
| PDF |
Page 155
last paragraph |
In the last paragraph on the page it says:
"To select a font, you use the font-family attribute."
The usage of the word 'attribute' is misleading, since it is already introduced in various sections of the book as meaning 'XHTML attribute' (e.g. 'src' or 'href')
Therefore, this should read IMHO:
"To select a font, you use the font-family property."
|
Joergen W. Lang |
| PDF |
Page 159
section "Keyword sizing", 3rd paragraph |
The first sentence says:
"The standard font size for most browsers is 12points..."
In most modern browsers (IE7, FF3, Saf 3) the standard font size nowadays is 16 pt. Therefore the sentence should read:
"The standard font size for most browsers is 16 points..."
|
Joergen W. Lang |
| PDF |
Page 161
last paragraph, last sentence + following code example |
(referring to resizing fonts by multiple steps at once).
The text says:
"For example, a size of +2 is a relative size that increments a font two levels."
The CSS specifications (1 and 2.1) do not mention such a mechanism, although this has been possible in several versions of HTML (e.g.:<font="+2">).
Thus a declaration as in p. 162 top (font-size: +2;) will very likely be ignored by most browsers.
|
Joergen W. Lang |
| PDF |
Page 163
Table 6-3 entry 'padding' |
The description for the CSS property 'padding' says:
"Sets the spacing added around the inside of a block element."
This should read:
"Sets the spacing added around the inside of a block or inline element."
Explanation: The CSS 'padding' property is not limited to block elements but can also be used for inline elements. See: http://www.w3.org/TR/CSS21/box.html#padding-properties
|
Joergen W. Lang |
| PDF |
Page 177
last section (Style Sheet for Entire Site) |
[marked as 'minor' since it's not really a mistake, but maybe a major improvement]
(This section introduces a technique to define individual styles for different pages in one common style sheet. For this a matching class name (reume, trip, gallery) is appended to the name of the tag in question.)
The method described in this section has a serious drawback since it necessitates the usage of a multitude of class attributes within in the pages that should be styled individually.
A lot of clutter in the XHTML document (and even more tedious work) can be avoided if the method described in the section before (<div class="">) is applied to this example.
Instead of writing things like
<p class="resume">
<p class="trip">,
etc., over and over again, it just takes a simple <div> that surrounds the content, like so:
<body>
<div class="resume">
<p>...</p>
<li>...</li>
...
</div>
</body>
or even better: Just add the class attribute directly to the <body> tag:
<body class="resume">
<p>...</p>
<li>...</li>
...
</body>
All you have to do to make this work is to change the order of the two parts of the selector:
What was:
p.resume { ... }
becomes (note the space between '.resume' and 'p'):
resume .p { ... }
And presto! A lot unnecessary typing, possible mistakes, mainteneance trouble saved.
|
Joergen W. Lang |
| PDF |
Page 177
last section (Style Sheet for Entire Site) |
(referring to the alternate method of creating styles for a whole site)
In the above suggestion I wrote:
resume .p { ... }
This is wrong. Certainly the dot still has to be in front of the class name and *not* the type selector. The above should really be:
.resume p { ... }
Sorry for the confusion.
jwl
|
Joergen W. Lang |
| PDF |
Page 181
section "Alternate Text", 4th list item |
The text in the brackets says:
"(a program that “speaks” text, including the words in an alt tag). "
Although commonly referred to as "the alt tag", this should really be the alt *attribute*. Thus the text should actually read:
"(a program that “speaks” text, including the words in an alt attribute). "
|
Joergen W. Lang |
| PDF |
Page 193
paragraph above last code example |
The first sentence of this paragraph starts with:
"When you set the float attribute...."
This should probably be:
"When you set the float property...."
|
Joergen W. Lang |
| PDF |
Page 209
4th paragraph 1st sentence |
The first sentence says:
"A better way to create colorful links is to use another style sheet trick: pseudo-selectors."
These should really be pseudo-classes.
|
Joergen W. Lang |
| Printed |
Page 211
Box "Navigating and Frames" |
In the box they talk about clicking an external link, but the code example shows a relative (internal) link.
So the link should really be something like:
<a href="http://www.whateverwebsiteyoufavor.com/linked_page.html" target="_blank">Click me</a>
|
Some attentive reader |
| Printed |
Page 218
last paragraph, end of 2nd sentence |
at the end ot teh 2nd sentence the brackets read:
"(the cords attribute)" This should be
"(the coords attribute)"
|
Jimmy |
| Printed |
Page 221
last par. 2nd sent. |
The 2nd sentence:
What you do supply is the name attribute.
Use of the 'name' attrb. is deprecated. Attribute 'id' should be used instead. 'name' can be used for downward compatibility.
The above sentence shld. b:
What you do supply is the id attribute.
|
Johnny Mnemonic |
| Printed |
Page 225
Link Checkers/#3/para. 2/line 3 |
reads: ...you should updated it to point...
should read: ...you should update it to point...
|
Anonymous |
| Printed |
Page 237
1st paragraph |
In the first paragraph (just below the Tip) it says:
"There’s one hiccup to watch for when you create tables with borders. If the table includes empty cells, they’ll appear “collapsed,” which means they won’t get any borders at all "
This problem occurs only in versions of IE before IE8 RC1.
Tested also with recent versions of Opera, FF, Chrome, Safari (Mac).
|
Anonymous |
| PDF |
Page 243
1st paragraph of section "Sizing a row" |
The 2nd sentence reads:
"The best approach is to use the height property in the <tr> attribute..."
<tr> is either a tag or an element. So the above sentence should be:
"The best approach is to use the height property in the <tr> element..."
|
never never again |
| Printed |
Page 246
2nd code exmaple |
A font is specified for the whole document by using the following rule:
body {
font-family: Trebuchet MS, serif;
}
According to the CSS 2.1 specification (http://www.w3.org/TR/CSS21/fonts.html#font-family-prop) it is recommended to enclose font family names that contain white space (and other unusual characters) in single or double quotes. Thus the above rule would better be written as:
body {
font-family: "Trebuchet MS", serif;
}
|
Joergen W. Lang |
| Printed |
Page 263
Figure 10-1 |
The caption describes expedia.com, while the graphic shows expedia.ca.
|
Anonymous |
| Printed |
Page 264
markup in center of page |
Text in markup (Templates Rule!, etc.) not consistent with alternate markup on p.265, nor with fig. 10-2.
|
Anonymous |
| Printed |
Page 411
2nd Paragraph after "Modifying variables" |
The phrase "parentheses first, then addition and subtraction, then multiplication and division" should read "parentheses first, then multiplication and division, then addition and subtraction".
|
Scott A Thisse |
| Printed |
Page 415
Javascript at bottom of page |
The function being discussed is "ShowAlertBox()." The function written in the script shows merely "ShowAlert()."
|
Anonymous |
| Printed |
Page 416
4th and following paragraphs |
This is admittedly a bit pedantic, but _arguments_ are technically only the values sent into functions. The placeholders that received the values of those arguments are _parameters_. Even though this book is obviously geared toward novices, the difference should be stated, if for no other reason than to mitigate confusion when looking at descriptions of scripts available on the web. Perhaps this would be a great item for one of those wonderful sidebars.
|
Scott A Thisse |
| Printed |
Page 436
3rd Code snippet |
The electronic version of the code has a typo in the BMI formula; the second "/ 10" and a newline is missing.
instead of:
-----
resultElement.innerHTML = Math.round(pounds * 703 * 10 / totalInches / totalInches) / 10
}
-----
it has:
-----
resultElement.innerHTML = Math.round(pounds * 703 * 10 / totalInches / totalInches) }
-----
|
Scott A Thisse |
