<HTML>
<HEAD>
<TITLE>Re: [mpeg-OTspec] Composite Fonts Policy</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Colleagues,<BR>
<BR>
Many thanks for the conference call. It seems to stoke fertile discussion after weeks of (also productive) e-mail.<BR>
<BR>
Concerning the matter of policy, I proposed three possible approaches that could inform our decisions and perhaps help automate them.<BR>
<BR>
</SPAN></FONT><OL><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><B>Simple.</B> Specify the minimum necessary for a font engine to realize the intent of the composite font under favorable conditions. I see benefits as: Shorter time to reach a specification; shorter development times for font engines; easy construction of composite fonts; presumably broader adoption. Hazards: Infidelity to the original intent of a composite font, since that intent would not be fully recorded in the composite font; nor would fidelity be required; possible proliferation of proprietary implementations to fill the gaps.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><B>Pedantic.</B> Craft the specification in detail, making as little of it elective as practical. Benefits: Fidelity of original intent of composite fonts across font engines and environments. Hazards: Greater development time of specification and font engines; attendant narrower adoption; defeat of purpose when the inevitable violations of the specification crop up.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><B>Elective detail.</B> Mandate as little as required for font fidelity under favorable conditions, but accommodate as much information as required to specify the intent. Benefits: Easy construction of composite fonts and font engines when the intent is mere legibility; possibility of constructing composite fonts that encode complete intent for full fidelity; choice of sophistication in construction of font engines and composite fonts; presumably broad adoption but at varying levels of sophistication. Hazards: Greater development time of specification.<BR>
</SPAN></FONT></OL><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Regards,<BR>
<BR>
— daan Strebe<BR>
Senior Computer Scientist<BR>
Adobe Systems Incorporated<BR>
<BR>
<BR>
<BR>
<BR>
On 09/04/28 13:46, "Levantovsky, Vladimir" <<a href="vladimir.levantovsky@monotypeimaging.com">vladimir.levantovsky@monotypeimaging.com</a>> wrote: <BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Dear all,<BR>
<BR>
The AHG mandate has been extended to continue the exploration activities on Composite Fonts solution. Like we discussed and agreed earlier this month, we will have a conference call on May 4th discussing Composite Fonts Requirements (</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'><a href="http://groups.yahoo.com/group/mpeg-OTspec/files/Composite%20Fonts%20Requirements.doc">http://groups.yahoo.com/group/mpeg-OTspec/files/Composite%20Fonts%20Requirements.doc</a> <<a href="http://groups.yahoo.com/group/mpeg-OTspec/files/Composite%20Fonts%20Requirements.doc">http://groups.yahoo.com/group/mpeg-OTspec/files/Composite%20Fonts%20Requirements.doc</a>> </SPAN></FONT><SPAN STYLE='font-size:11pt'>).<BR>
<BR>
I suggest that we have a conference call starting at 3:00pm PDT (6:00pm EDT, 7:00 am May 5th Nippon – Tokyo).<BR>
The conference bridge information is as follows:<BR>
<BR>
<B>Dial-In Numbers</B>:<BR>
<B>USA</B>: <BR>
<BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>Toll free: </SPAN></FONT><SPAN STYLE='font-size:11pt'> </SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>1-866-546-3377</SPAN></FONT><SPAN STYLE='font-size:11pt'> <BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>Toll: </SPAN></FONT><SPAN STYLE='font-size:11pt'> </SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>1-719-234-7872</SPAN></FONT><SPAN STYLE='font-size:11pt'> <BR>
<BR>
<B>Japan</B>:<BR>
<BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>Toll free: </SPAN></FONT><SPAN STYLE='font-size:11pt'> </SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>00531 16 0959</SPAN></FONT><SPAN STYLE='font-size:11pt'> <BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>Toll: </SPAN></FONT><SPAN STYLE='font-size:11pt'> </SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>+81 (0) 3 4455 1494</SPAN></FONT><SPAN STYLE='font-size:11pt'> <BR>
<BR>
<BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'><B>Participant Passcode</B>:</SPAN></FONT><SPAN STYLE='font-size:11pt'> </SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>7758315606</SPAN></FONT><SPAN STYLE='font-size:11pt'> <BR>
<BR>
Please let me know if the time is good. If there are any participants from other countries who would like to join the call, please let me know and I will provide the updated dial-in information.<BR>
<BR>
Thank you,<BR>
Vladimir<BR>
<BR>
<BR>
<BR>
<FONT COLOR="#FFFFFF"><BR>
</FONT><BR>
</FONT></SPAN></BLOCKQUOTE>
</BODY>
</HTML>