<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: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;}
/* 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";}
span.cat
{mso-style-name:cat;}
span.ct
{mso-style-name:ct;}
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:"Calibri","sans-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:1227106153;
mso-list-template-ids:1567782474;}
@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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hello Ken, all,<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'>I agree that Composite Fonts activity would benefit from the new
name to prevent the conflict between Composite Font and Compact Font Format
(CFF). However, there is an organization called the Khronos Group that develops
specifications for graphics acceleration and system integration APIs, and their
trademarked names always start with Open… – they are most famous
for the names like OpenGL and OpenGL ES, but there are many other specs that
already have been released under the names like OpenVG, OpenMAX, OpenML,
OpenKODE, OpenWF and OpenCL (to name a few). I am afraid the name like OpenCF
may be mistakenly attributed to their line of standards, and may even be viewed
as a trademark violation - I am not a lawyer, so the above statement should
be considered a concern, not a legal opinion.<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'>I believe that the future Composite Font specification will
likely become a new clause of the ISO OFF spec, and I like one of the names “Composite
Font Standard” John Hudson has proposed. IMHO, CFS would fit well
with the existing abbreviations OFF and CFF.<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"'>
mpeg-OTspec@yahoogroups.com [mailto:mpeg-OTspec@yahoogroups.com] <b>On Behalf
Of </b>Ken Lunde<br>
<b>Sent:</b> Sunday, December 13, 2009 8:47 AM<br>
<b>To:</b> leonardo@chiariglione.org<br>
<b>Cc:</b> mpeg-OTspec@yahoogroups.com<br>
<b>Subject:</b> Re: [mpeg-OTspec] Re: A path through the thicket<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>
<p style='margin-bottom:12.0pt'>Many thanks, Leonardo. This is incredibly
helpful. I will work on a revised document on Monday, which will reflect your
suggestions.<br>
<br>
With regard to the full name and abbreviation, as Manlio pointed out, CFF is
not a good choice because it conflicts with another font-related format,
specifically Compact Font Format, and is also the tag for the corresponding
OpenType table. I completely agree.<br>
<br>
Given the cross-platform and rich nature of this Composite Font format, along
with the fact that it is XML-based, I have one abbreviation/name suggestion:<br>
<br>
OpenCF (Open Composite Font)<br>
<br>
I chose OpenCF over OCF as the abbreviation for "Open Composite Font"
because OCF is already an abbreviation for a legacy PostScript font format
called "Original Composite Font." I also like the emphasis of the
word Open, which works well with OFF.<br>
<br>
Regards...<br>
<br>
-- Ken<br>
<br>
On 2009/12/12, at 9:17, Leonardo Chiariglione wrote:<br>
<br>
> Ken,<br>
> Thank you. This time I could see your attachment.<br>
> I have comments to your document.<br>
> At the beginning you say<br>
> <br>
>> The purpose of this Composite Font specification is to replace
existing<br>
> Composite Font and Fallback Font formats, as used by today's OSes and<br>
> applications, with one that is cross-platform and standards-based, thus<br>
> bringing uniformity to the specification and use of Composite Fonts.<br>
> <br>
> In the MPEG world this does not convey a lot of meaning as the Composite<br>
> Font Format (what about CFF?) will (we hope it will) become an ISO
standard.<br>
> <br>
>> Another purpose is to allow a Composite Font to reference more than
64K<br>
> glyphs by virtue of being able to reference two or more component fonts
that<br>
> each can include up to 64K glyphs.<br>
> <br>
> This is very good because it describes features of CFF that are not<br>
> currently provided by existing formats.<br>
> <br>
> Therefore what about the following<br>
> <br>
> The Composite Font Format (CFF) is an ISO standard with the following<br>
> features:<br>
> 1. is cross-platform<br>
> 2. allows a Composite Font to reference more than 64K glyphs by virtue of<br>
> being able to reference two or more component fonts that each can include
up<br>
> to 64K glyphs (a bit long, but I am unable to make it shorter without<br>
> damaging the message)<br>
> 3. is expressed in XML, and any non-ASCII characters that are specified<br>
> (e.g. for localized menu names), are to be represented via UTF-8 or as<br>
> Numeric Character References (shorter would be better but this is as much
as<br>
> I can do).<br>
> <br>
> If there are more features that you think are important for our
"customers"<br>
> please add.<br>
> <br>
>> The Composite Font recipe is the means by which the creator specifies
the<br>
> intent to the consumer<br>
> <br>
> Whose intent is it? From the text following it seems the creator. If that
is<br>
> the case let's spend another word. But then, the intent of what?<br>
> <br>
>> it is the responsibility of the consumer to support as much of the<br>
> creator's intent as possible for the benefit of the user<br>
> <br>
> There is clearly a gap in our historical background. But don't worry the<br>
> reason (one of the reasons...) I am interested in you work is because I
want<br>
> to understand what it is. MPEG may have something to learn, after all ;-)<br>
> <br>
> The perception of a gap stems from the fact that in a typical MPEG
standard<br>
> a conforming "decoder" of a certain profile and level has all
the tools (the<br>
> intelligence) to carry out the work to the encoder expected it to do.<br>
> What I think I understand from your words (please correct me if I am
wrong)<br>
> is that a CFF receiver, because of the nature of font information, can
still<br>
> do a decent or passable job, even if it does not have the intelligence to
do<br>
> what the encoder expects.<br>
> In some MPEG standard we have something resembling this. An MPEG-1 Audio<br>
> layer II decoder can decode an MPEG-2 Audio layer II bitstream, but don't<br>
> expect the output to be 5.1. because it will only be stereo. <br>
> If I am still in sync with you, what about replacing your text above (and<br>
> following) with<br>
> <br>
>> the decoder will support as much of the creator's intent as instructed
by<br>
> the user, bearing in mind that missing component fonts and technical<br>
> limitations may impair a consumer's ability to completely support the
intent<br>
> of the creator.<br>
> <br>
> In the MPEG world this is kind of obvious, but let's keep it, at least for<br>
> moment.<br>
> <br>
>> It is the intent of this specification that a Composite Font recipe<br>
> specifies only the information that the creator wishes to convey, and<br>
> nothing more. For any attribute that is not specified by the Composite
Font<br>
> recipe, the consumer must therefore defer to the appropriate component<br>
> fonts.<br>
> <br>
> At this moment the implications of this sentence are not clear to me.<br>
> May I propose that you to edit your text according to my suggestions, of<br>
> course to the extent that they do not alter your intention :-( and send it<br>
> back for another round?<br>
> Leonardo <br>
> <br>
> <br>
> -----Original Message-----<br>
> From: Ken Lunde [mailto:<a href="mailto:lunde%40adobe.com">lunde@adobe.com</a>]
<br>
> Sent: 12 December 2009 14:39<br>
> To: <a href="mailto:leonardo%40chiariglione.org">leonardo@chiariglione.org</a>;
<a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a><br>
> Subject: Re: [mpeg-OTspec] Re: A path through the thicket<br>
> <br>
> Leonardo and others,<br>
> <br>
> Attachments seem to be easy to overlook due to where and how they are<br>
> attached when sending to this distribution list. I am attaching the PDF
file<br>
> again, but I have also hosted it at the following URL, giving everyone two<br>
> chances to grab the document:<br>
> <br>
> <a href="http://lundestudio.com/PDF/CompositeFont-11252009.pdf">http://lundestudio.com/PDF/CompositeFont-11252009.pdf</a><br>
> <br>
> Regards...<br>
> <br>
> -- Ken<br>
> <br>
> <br>
> No virus found in this incoming message.<br>
> Checked by AVG - www.avg.com <br>
> Version: 8.5.427 / Virus Database: 270.14.102/2556 - Release Date:
12/11/09<br>
> 19:37:00<br>
> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:white'><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>