<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.attach, li.attach, div.attach
{mso-style-name:attach;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:9.0pt;
font-family:"Arial","sans-serif";}
p.bold, li.bold, div.bold
{mso-style-name:bold;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial","sans-serif";
font-weight:bold;}
p.green, li.green, div.green
{mso-style-name:green;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#628C2A;}
p.replbq, li.replbq, div.replbq
{mso-style-name:replbq;
margin:3.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad, li.ad, div.ad
{mso-style-name:ad;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.underline, li.underline, div.underline
{mso-style-name:underline;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yshortcuts
{mso-style-name:yshortcuts;}
p.ad1, li.ad1, div.ad1
{mso-style-name:ad1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad2, li.ad2, div.ad2
{mso-style-name:ad2;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.underline1, li.underline1, div.underline1
{mso-style-name:underline1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
text-decoration:underline;}
span.yshortcuts1
{mso-style-name:yshortcuts1;
font-family:"Verdana","sans-serif";
font-weight:bold;}
span.yshortcuts2
{mso-style-name:yshortcuts2;
font-family:"Verdana","sans-serif";
font-weight:normal;}
span.EmailStyle34
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1622805009;
mso-list-template-ids:-602003322;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">IF a font supports only some characters used for a given language, then the font can hardly have been meant for use with that language. This should be used
to indicate languages that the font developer was intending to support. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Put another way, is the font a value-add for a user of language X? For instance, most Chinese fonts will support the characters needed for English, but often
they would not provide any additional benefit for English users (or may even be a decidedly bad choice for an English user). In this case, this entry should _<i>not</i>_ list English.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> mpeg-OTspec@yahoogroups.com [mailto:mpeg-OTspec@yahoogroups.com]
<b>On Behalf Of </b>Sairus Patel<br>
<b>Sent:</b> Thursday, January 03, 2013 12:00 PM<br>
<b>To:</b> opentype-migration-list@indx.co.uk; mpeg-OTspec@yahoogroups.com; Dwayne Robinson<br>
<b>Subject:</b> [mpeg-OTspec] RE: [OpenType] MS Proposal for a new Name Table ID<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div id="ygrp-mlmsg">
<div id="ygrp-msg">
<div id="ygrp-text">
<p style="margin-bottom:12.0pt">Dwayne, <br>
<br>
> the language the font was really designed for [...] If the font genuinely targets and fully supports
<br>
<br>
The notion of "fully supporting" a language is problematic, just as the notion of codepages bits (or Unicode block bits) was problematic. Fonts can and often do support only a subset of characters in a language. What if a font supports only one, or a few characters
in a language -- but those characters are central to the font's purpose, e.g. a digits-only font, or an A-Z only display font? I wouldn't want my text editor -- to use your example -- to filter out those fonts when I set my language to English.
<br>
<br>
> These strings are encoded in UTF-16BE using platform ID 0, encoding ID 3 ... <br>
<br>
The spec for a new name ID should be independent of particular platform and encoding IDs, since name IDs can be present in any of various platform/encoding combinations. If particular implementations support only particular platform/encoding combinations, that
should be recorded in the Recommendations section (e.g. "Windows version xxx supports name ID 23 strings only for platform ID 0, encoding ID 3"). I realize the 'name' spec doesn't currently do this, and there have been attempts at remedying this, but I feel
least additions to the spec should be cleanly done in this regard. <br>
<br>
Also, specifying the string's encoding as UTF-16BE belongs not to the spec for this name ID but rather to the spec for platform ID 0, encoding ID 3.
<br>
<br>
> ... and the respective language id. <br>
<br>
The platform ID 0 spec doesn’t define any language IDs (except for 0, which does not indicate any particular language).
<br>
<br>
If "the respective language id" means the same ID as the name ID string itself, then should we be assuming that this proposed name ID will be present only in format 1 'name' tables, e.g. the name ID 23 string is "zh-Hans" under {platform 0, encoding 3, and
language "zh-Hans"}? <br>
<br>
If so, then under which language ID should a comma-separated string of language IDs be registered?
<br>
<br>
Best, <br>
Sairus <br>
<br>
<br>
-----Original Message----- <br>
From: <a href="mailto:listmaster%40indx.co.uk">listmaster@indx.co.uk</a> [mailto:<a href="mailto:listmaster%40indx.co.uk">listmaster@indx.co.uk</a>] On Behalf Of Jonathan Kew
<br>
Sent: Thursday, January 03, 2013 10:20 AM <br>
To: <a href="mailto:%26quot%3Bmultiple+recipients+of+OpenType%26quot%3B%40mail.indx.co.uk">
multiple recipients of OpenType@mail.indx.co.uk</a> <br>
Subject: Re: [OpenType] MS Proposal for a new Name Table ID <br>
<br>
Message from OpenType list: <br>
<br>
<br>
On 3/1/13 17:33, Michelle Perham wrote: <br>
<br>
> Microsoft has several small changes we'd like to propose. I'll be <br>
> sending them out over the next 2 days. The first proposal is for an <br>
> addition to the 'name' table. The proposal comes from Dwayne Robinson, <br>
> who I've cc'd on this email. Please include him on your responses. <br>
> <br>
> Justification: OpenType fonts need a way to identify their intended <br>
> language usage so that scenarios like text editing can choose <br>
> appropriate fonts which switching language/IME. The inadequate legacy <br>
> codepage bits have been long exhausted, so I propose adding name table <br>
> id 23 containing an IETF language tag <br>
> (<a href="http://www.microsoft.com/typography/otspec/name.htm">http://www.microsoft.com/typography/otspec/name.htm</a>).
<br>
> <br>
> The following description would be added to the documentation table. <br>
> "Intended Language. This is the language the font was really designed <br>
> for, which is not necessarily the same as character coverage. This <br>
> allows distinction, for example, amongst Asian fonts as being <br>
> Traditional Chinese vs Simplified Chinese vs Japanese, even though the <br>
> fonts may have cmap coverage for a subset of each. All language <br>
> identifiers follow the IETF format with an optional language and <br>
> country and mandatory script subtag. These strings are encoded in <br>
> UTF-16BE using platform ID 0, encoding ID 3, and the respective <br>
> language id. Examples include "*-Jpan", "zh-Hans", "zh-Hant". If the <br>
> font genuinely targets and fully supports more than one language, it <br>
> will include more than one name table entry separated by commas." <br>
<br>
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?
<br>
<br>
JK <br>
<br>
<br>
<br>
<br>
List archive: <a href="http://www.indx.co.uk/biglistarchive/">http://www.indx.co.uk/biglistarchive/</a>
<br>
<br>
subscribe: <a href="mailto:opentype-migration-sub%40indx.co.uk">opentype-migration-sub@indx.co.uk</a>
<br>
unsubscribe: <a href="mailto:opentype-migration-unsub%40indx.co.uk">opentype-migration-unsub@indx.co.uk</a>
<br>
messages: <a href="mailto:opentype-migration-list%40indx.co.uk">opentype-migration-list@indx.co.uk</a>
<br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:white"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>