- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Sun, 29 Jun 2014 09:52:08 -0700
- To: Koji Ishii <kojiishi@gluesoft.co.jp>
- Cc: Jonathan Kew <jfkthame@gmail.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Anne van Kesteren <annevk@annevk.nl>, Zack Weinberg <zackw@panix.com>, fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
On Jun 29, 2014, at 4:51 AM, Koji Ishii <kojiishi@gluesoft.co.jp> wrote: >> Now, I suppose we could specify (somewhere - though I don't see how this would fall within the scope of CSS) that text processes such as searching, sorting, indexing, etc., within the web platform should base their behavior *not* on the (normative) Unicode character properties, but on something else that we specify independently. But IMO this would be a *REALLY* bad idea. There's a standard; we should follow it. >> >> This isn't just about behavior within the web platform, but also consistency and interoperability with text processing in other environments. The more closely we all keep to the relevant standards, the better for everyone. > > First of all, CSS defines surrendering, so searching, sorting, indexing, etc. are out of scope. Second. As far as I understand, there¡¯s nothing in Unicode stating higher-level protocols should render control characters, though it may also not recommend not to. In that case, we¡¯re not violating the normative Unicode character properties at all. I agree. If there is a browser that can't find a word because it has an invisible control character in it, then it should be handled by filing a bug report to the browser maker for its silly usability problem, but it is not in scope for CSS to dictate that.
Received on Sunday, 29 June 2014 16:52:37 UTC