<trackbot> Date: 15 December 2010

Described new language proposed to add WOFF support to EPUB spec...

http://groups.google.com/group/epub-21-working-group/browse_thread/thread/4f7a7975aaec459b#

EPUB will support both WOFF and obfuscated OpenType.

Concern that desktop apps (e.g. Word) will be interested in "supporting" WOFF i order to become better web authoring apps.

John Hudson will consider current language in WOFF spec.

Skipping open action items, since most/all are for C. Lilley and J. Kew.

Reviewing Last Call comments.

Vlad will ensure all comments received are documented.

Discuss use of xml:lang.

tal: Don't want to break anything that's out there.

Vlad: Let's defer this to the next conference call.

John: Who's strong with XML?

tal: Liam.

xml: lang discussion: http://lists.w3.org/Archives/Public/www-font/2010OctDec/0092.html

<Vlad> http://lists.w3.org/Archives/Public/www-font/2010OctDec/0095.html

J. Kew should ensure that sfnt ordering issue is resolved.

Discussing testable assertions.

<Vlad> scribe: cslye

<tal> http://dev.w3.org/webfonts/WOFF/tests/UserAgent/Tests/testcaseindex.xht

tal: Will post to the list soon about the state of the test suite.

<tal> http://dev.w3.org/webfonts/WOFF/spec/#conform-sameorder

tal: Checking table order cannot be a file format testable assertion because it cannot be confirmed if the original font is not necessarily around for reference.
... Should be an authoring tool check.

<tal> sfnt fonts store a checksum for each table in the table directory, and an overall checksum for the entire font in the head table (see the TrueType, OpenType or Open Font Format specifications for the definition of each calculation). Tools producing WOFF files MUST validate these checksums, and reject the font if errors are found.

John: Why are we validating the checksum in the head table?

tal: Should a validator also check it?

Vlad: Yes, it's a good thing.
... Do we need to have a call next week?

John: If something comes up in the last call comments, we might need to, but otherwise not.

tal: No need to meet for Test Suite.

Vlad: No call next week unless something urgent comes up.
... We'll use the email list instead.
... Next year: Keep same schedule?
... I might be traveling on Jan 5.

Next meeting might not be until Jan 12. TBD on the email list.

Vlad: Promotion to Candidate Recommendation might happen near end of January.

<Vlad> adjourned

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/is not around for reference/is not necessarily around for reference/
Found Scribe: cslye
Inferring ScribeNick: cslye

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: John Vlad aaaa aabb aacc aadd aaee aaff cslye erik joined sergeym sylvaing tal trackbot webfonts xml
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 15 Dec 2010
Guessing minutes URL: http://www.w3.org/2010/12/15-webfonts-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report