Confusability (Re: New version,
duerst at it.aoyama.ac.jp
Mon Jun 18 08:57:25 CEST 2007
I only started to talk about confusability because several of the
preceeding messages re. rule H were mentioning this, or things
very closely related.
I think it's wise not trying to address confusability in our work,
but if we indeed are doing so, I have no clue why anybody ever
brought up RFC 3743, which is about a method to address confusability
issues in CJKV ideograms, nothing else.
In general, I think we have to be careful to just outlaw confusability
as an issue. As an example, the effort to address issues surrounding
ZWNBSP are very much related to confusability: How can we make sure
that things that are perceived differently by script users can indeed
be represented without introducing additional confusability through
a back door.
At 14:18 07/06/18, Harald Alvestrand wrote:
>Martin Duerst wrote:
>> As already said, starting with Latin/Greek/Cyrillic in and
>> all the rest out of the STABLE (or whatever) category isn't
>> really appropriate. As an example, the current draft includes
>> all IPA characters
>> (024F..02AF ; ALWAYS # LATIN SMALL LETTER Y WITH STROKE..LATIN SMALL L)
>> Some of these, in particular U+0251 and U+0261, are indistinguishable
>> from a lower case 'a' or 'g' in an italic font.
>How can we rephrase text in idnabis-issues to make it clear that we ARE NOT solving confusability?
>Given that we have already concluded that outlawing the Greek omicron is impossible, we need to put this issue strictly out of scope as a selection criteria.
>(One version did put the IPA block as "out", but that was retracted after rather fierce opposition on this very list - see Ken Whistler's message of Dec 14, 2006, for instance).
#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp
More information about the Idna-update