[mpeg-OTspec] Re: Draft CFS requirements

[Ken Lunde]

*** I am resending this because I didn't see it show up on the mailing list. ***

Michael,

First, welcome.

The "contingency processing" is inherent in the CFS object's definition. You see, today's "contingency processing" is done via font-fallback, which is based on a definition remarkably similar to CFS. In other words, developers who are currently using or depending upon font-fallback merely rewrite the definition as a CFS object.

Regards...

-- Ken

On 2010/01/22, at 12:49, Michael wrote:

> 
> 
> First let me introduce myself. My name is Michael Warning and I'll be replacing Mikhail Leonov on the Microsoft side of things. I'm new to this whole process so I hope you'll bear with me as I get up to speed.
> 
> The summary looks reasonable to me. My only comment is not so much about the document as about future agendas. In reference to "therefore component fonts are expected to be missing or misidentified and contingency processing is normal and expected", is it generally expected that the spec will define what that contingency processing is?
> 
> --- In mpeg-OTspec at yahoogroups.com, "Levantovsky, Vladimir" <vladimir.levantovsky at ...> wrote:
> >
> > Hi Ken,
> > 
> > Thank you very much for your comments. Regarding the terminology - I will review it once again and replace Composite Font Format with CFS where appropriate; as far as CFS object is concerned - "Composite Font Standard object" (or CFS object) doesn't sound right, I think that "Composite Font object" (or CF object) would be a better term for it.
> > I will also review use cases and try to accommodate your comments.
> > 
> > Thank you and best regards,
> > Vladimir
> > 
> > > -----Original Message-----
> > > From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com]
> > > On Behalf Of Ken Lunde
> > > Sent: Wednesday, January 20, 2010 9:07 AM
> > > To: mpeg-OTspec at yahoogroups.com
> > > Subject: Re: [mpeg-OTspec] Draft CFS requirements
> > > 
> > > Vladimir,
> > > 
> > > I am away from work through the end of the week, attending the 2010
> > > SHOT Show, but I spent a few minutes going through this. It is a good
> > > summary of the requirements. The only suggestion I would make is one of
> > > terminology, specifically the following:
> > > 
> > > CF object -> CFS object
> > > Composite Font (or Fonts) Format -> Composite Font Standard (or CFS)
> > > 
> > > In other words, using the decided-upon terminology, meaning "Composite
> > > Font Standard" or "CFS," would be a a good thing.
> > > 
> > > Also, in the "Use case descriptions" section, I think that the two
> > > distinct uses of CFS objects, specifically as a Composite Font or
> > > Fallback Font, should be explicitly mentioned.
> > > 
> > > Regards...
> > > 
> > > -- Ken
> > > 
> > > On 2010/01/19, at 20:39, Levantovsky, Vladimir wrote:
> > > 
> > > > [Attachment(s) from Levantovsky, Vladimir included below]
> > > >
> > > > Dear all,
> > > >
> > > > I was asked to prepare a document that would summarize the draft
> > > requirements for CFS. Please see attached draft that is based on the
> > > document I submitted during the last ISO MPEG meeting. The current
> > > draft was extended to include the results of the discussion we had
> > > since the MPEG meeting in October.
> > > >
> > > > Your comments are very much appreciated, please submit them no later
> > > than by the end of the day tomorrow (Wednesday, Jan. 20).
> > > >
> > > >
> > > >
> > > > Thank you,
> > > >
> > > > Vladimir
> > > >
> > > >
> > > >
> > > >
> > > >
> > > 
> > > 
> > > 
> > > ------------------------------------
> > > 
> > > Yahoo! Groups Links
> > > 
> > > 
> > >
> >
> 
>