Java Internationalization By Andrew Deitsch and David Czarnecki 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. This page was updated October 22, 2002 Here's the 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 UNCONFIRMED errors and suggestions from readers: [12] Last paragraph; The description of US and British conventions for the first day of week seems wrong to me. Having lived in both countries, I would have said the reverse was true - in Britain, the first day of the week is Sunday, but in the US it's Monday. British friends confirm this (though everybody feels it's a bit of a grey area). (28) Second line of 1st paragraph: The second Katakana character from the right should be printed a little smaller and moved to the bottom of the line (i.e. it is i.n.ta.ne.tto , not i.n.ta.ne.tu.to. (34) Table 2-15; The vowel name Dumma is wrong it is supposed to be Damma. 'a' instead of 'u'. Arabic is my native language. (43) Table 2-22, under the column labelled "Devanagari" ; The entries at postition 1 (first row) through 5 have been repeated again at rows 6 through 10. So, the consonant under the column "Sound" beginning row 6 aligns with entries under "Devnagari" starting at row 11. For the same reason, the last five "Devnagari" consonants have been pushed out of the bottom of the table (on Page 44). [43-44] Table 2.22, Column 2 (Devanagari) First five rows duplicated leading to an additional offset of 5 rows in column 2 and missing five entries at the end (on page 44). Also, one of the letters is completely missing corresponding to the sound 'jn' (a compound nasalized consonant formed by combining 8th and 10th entry in the table - there is a separate Devanagari character for it and is widely used). (46) Figure 2-4; "Figure 2-4. Thai text showing four separate levels" The normal position of Thai tonemark should be at level 3, not 4. Tonemark can be hanged at the level 4, only if there's an "above vowel" at the level 3. Please see page 5 of http://www.nectec.or.th/it-standards/thaistd.pdf in this doc, you can see "Figure 2 -- Thai 4-level writing system", a good example of Thai glyphs positioning. In the same page, see "Figure 3 -- Added glyphs for quality text representations". This has mentioned that Thai writing system has something that can be considered like a chapter 6's "Ligature". Note about Thai char encoding, ISO-8859-11 is not yet approved as an international standard. In this meanwhile, most of the text in Thailand is encoded in TIS620-2533 (Thai Industrial Standard for Character Encoding). (106) footnote; the correct url is http://www.norbyhus.dk/calendar.html there is already an errata on this error (advising to omit the space in the url), but even it is not fully correct. the correct url omits the hypen shown in the book (norby-hus). this is due to autohypenation at end of line. urls are not words subject to additio nal hyphenation. {119} 6th line from the bottom: Page 119 says: "Notice that the number format for both [Euro] entries with respect to decimal and grouping characters is the same ..." But Table 5.15 shows, that this is not the case. There I read: France 1 234,56 Euro (without a dot) Italy 1.234,56 Euro {120} Last code fragment on the page: The line should read "String formattedOutput = numberFormatter.format(1234.56);" ----------------------------^ (No capital letter N) [167] 7nd paragraph (including code); Since the byte array is encoded in sjis, shouldn't the nihongo_unicode string's encoding be either "UTF-16" or nothing instead of SJIS? nihongo_unicode = new String( nihongo_sjis ); or nihongo_unicode = new String( nihongo_sjis, "UTF-16"); [179] Table 7-2, Row "Katakana", Column "Half-Width": Your "half-width" Katakana-A (first symbol of the entry) looks to me like a "full-width" Katakana-A. At least I can't see a difference compared to the entry to the right. {269} Bottom: Method loadResources() catches MissingResourceExceptions, which can never occur. Method reloadResources() on page 274 is identical to loadResources. loadResources() could hence be reused. {270} In the middle of the upper half of the page (3 lines after "// Setup the fonts"): The application didn't work on my German Winnt 4.0 (Build 1381: Service Pack 5). After replacing the entry "Bitstream Cyberbit" by "Arial Unicode MS", it worked. (277) First code line in "Example 9-18. Simple_de.properties": The property Hello should read "Hallo Welt!" or maybe "Guten Tag, Welt!", but certainly not "Guten label Welt!". [285] 2nd paragraph under "Selecting Input Methods"; The text does not explain how to select an input method on Mac OS X.