- From: aphillips via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Apr 2016 22:38:22 +0000
- To: public-i18n-archive@w3.org
@johnwcowan That's possibly true, save that that people are frequently lazy or impeded in typing. There is a difference in perceived code points in the examples you use (even if, say, the Latin/Cyrillic pair look the same, they are neither the same code points nor the same perceived characters). Users would not expect to find Latin words typing Cyrillic letters, no matter what their shape. I'll admit that I was being clever in my locution, but I was also careful to use the ZWNJ-free string as the search term. If you do a "find" on this page in your browser, typing "die" finds "bodies" and (unless you do something about matching case), typing "DIE" finds "bodies" too. Customers expect matches to be more permissive under certain circumstances (such as find) as compared to algorithmic access methods (where rigor is called for). We also suggest elsewhere in the document that when users expend more effort on input that their input should be taken into account. If I type the ZWNJ (or VS or whatever) in as the "find" term, only strings actually containing ZWNJ et al should be found. -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/charmod-norm/issues/44#issuecomment-206017870 using your GitHub account
Received on Tuesday, 5 April 2016 22:38:23 UTC