<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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
--></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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’ve taken a stab at updating the proposal for DR 09-0061 based on our call last week. I figure it will need some input, so I’ve attached it for review and
comments.<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">I have two questions in comments and I’d appreciate any suggestions on them. Otherwise, I kept it short since it’s not the place to get into all the historical
complications of Panose. The red faux tracked changes is Chris’ original write-up. The blue is my further changes.<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">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John<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""> John Haug [mailto:johnhaug@exchange.microsoft.com]
<br>
<b>Sent:</b> Thursday, March 22, 2012 12:08 PM<br>
<b>To:</b> SC34<br>
<b>Cc:</b> mpsuzuki@hiroshima-u.ac.jp<br>
<b>Subject:</b> RE: Status of DR 09-0061<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Here is a written form of what I talked through on the call today. It was a lot to digest, so hopefully this is helpful to anyone who missed part of the discussion.
As discussed today, I’ll look into Office’s use of PANOSE (e.g., “v1.0” vs. “v1.5”) and think more about Caroline’s suggestion to include both regexes. So far, I’m liking the idea, since it provides full info for a validation implementation to check any OOXML
file, regardless of how the producer understands PANOSE-1 numbers.<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="MsoPlainText">The meeting I mentioned was primarily between Vladimir from Monotype (SC 29 member) and Greg Hitchcock (Microsoft font expert) in a lengthy discussion around how to handle the messy history of PANOSE* with respect to ISO/IEC 14496-22
(Open Font Format, the ISO version of OpenType). SC 34/WG 2 had sent a liaison statement to SC 29 about changes they wanted to see to make PANOSE more usable for East Asian scripts which precipitated the meeting. Our WG 4 involvement via the fonts DR was
a separate issue, and dependent on what they decide.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Greg and Vladimir reached a delicate conclusion that PANOSE was never designed for extensibility and trying to make it workable for non-Latin fonts wasn’t feasible because the core character measurements represented by the PANOSE fields
are fundamentally Latin-oriented. Further, because of the messy history of PANOSE, PANOSE numbers in fonts are frequently not reliable and many apps do not rely heavily on PANOSE information anymore. They’re going to preserve the current behavior, remove
some restrictions about its use (which I think allows people to play unofficially with PANOSE fields, which sort of loosely satisfies WG 2) and make the reference from 14496-22 to the online PANOSE documentation (v”1.5”, see below) informative. For the WG
4 fonts DR, that means we ought to try to close the DR without action, since we’d be providing a restriction, albeit informative, based on something loosely defined in 14496-22 with an informative reference to the details.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">* PANOSE has been around for a long time, last owned by ElseWare, bought by HP in the mid-90s. Microsoft has documentation of PANOSE (call it “v1.0”) it uses for TrueType/OpenType. ElseWare made their own changes to PANOSE before
stopping work on it. These modified PANOSE docs (call it “v1.5”) are published online for reference, though not really owned or maintained, by Monotype. So, there are two different sets of PANOSE-1 documentation out there and people have coded to both, leaving
PANOSE numbers in fonts unreliable to apps.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Other WG 4 discussion reference: <a href="http://mailman.vse.cz/pipermail/sc34wg4/2012-January/002560.html">
http://mailman.vse.cz/pipermail/sc34wg4/2012-January/002560.html</a><o:p></o:p></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"><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"">
<a href="mailto:eb2mmrt@gmail.com">eb2mmrt@gmail.com</a> <a href="mailto:[mailto:eb2mmrt@gmail.com]">
[mailto:eb2mmrt@gmail.com]</a> <b>On Behalf Of </b>MURATA Makoto<br>
<b>Sent:</b> Saturday, February 04, 2012 1:05 AM<br>
<b>To:</b> SC34<br>
<b>Subject:</b> Fwd: Status of DR 09-0061<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Suzuki-san's document about DR 09-0061. Sorry for this belated input.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Makoto<o:p></o:p></p>
<div>
<h1>Status of DR 09-0061, clarification of ST_Panose<o:p></o:p></h1>
<p>2012-01-17<o:p></o:p></p>
<p>Source: suzuki toshiya, member of SC34/WG2, and the submitter of DR 09-0061<o:p></o:p></p>
<h2>1. Introduction<o:p></o:p></h2>
<p>DR 09-0061 was submitted by me in 2009, and it is now marked as closed, but its solution is not included in forthcoming Corrigendum. This document describes the current status of DR 09-0061.<o:p></o:p></p>
<h2>2. Activities to close DR 09-0061 from previous Prague meeting 2011<o:p></o:p></h2>
<p>The defect was difficult to close quickly, because existing specifications of OpenType (ISO/IEC 14496-22) refers genuine Panose at
<a href="http://www.panose.com" target="_blank">http://www.panose.com/</a>, but the text in the spec was incompatible with genuine Panose spec. Also other documents related with existing implementations have incompatible definitions. After the long investigation
by Chris Rae, it was commented that existing implementations had been designed to follow the genuine Panose.
<o:p></o:p></p>
<p>During SC34/WG4 meeting at Prague in April 2011, Chris Rae from Microsoft and I reached an agreement how to close the defect; adding an informative regex to validate the Panose values included in OOXML document. Considering the exist of the fonts violating
the Panose specified by Panose spec referred by ISO/IEC 14496-22 <a href="http://www.panose.com/" target="_blank">
http://www.panose.com/</a>, we decided that ISO/IEC 29500 should not include the normative text that classify them as invalid fonts. Also it was agreed that using existing reference ISO/IEC 14496-22 as the reference of Panose spec is better than adding yet-another
reference for Panose. I drafted the regular expression based on <a href="http://www.panose.com/" target="_blank">
http://www.panose.com/</a> spec, and Chris checked that it does not invalidates the fonts in existing implementations.<o:p></o:p></p>
<p>However, when I repored the inconsistency of genuine Panose spec and misleading text in ISO/IEC 14496-22 spec to SC29/WG11 (the group maintaining ISO/IEC 14496-22) and proposed to drop the misleading text in next version, the font experts in SC29/WG11 commented
that it is incompatible change and further investigation is needed. Their feedback to SC34 is filed as SC34 N1663. Thus I stopped pushing the regex draft to DCOR. Greg Hitchcock, a participant in SC29/WG11 from Microsoft commented that the existing implementation
follow to older revision of Panose spec which was different from current "genuine" spec at
<a href="http://www.panose.com/" target="_blank">http://www.panose.com/</a>. It makes difficult to determine appropriate document for the reference of Panose.
<o:p></o:p></p>
<h2>3. How to close DR 09-0061, and Schedule<o:p></o:p></h2>
<p>Although SC29/WG11 recognized there is a problem, but unfortunately they have not decided how to fix it. Anyway, considering that both of
<a href="http://www.panose.com/" target="_blank">http://www.panose.com/</a> and existing ISO/IEC 14496-22 is now known to be inappropriate reference for Panose, the solution should be the informative regex with the note that the regex is designed for the compatibility
with the existing implementations of OOXML. The updated draft of regex is sent to Greg Hitchcock.
<o:p></o:p></p>
<p>When SC34/WG4 holds a meeting in Prague, SC29/WG11 holds a meeting in San Jose. I asked whether SC29/WG11 can determine the schedule to update ISO/IEC 14496-22 spec to clarify their own Panose and waiting for their reply. However, if the regex for ST_Panose
is defined for the compatibility with the existing implementation of ISO/IEC 29500 (not of ISO/IEC 14496-22), it would not have serious impact against ISO/IEC 14496-22.
<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
<br>
Praying for the victims of the Japan Tohoku earthquake<br>
<br>
Makoto<o:p></o:p></p>
</div>
</body>
</html>