On 5/25/07, Adam Olsen <[EMAIL PROTECTED]> wrote: > On 5/25/07, Jim Jewett <[EMAIL PROTECTED]> wrote: > > On 5/25/07, Adam Olsen <[EMAIL PROTECTED]> wrote: > > > If we allowed an underscore as a mixed-script separator > > > (allowing "def get_原料(self):"), does this let us get away > > > with otherwise banning mixed-scripts?
... > Indeed, the whole-script confusables does create significant > holes, but I think the best solution is still to ban mixed-scripts > and accept that it's only a "75% solution". Using an "I'm > expecting cyrillic" flag makes it harder for those who need > cyrillic AND still leaves them vulnerable to the same problem > we're trying to protect ourselves from. hmm... I had thought they should either not include the confusable letters, or use different fonts -- whatever they normally do. But I suppose using an _ separator could still be a useful crutch. Whether it is useful enough ... I'll let others chime in. > A more extreme solution would be to introduce a symbol type that > converts that converts whole-script confusables to a canonical > form The unicode consortium recommends against this. I'm not sure if it is just a presentation issue, or concerns about compatibility; the "confusables" lists are explicitly allowed to change. -jJ _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
