Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 18 Sep 2012 22:59:56 -0400
From: Rich Felker <>
Subject: Re: R/GNU S: up with a couple hitches...

On Tue, Sep 18, 2012 at 08:19:17PM -0400, wrote:
> BTW, Rich, here's what that page says about iconv:
> | The R usage requires iconv to be able to translate between "latin1"
> | and "UTF-8", to recognize "" (as the current encoding) and "ASCII",
> | and to translate to and from the Unicode wide-character formats
> | "UCS-[24][BL]E"
> How much of this should musl support?

I've never heard of using "" (blank string) to mean "the current
encoding". If it's documented usage for glibc, it must be buried
somewhere in the docs; it's definitely not a standard usage. The
standard way to get the locale's encoding is nl_langinfo(CODESET); on
any good implementation it will be accepted as an argument to

As for the others (UTF-8, latin1, UCS-[24][BL]E, and ASCII) they
should all be accepted just fine. But it would probably be smarter to
use the standard name for latin1, ISO-8859-1.


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.