<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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: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;}
/* 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.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:7.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:8.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:2.4pt;
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:6.0pt;
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.EmailStyle34
{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:1694114616;
mso-list-template-ids:-1630380124;}
@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'>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'>Thank you for your active participation and support of Composite
Font Standard activity. I uploaded the draft requirements document that we discussed
and approved during the last ISO MPEG meeting in January. The document can be
downloaded using the following link: </span><a
href="http://groups.yahoo.com/group/mpeg-OTspec/files/w11212-DraftRequirements_CFS.zip">http://groups.yahoo.com/group/mpeg-OTspec/files/w11212-DraftRequirements_CFS.zip</a><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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The next MPEG meeting will be held in April 19-23, and part of
our mandate is to finalize the requirements and use case document, and to
prepare a draft text for Call for Proposals where we should clearly outline the
features of the CFS (including expectations for future implementations based on
the requirements document) and evaluation criteria for submitted proposals, as
well as the estimated schedule of the development of the CFS specification. <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 will make a first stub at drafting the text of CFP; meanwhile
I would like to ask all AHG members to review the draft requirements document
and submit your comments and proposed changes/clarifications (if any). I would expect
to have final drafts of both document (requirements / use cases, and draft CFP)
finalized no later than April 12, 2010.<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 also would like to remind the AHG that the text of the draft
corrigendum for ISO/IEC 14496-22 OFF is now under open ballot, and that we had
some comments submitted by Microsoft. We need to discuss and finalize the text
of the corrigendum and prepare ballot comments to have the proposed changes
incorporated in the current text. <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><o:p> </o:p></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> Thursday, February 11, 2010 5:47 PM<br>
<b>To:</b> mpeg-OTspec@yahoogroups.com<br>
<b>Cc:</b> David Lemon<br>
<b>Subject:</b> Re: [mpeg-OTspec] AHG on Font Format Kick-off<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'>Vladimir,<br>
<br>
Are you planning to drive the schedule for the required bits, such as turning
the list of requirements for the CFS into something that is no longer draft,
and issuing the CFP? Unless we have feasible dates attached to these
milestones, things will continue to delay. As usual, if there is anything I can
do to push things along, you can count on my help and support.<br>
<br>
Thanks...<br>
<br>
-- Ken<br>
<br>
On 2010/02/01, at 14:40, Levantovsky, Vladimir wrote:<br>
<br>
> Dear Ken, all,<br>
> <br>
> Thank you very much for your efforts and support for CFS development
activity. I agree with you that any existing technology that is potentially a
good fit for what we are trying to accomplish with CFS should be considered and
discussed in details. I am happy to hear that Apple is open to contributing
their Spliced Font Format as a basis for CFS effort, and that they are open to
adding support for additional elements or attributes.<br>
> However, from the AHG perspective - in order to successfully evaluate any
and all candidate technologies, and determine and finalize the set of tags,
elements and arguments needed to fulfill the stated goals it would be both
useful and necessary to create a list of requirements we need to address. The
requirements, and the open Call for Proposals that will follow, would allow us
to make sure that we:<br>
> - have a strong foundation for evaluating candidate technologies (such as
Apple's Spliced Font Format, and maybe other solutions, including what AHG came
up with during the exploration stage), and<br>
> - develop a final solution that would fully satisfy the stated
requirements, possibly by combining the best of all proposals we will have
submitted in response to CFP. (It could be that we end up taking one particular
solution as a basis and adding features from other solutions we discussed earlier
- at this point I am reluctant to try and predict the outcome of this effort.)<br>
> <br>
> I also agree with Ken that CFS should be able to serve both as a composite
font and as a fallback font mechanism. Nesting and recursion can be allowed if
necessary, but, again - this is something we as the AHG will determine in the
process of finalizing CFS requirements.<br>
> <br>
> Thank you and best regards,<br>
> Vladimir<br>
> <br>
> P.S. I know some of you may wonder why Call for Proposals would even be
necessary after all the efforts we, as the AHG, put in place to engage industry
experts and invite them to join the group. Yes, we made a concerted effort to
make public aware of this activity by distributing the information in all
relevant public forums; however, the ISO process requires that public Call for
Proposal should be issued to insure that all interested parties are notified
about this activity through the official channels. In the end, it will only
help us ensure that we have the best pool of contributors to this activity, even
if the CFP itself doesn't bring 'new' proposals for consideration.<br>
> <br>
>> -----Original Message-----<br>
>> From: <a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>
[mailto:<a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>]<br>
>> On Behalf Of Ken Lunde<br>
>> Sent: Monday, February 01, 2010 12:29 PM<br>
>> To: <a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a><br>
>> Cc: David Lemon<br>
>> Subject: Re: [mpeg-OTspec] AHG on Font Format Kick-off<br>
>> <br>
>> Vladimir,<br>
>> <br>
>> I am very glad to see that WG11 is pushing us toward a standard.<br>
>> <br>
>> With that said, the highest priority for the AHG, in my opinion, is to<br>
>> determine whether Apple's "Spliced Font Format" is suitable
as the<br>
>> basis for CFS. Apple confirmed that they are open to this, and they
are<br>
>> also open to adding support for any additional elements or attributes,<br>
>> as long as they are considered optional. (The vast majority of
elements<br>
>> and attributes are optional, so I don't anticipate any issues.)<br>
>> <br>
>> To help with this effort, please reference/re-read my 01/15/2010 email<br>
>> to the AHG that summarized Apple's Spliced Font Format.<br>
>> <br>
>> Secondly, I once brought up the issue of nesting in the context of
CFS,<br>
>> and stated that it should not be allowed due to recursion and<br>
>> complexity issues. However, I now believe that this should be allowed<br>
>> in a specific context, because I believe that we can now distinguish<br>
>> CFS objects that serve as composite fonts versus as fallback fonts.
Let<br>
>> me explain.<br>
>> <br>
>> CFS objects can serve two main purposes or functions, specifically as<br>
>> composite fonts or as fallback fonts. I started going into this<br>
>> distinction in my 01/08/2010 post to the mailing list. Specifically, a<br>
>> CFS object functioning as a composite font requires a unique name,<br>
>> meaning a name that is unique from any installed font, and unique from<br>
>> any other CFS object that is functioning as a composite font. However,<br>
>> a CFS object that functions as a fallback font takes on the name of an<br>
>> existing font, which may be a standard font or potentially a CFS
object<br>
>> that functions as a composite font. This means that CFS-savvy OSes and<br>
>> applications need to be prepared to deal with a CFS object and an<br>
>> installed font with the same name, and to prioritize the CFS object
for<br>
>> obvious reasons.<br>
>> <br>
>> If you consider how fallback fonts work today, they take on the name
of<br>
>> an existing font resource, and describe composite font-like behavior,<br>
>> such as referencing other font resources to provide glyphs for<br>
>> characters that are not supported by the parent font resource.<br>
>> <br>
>> Getting back to the nesting of CFS objects, I now believe that this
can<br>
>> be allowed in CFS objects as long as what is being nested is a CFS<br>
>> object that is functioning as a composite font. Furthermore, I propose<br>
>> that the nesting depth should be one, meaning a top-level CFS object<br>
>> that functions as a fallback font can reference one or more CFS
objects<br>
>> that function as composite fonts, but that those "nested"
CFS objects<br>
>> that function as composite fonts cannot reference any CFS objects<br>
>> themselves.<br>
>> <br>
>> Regards...<br>
>> <br>
>> -- Ken<br>
>> <br>
>> On 2010/01/28, at 12:39, Levantovsky, Vladimir wrote:<br>
>> <br>
>>> <br>
>>> Dear AHG,<br>
>>> <br>
>>> <br>
>>> First of all, I'd like to welcome many new members who have
recently<br>
>> joined the group - just for the past couple of weeks our group grew<br>
>> stronger by 20+ members.<br>
>>> <br>
>>> At this time, the mandate for the AHG has been extended with new
work<br>
>> items - to produce the report summarizing the results of the<br>
>> exploration activities and to propose and develop a timeline for WG11<br>
>> to achieve stated goals of CFS standardization.<br>
>>> <br>
>>> The timeline should include the following steps that are part of
the<br>
>> ISO standards development process:<br>
>>> <br>
>>> - Finalization of complete list of requirements for Composite<br>
>> Font Standard - these should include any and all features that we<br>
>> believe should be part of the CFS (expected to be finished by the next<br>
>> WG11 meeting in April 2010);<br>
>>> <br>
>>> - Creation and publication of the Call for Proposals for<br>
>> either existing or developing technical solutions that would address<br>
>> indentified list of requirements.<br>
>>> <br>
>>> - Review and analysis of responses to the Call for Proposal,<br>
>> and publication of a working draft specification;<br>
>>> <br>
>>> - Creation of the Committee Draft (Proposed Draft Amendment if<br>
>> applicable);<br>
>>> <br>
>>> - Final Committee Draft ;<br>
>>> <br>
>>> - Final Draft International Standard.<br>
>>> <br>
>>> As part of the requirements work, I suggest that we should
identify<br>
>> and document both features that are already supported by known /<br>
>> existing technical solutions (such as features proposed by Adobe), as<br>
>> well as features / capabilities implemented in Apple's Spliced Font<br>
>> format and other technologies.<br>
>>> <br>
>>> We should also review and discuss the text of the draft
corrigendum<br>
>> for ISO OFF standard that was prepared at the WG11 meeting last week.<br>
>> If there are any changes or corrections that need to be made - we<br>
>> should review them and bring to the attention of the respective<br>
>> National Bodies to be included as part of the ballot comments. I have<br>
>> uploaded the draft to the AHG files.<br>
>>> <br>
>>> <br>
>>> <br>
>>> Thank you,<br>
>>> <br>
>>> Vladimir<br>
>>> <br>
>>> <br>
>>> <br>
>>> <br>
>>> <br>
>>> <br>
>>> <br>
>> <br>
>> <br>
>> <br>
>> ------------------------------------<br>
>> <br>
>> Yahoo! Groups Links<br>
>> <br>
>> <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>