- From: Phillips, Addison <addison@lab126.com>
- Date: Wed, 4 May 2011 07:41:07 -0700
- To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "www-style@w3.org" <www-style@w3.org>
Hi Daniel, I have added it to our agenda for our next teleconference (in about 20 minutes from now). Thanks, Addison Addison Phillips Globalization Architect (Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. > -----Original Message----- > From: public-i18n-core-request@w3.org [mailto:public-i18n-core- > request@w3.org] On Behalf Of Daniel Glazman > Sent: Wednesday, May 04, 2011 5:57 AM > To: Leif Halvard Silli > Cc: public-i18n-core@w3.org; www-style@w3.org > Subject: CSS WG request to I18N WG about Unicode Normalization in CSS 3 > Namespaces > > Leif, > > We're still at odds about this issue, and it blocks moving CSS 3 Namespaces to > the next stage along the REC track. > > 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. > > It seems to me the best summary of open options was a message by David > Baron [1]. > > [1] http://www.w3.org/mid/20090206225832.GA868@pickering.dbaron.org > > Thanks. > > </Daniel> > -- > W3C CSS WG, Co-chairman
Received on Wednesday, 4 May 2011 14:41:33 UTC