[mpeg-OTspec] New "Composite Font Standard" document

[Ken Lunde]

Leonardo,

This all makes sense. I am continuing the editing of this document in MS Word using the "track change mode," and will issue a new version later today, which will reflect the current discussions about three attributes for the ComponentFont tag.

Regards...

-- Ken

On 2009/12/15, at 4:12, Leonardo Chiariglione wrote:

> Ken,
> Excellent.
> I have done the following
> 1.      Converted your pdf file to a doc file (MS word is the format adopted by MPEG because it allows reuse of text, a basic feature in a collaborative environment like this)
> 2.      Edited the file in track change mode
> 3.      Changed the file name by using yyyymmdd_lc
> 4.      Attached the file to this email
> You may think that some changes are not essential and there may be elements of truth in this. However, if you agree to the changes we get agreement on issues that I believe are of substance.
> I will try and explain my point
> 1.      The title of the first section has been changed to “Design features”. OS independence is a consequence of the fact that CFS is an information representation standard, so it has been taken out of the bulleted list
> 2.      At the abstract level there are 4 actors: creator, encoder, decoder, consumer. Don’t let’s talk about the names, yet. If you don’t like the names I am fine with calling the actors A,B, C and D, Creator and consumer are humans (maybe there are more general cases when they are not, but let’s stick to humans for the moment).
> 3.      Creator has intentions that he captures in his encoder – an application
> 4.      Consumer has intentions that he expresses by setting his decoder
> 5.      The standard only addresses the decoder. The document is silent on exactly “what” of the decoder is specified. I guess that the interface through which the consumer sets the decoder is not part of the standard, but then it would be good to say this explicitly (note that all this is work saved for the moment in which the standard will be written)
> 6.      In MPEG we use the name conformance, but you can read it as compliance
> Please feel free to react on anything I did.
> For me this is a very pleasant experience.
> Leonardo
>  
> From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On Behalf Of Ken Lunde
> Sent: 14 December 2009 19:07
> To: mpeg-OTspec at yahoogroups.com
> Subject: [mpeg-OTspec] New "Composite Font Standard" document
>  
>  
> All,
> 
> In an effort to move this along, I spent the morning incorporated Leonardo's comments and suggestions, and produced a new version of the document. You should have received a "new document notification" email with the following URL:
> 
> http://groups.yahoo.com/group/mpeg-OTspec/files/CompositeFontStandard-12142009.pdf
> 
> I also hosted the same file on my website:
> 
> http://lundestudio.com/PDF/CompositeFontStandard-12142009.pdf
> 
> When you have a chance, please read this document and provide feedback.
> 
> Regards...
> 
> -- Ken
> 
> 
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.427 / Virus Database: 270.14.106/2563 - Release Date: 12/13/09 19:47:00
> 
> <CompositeFontStandard-20091214_lc.doc>