<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)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
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;}
@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";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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'>If we want to make sure that the media type definition stays as part of the current amendment, we need to update and finalize the text soon to be included in the next ISO draft. It doesn’t mean that it can no longer be amended, and most likely it will be when and if new outline types and/or supported text layout mechanisms are introduced. I’d say that one such opportunity is going to be if SVG-in-OpenType proposal is accepted as a new work item.<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'>Speaking of which – I am sure many of you have seen the email discussions conducted in parallel on OpenType and www-font (<a href="http://lists.w3.org/Archives/Public/www-font/2011JulSep/thread.html">http://lists.w3.org/Archives/Public/www-font/2011JulSep/thread.html</a>) lists. There have been different ideas proposed and discussed, and I believe that combining SVG outline descriptions (that can bring multi-colored and animated glyphs) with OpenType advanced layout features would be a valuable technology to explore. I‘d like to ask you to get engaged in the informal discussions – the participation in the W3C www-font <a href="http://lists.w3.org/Archives/Public/www-font/">http://lists.w3.org/Archives/Public/www-font/</a> list is open to general public.<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'>Thank you,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Vladimir<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><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><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"'> thomas.phinney@gmail.com [mailto:thomas.phinney@gmail.com] <b>On Behalf Of </b>Thomas Phinney<br><b>Sent:</b> Tuesday, July 05, 2011 5:08 PM<br><b>To:</b> Levantovsky, Vladimir<br><b>Cc:</b> David Singer; Bob Hallissy; mpeg-OTspec@yahoogroups.com; lemon@adobe.com; chris@w3.org; tabatkins@google.com; karsten.luecke@kltf.de<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><div><p class=MsoNormal>On Tue, Jul 5, 2011 at 12:37 PM, Levantovsky, Vladimir <<a href="mailto:vladimir.levantovsky@monotypeimaging.com">vladimir.levantovsky@monotypeimaging.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal style='background:white'> <o:p></o:p></p><div><div><div><p style='background:white'>On Monday, May 02, 2011 11:14 AM I wrote:<br>> <br>> the alternative approach would be to define a single media<br>> type, e.g. "application/font-sfnt" with two sets of optional parameters<br>> like:<br>> <br>> 1) Name: Format<br>> Value: TTF, CFF<br>> 2) Name: Layout<br>> Value: OTF, AAT, SIL<br>> <br>> All, for the purposes of a straw poll only - please respond to this<br>> email with your preferred choice (I would specifically want to hear<br>> from those who proposed this activity)!<br>> <br><br>There was one positive response submitted by Thomas Phinney advocating for an alternative approach above, and suggesting to replace parameter name "Format" with "Outlines". In case there are no objections to the above (i.e. to changing the media type definitions to "application/font-sfnt" with two optional parameters "outlines" and "layout") - I will draft a contribution to WG11 suggesting this change and, pending the WG11 approval, we will be able to prepare and submit an application to IANA. If any of you do have objections, please respond to this email.<br><br>Thank you,<br>Vladimir<span class=apple-style-span><span style='color:white'></span></span><o:p></o:p></p></div></div></div></div></div><p class=MsoNormal>Perhaps we should make two things explicit in this proposal: (1) more values may be added to either parameter in the future, and (2) there may be multiple values for a single parameter. I'm thinking here of the SVG-in-OpenType-clothing proposal we have on the table on the OpenType and www-fonts lists.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Alternatively, we might want to wait until that proposal is resolved or further along, before making this submission, so as to include SVG outlines if needed.<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><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>T<br clear=all><br>-- <br><span style='font-family:"Verdana","sans-serif"'>“Puritanism: The haunting fear that someone, </span><o:p></o:p></p><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'> somewhere, may be happy.”</span><o:p></o:p></p><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'> —H.L. Mencken</span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></body></html>