See also: IRC log
close action-282
<trackbot> Closed action-282.
close action-283
<trackbot> Closed action-283.
<r12a> http://www.w3.org/International/track/actions/open
close action-285
<trackbot> Closed action-285.
JcK: martin duerst and I talking
to dennis
... about punycode and IDNA in HTML5
... much confusion
<r12a> Form input type=email [1]
<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> 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> http://rishida.net/scripts/block/balinese
richard: can see all characters
in a Unicode block
... more to come
<r12a> 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.)
https://lists.w3.org/Archives/Member/member-i18n-core/2014Feb/0015.html
https://www.w3.org/2002/09/wbs/33280/mathml3-2e/
> http://www.w3.org/TR/2014/PER-MathML3-20140211/ > http://www.w3.org/TR/2014/PER-xml-entity-names-20140211/
addison: probably should review entity names
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 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].
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)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16970
ISSUE-105?
<trackbot> ISSUE-105 -- Compatibility caseless matching -- open
<trackbot> http://www.w3.org/International/track/issues/105
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 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]
addison: need to fix poll
... use UTC or fix the poll to do time zones
... FPWD in about eight weeks?