<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Source Code Pro";
panose-1:2 11 5 9 3 4 3 2 2 4;}
@font-face
{font-family:"Adobe Clean";
panose-1:2 11 5 3 2 4 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Source Code Pro";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Source Code Pro";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Source Code Pro";
color:windowtext;}
span.EmailStyle20
{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;}
--></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><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>Vlad-</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>Thanks very much for making this an official effort. At Adobe, members of the Adobe Type Team feel it is the right time to extend the OFF/OpenType specification, which can only result in overall added value for type users, content consumers and the type industry as a whole. Visual richness is something that we see burgeoning across the web, numerous devices and the traditional desktop. </span><span style='font-size:10.0pt;font-family:"Source Code Pro"'>It only seems appropriate that we broaden the capabilities of type – something that is so pervasive and essential for expressive communication around the world.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>We are pleased by recent efforts by many of our partners (Apple, Google, Microsoft) and their color font initiatives. While many of these efforts surround the addition of color for the express purpose of offering richer emoji fonts, we feel that we should be looking well beyond that toward the future. As Dr. Ken Lunde, our CJKV type expert said, “When you do open heart surgery, you’d best fix anything else that needs fixing while you are in there. You don’t want to have to crack that chest, again.” A somewhat graphic analogy, but at Adobe we feel that if there is going to be an effort to modify the spec, then let’s add functionality from which everyone can benefit – functionality that customers and developers can use for the next ten years or so.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>While the addition of color is a nice start, we feel there is an opportunity to also add:</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Scalability (bitmap solutions can solve some problems but are functionally restrictive)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Designs which can be used in multiple sizes across multiple devices</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Design once, use everywhere</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Color gradients (Move beyond solid color)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Support for Animation (even if not implemented initially)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Fonts which grab the attention of the viewer</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Animation support to show stroke sequence and direction (for teaching writing / Asian font education)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>Adobe has been interested in this functionality for some time. Please check out a Flash-based example of how an SVG-based solution could be used:</span><span style='color:black'><o:p></o:p></span></p><p class=MsoPlainText><a href="http://www.adobe.com/devnet-apps/type/EmojiGradient.html">http://www.adobe.com/devnet-apps/type/EmojiGradient.html</a><o:p></o:p></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>This example, designed by Ryoko Nishizuka in our Tokyo office, offers vector-based content which is both animated and supports gradient areas. While yet another example of an emoticon solution, this could be expanded to support any kind of display font which could benefit from color, animation or scalability. Examples are creative titling, drop-caps, other display usage in digital publishing (HTML pages and e-magazines); online advertisements, and e-learning materials. </span><span style='font-size:10.0pt;font-family:"Source Code Pro"'>It is our belief that this functionality could be addressed by using SVG<span style='color:black'>. Our recommendation would require the addition of an SVG table to the OFF which could, not only provide solutions for color, but also provide for the added functionality noted above. Already a part of the HTML specification, as well as supported in many software programs and devices, the SVG model when combined with the next OFF standard could provide the basis which will help us get closer to bringing the same visual richness we currently enjoy in print to the screen. Sairus Patel, of our CoreType team, can speak more deeply to the technical requirements and has been working with the Mozilla team to promote SVG support in OpenType fonts.</span></span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>Below is a shortened summary of the requirements categories you suggested in your previous email:</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Expressiveness</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> The list above falls into this category</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> The model can support developer defined color specification (not locked into colors specified by the designer)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Compatibility with existing glyph mechanisms</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Monochrome instance of the font is supported as usual</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> SVG table and added functionality ignored if not supported</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> SVG renderer called when table is present</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Performance</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Font file size is always a consideration, but should be a decision made by the content creator based on their targeted consumers</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Constrained devices will ignore added functionality</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> While this added functionality may increase file size (negative impact to download performance), this may not be a concern in the future as technology improves (Moore’s Law)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Asian fonts similarly continue to suffer from the same problems due to file size. We need tech solutions (compression, glyph streaming, etc.) to solve for this problem anyway.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Rendering environment constraints</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> For many constrained environments, this added functionality will not be desired, <however></span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Device manufacturers will continue to differentiate based on functionality. We can provide them with design options if the spec is expanded to support more functionality.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>-Scalability and co-existence</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Adding additional functionality doesn’t preclude support for bitmap-based solutions for constrained environments</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> Fonts created with SVG support will not be limited to a fixed size, but can be scaled up or down to suit the environment or the needs of the designer</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>Finally, I would like to make a case for the value proposition: For content consumers, more expressive fonts will provide for visually richer customer experiences. For content creators, straight out of the box (or should I say “straight out of the font”) enriched fonts will provide designers with solutions which require little tweaking – are ready to go, and can help draw attention to web content. For font foundries, added functionality provides new opportunities to build new types of fonts, or add additional functionality to their existing libraries and sell upgrades. Think of the large markets around clip art and stock photography. Typographers may want to do much of this themselves, but for every knowledgeable type user, there are plenty of potential content creators who will need a solution but don’t have the time to create it themselves.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'>Caleb</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Adobe Clean","sans-serif";color:#1F497D'>______________________</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Adobe Clean","sans-serif";color:#1F497D'>Caleb Belohlavek</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Adobe Clean","sans-serif";color:#1F497D'>Principal Product Manager </span><span style='font-size:12.0pt;font-family:"Adobe Clean","sans-serif";color:#1F497D'>•</span><span style='font-family:"Adobe Clean","sans-serif";color:#1F497D'> Type </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-family:"Adobe Clean","sans-serif";color:#1F497D'>Adobe </span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Adobe Clean","sans-serif";color:#1F497D'><a href="mailto:caleb@adobe.com">caleb@adobe.com</a></span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Adobe Clean","sans-serif";color:#1F497D'>408.536.3706</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Source Code Pro"'><o:p> </o:p></span></p></div></body></html>