Re: [idn] Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt (in ksc5601-1987)

["Doug Ewell" <dewell@adelphia.net>]

Soobok Lee <lsb at postel3 dot postel dot co dot kr> wrote:

> What if  proper and stable implementation of legacy encodings in
> IDNA is not a tangilbe object due to their frequent updates/
> additions ?

How "frequent" are updates to legacy encodings, or updates to the
mapping tables between legacy encodings and Unicode?

As for additions, they shouldn't cause a problem anyway, because they
don't break existing legacy-to-Unicode mappings.  An often-mentioned
case of adding to a legacy encoding was when Microsoft retrofitted
U+20AC EURO SIGN onto their Windows code pages (mostly at previously
unassigned code position 0x80).  The only people who suffered at all
were the ones who thought "unassigned" somehow meant that they should
map 0x80 to U+0080.  Everyone else made it just fine.

-Doug Ewell
 Fullerton, California
 (would prefer to receive only one copy of these messages)