[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] stringprep comment 5: hangul conjoining sequence

To: idn@ops.ietf.org
Subject: Re: [idn] stringprep comment 5: hangul conjoining sequence
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
Date: Mon, 11 Feb 2002 21:48:32 +0000
In-reply-to: <001201c1b322$0d156350$d5d61081@chalmers95a69n>
References: <0c0601c1b316$dfc16350$2b19fea9@temp> <001201c1b322$0d156350$d5d61081@chalmers95a69n>
Reply-to: IETF idn working group <idn@ops.ietf.org>
User-agent: Mutt/1.3.25i

Kent Karlsson <kentk@md.chalmers.se> wrote:

> Compatibility (non-conjoining) Hangul letters are best prohibited.

Stringprep does normalization before prohibition, so prohibiting
compatibility characters would have no effect.  After the normalization
step, there are no compatibility characters in the string.

A trick you could play, however, would be to map the characters in
question to an arbitrary prohibited character that survives the
normalization step (like U+0000).

AMC

Follow-Ups:
- RE: [idn] stringprep comment 5: hangul conjoining sequence
  - From: "Kent Karlsson" <kentk@md.chalmers.se>

References:
- [idn] stringprep comment 5: hangul conjoining sequence
  - From: "Soobok Lee" <lsb@postel.co.kr>
- RE: [idn] stringprep comment 5: hangul conjoining sequence
  - From: "Kent Karlsson" <kentk@md.chalmers.se>

Prev by Date: Re: [idn] last call reminder - Hebrew
Next by Date: Re: Inputting mixed SC/TC (Re: [idn] A question...)
Previous by thread: RE: [idn] stringprep comment 5: hangul conjoining sequence
Next by thread: RE: [idn] stringprep comment 5: hangul conjoining sequence
Index(es):
- Date
- Thread