L2/04-244 My comments #1-3 have been resolved in SC 2 N 3728. Comment #1 was resolved differently, but the proposal from Shoichi Senda (Japan) addressed my concern so was entirely acceptable. Comment #4 (making references from related registrations in accordance with ISO/IEC 2375 Clause 17.1.3) cannot be done until final approval and processing of the registration. -- Joan Aliprand, RLG US representative on RA-JAC ----- Forwarded by Joan Aliprand/RLG on 06/10/2004 12:41 PM ----- Dear Ms. Kimura: I have the following comments on Registration Application No. 234. (1)Discrepancy in hex codes used in Registration Application No. 234 and in the mapping table (a) The hex codes in the code chart and the character names list (range 02/00 through 07/14) in Registration Application No. 234 (distributed as ISO-IR 234.pdf) do not match those in the mapping table (range A0 through FE) (distributed as mapping234.txt). (b) The mapping table states "Column #1 is the ISO-IR 234 code (in hex as XX) Column #1 in the mapping table does not show the codes that appear in ISO-IR 234 (range 02/00 through 07/14). It shows the codes for ISO-IR 234 used as the G1 set. (That is, all values in Column #1 are incremented by hex 80 = 128 decimal). To resolve the discrepancy, I suggest that the definition of Column #1 be changed to: Column #1 is the ISO-IR 234 code as the G1 set (in hex as XX) This interpretation can be inferred from the fact that no G0 escape sequence is to be assigned, but it would be better to explain the difference explicitly. (2) Reference to a specific version of Unicode Standard Annex #9 versus the latest version UAX = abbreviation for "Unicode Standard Annex" The Notes for Implementers in the mapping table give this URL for UAX #9 http://www.unicode.org/reports/tr9/tr9-11.html This URL identifies a specific version of UAX #9 (the one dated 2003-04-17). The latest version of UAX #9 has this URL http://www.unicode.org/reports/tr9/ A Proposed Update for UAX #9 is publicly available (see http://www.unicode.org/reports/index.html). If this is progressed and eventually replaces the current version, the citation in the mapping table will point to an obsolete version. I am copying Mr. Fuchs so he can consult with SII colleagues about which URL should be cited. "About Technical Reports" (http://www.unicode.org/reports/about-reports.html) includes a discussion of versioning and how to cite versions. (3) Conflicting information on the cover sheet The Description states: Intended to be used with ISO/IEC 8859-8. But the Origin states: A superset of registered sets ISO-IR 138 and ISO-IR 198 ISO-IR 138 = Latin/Hebrew Alphabet Standard ECMA-121. This is the antecedent of the upper range of ISO/IEC 8859-8. ISO-IR 198 = Latin/Hebrew Alphabet. This registration was submitted by the SII. Its content is identical to the upper range of ISO/IEC 8859-8:1999. Since a GO escape sequence is not assigned, it can be assumed that ISO-IR 234 should be used with ISO/IEC 646 as the G0 set, thus creating a superset of ISO/IEC 8859-8. The sentence in the Description should be reworded. (4) Cross-references should be added to the subsets A reference to Registration 234 should be added to the cover sheets of Registrations 138 and 198. Suggested wording: ISO-IR 234 is a superset of this coded character set I deleted the attachments ISO-IR 234.pdf and mapping234.txt in the "history" to reduce the size of this message. Sincerely, -- Joan Aliprand, member of RA-JAC Joan Aliprand Senior Analyst, RLG 2029 Stierlin Court, Suite 100, Mountain View, CA 94043 Phone: +1 (650) 691-2258 Fax: +1 (650) 964-1461 RLG's Web Site: www.rlg.org