<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=us-ascii">
<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:#1E66AE;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#1E66AE;
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","serif";}
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:335575693;
mso-list-template-ids:1958526898;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
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:\F0A7;
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:\F0A7;
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:\F0A7;
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:\F0A7;
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:\F0A7;
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:\F0A7;
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:\F0A7;
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-US" link="#1E66AE" vlink="#1E66AE">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We’ve had a bit more time to investigate this issue further. Considering the fact that the majority of the new implementations are based on Panose 1.5 – Microsoft
agrees with the proposal to remove Panose 1.0 values from OS/2 description and simply reference the 1.5 spec as is.
<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">Michelle<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 style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> mpeg-OTspec@yahoogroups.com [mailto:mpeg-OTspec@yahoogroups.com]
<b>On Behalf Of </b>suzuki toshiya<br>
<b>Sent:</b> Thursday, January 19, 2012 10:17 PM<br>
<b>To:</b> Greg Hitchcock<br>
<b>Cc:</b> David Lemon; Levantovsky, Vladimir; OTspec<br>
<b>Subject:</b> Re: Panose issue status? (Re: [mpeg-OTspec] AHG activity kick-off)<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">Dear Greg,<br>
<br>
Thank you for reply, with concrete option.<br>
I think your proposal is reasonable because the web page you<br>
gave would be one of the most referred one, and the impact<br>
to the existing implementation would be minimized.<br>
<br>
Maybe asking for the description about the measurement from<br>
non-LatinText typeface to the values designed for LatinText typeface<br>
would be slightly out of scope of ISO/IEC 14496-22 maintenance,<br>
but I have to point it out that there is a mismatch between<br>
<a href="http://panose.com/">http://panose.com/</a> versus Microsoft's OpenType spec, even if<br>
we restrict the scope to LatinText.<br>
<br>
In <a href="http://panose.com/">http://panose.com/</a> spec, the range of Stroke Variation byte<br>
is 0x00-0x0A. In Microsoft's OpenType spec, the range of<br>
bStrokeVariation is 0x00-0x08.<br>
<br>
The symbolic names of the decimal values are different as<br>
following:<br>
panose.com syntax: 0x00=any, 0x01=no_fit, 0x02=no_variation, 0x03=gradual_diagonal, ..., 0x09=instant_vertical, 0x0A=instant_horizontal<br>
Microsoft syntax: 0x00=any, 0x01=no_fit, 0x02=gradual_diagonal, ..., 0x08=instant_vertical<br>
<br>
There is something like off-by-one issue.<br>
<br>
Thus, I ask for the consideration to add a description about<br>
how the invalid values should be dealt.<br>
<br>
Regards,<br>
mpsuzuki<br>
<br>
Greg Hitchcock wrote:<br>
> From my point of view, I'd consider the "official" PANOSE specification for *OpenType* to be
<a href="http://www.microsoft.com/Typography/otspec/os2ver1.htm#pan">http://www.microsoft.com/Typography/otspec/os2ver1.htm#pan</a> . The documentation on
<a href="http://panose.com">http://panose.com</a> was *only* meant as a guide for how to calculate the values.<br>
> <br>
> The primary difference between this one and <a href="http://panose.com">http://panose.com</a> is the keying off of the family kind field in order to define the later PANOSE fields and the adjustments for Stroke Variation.<br>
> With the former, the fields in the OS/2 spec were always meant to be static. With the later, I've recently become aware of this and I'll try to see where the change crept in.<br>
> <br>
> Greg<br>
> <br>
> -----Original Message-----<br>
> From: suzuki toshiya [mailto:<a href="mailto:mpsuzuki%40hiroshima-u.ac.jp">mpsuzuki@hiroshima-u.ac.jp</a>]
<br>
> Sent: Sunday, January 15, 2012 11:53 PM<br>
> To: Greg Hitchcock; David Lemon<br>
> Cc: Levantovsky, Vladimir; OTspec<br>
> Subject: Panose issue status? (Re: [mpeg-OTspec] AHG activity kick-off)<br>
> <br>
> Dear Greg and David,<br>
> <br>
> If you got any investigation results on the difference between <a href="http://panose.com/">
http://panose.com/</a> versus the Panose assumed by existing implementation, could you post to the list?<br>
> <br>
> In my understanding; during the discussion about Panose spec clarification in July 2011, you had expressed the concern that the Panose data structure assumed by the existing implementations by Microsoft and Adobe might be different from the spec currently
published via <a href="http://panose.com/,">http://panose.com/,</a> so referring the latest official Panose as the normative part of the standard might introduce some incompatibility issues between the existing font processing system versus the standard 'conforming'<br>
> fonts. Also I'm interested in hearing the comments by other experts dealing with different existing implementations (e.g. Apple).<br>
> <br>
> Panose is used by several dejure or defacto standards (e.g. CSS, SVG, OOXML, etc), but the implmentation around OpenType would be the most respected one. If the latest official Panose at
<a href="http://panose.com">http://panose.com</a> is not appropriate spec for OpenType implementation to refer normatively, ISO/IEC 14496-22 is expected to define what should be referred.<br>
> <br>
> When SC29/WG11 is held in San Jose, SC34/WG4 (OOXML maintenance WG) is held in Prague, Checz. So as a member of SC34, I want to know what kind of inputs are prepared for next SC29/WG11 meeting.<br>
> <br>
> Regards,<br>
> suzuki toshiya, Hiroshima University, Japan member of SC34<br>
> <br>
> Levantovsky, Vladimir wrote (2011/12/22 0:59):<br>
>> Dear AHG members,<br>
>><br>
>> The next WG11 )MPEG) meeting will take place in early February (Feb. 6-10, 2-12) in San Jose, CA. The meeting notice can be found at:<br>
>> <a href="http://registrationassistant.com/meetingplanit/2012ISO/default.asp">http://registrationassistant.com/meetingplanit/2012ISO/default.asp</a><br>
>><br>
>> The AHG mandate for this period includes the following items:<br>
>><br>
>> 1. To study the text of the amendment ISO/IEC 14496-22/DAM2 "Open Font Format, Amendment 2: Additional script and language tags"<br>
>><br>
>> 2. To study the text of the ISO/IEC 14496-28/DIS "Composite font representation"<br>
>><br>
>> (Both 14496-22 and 14496-28 documents are currently under open ballots <br>
>> that will be closed in the end of January.)<br>
>><br>
>><br>
>> 3. To study the impact of the proposed changes to OS/2 'Panose' field on the existing implementations and to recommend a way the proposed changes can be implemented<br>
>><br>
>> As you remember, a proposal has been made to extend Panose settings to improve classification for non-Latin scripts. I would like to us to continue the discussion and come up with the recommendations for WG11 to proceed.<br>
>><br>
>><br>
>> 4. To conduct exploration activities on integrating SVG as new glyph description format in OFF in collaboration with the W3C<br>
>><br>
>> 5. To collect and evaluate the proposed changes and improvements to the OFF standard and produce a report with recommended work items for WG11<br>
>><br>
>> A new proposal to extend OFF/OpenType capabilities using SVG glyph descriptions to support multi-colored glyphs and animations had been made earlier this year and the discussions are now conducted in W3C Community group
<a href="http://www.w3.org/community/svgopentype/">http://www.w3.org/community/svgopentype/.</a> I would like to invite all interested parties to contribute to this discussion.<br>
>><br>
>> Over the last few months, a number of the proposed changes were <br>
>> submitted to the AHG email list with the intent to improve the clarity <br>
>> of the spec and to correct some wording and minor mistakes in the text <br>
>> of the standard. I would like us to finalize the list of changes we <br>
>> want to see implemented in the spec and produce a recommendation to <br>
>> MPEG on how to proceed. Since the second edition of the OFF standard <br>
>> was published (which is identical to OpenType ver. 1.6), we already <br>
>> had two amendments (including the current one) and one corrigendum. <br>
>> According to the ISO process document, the next set of changes would <br>
>> need to be implemented as a new edition of the standard, which makes <br>
>> sense considering not only the changes and clarifications in the <br>
>> current text but also a new addition of the SVG functionality in the <br>
>> future standard (subject to reaching a consensus among all group <br>
>> members). Therefore, I would like to suggest that we should plan our <br>
>> work as an exploration activity fo<br>
> r SVG glyphs and to collect and finalize the list of all changes that need to be implemented in the next edition of the standard.<br>
>> Thank you and happy holidays!<br>
>> Vladimir<br>
>><br>
>><br>
> <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>