- From: Richard Ishida <ishida@w3.org>
- Date: Thu, 20 Feb 2014 11:22:36 +0000
- To: www International <www-international@w3.org>
http://www.w3.org/2014/02/13-i18n-minutes.html
Text excerpt follows:
Internationalization Working Group Teleconference
13 Feb 2014
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2014Feb/0016.html
See also: [3]IRC log
[3] http://www.w3.org/2014/02/13-i18n-irc
Attendees
Present
Addison, Richard, JcK, Mati
Regrets
felix
Chair
Addison Phillips
Scribe
Addison Phillips
Contents
* [4]Topics
1. [5]Agenda
2. [6]Action Items
3. [7]Info Share
4. [8]RADAR
5. [9]Counter Styles
6. [10]Info Share additional
7. [11]HTML5 caseless matching
8. [12]charmod
9. [13]AOB?
* [14]Summary of Action Items
__________________________________________________________
Agenda
Action Items
close action-282
<trackbot> Closed action-282.
close action-283
<trackbot> Closed action-283.
<r12a> [15]http://www.w3.org/International/track/actions/open
[15] http://www.w3.org/International/track/actions/open
close action-285
<trackbot> Closed action-285.
Info Share
JcK: martin duerst and I talking to dennis
... about punycode and IDNA in HTML5
... much confusion
<r12a> Form input type=email [1]
[1] http://www.w3.org/
<r12a>
<r12a> Constraint validation: While the user interface is
representing input
<r12a> that the user agent cannot convert to punycode, the
control is suffering
<r12a> from bad input.
<r12a> ]]
richard: small item in the interim
<r12a> [16]http://rishida.net/writing
[16] http://rishida.net/writing
richard: as part of rewriting my site, I made one or two new
things
... one that is coming is tibetan layout requirement document
... if you look at above link
<r12a> [17]http://rishida.net/scripts/block/balinese
[17] http://rishida.net/scripts/block/balinese
richard: can see all characters in a Unicode block
... more to come
<r12a> [18]http://rishida.net/scriptlinks
[18] http://rishida.net/scriptlinks
richard: another thing more useful (?)
... is above link
... if you select from lists
... and you get links to various resources about each script
(articles, fonts, etc.)
RADAR
[19]https://lists.w3.org/Archives/Member/member-i18n-core/2014F
eb/0015.html
[19]
https://lists.w3.org/Archives/Member/member-i18n-core/2014Feb/0015.html
[20]https://www.w3.org/2002/09/wbs/33280/mathml3-2e/
[20] https://www.w3.org/2002/09/wbs/33280/mathml3-2e/
> [21]http://www.w3.org/TR/2014/PER-MathML3-20140211/ >
[22]http://www.w3.org/TR/2014/PER-xml-entity-names-20140211/
[21] http://www.w3.org/TR/2014/PER-MathML3-20140211/
[22] http://www.w3.org/TR/2014/PER-xml-entity-names-20140211/
addison: probably should review entity names
Counter Styles
[23]http://www.w3.org/International/track/products/46
[23] http://www.w3.org/International/track/products/46
richard: believe these can be all closed
... hebrew number converter (which mati commented on)
... if you got to 2500 or something
... you add extra character until you get to quite a few of
these
... kind of unhelpful
... mati proposed alternative
... to go in our Note
... solution was to limit number of counters to 2000 to prevent
over-long strings
... actually, 3 browsers have implementred
... what mati suggested
... and none have done what is in spec
... so wrote to Tab to change spec
... and it's done now
... only open item is one of the complicated Ethiopian styles
won't produce a counter for "1"
... haven't had a response from Tab yet
... otherwise close them all
... keep issue 282
<scribe> ACTION: richard: inform CSS that we are satisfied with
counter styles now (save for issue 282) [recorded in
[24]http://www.w3.org/2014/02/13-i18n-minutes.html#action01]
<trackbot> Created ACTION-286 - Inform css that we are
satisfied with counter styles now (save for issue 282) [on
Richard Ishida - due 2014-02-20].
Info Share additional
richard: number of issues with W3C test framework
... where our tests currently live
... lack of maintenance
... could dissappear
... framework fails on IE
... doesn't separate opera from chrome
... etc. etc.
... made a new architecture
(discussion of a private link)
HTML5 caseless matching
[25]https://www.w3.org/Bugs/Public/show_bug.cgi?id=16970
[25] https://www.w3.org/Bugs/Public/show_bug.cgi?id=16970
ISSUE-105?
<trackbot> ISSUE-105 -- Compatibility caseless matching -- open
<trackbot> [26]http://www.w3.org/International/track/issues/105
[26] http://www.w3.org/International/track/issues/105
[27]http://people.mozilla.org/~jdaggett/tests/radiobuttonnameca
se.html
[27]
http://people.mozilla.org/~jdaggett/tests/radiobuttonnamecase.html
<scribe> ACTION: addison: pull together wiki page of the
caseless matching problem, mining the past conversation with
CSS plus charmod plus bug 16970 [recorded in
[28]http://www.w3.org/2014/02/13-i18n-minutes.html#action02]
<trackbot> Created ACTION-287 - Pull together wiki page of the
caseless matching problem, mining the past conversation with
css plus charmod plus bug 16970 [on Addison Phillips - due
2014-02-20].
However, Anne, all of those identifiers are themselves ASCII
only. That's what makes ACI acceptable there. For Unicode name
spaces, I think I18N rightly would insist that, if case
sensitive is not used, UCI is the the next appropriate choice
and ACI I'd wholly unacceptable. However, case sensitive is
usually our first recommendation and, as you say, recommending
lowercase and consistent normalization. What would we be
breaking if we did that though? Like[CUT]
charmod
addison: need to fix poll
... use UTC or fix the poll to do time zones
... FPWD in about eight weeks?
AOB?
Summary of Action Items
[NEW] ACTION: addison: pull together wiki page of the caseless
matching problem, mining the past conversation with CSS plus
charmod plus bug 16970 [recorded in
[29]http://www.w3.org/2014/02/13-i18n-minutes.html#action02]
[NEW] ACTION: richard: inform CSS that we are satisfied with
counter styles now (save for issue 282) [recorded in
[30]http://www.w3.org/2014/02/13-i18n-minutes.html#action01]
[End of minutes]
Received on Thursday, 20 February 2014 11:23:05 UTC