mailing list of musl libc
 help / color / mirror / code / Atom feed
From: LM <lmemsm@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Iconv and old codepages
Date: Wed, 26 Jun 2013 14:39:59 -0400	[thread overview]
Message-ID: <CAFipMOG1TjuWHowjSJQER=jbv9W5qVNhSMZY3_GkHK8euVBrVQ@mail.gmail.com> (raw)
In-Reply-To: <20130627021539.76b69eea@sibserver.ru>

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

On Wed, Jun 26, 2013 at 2:15 PM, orc <orc@sibserver.ru> wrote:

> I also noticed alternative libs thread and corresponding wiki page.
> Does someone know lightweight iconv replacement as a temporary measure
> (other than libiconv for example)?
>

Thought I had the Apache Portable Runtime project listed on the
alternatives page.  Will update that.
APR has a version of iconv.

BSD systems have their own implementations of iconv.  Haven't found a
standalone version.  There may be some code in obase (listed on wiki).
There's mention of a BSD licensed libiconv (
https://wiki.freebsd.org/G%C3%A1borSoC2009 ) as part of Citrus (which was
also supposed to have a gettext alternative).  The web page on Citrus is at
http://citrus.bsdclub.org/ but I haven't found the source code for the
project.  ICU ( http://site.icu-project.org/) provides uconv instead of
iconv.  On Windows, they typically use GNU libiconv since iconv isn't part
of the C runtime library.

If anyone thinks these (or possibly some other alternatives) are useful, I
can add the links for them to the wiki.  Please let me know if they any of
them don't appear too bloated and would be worth adding.

Thanks.
Laura
http://www.distasis.com/cpp

[-- Attachment #2: Type: text/html, Size: 1714 bytes --]

  parent reply	other threads:[~2013-06-26 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 18:15 orc
2013-06-26 18:34 ` Rich Felker
2013-06-26 18:56   ` orc
2013-06-26 18:39 ` LM [this message]
2013-06-26 18:47   ` Rich Felker
2013-06-27  0:37   ` Isaac
2013-06-27  1:25     ` Luca Barbato

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='CAFipMOG1TjuWHowjSJQER=jbv9W5qVNhSMZY3_GkHK8euVBrVQ@mail.gmail.com' \
    --to=lmemsm@gmail.com \
    --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).