Re: Security Issues

• Previous message: Peter Constable: "RE: 'lower case a' and 'script a' in unicode"
• In reply to: Peter Constable: "RE: Security Issues"
• Next in thread: Mark Davis: "Re: Security Issues"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

That's exactly the kind of feedback I need, about possible problems with
different approaches. I hope that others also look at the charts and review
the implications for languages they are familiar with.

‎Mark

----- Original Message -----
From: "Peter Constable" <petercon@microsoft.com>
To: "Unicode Mailing List" <unicode@unicode.org>; "UnicoRe Mailing List"
<unicore@unicode.org>
Sent: Wednesday, March 23, 2005 17:55
Subject: RE: Security Issues

> > From: unicore-bounce@unicode.org [mailto:unicore-bounce@unicode.org]
> On
> > Behalf Of Mark Davis
>
>
> > A. Currently, compatibility decomposables are mapped to their NFKC
> form.
> > So
> > if you type in a half-width katakana form, it will map to the
> fullwidth
> > form. There is a proposal to simply forbid compatibility decomposable
> > instead of mapping them. Is this acceptable (eg in Japan)?
>
> This will mean that e.g. U+0E33 THAI CHARACTER SARA AM will not be
> usable in IDN. That could be a serious problem in Thailand. And three
> Lao characters that are commonly used would be blocked, which would be a
> problem in Laos.
>
>
>
> Peter Constable
>
>
>
>

• Next message: Jörg Knappen: "Finnish Romany"
• Previous message: Peter Constable: "RE: 'lower case a' and 'script a' in unicode"
• In reply to: Peter Constable: "RE: Security Issues"
• Next in thread: Mark Davis: "Re: Security Issues"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.5 : Thu Mar 24 2005 - 09:53:31 CST