<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 12 (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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Verdana;
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:Times;
panose-1:2 2 6 3 5 4 5 2 3 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.left
{mso-style-name:left;}
span.bld
{mso-style-name:bld;}
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.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;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad3, li.ad3, div.ad3
{mso-style-name:ad3;
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";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.replbq, li.replbq, div.replbq
{mso-style-name:replbq;
margin:3.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yshortcuts
{mso-style-name:yshortcuts;}
p.ad4, li.ad4, div.ad4
{mso-style-name:ad4;
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.ad5, li.ad5, div.ad5
{mso-style-name:ad5;
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.ad6, li.ad6, div.ad6
{mso-style-name:ad6;
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.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.EmailStyle36
{mso-style-type:personal-reply;
font-family:"Georgia","serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:460731741;
mso-list-template-ids:-361735382;}
@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;}
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=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif";
color:#1F497D'>All,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif";
color:#1F497D'>I’ve modified the proposal per 1 and 2 below.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif";
color:#1F497D'><a
href="http://groups.yahoo.com/group/mpeg-OTspec/files/lastResortFonts_AdobeProposal_v2.doc">http://groups.yahoo.com/group/mpeg-OTspec/files/lastResortFonts_AdobeProposal_v2.doc</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif";
color:#1F497D'>Sairus<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","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>Sairus Patel<br>
<b>Sent:</b> Thursday, April 09, 2009 11:03 AM<br>
<b>To:</b> Levantovsky, Vladimir; mpeg-OTspec@yahoogroups.com<br>
<b>Cc:</b> Michelle Perham (HILL); John H. Jenkins; Daniel Fenwick; Julio
Gonzalez; Simon Daniels; Sergey Malkin; John Hudson; Peter Constable; Peter
Lofting; Greg Hitchcock; Christopher Slye<br>
<b>Subject:</b> RE: [mpeg-OTspec] Proposal related to Last Resort fonts<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div id=ygrp-mlmsg>
<div id=ygrp-msg>
<div id=ygrp-text>
<p class=MsoNormal><br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>Vladimir,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>1. The
intention of head.flags bit 14 being set to 0 is that this is not a last resort
font (and we can append this to the proposed spec for bit 14 to clarify things):</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>“If unset,
indicates that all glyphs encoded in the cmap subtables represent support for
those code points.”</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>Since this
is a font-wide flag defined in the above way, we aren’t allowing for fonts that
mix standard support and last-resort support (if we did, we’ve have to account
for how conflict resolution is done, i.e. if there exists a standard mapping
and a last resort mapping for the same code point, and this functional area is
not worth this complication).</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>2.
Actually, Unicode platform encoding IDs 3 and up (including encoding ID 6) are
all “Unicode 2.0 and onwards semantics” – we’ve just stopped saying that
explicitly since Unicode has guaranteed a while back not to change code point
assignments. What differentiates encoding ID 6 from encoding ID 4 is not the
version of Unicode supported but the list of cmap subtables that are allowed to
be used.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>So the
parenthetical references to the OT spec versions are in fact references to
particular lists of cmap subtable formats. We can make this explicit, if you’d
rather not have OT spec version numbers in OFF (I’ve also clarified encoding ID
5 for completeness here):</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Times","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;font-family:"Courier New";color:#1F497D'>encodingID
Description</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;font-family:"Courier New";color:#1F497D'>----------
-----------------------</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;font-family:"Courier New";color:#1F497D'>3
Unicode 2.0 and onwards semantics, Unicode BMP only (cmap subtable formats 0,
4, 6)</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;font-family:"Courier New";color:#1F497D'>4
Unicode 2.0 and onwards semantics, Unicode full repertoire (cmap subtable
formats 0, 4, 6, 10, 12)</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;font-family:"Courier New";color:#1F497D'>5
Unicode Variation Sequences(cmap subtable format 14)</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;font-family:"Courier New";color:#1F497D'>6
Unicode full repertoire (cmap subtable formats 0, 4, 6, 10, 12, 13)</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;font-family:"Courier New";color:#1F497D'>----------
-----------------------</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>This makes
the Descriptions in the table a bit longer, but they’re very explicit (which is
good) and don’t refer to specific versions of OT (which I’m hearing you say is
good for OFF). The paragraph describing them can be modified suitably. I think
this should address your concerns. I can write up a revised proposal if there
is agreement around this.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>Note that
the parenthetical additions to the Descriptions for encoding IDs 3-5 above are
not new specifications, they’re just put all in one place; they currently exist
in different parts of the spec.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>And thanks
for correcting the URL; I changed the name of the file at the last moment and
forgot to update the link.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>Sairus</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'>[BTW, my
messages to this list composed in Outlook 2007 sometimes seem to appear with
multiple blank lines inserted when I receive the message from the list… let me
know if there’s a way in which I can address this.]</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif";color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:0in 0in 0in 0in'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'>
Levantovsky, Vladimir [mailto:Vladimir.Levantovsky@MonotypeImaging.com] <br>
<b>Sent:</b> Thursday, April 09, 2009 9:27 AM<br>
<b>To:</b> Sairus Patel; mpeg-OTspec@yahoogroups.com<br>
<b>Cc:</b> Michelle Perham (HILL); John H. Jenkins; Daniel Fenwick; Julio
Gonzalez; Simon Daniels; Sergey Malkin; John Hudson; Peter Constable; Peter
Lofting; Greg Hitchcock; Christopher Slye<br>
<b>Subject:</b> RE: [mpeg-OTspec] Proposal related to Last Resort fonts<br>
<b>Importance:</b> High</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>Thank you Sairus for presenting your
proposal.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>All, please notice that the corrected link
to the uploaded file is </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'><a
href="http://groups.yahoo.com/group/mpeg-OTspec/files/lastResortFonts_AdobeProposal.doc"><span
lang=EN>http://groups.yahoo.com/group/mpeg-OTspec/files/lastResortFonts_AdobeProposal.doc</span></a>
</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>I would urge all AHG members to review the
proposal from Adobe and provide your feedback and any objections to it no later
than Monday, April 13th. The deadline for input contribution to the WG11
meeting is April 14th.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>The proposal addresses important subject of
backward compatibility with the existing font engines, and helps insure that
processing of fonts implementing newly introduced functionality (cmap format
13) will not affect existing rasterizers.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>Sairus, I have some questions and comments
regarding your proposal:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>1) My understanding is that by introducing
the new encoding ID = 6 we will provide a clear indication that a font may be
developed using new cmap format 13, in addition to any other cmap formats
defined in the previous versions of the specification. You also proposed to use
bit 14 of the 'head' table to indicate that the glyphs encoded in the cmap
subtables do not truly represent the encoded code points.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>Question:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>Is it your intention that</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>- when bit 14 is set to '1' it indicates
that the <strong>all </strong>code points encoded in a font are not truly
represented, and the font can only be used as a last resort font, while</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>- when bit 14 is set to '0' it would mean
that any cmap subtable format can be used by a font, and that a font may
contain a mix of glyphs, some of them providing true representation of encoded
code points and other glyphs used as a "last resort" glyphs for
particular ranges of code points?</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>If this is true, it seems that the use of
bit 14 may be redundant, since the new Encoding ID = 6 would clearly
differentiate a font that can use any cmap subtable format, including format
13. It seems likely that most fonts would use different subtable formats
(including format 13 for unsupported code points), and that in rare
circumstances a font may only provide cmap format 13 subtable as a last resort.
However, I don't see why we would need to flag this font. Existing font engines
would likely not bother checking this new flag and the new rasterizers will be
able to properly handle the font with the support for the new Encoding ID.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>2) I think that providing historical
references to previous versions of the OpenType specification as part of the
Encoding ID descriptions would be detrimental to the readability of the OFF
spec. I suggest that we should rather stick with the established naming
conventions of different Encoding IDs. I propose that we should add new row in
the Encoding ID table with the value = 6 and the description field
"Unicode 5.0 and onward semantics, Unicode full repertoire", and
leave all other description fields unchanged. This description would provide
distinct meaning for the new ID, and at the same time can be used to encode
cmap table encoding records.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>Thank you,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:blue'>Vladimir</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<blockquote style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 0in;
margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'>
mpeg-OTspec@yahoogroups.com [mailto:mpeg-OTspec@yahoogroups.com] <b>On Behalf
Of </b>Sairus Patel<br>
<b>Sent:</b> Thursday, April 09, 2009 12:24 AM<br>
<b>To:</b> mpeg-OTspec@yahoogroups.com<br>
<b>Subject:</b> [mpeg-OTspec] Proposal related to Last Resort fonts</span><o:p></o:p></p>
<div id=ygrp-mlmsg>
<div id=ygrp-msg>
<div id=ygrp-text>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>
<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif"'>I’ve discussed the
concepts in the following Adobe proposal with various interested parties,
including MS and Apple, on an off-list thread:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif"'><a
href="http://tech.groups.yahoo.com/group/mpeg-OTspec/files/lastResortFont_AdobeProposal.doc">http://tech.groups.yahoo.com/group/mpeg-OTspec/files/lastResortFont_AdobeProposal.doc</a></span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif"'>I think it will very
nicely allow for “Last Resort” fonts and cmap subtable format 13 to fit cleanly
into the OpenType/OFF specifications.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif"'>Since this proposal has
Apple’s LastResort.ttf in mind (this is a Snow Leopard pre-release font), Adobe
would like it to be introduced as an amendment to the OFF standard at the next
WG11 meeting (April 19-24). Thus, please review it at your earliest convenience.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif"'>Best,</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Georgia","serif"'>Sairus</span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal><span style='color:white'><o:p></o:p></span></p>
</div>
</div>
</body>
</html>