mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: iconv Korean and Traditional Chinese research so far
Date: Mon, 5 Aug 2013 08:46:18 -0400	[thread overview]
Message-ID: <20130805124618.GF221@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130804232816.dc30d64f61e5ec441c34ffd4f788e58e.313eb9eea8.wbe@email22.secureserver.net>

On Sun, Aug 04, 2013 at 11:28:16PM -0700, writeonce@midipix.org wrote:
>      -------- Original Message --------
>      Subject: Re: [musl] iconv Korean and Traditional Chinese research so far
>      From: Rich Felker <[1]dalias@aerifal.cx>
>      Date: Sun, August 04, 2013 10:00 pm
>      To: [2]musl@lists.openwall.com
>      Being that HKSCS is a standard, registered MIME charset and the cost
>      is only 10k, and that it seems necessary for real world usage in Hong
>      Kong, I think it's pretty obvious that we should support it. So I
>      think the question we're left with is whether the CP949 (MS encoding)
>      extension for Korean is important to support. The cost is roughly 37k.
> 
>    In case that helps: Korean typesetting packages for
>    TeX/LaTeX/XeLaTeX/LuaLaTeX do provide support for CP949.  This includes
>    the most recent versions; see, for instance:
>    [3]http://osl.ugr.es/CTAN/macros/luatex/generic/luatexko/luatexko-uhc2utf8.lua
>    There are also several packages that support UHC, which allegedly overlaps
>    with CP949:
>    [4]http://www.ctan.org/topic/korean
>    Best regards,
>    zg

Thanks. I've also seen a fair number of bug reports asking for
programs that lack it to add support, so it seems there is at least
some demand. I'm going to go ahead and look into whether there's a way
we could do slow but algorithmic conversion (e.g. are all the
characters outside the standard range allocated sequentually based on
the set missing from the standard range?) since that would make the
question of whether or not it's needed fairly irrelevant.

Rich


       reply	other threads:[~2013-08-05 12:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130804232816.dc30d64f61e5ec441c34ffd4f788e58e.313eb9eea8.wbe@email22.secureserver.net>
2013-08-05 12:46 ` Rich Felker [this message]
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

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=20130805124618.GF221@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).