The relationship between Part 4 s2.8.2.2 and other standards should be clarified. Furthermore, IS 29300 matches fonts based on their IANA name, as may be more suited for non-Open Font fonts, such as fonts on Linux. Some reviewers made general comments on the desirability of removing any platform dependencies. Even though Open Font is a standard and Open Type is available on all major platforms, there are some systems, such as Linux systems, where many fonts may use pre-Unicode conventions such as the name of the charset.

The mapping from values in IS 9541-4 or other standards should be clarified. If there is no specific mapping, then the definition of s2.8.2.2 should be broadened to also allow characters identified by any string: such as an IANA font name.

Part 4, s2.8.2.2 charset

te

Proposed Disposition of DIS 29500 Comment AU-0014 (Modified: 2008-01-03) Agreed; all of the values here require additional description. Although IS 14496-22:2007 defines each of the values used here, one of the comments also suggests that using the name of the corresponding IANA character set would be preferable for interoperability with other document interchange standards. Accordingly, the following changes will be made to improve the interoperability of all items in this list: In Part 4, §2.8.2.2, page 739, line 11: Value Description 0×00 Specifies the ANSI character set. (IANA name iso-8859-1) 0×01 Specifies the default character set. 0×02 Specifies the Symbol character set. This value specifies that the characters in the Unicode private use area (U+FF00 to U+FFFF) of the font should be used to display characters in the range U+0000 to U+00FF. 0×4D Specifies a Macintosh (Standard Roman) character set. (IANA name macintosh) 0×80 Specifies the JIS character set. (IANA name shift_jis) 0×81 Specifies the Hangul character set. (IANA name ks_c_5601-1987) 0×82 Specifies a Johab character set. (IANA name KS C-5601-1992) 0×86 Specifies the GB-2312 character set. (IANA name GBK) 0×88 Specifies the Chinese Big Five character set. (IANA name Big5) 0xA1 Specifies a Greek character set. (IANA name windows-1253) 0xA2 Specifies a Turkish character set. (IANA name iso-8859-9) 0xA3 Specifies a Vietnamese character set. (IANA name windows-1258) 0xB1 Specifies a Hebrew character set. (IANA name windows-1255) 0xB2 Specifies an Arabic character set. (IANA name windows-1256) 0xBA Specifies a Baltic character set. (IANA name windows-1257) 0xCC Specifies a Russian character set. (IANA name windows-1251) 0xDE Specifies a Thai character set. (IANA name windows-874) 0xEE Specifies an Eastern European character set. (IANA name windows- 1250) Value Description 0xFF Specifies an OEM character set not defined by this Office Open XML Standard. Any other value Application-defined, may be ignored. In Part 4, §2.8.2.2, page 740, attribute table: characterSet (IANA Name of Character Set) Name of the character set associated with the font. The values allowed by this attribute are defined by the names and aliases listed in the IANA registration table (IANA n.d.). If this value is specified, the value of the val attribute is ignored. The possible values for this attribute are defined by the XML Schema string datatype. To the normative references: IANA. CHARACTER SETS. http://www.iana.org/assignments/character-sets. Finally, the val attribute will be deprecated. Accordingly, we will remove it from its current location in the specification (Part 4, §2.8.2.2, page 740, attribute table), and place it into a new annex for deprecated features. Following the precedent set by other ISO standards (such as SQL’s ISO 9075:2003 Part 1 and C++’s ISO/IEC 14882:1998), we will make use of a new Annex that contains normative descriptions of all deprecated features. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features to preserve their fidelity, while noting that new documents should not use them. Accordingly, the Conformance clause will also be changed to state that newly created documents (those not created by migrating existing binary documents) should not use deprecated features. All deprecated features will be removed from their current locations in the standard, but will be fully defined in this new Annex. Similar Comments: CL-0141 , CO-0092 , DK-0113 , FR-0417 , GB-0209 , GR-0100 , IN-0072 , US-0170