Unicode Explained Unconfirmed Errata

Errata

Submit your own errata for this product.

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.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question

Version	Location	Description	Submitted By
Printed	Page 14 end of 2nd paragraph	currently it says: "image; as so many compromises, it combines" and it should likely say: "image; as with so many compromises, it combines".	Anonymous
Printed	Page 39 Table 1-2, WGL4 characters, "Classification" column, "Space characters" row;	space is mentioned as U+0040. Should that not be U+0020 instead, as U+0040 is the COMMERCIAL AT?	Anonymous
Printed	Page 47 2nd paragraph	The octet with value 33 in decimal is 00100001 in binary and not 00010001.	Anonymous
Printed	Page 297 Last line of 3rd paragraph from the bottom	The last sentence of the first paragraph of "Some Properties of UTF-16" is "Since it is not a low surrogate, we can know that the previous code point is erroneous data". However the previous code point (a high surrogate) could be correct and the code point in this position could have been corrupted from a low surrogate to a normal code point. It is still true that only one character will be corrupted.	Anonymous
Printed	Page 297 3rd paragraph	the convertion surrogates to utf-32 supplied: u=(h-d800)400+(L-dc00)10000 (all in hex) is incorrect. For example the surrogates pair supplied earlier in the page: d835 and dc05 will result in: u=(d835 - d800) * 400 + (dc05 - dc00) * 10000 u = 35 * 400 + 5 * 10000 u = d400 + 50000 u = 5d400 while the correct answer (written in the same page earlier) is 1d405 !	Anonymous
Printed	Page 302 5	The text suggests that if data is known or expected to be in UTF-32 encoding then the byte order mark should appear as 00 00 FE FF or 00 00 FF FE. To me this seems incorrect, as I would expect the value 00 00 FE FF taken as a 32 bit number would end up as FF FE 00 00 if the byte order was swapped.	Peter Friend
Printed	Page 304 Table 6-3	The row describing "UTF-16LE" contains "As UTF-8, but with Little Endian byte order fixed". I believe that this was intended to read "As UTF-16...".	Anonymous
Printed	Page 305 4th paragraph	There is an unmatched ")" after UTF-16. Either it should be removed or perhaps a matching "(" should be placed in front of the previous "as".	Anonymous