W3C

- DRAFT -

WebFonts Working Group Teleconference

26 Jan 2011

Agenda

See also: IRC log

Attendees

Present
Regrets
Tal, ChrisL, Sylvain
Chair
Vlad
Scribe
Tal

Contents


<Vlad> rrsagent help

<Vlad> trackbot, start telcon

<trackbot> Date: 26 January 2011

<Vlad> Chair Vlad

<jfkthame> vlad, i'm only catching 50% of what you're saying, at best

<erik> I'm calling in on skype, I can't actually make out anyone, sorry.

Reviewing open actions.

<Vlad> action 56?

<trackbot> Sorry, bad ACTION syntax

<Vlad> action-56?

<trackbot> ACTION-56 -- Jonathan Kew to tag wrng size compressed meta as a ua assert -- due 2010-12-15 -- OPEN

<trackbot> http://www.w3.org/Fonts/WG/track/actions/56

<Vlad> action-56: pending

<trackbot> ACTION-56 Tag wrng size compressed meta as a ua assert notes added

Changed Action-56 to "pending review."

Action-60 can be closed.

Discussion about Action-62.

Will pick up later or discuss later.

Discussion about the meaning Action-66.

Action-69 can be closed. Vlad completed this one.

Discussion of comments from Bert Bos.

http://lists.w3.org/Archives/Public/www-font/2011JanMar/0009.html

Point 1: Vlad asked for clarification.

Håkon: agrees with Bert's comment.

Thinks that the comment is about SOR and relates to recent discussion on list.

Vlad: not sure that it is about SOR.

Håkon: Thinks that there is not yet a consensus on SOR.

Håkon: WOFF would have a better shot at interoperability if there is consensus on SOR.

Vlad: We should discuss this but not today as we are discussion Bert's comments.

Discussion about when to discuss SOR.

Håkon: We don't have all browser vendors here.

Tal: They have been invited. It is their responsibility to call in.

Vald: This is not on the agenda for the day. Let's discuss this later.

Vlad: THis will be a detailed discussion so let's set up a call specifically for this topic.

Back to Bert's comments.

Point 2:

Vlad: We agree with Bert that we have made the intro as clear as we can. Any other comments for making it even more clear are welcome.

Vald: "Despite this name, WOFF should be regarded as a container format or "wrapper" for font data in already-existing formats rather than an actual font format in its own right."

Vlad: Perhaps add "Despite the name, WOFF is not a new font format and should be regarded as..."

Christopher: Thinks that the language is clear enough as is.

Jonathan: No strong view either way. Doesn't mind changing it but isn't sure that any value will be added.

Vlad: Should we create an action item to review the first paragraph of the introduction?

Christopher: Bert's comment was "it sounds good" so why are we discussing changing it?

Vlad: This one particular sentence could be more specific.

Point 3:

Jonathan: His original tool, and the spec, did not pad. Not sure when the optional padding made it into the spec.

Vlad: Any objections to wat Bert proposes?

Tal: If we make that SHOULD a MUST, would a UA have to test and reject?

Jonathan: UA could test with the header length of file and length of block.

Vlad and Tal: Would that contradict the "Private Data should not effect the font data..." section of the spec?

Jonathan: This would be a problem with the header, not the private data.
... UA could do simple sanity checks on header fields.

Vlad: Does that need to be mentioned in the header?

Jonathan: Reads spec. We already call for the UA to check those offsets.

Vlad: Should we not mention padding the private data?

Jonathan: We could repeat that the end of the private data block must be the end of the file.

Vlad: Agrees with Jonathan.

Tal: Agrees.

<Vlad> Scribe: Tal

Action Jonathan Replace last sentence of section 7: End of Private Data block must correspond with the end of the last file.

<trackbot> Created ACTION-70 - Replace last sentence of section 7: End of Private Data block must correspond with the end of the last file. [on Jonathan Kew - due 2011-02-02].

<Vlad> Scribenick: tal

Discussion on if this should apply to the metadata block as well.

Vlad: Metadata section is clear.

Point 4:

Vlad: Can anyone clarify what this means?

Action Chris Clarify Bert Bos' Point 4

<trackbot> Created ACTION-71 - Clarify Bert Bos' Point 4 [on Chris Lilley - due 2011-02-02].

Point 5:

Vlad: not sure how useful it would be to not store origLength.

Jonathan: UA needs to know original length to allocate buffer otherwise it is more cumbersome to decode.

Action Jonathan Respond to Bert Bos' Point 5.

<trackbot> Created ACTION-72 - Respond to Bert Bos' Point 5. [on Jonathan Kew - due 2011-02-02].

Sergey: origLength is also useful for recreating table directory.
... Mentions email to list that has not been discussed: http://lists.w3.org/Archives/Public/www-font/2011JanMar/0005.html

Tal: This can be created dynamically.

Sergey: Yes. We should mention this in the spec.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2011/01/26 16:06:11 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Found Scribe: Tal
Inferring ScribeNick: tal
Found ScribeNick: tal

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: Christopher Jonathan P13 P16 Scribenick Sergey Tal Vald Vlad aabb aacc aadd aaee aaff action-56 cslye erik jfkthame jfkthame_afk joined sergeym trackbot webfonts
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Regrets: Tal ChrisL Sylvain
Agenda: http://lists.w3.org/Archives/Public/public-webfonts-wg/2011Jan/0024.html
Found Date: 26 Jan 2011
Guessing minutes URL: http://www.w3.org/2011/01/26-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


[End of scribe.perl diagnostic output]