<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:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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: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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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";}
p.ms, li.ms, div.ms
{mso-style-name:"ms\!";
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.m, li.m, div.m
{mso-style-name:"m\!";
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.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.EmailStyle36
{mso-style-type:personal-reply;
font-family:"Georgia","serif";
color:windowtext;}
.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:912928767;
mso-list-template-ids:-255956296;}
@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="#1E66AE" vlink="#1E66AE"><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'>a. What about TTCs?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'>b. I’m unclear about the actual problem the MIME types are supposed to solve. Why is it useful to know the glyph outline technology but not the layout table technology (OTL vs AAT) in a MIME type? If an HTML UA doesn’t support AAT, for example, it could skip trying to download a font.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'>c.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'>> SFNT structures that are not compliant with the ISO standard<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'>I do not think that OT/OFF forbids AAT tables (or any other tables unknown to OT/OFF) to be present in an sfnt. An sfnt containing TT outlines, cmap/hmtx and other required tables, and AAT layout tables but no GSUB/GPOS/ OTL tables should be considered to be a valid OT/OFF font. The AAT tables certainly aren’t required to be supported by an OT/OFF engine.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'>Best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'>Sairus<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Georgia","serif"'><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>Levantovsky, Vladimir<br><b>Sent:</b> Tuesday, April 05, 2011 1:13 PM<br><b>To:</b> Thomas Phinney<br><b>Cc:</b> John Hudson; David Lemon; OTspec; Chris Lilley; Tab Atkins; Karsten Luecke<br><b>Subject:</b> RE: [mpeg-OTspec] RE: font media types<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><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>Okay, thanks.</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;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:11.0pt;color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 0in'><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'> thomas.phinney@gmail.com [mailto:thomas.phinney@gmail.com] <b>On Behalf Of </b>Thomas Phinney<br><b>Sent:</b> Tuesday, April 05, 2011 4:13 PM<br><b>To:</b> Levantovsky, Vladimir<br><b>Cc:</b> John Hudson; David Lemon; OTspec; Chris Lilley; Tab Atkins; Karsten Luecke<br><b>Subject:</b> Re: [mpeg-OTspec] RE: font media types</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'>If you dropped explicit mention of having both outlines a! t once, you could just sy that OFF was a generic type that could have either kind of outlines. I think that is fine (and potentially useful under some circumstances).<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>T<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Tue, Apr 5, 2011 at 1:01 PM, Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotypeimaging.com">Vladimir.Levantovsky@monotypeimaging.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>I agree with you, but this is only a recommendation - there is no guarantee that this [mixing both types of outlines. i.e.] would never happen.</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;color:#1F497D'>What would be your recommendation - should we account for it? Would having a generic type that indicates compliance with th! e OpenType / OFF spec be useful?</span><o:p></o:p></p><p class=ms><span style='font-size:11.0pt;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:11.0pt;color:#1F497D'>Regards,</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;color:#1F497D'>Vlad</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;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:11.0pt;color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 0in'><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'> <a href="mailto:thomas.phinney@gmail.com" target="_blank">thomas.phinney@gmail.com</a> [mailto:<a href="mailto:thomas.phinney@gmail.com" target="_blank">thomas.phinney@gmail.com</a>] <b>On Behalf Of </b>Thomas Phinney<br><b>Sent:</b> Tuesday, April 05, 2011 3:54 PM<br><b>To:</b> Levantovsky, Vladimir<br><b>Cc:</b> John Hudson; David Lemon; OTspec; Chris ! Lilley; Tab Atkins; Karsten Luecke</span><o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><b>Subject:</b> Re: [mpeg-OTspec] RE: font media types<o:p></o:p></p></div></div></div></div><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'>That's a couple of times you've mentioned a font having both kinds of outlines. I don't think that's a possibility that should be encouraged, and I for one would prefer NOT to explicitly designate how to handle it. It is specifically recommended against in the OT spec: "Both Microsoft and Adobe recommend against mixing outline formats within a single font. Choose the format that meets your feature requirements." (<a href="http://www.microsoft.com/typography/otspec/recom.htm" target="_blank">http://www.microsoft.com/typography/otspec/recom.htm</a>)<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Cheers,<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></div><div><p class=m>T<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></div></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Tue, Apr 5, 2011 at 12:26 PM, Levantovsky, Vladimir <<a href="mailto:vladimir.levantovsky@monotypeimaging.com" target="_blank">vladimir.levantovsky@monotypeimaging.com</a>> wrote:<o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white'> <o:p></o:p></p><div><div><div><div><div><p style='background:white'>Thank you John,<br><br>I believe making a distinction based on the types of glyph outline data has always been the primary goal, and what you proposed seem to make perfect sense. However, I'd like to keep an "umbrella" media type to separate OpenType/OFF-based SFNT objects vs. arbitrary SFNT-based format.<br><br>Strictly speaking, defining a media type for an arbitrary SFNT-based format would go beyond the scope of ISO OFF specification, but I think it would be acceptable to attempt to define this media type as part of the ISO document anyw! ay, to offer a way to distinguish SFNT font structures that are not compliant with the ISO standard (and we know there are many of them out there). With this in mind, would the following be acceptable to everyone:<br><br>- application/font-ttf - for traditional TrueType fonts and OpenType/OFF fonts with TrueType outlines;<br>- application/font-cff - for OpenType/OFF fonts with CFF outlines;<br>- application/font-off - for OpenType/OFF fonts with both TrueType and CFF outlines, or as a generic type for a font that is compliant to ISO OFF spec, and<br>- application/font-sfnt - for generic SFNT-based font formats.<br><br>Please voice your objections / concerns / comments / agreement - I need to finalize the text of the annex and submit it to ISO SC29 by the end of the week.<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white'><br><br>Thank you,<br>Vlad<br><br>> -----Original Message-----<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white'>> From:! John Hudson [mailto:<a href="mailto:john%40tiro.ca" target="_!
blank">j ohn@tiro.ca</a>]<br>> Sent: Tuesday, April 05, 2011 2:08 PM<br>> To: Levantovsky, Vladimir<br>> Cc: David Lemon; OTspec; Chris Lilley; Tab Atkins; Karsten Luecke<o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white'>> Subject: Re: [mpeg-OTspec] RE: font media types<br>> <br>> Vladimir wrote:<br>> <br>> > We can also consider changing the proposed<br>> > media types, e.g. to be more specific and use font-ttf, font-cff and<br>> > font-otf for the purposes outlined above.<br>> <br>> If the distinction is to be based on outline type, then I think<br>> 'font-ttf' and 'font-cff' is much preferable to using 'font-otf' for<br>> the<br>> latter. The only reason .otf is not typically used as a file extension<br>> for TrueType fonts is so that the latter are backwards compatible with<br>> older Windows systems that do not recognise .otf; this is obviously<br>> less<br>> of a practical concern than it w! as in 1998, and now persists mostly as<br>> convention. I have, however, seen some TrueType fonts with an .otf<br>> extension.<br>> <br>> OTF stands for OpenType Font, not PostScript OpenType Font, and the<br>> first item in the OpenType catechism is that an OpenType font may<br>> contain either TrueType or PostScript outlines. Hence, I think it is<br>> misleading or at least confusing to identify 'font-otf' with PostScript<br>> outlines.<br>> <br>> I also wonder about using either 'font-off' or 'font-otf' to indicate<br>> an<br>> unknown outline type: the former because OFF is not a widely used or<br>> recognised abbreviation -- the Open Font Format being reasonably seen<br>> as<br>> a particular publication of the OpenType Font specification --, and the<br>> latter because of potential confusion in the minds of those who, due to<br>> convention, associate .otf with PostScript outlines.<br>> <br>> I wonder if there m! ight be grounds for a generic 'font-sfnt' MIME type,<br>> w! hich wou ld not only express the desired agnosticism regarding outline<br>> type, but would also be useful for fonts containing non-OTL layout<br>> tables.<br>> <br>> So we might have:<br>> <br>> application/font-ttf<br>> application/font-cff<br>> application/font-sfnt<br>> <br>> <br>> JH<br>> <br>> --<br>> <br>> Tiro Typeworks <a href="http://www.tiro.com" target="_blank">www.tiro.com</a><br>> Gulf Islands, BC <a href="mailto:tiro%40tiro.com" target="_blank">tiro@tiro.com</a><br>> <br>> A pilgrimage is a journey undertaken in the<br>> light of a story. -- Paul Elie<o:p></o:p></p></div></div></div></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br clear=all><br>-- <br>“Puritanism: The haunting fear that someone, <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> somewhere, may be happy.”<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&! nbsp;—H.L. Mencken<o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div></div></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br clear=all><br>-- <br>“Puritanism: The haunting fear that someone, <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> somewhere, may be happy.”<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> —H.L. Mencken<o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div></div></div></div></div></div></div><div><p class=MsoNormal><span style='color:white'><o:p></o:p></span></p></div></div></body></html>