trackbox, setup teleconference

<scribe> Scribe: Addison Phillips

<scribe> ScribeNick: aphillip

<r12a> hello john

<r12a> are you joining our call or just tracking ?

Minutes and Agenda review

richard: review documents that need reviewing

Action Items

<r12a> http://www.w3.org/International/track/actions/open

close ACTION-5

<trackbot> ACTION-5 Check on HTML5 language tag validator and send any comments closed

Check into digit shaping with CSS

close ACTION-35

<trackbot> ACTION-35 Add comment to bug 10830 supporting opening of it closed

Talk with Bert about how to deal with change marks in Ruby spec

Propose move of Ruby CSS spec to WD on agenda for CSS WG

next week

Info Share

richard: new version of JLReq is nearing completion

(discussion of where the English is coming from, status of draft, etc.)

CSS and Unicode Normalization

http://lists.w3.org/Archives/Public/public-i18n-core/2011AprJun/0061.html

Could the I18N Working Group, and that's an official request from the CSS WG here, please tell us exactly what we should add to the spec wrt Unicode normalization? I respectfully suggest you write the prose for us, given the complexity of the issue. Of course, your answer will go through our WG and in particular browser implementors, since this has potential huge impacts on performance.

http://www.w3.org/mid/20090206225832.GA868@pickering.dbaron.org

addison: brief intro...

richard: for normalization to be effective, the thing that uses CSS has to have text in the same normalization form
... so question in my mind is "yes, it's good to have a standard form, but go ahead and normalize"
... "or do we have to wait on content such as HTML5"

addison: two cases: (a) transcoding and (b) do selectors normalize to match

norbert: also consider ecmascript

addison: require or not normative normalization for selectors?
... base+combining and precomposed values want to be selected together
... problem is: this imposes normalization required on the DOM

<p class="a\u0301">

class = (precomposed)

(review david's summary)

addison: what would (a) we prefer the solution to be? and (b) what is acceptable?
... would #4 be preferable (although maybe not possible)?

richard: probably not realistic

addison: isolated for implementation (and thus possible), but might be hairy to test

<kojiishi> http://blog.antenna.co.jp/PDFTool/archives/2006/02/pdf_41.html

koji: concerned that we restrict this only to non-displayed content
... for comparison
... because it could affect the glyphs

addison: early or late normalization is the difference?
... are we close to something?

norbert: anyone studied how common?

addison: only this one very isolated corner of the Web has normalization?
... although this is where CSS, JS and HTML come together

richard: need to write it down

david: css has a wiki page of their own?
... will put URI on members list if/when find it

<David> http://www.w3.org/wiki/I18N/CanonicalNormalization

<scribe> ACTION: addison: draft a summary for review next week responding to the CSS selectors request outlining potential response(s) [recorded in http://www.w3.org/2011/05/04-i18n-minutes.html#action01]

<trackbot> Created ACTION-39 - Draft a summary for review next week responding to the CSS selectors request outlining potential response(s) [on Addison Phillips - due 2011-05-11].

AOB?

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: Addison Phillips
Found ScribeNick: aphillip
Default Present: Addison_Phillips, Richard, +44.141.888.aaaa, David, kojiishi_, +1.415.885.aabb, Norbert, [Microsoft], Gwyneth
Present: Addison_Phillips Richard +44.141.888.aaaa David kojiishi_ +1.415.885.aabb Norbert [Microsoft] Gwyneth
Regrets: Felix
Agenda: http://lists.w3.org/Archives/Member/member-i18n-core/2011May/0000.html
Got date from IRC log name: 04 May 2011
Guessing minutes URL: http://www.w3.org/2011/05/04-i18n-minutes.html
People with action items: addison