W3C home > Mailing lists > Public > www-tag@w3.org > June 2011

Re: Unicode Normalization: request for TAG discussion and a finding

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 29 Jun 2011 18:33:52 +0200
To: "Phillips, Addison" <addison@lab126.com>
Cc: "www-tag@w3.org" <www-tag@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <irjm07l2ici4lb74rk83u8kcd34m5ege1a@hive.bjoern.hoehrmann.de>
* Phillips, Addison wrote:
>Therefore, we would like to request that TAG schedule time in about four
>weeks to review I18N WG's proposed recommendations concerning Unicode
>Normalization. We would like to have some time so that we can prepare
>materials for TAG including the options available.

Most helpful I think would be some user stories where people actually
run into Unicode Normalization problems in day to day practise with the
technologies under consideration. Someone posting on their blog how they
had trouble debugging why their CSS Selectors did not match because the
style sheet and the markup document used strings that looked the same
but were encoded differently, for instance. Or people with accounts they
created on one computer, but cannot log in to from another one.

So far I've largely not encountered people having problems with this,
and believe past requests for affected users didn't quite unearth any,
and I do not see any references to affected users in your references. I
would think we can't find large groups of people who are bitten by this
every day, there is not much of a problem to be solved, so we'd say it'd
be a good idea if browser's exposed their NFC/NFD implementations as API
and leave it that.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 29 June 2011 16:34:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:39 UTC