[OpenType] MS Proposal for a new Name Table ID

[Michelle Perham]

You are correct, Jonathan.

"more than one name table entry" should read "more than one tag in the name table entry."

Michelle

-----Original Message-----
From: listmaster at indx.co.uk [mailto:listmaster at indx.co.uk] On Behalf Of Jonathan Kew 
Sent: Thursday, January 3, 2013 10:20 AM
To: "multiple recipients of OpenType"@mail.indx.co.uk
Subject: Re: [OpenType] MS Proposal for a new Name Table ID

Message from OpenType list:


On 3/1/13 17:33, Michelle Perham wrote:

> Microsoft has several small changes we'd like to propose. I'll be 
> sending them out over the next 2 days. The first proposal is for an 
> addition to the 'name' table. The proposal comes from Dwayne Robinson, 
> who I've cc'd on this email. Please include him on your responses.
>
> Justification: OpenType fonts need a way to identify their intended 
> language usage so that scenarios like text editing can choose 
> appropriate fonts which switching language/IME. The inadequate legacy 
> codepage bits have been long exhausted, so I propose adding name table 
> id 23 containing an IETF language tag 
> (http://www.microsoft.com/typography/otspec/name.htm).
>
> The following description would be added to the documentation table.
> "Intended Language. This is the language the font was really designed 
> for, which is not necessarily the same as character coverage. This 
> allows distinction, for example, amongst Asian fonts as being 
> Traditional Chinese vs Simplified Chinese vs Japanese, even though the 
> fonts may have cmap coverage for a subset of each. All language 
> identifiers follow the IETF format with an optional language and 
> country and mandatory script subtag. These strings are encoded in 
> UTF-16BE using platform ID 0, encoding ID 3, and the respective 
> language id. Examples include "*-Jpan", "zh-Hans", "zh-Hant". If the 
> font genuinely targets and fully supports more than one language, it 
> will include more than one name table entry separated by commas."

I think there's a problem with this wording: Do you really mean that it will include "more than one name table entry", or (as I suspect) that the (single) name table entry will include multiple, comma-separated IETF language tags?

JK




List archive: http://www.indx.co.uk/biglistarchive/

subscribe: opentype-migration-sub at indx.co.uk
unsubscribe: opentype-migration-unsub at indx.co.uk
messages: opentype-migration-list at indx.co.uk