From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Re: iconv Korean and Traditional Chinese research so far
Date: Mon, 5 Aug 2013 15:12:47 -0400 [thread overview]
Message-ID: <20130805191246.GM221@brightrain.aerifal.cx> (raw)
In-Reply-To: <op.w1b4hubbdyj81a@monster.itedn32a.localdomain>
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 "ptt.cc".
>
> It has two tables, one for Big5-UAO to Unicode, another one is
> Unicode to Big5-UAO.
> http://moztw.org/docs/big5/table/uao250-b2u.txt
> http://moztw.org/docs/big5/table/uao250-u2b.txt
>
> Which extends DBCS lead byte to 0x81.
OK, I've been trying to do some research on this and I turned up:
http://lists.w3.org/Archives/Public/public-html-ig-zh/2012Apr/0061.html
http://lists.gnu.org/archive/html/bug-gnu-libiconv/2010-11/msg00007.html
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.
Rich
next prev parent reply other threads:[~2013-08-05 19:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 16:51 Rich Felker
2013-08-04 22:39 ` Harald Becker
2013-08-05 0:44 ` Szabolcs Nagy
2013-08-05 1:24 ` Harald Becker
2013-08-05 3:13 ` Szabolcs Nagy
2013-08-05 7:03 ` Harald Becker
2013-08-05 12:54 ` Rich Felker
2013-08-05 0:49 ` Rich Felker
2013-08-05 1:53 ` Harald Becker
2013-08-05 3:39 ` Rich Felker
2013-08-05 7:53 ` Harald Becker
2013-08-05 8:24 ` Justin Cormack
2013-08-05 14:43 ` Rich Felker
2013-08-05 14:35 ` Rich Felker
2013-08-05 0:46 ` Harald Becker
2013-08-05 5:00 ` Rich Felker
2013-08-05 8:28 ` Roy
2013-08-05 15:43 ` Rich Felker
2013-08-05 17:31 ` Rich Felker
2013-08-05 19:12 ` Rich Felker [this message]
2013-08-06 6:14 ` Roy
2013-08-06 13:32 ` Rich Felker
2013-08-06 15:11 ` Roy
2013-08-06 16:22 ` Rich Felker
2013-08-07 0:54 ` Roy
2013-08-07 7:20 ` Roy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130805191246.GM221@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).