Part 4, Section 2.18.66 "decimalFullwidth", etc. - There are several mentions of double-byte and single-byte Arabic numbering schemes. Since the conformance clause for OOXML requires the use of Unicode in UTF8 or ITF16 encodings, there should be no mention of other encodings.

Reconcile the text and the conformance clause.

2.18.66

te

Proposed Disposition of DIS 29500 Comment IN-0044 (Modified: 2008-01-11) Agreed; these references were incorrect. They implied that these numbering schemes varied based on the underlying encoding, when they should have referred to half width and full width character forms, as defined by Unicode (see http://unicode.org/charts/PDF/UFF00.pdf for an example). The following changes will be made in Part 4, §2.18.66, page 1,773 within the enumeration value table: decimalFullWidth ( Double Byte Full Width Arabic Numerals) Specifies that the sequence shall consist of double- byte full-width Arabic numbering. [Example: , , . end example] decimalFullWidth2 ( Double Byte Full Width Arabic Numerals Alternate) Specifies that the sequence shall consist of an alternative set of full-width double-byte Arabic numbering, if one exists in the run font. [Example: , , . end example] decimalHalfWidth ( Single Byte Half Width Arabic Numerals) Specifies that the sequence shall consist of single- byte half-width Arabic numbering. [Example: 1, 2, 3. end example] Similar Comments: BR-0036 , CA-0033 , DE-0077 , GB-0283 , JP-0063 , PT-0072 , VE-0046