apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Covener" <cove...@gmail.com>
Subject Re: Problem with iconv charsets...
Date Tue, 26 Jun 2007 01:19:24 GMT
On 6/25/07, William A. Rowe, Jr. <wrowe@rowe-clan.net> wrote:
>  * At run-time this should probably be determined by parsing first the
>    LC_CTYPE, or LC_ALL in it's absense, or the fallback to the LANG
>    envvar if neither LC_ variable is defined.  The codepage follows
>    the period, e.g. LANG=en_US.UTF-8 would be parsed as 'UTF-8'.

Wouldn't runtime checks would mean xlate/xlate.c needs to find a new
way to figure out what the codepage of the source code was (to
translate compiled-in strings)?

Perhaps APR_DEFAULT_CHARSET could be split into two different
identifiers APR_CURRENT_CHARSET/APR_BUILD_CHARSET that xlate callers
would have to think about.

-- 
Eric Covener
covener@gmail.com

Mime
View raw message