HTML Pocket Reference, 2nd Edition By Jennifer Niederst The unconfirmed error reports are from readers. They have not yet been approved or disproved by the author or editor and represent solely the opinion of the reader. Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification This page was updated March 13, 2003. UNCONFIRMED errors and comments from readers: [8] HTML Document; The HTML document does not validate with the strict DTD. If this book covers the strict DTD, it should give enough information that web developers don't have to use trial-and-error to get web pages to validate with it. [10] Client-Side Image Map example; In the usemap attribute of the tag, "map1" should be "#map1" (note the missing "#"). [11] Framed documents HTML code; The first framed document should have the tag inside the <frameset> tag. The second framed document is missing one </frameset> tag at the end. These errors cause these documents to be invalid HTML. (11) end of first code align end tag with start tag in line above [13] Examples; The examples are missing the frameset DTD. This is needed to create a valid frameset document. (14) last line; the description of the "rev" attribute states that it is the opposite of the rev attribute. should read "opposite of the rel attribute". {14} accesskey Shouldn't it be "Alt-character" and "Ctrl-character" in the last line (as in "accesskey=character")? (15) 1st paragraph; definition of rev=relationship states: "Specifies the relationship from the target back to the source (the opposite of the rev attribute)." The parenthetical remark should read "the opposite of the ren attribute". {18} object attribute; description Shouldn't "code" and "object" (each twice) be set in constant-width font (since they refer to attribute names)? {18} tag; The book does not give the specific syntax of the coords for each shape. Without this information, a reader cannot use this tag. {22-23} tag attributes; The alink, background, bgcolor, link, text, and vlink attributes of the tag should all be marked as deprecated. (29) 2nd-to-last line The semicolon should be a comma, since it indicates a list (of possible values). (43) beginning of iframe tag description; The iframe tag is fully described on pp 41-43. The iframe tag description begins again in the middle of page 43. The top of page 44 begins describing the next tag (ilayer), so the iframe tag description is only partially duplicated. A correction would strike out the bottom half of page 43. {44} tag; When the tag is added to the book, it would help greatly to have a table that shows which browsers support which formats. Which browsers support PNG, PNG with alpha transparency, MNG, JPEG2000, etc.? {45} Just below: input type=file; Many items in the book, including the one cited here, are missing the reference about whether or not the tag is supported for IE5. For example, the list on this item is MSIE 2,3,4,5.5,6 Other tags missing IE5 information are: button, fieldset, form, all input type= tags, isindex, label, legend, optgroup, option, script, select, textarea. The rest of the tags in the book list the full set of MSIE versions for compatibility: MSIE 2,3,4,5,5.5,6 (46) input type=hidden Header "Attributes" is missing. {58} tag attributes description; The description of the http-equiv and name attributes of the tag do not list the possible values for these attributes. Without this information, a reader cannot use this tag. {61} type attribute; The "media type" referred to in the type attribute is really the MIME type. A table of the common MIME types are corresponding file extensions would be helpful, as would examples of uses of the tag such as how to use it with a Java applet. (74-75,79-80) attribute descriptions; For TBODY, TD and TR tags, 'align' and 'valign' are NOT deprecated. For TBODY, 'background' should be marked "Nonstandard." TBODY attributes are missing "%core, %i18n, %events" (75) tag, attribute descriptions; 'hspace' and 'vspace' attributes should be marked "Nonstandard" {76 and 80} Internet Explorer only Shouldn't bordercolorlight and bordercolordark be exchanged (while their explanations shouldn't--as it is they describe the opposite respectively)? {82} last para before list - There is no "4.01" in the list, just "4.0" - nit-pick: "4.0" and "N" don't appear in the column "Description" (as in the 1st Edition) but in the new column "Version". #034; The symbol should be a straight (") quotation mark, not curled. #139; Description should be "Left single angle quote" and symbol should be changed accordingly. (In some fonts this might look similar as a less-than sign, but appearance and function of this sign is different. See also the symbols for #171 and #187.) (Same in ""Webdesign in a Nutshell", page 579.) #155; Description should be "Right single angle quote" and symbol should be changed accordingly. (Same in ""Webdesign in a Nutshell", page 579.) #222; Capital Thorn #240; Small eth The symbols (especially for Thorn) look different to how we know these characters (and how they appear when we test the entities in a HTML page). Maybe this is a bug in the Birka font? (Same in ""Webdesign in a Nutshell", page 580-581.) #8230; Name should read … {82} Character Entity Chart description; The description of the character entity chart should explain that the "normal alphanumeric character set" is the characters 0-127 and is the US-ASCII charset, the characters that are standard entities is the ISO-8859-1 charset, and the chart shows the windows-1252 charset. Additionally, it should explain that pages that do not use the US-ASCII or ISO-8859-1 charsets should explicitly state the charset so the browser will display the page properly. It would also help greatly to give a list of the other most common charsets, such as UTF-8, ISO-8859-15, EUC-JP, EUC-KR, Big5, etc. {84} Character Entities table; The following character entities are missing from the table: € Euro symbol Ž Capital Z, caron ž Small z, caron The following character entites are misnamed: ƒ Florin ‹ Left single angle quote ˜ Small tilde › Right single angle quote [87] entry for "p"; The glyph pictured for eth is close, but incorrect. A correct lowercase edh has to have a crossbar on the ascender, as shown in . (Otherwise it's the partial differential symbol!) {88} 1st paragraph; The latest IE version is 6, not 5.5. {88} 1st paragraph; The latest Netscape version is 7, not 6. (88-93) Extended HTML 4.01 Entities; The character entities 376, 919, 8207, and 8713 are missing semicolons. {91} Character Entities table; The left and right single angle quotes are listed as both nonstandard and part of the 4.0 standard. These characters are in the Unicode character set so are standard, as opposed to the angle quotes that are in windows-1252 but not ISO-8859-1 and so are non-standard. (91) Character Entities table; "Ellipses" should be "Ellipsis" [91] entry for "&hellep;"; correct "&hellep;" to "" (94) Character Entities table; The character entities sube, supe, rfloor, clubs, and diams are missing semicolons. (95) Dec to Hex Conversion Chart; The entry "155 = 9B" is in italics. [96] Color Name Chart; The list of color names is missing from this edition of the book. If this was a deliberate omission, at least the RGB syntax for colors (hex format, larger numbers are brighter), the web-safe colors (00, 33, 66, 99, CC, FF), and the standard 16 color names should be explained. Ideally, all the colors recognized by the newer browsers should be listed. Without this information, there is no explanation in the book for how to specify colors beyond the cryptic "#RRGGBB or color name".