General question about errata

MichielM · June 19th, 2009, 05:17 PM

Hello all, I purchased the book and followed the instructions to download the code. So far so good, yet:

when I click the errata link I just get an option to report a possible error, I do not see a list or errata posts anywhere. Does this mean no errata exist and/or have been found?

Greetings, M.

RickBlacker · June 19th, 2009, 06:48 PM

I noticed the same thing.

richard.york · June 19th, 2009, 07:07 PM

I found a couple of errors recently, which should be posted soon. Otherwise, I don't think any errata has been reported yet. Do you think you've found something?

RickBlacker · June 19th, 2009, 07:14 PM

not sure that I have, but did want to see if there were any updates. Having trouble with an example.

MichielM · June 20th, 2009, 01:08 PM

Quote:

Originally Posted by richard.york

I found a couple of errors recently, which should be posted soon. Otherwise, I don't think any errata has been reported yet. Do you think you've found something?

Hey hello Richard; no I haven't found anything. I just wanted to check if there were any and then noticed the absence of a list/posts...etc.

Thanks for your response,
Greetings, Michiel

richard.york · June 20th, 2009, 01:37 PM

The two things I found are as follows:

On page 72, the sentence "This will produce Figure 3-2 when run, although that figure is not actually shown here."... is ambiguous and should say something along these lines... "The preceding code results in the same output you saw in Figure 3-1. You'll find the preceding code in the source code download materials at www.wrox.com as Figure 3-2.html. Figure 3-2 isn't shown here because it is identical to Figure 3-1."

Also on page 72, the first sentence after the first block of code should be deleted, it is redundant.

So, not big show stopping things here, just a couple of editorial oversights. But things that should be changed none-the-less. Other than the problem I found with the source code download, which I brought up in another thread, nothing has been reported to me. If you find something, feel free to let me know here in this forum, through the errata submission form, or through my personal website. Even little things like grammatical errors.

Thanks!

MichielM · June 20th, 2009, 02:58 PM

Quote:

Originally Posted by richard.york

If you find something, feel free... ... Even little things like grammatical errors.

Hi again, well I did notice something... no biggie either- worth mentioning though:

Check:
Chapter one, page 5, section: installing jQuery
..second paragraph*, bookquote:

Quote:

jQuery would have this path from the document root, /Source Code/jquery/jquery.js.

Here's the point:
In the code examples of the book (and in the downloadable code) the final directory and the jquery.js file itself are both written with a capital Q.
As can be seen on page six [just giving the relevant code lines of Example 1-1.html here]

HTML Code:

.....<script type='text/javascript' 
            src='../../../Source Code/jQuery/jQuery.js'></script>

So there's two typo's on page 5 here; nothing alarming but I know how busy we can be trying to solve something while all the time the mistake was in the reference to an external file.
Just read about this thing happening so thought i'd post this.

Greetings, Michiel.

* in the first paragraph of this section the final dir. and file name are also written as : jquery/jquery.js

jminatel · June 22nd, 2009, 01:59 PM

I'll get Rich's 2 errata posted (he'd sent those to me earlier and when I saw that they weren't technical show-stoppers, I hadn't rushed).

Other than those, no, there are no confirmed technical errata. Rich has had a few reported that turned out to be user/reader error. That happens and it's why we wait for the author to confirm errata before we post.

Generally speaking, I only post the technical errata related to the books I've worked on. Other Wrox editors and their authors may handle it differently but I don't post spelling or grammar errors for example unless they impact technical issues (spelling errors in code are a code error) or really make something hard to understand. I think that helps readers find the most meaningful and useful errata without having to wade through spelling corrections that don't really help.

skr · August 4th, 2010, 10:09 AM

Although I find no reported technical errata (in fact no errata at all) for this book, I do believe I may have a candidate. The code on page 52, $('ul#tmpSlapstick li').slice(0, 4).addClass('tmpReallyFunny'); I believe should read .slice(0, 3) in order to coincide with Figure 2-13.

samjudson · August 4th, 2010, 10:18 AM

The slice() method, rather confusingly in my opinion takes two parameters, the second of which is the zero based index where the slice should end before - therefore I believe this code is actually correct.

http://api.jquery.com/slice/

p.s. and the reason there is no technical errata is because I technical edited it, and I'm just brilliant...! :)