Tables and contextual rule for Katakana middle dot
vint at google.com
Wed Apr 8 00:53:18 CEST 2009
I would imagine, perhaps naively, that punctuation ought generally to
be disallowed and that exceptions should be handled as exceptions for
what I hope would be compelling reasons.
1818 Library Street, Suite 400
Reston, VA 20190
vint at google.com
On Apr 7, 2009, at 6:50 PM, Eric Brunner-Williams wrote:
> Mark Davis wrote:
>> There are other dot-like characters that are far more visually
>> to dot, like Arabic zero.
>> عربي٠عربي.com <http://xn--ngbazb1bc2jd8q.com>
>> عربي.عربي.com <http://xn--ngbrx4e.xn--ngbrx4e.com>
>> But more importantly, there is a real lack of data presented for
>> kinds of positions. When excluding characters that are in common use
>> on the basis of visual confusability, such as Katakana middle dot,
>> let's see some real data on what a difference this would make in
>> overall visual confusability of characters. Of all of the visually
>> confusable characters in PVALID, what would be the percentage
>> difference but adding or removing Katakana middle dot? And why do
>> people think this can't be handled by exactly the same mechanisms
>> programs have to handle the visually confusable characters that *are*
> I applied the no-punctuation principle when looking at U+166E.
> it (a very small baseline aligned "x") really doesn't look like a
> separator, and there really is no harm in a Cree full stop appearing
> within a Cree character string, creating labels of the form
> So, I have some second thoughts about DISALLOWED for U+166E. The case
> for PVALID is ... well ... inventive, not compelling.
> For U+166D, a symbol, I'm willing to keep it DISALLOWED, for several
> I wrote this because I think you're correctly asking what's really
> confusable, and the question is larger than just Katakana middle dot.
> Idna-update mailing list
> Idna-update at alvestrand.no
More information about the Idna-update