[mpeg-OTspec] MS Proposal for a new Name Table ID

[Ken Lunde]

Sorry, I now see that what the original proposal stated, but not explicitly, is the use of BCP 47 language tags. I am guessing that is what was meant by "IETF language tag."

-- Ken

On Jan 4, 2013, at 9:23 AM, Ken Lunde <lunde at adobe.com> wrote:

> Leonardo and others,
> 
> Another option to consider is the use of BCP 47 language tags, which are used for specifying language attributes in CFR objects (aka, ISO/IEC 14496-28:2012 or COmposite Font Representation). See:
> 
>  http://tools.ietf.org/html/bcp47
> 
> Regards...
> 
> -- Ken
> 
> On Jan 4, 2013, at 8:14 AM, Leonardo Chiariglione <leonardo at chiariglione.org> wrote:
> 
>> 
>> Michelle,
>> 
>> I assume that IETF language tag is ISO 639-1 (or is it ISO 639-2?).
>> 
>> As this is an ISO standard we should make reference to ISO standards
>> 
>> Leonardo
>> 
>> 
>> 
>> From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On Behalf Of Michelle Perham
>> Sent: Thursday, 03 January, 2013 18:33
>> To: opentype-migration-list at i! ndx.co.uk; OTspec (mpeg-OTspec at yahoogroups.com)
>> Cc: Dwayne Robinson
>> Subject: [mpeg-OTspec] MS Proposal for a new Name Table ID
>> 
>> 
>> 
>> 
>> 
>> As Vlad mentioned previously, the next MPEG meeting will be January 21-25 and he would like to have proposed changes finalized by January 11 to meet the deadline for document submission.
>> 
>> 
>> 
>> 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: O! penType fonts need a way to identify their intended language u! sage 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 su! btag. 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.”
>> 
>> 
>> 
>> Sorry to not get this out sooner! Like everyone else we’ve been very busy.
>> 
>> 
>> 
>> Happy new year!
>> 
>> 
>> 
>> Michelle
>> 
>> Microsoft Typography Group
>> 
>> 
>> 
>> 
>> 
>> 
>> <image002.jpg><image001.jpg>
> 
> 
> 
> ------------------------------------
> 
> Yahoo! Groups Links
> 
> 
>