[mpeg-OTspec] Proposal: Specify UTF encoding of Unicode strings
Dave Pawson
dave.pawson at gmail.com
Thu Nov 24 07:13:30 CET 2011
On 24 November 2011 00:05, Sairus Patel <sppatel at adobe.com> wrote:
>
> === Proposal { my comments are in curly brackets }
>
> { In http://www.microsoft.com/typography/otspec/name.htm [OFF sec. 5.2.6]: }
>
> 1. { Insert the following sentence at the end of the paragraph "Unicode platform encoding ID 5 can be used for encodings in the 'cmap' table but not for strings in the 'name' table.": }
>
> Strings for all Unicode platform encoding IDs other than 5 must be encoded in UTF-16 (big endian).
>
> 2. { Insert the following paragraphs at the end of the "Windows platform-specific encoding IDs (platform ID= 3)" section: }
>
> Strings for Windows platform encoding ID 0 are considered to have Unicode semantics (UCS-2).
>
> Strings for Windows platform encoding IDs 0, 1, and 10 must be encoded in UTF-16 (big endian).
Disagree. Specifying the encoding is a pain when done this way and too
expensive.
Specify the encoding used, don't require a particular one.
Allow iso-8859 or utf-8, just let the reader know what it is.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
More information about the mpeg-otspec
mailing list