Google Hacks
by Tara Calishain, Rael Dornfest

This errata page lists errors outstanding in the most recent printing.

If you have technical questions or error reports, you can send them to
booktech@oreilly.com.  Please specify the printing date of your copy.

This page was updated March 26, 2007.

Here's a key to the markup:
	[page-number]: serious technical mistake
	{page-number}: minor technical mistake
	<page-number>: important language/formatting problem
	(page-number): language change or minor formatting problem
	?page-number?: reader question or request for clarification



Confirmed errors:

(xi)  1st paragraph;
Last sentence, first paragraph.

Is
Who know that ...

S/B
Who knew that ...



(1)  5th paragraph (after "Google's index...";
"its all flowing too fast" 
should be 
"it's all flowing too fast."



(21)  Figure 1-4;
The text says "Search for the words (but not as a quote-enclosed phrase) hey diddle
diddle. Figure 1-4 shows the results."

But Figure 1-4 shows the results for the _quote-enclosed phrase_ "hey diddle diddle".


(23)  2nd paragraph, 4th line;
Where is says "drops dramatically to 3,490,000" 
it should say "drops dramatically to 3,470,000"
the number of results shown in Figure 1-8.


(58)  5th paragraph; 
In the 2nd line of the description of http://whatis.techtarget.com, 
"you're got a hardware-" 
should read 
"you've got a hardware".


(141)  3rd Paragraph;
where it says "looping through results, 10 at a time [Hack #1]."
it should say "looping through results, 10 at a time [Hack #51]."


{143 & 145}  In the code, within a doGoogleSearch() function call;
For ie and oe parameters of doGoogleSearch() function call, "latin1" is no longer a
valid value (as described earlier in this chapter).

"latin1" should be changed to "utf8".

AUTHOR: Indeed, every time ie or oe are set to "latin1", they should instead be
"utf8".

That said, the Google Web API ignores the encoding specification and forces
"utf8" so the there's no harm done by the current printing's use of
"latin1".


(163)  In the section entitled "Running the Hack";
The existing statement reads -
     % java -classpath .:googleapi.jar Googly "query words"

It's actually ; (semicolon) under win32

% java -classpath .;googleapi.jar Googly "query words"

and : (colon) under Unix and Mac OS X

% java -classpath .:googleapi.jar Googly "query words"