From: Рысь <lynx@sibserver.ru>
To: musl@lists.openwall.com
Subject: Re: Locales with legacy codepages
Date: Wed, 17 Sep 2014 09:49:16 +0800 [thread overview]
Message-ID: <82301568-12d3-4b96-86f7-93529720bb20@email.android.com> (raw)
In-Reply-To: <20140916164346.GA23340@brightrain.aerifal.cx>
17 сентября 2014 г. 0:43:46 KRAT, Rich Felker <dalias@libc.org> пишет:
>On Tue, Sep 16, 2014 at 11:23:35AM +0800, Рысь wrote:
>> Hello,
>>
>> I am running a server which needs to speak with connected clients on
>> a legacy codepage (in particular, cp1251, widely used by Russian
>> people on Windows), and it has built-in gettext translation which
>> can be activated only by setting a proper locale.
>> However I don't know how musl supports locales with legacy
>> codepages, if even. I don't fully understand how such translations
>> work, so if there any ways to make legacy codepage locales work?
>>
>> On previous glibc system I started such server with
>> LC_ALL=ru_RU.CP1251 environment variable and appropriate locale was
>> defined with localedef.
>>
>> I have an option to convert all outgoing locale messages with iconv
>> if musl does not have such support.
>
>Using iconv is the the way to do this with musl. The only encoding
>supported as the native locale encoding is UTF-8 and there are no
>plans to change this. Since musl's iconv is not optimized for
>conversion _to_ legacy codesets, if you find this is a performance
>bottleneck, you might do better just to skip iconv and use your own
>conversion function that's specific to cp1251.
>
>Rich
Ok, I understand that my case is from those that should not happen in modern environments like systems based on musl libc. I will try iconv then.
Thanks!
prev parent reply other threads:[~2014-09-17 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 3:23 Рысь
2014-09-16 16:43 ` Rich Felker
2014-09-17 1:49 ` Рысь [this message]
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=82301568-12d3-4b96-86f7-93529720bb20@email.android.com \
--to=lynx@sibserver.ru \
--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).