Internationalization WG TPAC -- 02 Nov 2012

<scribe> Scribe: Addison Phillips

<scribe> ScribeNick: aphillip

http://lists.w3.org/Archives/Public/www-international/2012OctDec/0036.html

HTML / I18N meeting notes review

richard: don't think ruby should be marked at risk
... some ideas that would be great to implement
... but not in the time needed
... and maybe not defined by then either
... need ruby, double-sided ruby
... so need to move forward

norbert: hoping for some quick way to fix it

richard: hoping what fantasai produces would be on top of current implementation
... extension spec would be an alternative, but not removing anything
... should say "disagree that we agree with 'at risk'"
... if can't be produced in current time frame, expect that current design is used
... want double-sides in html5
... without being at risk

fantasai: think we can get a draft out by end of the year
... with double-sided
... compatible with what is already deployed
... nesting might be at risk

richard: mobilizing folks to work on ruby
... fantasai should be hooked up with them
... outline soonest would be good

fantasai: can make outline by end of month-ish
... easier to explain in person than via email

(discussion of cast of implementers)

richard: key thing: don't want to end up with no complex ruby
... must get over hurdles with html5 and html.next

Norbert: local/floating time implementations
... issue 97 needs more text (locale negotiation)

addison: read bcp47 as rfc6067
... ?

richard: said "rest of WG doesn't agree me with, but think use calendar attr"
... didn't go into details
... will track cameron down

[[ WG heads off to meet with XLIFF folk ]]

<r12a> addison, you there?

<r12a> hey addison !

howdy

ready for more?

<r12a> yep

case sensitivity in CSS

Norbert: (summarizes)
... Tab prefers ASCII-sensitivity only
... our preference seems to be Unicode case folding
... has a few problems for Lt and Turkish

richard: is there is a possibility that we don't do case-insensitive stuff at all
... name counter styles need to be case-insensitive for existing items
... so liimit to just those defined by CSS?
... or extend to ASCII in general? Or to everything?

<Norbert> CSS has already decided:

<Norbert> http://lists.w3.org/Archives/Public/www-style/2012Aug/0899.html

richard: case insensitivity, with type to be defined
... minimum is only existing items are case insensitive
... Tab's preference was ASCII case insensitive
... implication was make everything insensitive
... if use case folding for full Unicode range, then turkic languages and lithuanian have problems

addison: ASCII case insense sometimes a problem in Turkish too
... users never see the case folded value?

norbert: some way to access it

koji: case folding slow?
... incomplete by design
... don't think it makes sense

richard: HIT -> hit but not h\u0131t

addison: that case never works with ASCII case-insensitive either

koji: support ASCII case insensitivty only for backwards compatibility
... not much use anyway, slightly better performance

rÖman vs. RÖMAN

Deutschland matches deutschland

but Österreich doesn't match....

(involved discussion)

consensus: full Unicode case folding without special cases

scribe: and add a note for Turkic languages