HTML Book To Be Updated (Again!)
It’s that time again… HTML: A Beginner’s Guide is now back on my plate to update. I love that Osborne/McGraw-Hill keeps this book current. Even though there isn’t a new version of HTML/XHTML, the new browser releases really require these types of books to be updated on a regular basis.
One new chapter to be included this time will cover HTML email (finally!). This is a chapter I’ve wanted to include for years, but for one reason or another it never got picked up. It’ll be a tough chapter to write, given all the less-than-stellar (i.e., crappy) email programs out there, but I’m just really excited to include it in the book.
So if you’ve read the current version and have comments/suggestions, bring ‘em on! 
kennis said,
September 9, 2008 @ 5:25 pm
I recently purchased your book for about $30 (Third Edition)from Barnes & Noble. It’s laid out very logically and the information is excellent and in an easy-to-understand format. I am learning from scratch and doing nicely, thank you!
However, I am very disappointed in the proofreading - there are too many typos, especially for a subject that depends absolutely on exact accuracy to function. For example:
p. 38 should be “É” not “é”
p. 39, top of the page “;” is a semicolon not a colon
p. 42 I believe the sentence “In the previous examples, a declaration was surrounded by curly quotes but inline declarations are enclosed in straight quotes” should read “In the previous examples, a declaration was surrounded by curly brackets but inline declarations are enclosed in straight quotes.”
p. 48 The answers to question #6 (B & D) do not match the answers listed for B & D on pp. 455 and 456.
Also on p. 48, for #9: the answers on p. 456 are all listed as “hr” rather than “br.”
I think this is far too many typos considering that I am just completing Module 2.
Thank you.
Kathleen Ennis
Naples, FL
Wendy said,
September 9, 2008 @ 5:34 pm
Kathleen - Thank you so much for your comments! This is the type of stuff I am working very hard to fix in the next edition. While these should have been caught during the editing process, I am taking extra measures to ensure these types of typos do not make it into this next manuscript. If you have time, I would love to receive any additional errors you find. And in the meantime, please don’t hesitate to let me know if you have any other questions about the material covered. I’m glad to hear you’re learning to code!!!
:-) Wendy