Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 5 Aug 2013 15:12:47 -0400
From: Rich Felker <>
Subject: Re: Re: iconv Korean and Traditional Chinese research so far

On Mon, Aug 05, 2013 at 04:28:32PM +0800, Roy wrote:
> Since I'm a Traditional Chinese and Japanese legacy encoding user, I
> think I can say something here.
> [...]
> There is another Big5 extension called Big5-UAO, which is being used
> in world's largest telnet-based BBS called "".
> It has two tables, one for Big5-UAO to Unicode, another one is
> Unicode to Big5-UAO.
> Which extends DBCS lead byte to 0x81.

OK, I've been trying to do some research on this and I turned up:

My impression (please correct me if I'm wrong) is that you can't use
Big5-UAO as the system encoding on modern versions of Windows (just
ancient ones where you install unmaintained third-party software that
hacks the system charset tables) and that it's not supported in GNU
libiconv. If this is the case, and especially if Big5-UAO's main use
is on a telnet-based BBS where everybody is using special telnet
clients that have their own Big5-UAO converters, I'd find it really
hard to justify trying to support this. But I'm open to hearing
arguments on why we should, if you believe it's important.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.