Conference call reminder and agenda for Wed., Jan. 19th

We will have our regularly scheduled telcon tomorrow, Wed. the 19th

US West Coast - 13:00
US East Coast - 16:00
Central Europe - 22:00
Japan - 06:00



Zakim telephone bridge:

     +1.617.761.6200 (Boston) or

     +33.4.26.46.79.03 (Paris) or

     +44.203.318.0479 (London)

     with conference code 3668 ("FONT")


IRC channel is #webfonts, irc://irc.w3.org:6665/webfonts

or http://irc.w3.org/?channels=webfonts

Our last call interrupted due to connection issues, we will use this time to finalize our position on the LC comments.
Let's use the same agenda I posted for the last week call, we will briefly review the comments we discussed (no minutes are available due to IRC server connection problems) and continue the discussion of the remaining comments.

Thank you,
Vlad


From: public-webfonts-wg-request@w3.org [mailto:public-webfonts-wg-request@w3.org] On Behalf Of Levantovsky, Vladimir
Sent: Tuesday, January 11, 2011 2:46 PM
To: WOFF Working Group FONT
Subject: Conference call reminder and agenda for Wed., Jan. 12th

Hello WG,

Just a reminder that we will have our regularly scheduled telcon tomorrow, Wednesday Jan. 12th at:


US West Coast - 07:00

US East Coast - 10:00

Central Europe - 16:00
Japan - midnight



Zakim telephone bridge:

     +1.617.761.6200 (Boston) or

     +33.4.26.46.79.03 (Paris) or

     +44.203.318.0479 (London)

     with conference code 3668 ("FONT")


IRC channel is #webfonts, irc://irc.w3.org:6665/webfonts

or http://irc.w3.org/?channels=webfonts

The agenda is to discuss Last Call comments.

Let's start by reviewing the action items http://www.w3.org/Fonts/WG/track/actions/open, followed by the discussion of Last Call comments (the rest of this email is just a copy of the agenda I sent last week).

We have started the discussion last year http://dev.w3.org/webfonts/WOFF/DoC/issues-lc-2010.html, but there are some items left to be discussed.

Open issues:

-          I18n-ISSUE-2 (r12a): Why not using xml:lang? [WOFF]

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

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0093.html

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0094.html

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0100.html

-          I18n-ISSUE-4: Language tag references [WOFF]

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0102.html

-          I18n-ISSUE-5: Use of attributes for human readable text [WOFF]

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0104.html

-          I18N-ISSUE-6: Localization mechanism too restricted [WOFF]

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0105.html

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0108.html

-          I18N-ISSUE-7: Paragraphs and inline content [WOFF]

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0106.html

-          I18N-ISSUE-8: Direction attributes needed [WOFF]

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0107.html


Resolved issues (sanity check):

-          Conflicting statements on WOFF font table order

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

Resolution (see http://www.w3.org/2010/12/15-webfonts-minutes.html) - "J. Kew should ensure that sfnt ordering issue is resolved." Do we need to make any changes in the spec in light of http://lists.w3.org/Archives/Public/www-font/2010OctDec/0099.html?

-          I18N-ISSUE-9: OpenType feature preservation [WOFF]

http://lists.w3.org/Archives/Public/www-font/2010OctDec/0109.html

Resolution: in the informative note in section 5, where it mentions that UA "need not necessarily reconstitute the input font as a whole" and "may access individual tables directly as needed" - add a language with the warning that removing or ignoring any font table may result in breaking the functionality of the font, which may affect text rendering results and text layout.




Thank you,
Vladimir