From: Рысь <lynx@sibserver.ru>
To: musl@lists.openwall.com
Subject: Re: Message localization [Was: Re: [musl] Adjustments to roadmap]
Date: Mon, 7 Sep 2015 20:51:19 +0700 [thread overview]
Message-ID: <20150907205119.5c6812e4@r2lynx> (raw)
In-Reply-To: <20150902022856.GF17773@brightrain.aerifal.cx>
On Tue, 1 Sep 2015 22:28:56 -0400
Rich Felker <dalias@libc.org> wrote:
> On Wed, Sep 02, 2015 at 09:26:57AM +0700, Рысь wrote:
> > On Tue, 1 Sep 2015 00:47:30 -0400
> > Rich Felker <dalias@libc.org> wrote:
> >
> > > On Tue, Sep 01, 2015 at 11:26:55AM +0700, Рысь wrote:
> > > > This is what I get when running musl 1.1.11 without patches
> > > > (untouched):
> > > >
> > > > % MUSL_LOCPATH=/tmp/l LC_ALL=ru_RU ./lib/libc.so ../date
> > > > Tue Sep 1 11:22:31 2015
> > > >
> > > > I attached strace output as well as compiled ru_RU data.
> > >
> > > The mo file is broken; it looks like it was produced with the
> > > buggy msgfmt from the sabotage repo that outputs the strings in
> > > the order they were in the source, rather than sorting them. If
> > > you write a perl/awk/whatever script to pre-sort them you should
> > > be able to get by with this msgfmt; otherwise, you could use the
> > > GNU version or try the other branch of gettext-tiny.
> >
> > How to sort strings (or there is a script I don't know about)?
> > Because I can't use gnu version, and using gettext-tiny which was
> > not updated for 3 years. Or there is another version with this
> > feature implemented?
>
> It was in gettext-tiny but then reverted because making msgfmt work
> exposed other limitations in it. You can check out the
> second-to-newest version or the 'full' branch that still has a working
> version.
>
> Rich
Many Thanks!
Sorry for late feedback, now only had time to test it. It works!
% MUSL_LOCPATH=/tmp/l LC_ALL=ru_RU ./date
Пн Сен 7 20:47:05 2015
Meow!!
I guess there is a root of lack of translation in my case: many
programs use msgfmt and friends to make .mo from .po. So if I
want to solve the problem, I must "update" gettext-tiny then rebuild
all affected software. Am I right?
next prev parent reply other threads:[~2015-09-07 13:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 2:43 Adjustments to roadmap Rich Felker
2015-08-28 3:38 ` Khem Raj
2015-08-28 4:21 ` Rich Felker
2015-08-28 6:57 ` Вася Бойцов
2015-08-28 12:47 ` Rich Felker
2015-08-28 12:16 ` Justin Cormack
2015-08-28 7:24 ` u-wsnj
2015-08-28 11:39 ` Рысь
2015-08-28 17:18 ` Rich Felker
2015-08-30 4:21 ` Рысь
2015-08-30 4:46 ` Rich Felker
2015-08-30 5:13 ` Рысь
2015-08-30 5:30 ` Rich Felker
2015-08-30 9:00 ` Szabolcs Nagy
2015-08-30 17:09 ` Rich Felker
2015-08-30 17:45 ` u-wsnj
2015-08-30 17:13 ` Рысь
2015-08-30 17:38 ` Rich Felker
2015-08-30 5:18 ` Рысь
2015-08-30 5:31 ` Rich Felker
2015-08-30 17:21 ` Рысь
2015-08-30 19:29 ` Message localization [Was: Re: [musl] Adjustments to roadmap] Rich Felker
2015-09-01 4:26 ` Рысь
2015-09-01 4:47 ` Rich Felker
2015-09-02 2:26 ` Рысь
2015-09-02 2:28 ` Rich Felker
2015-09-07 13:51 ` Рысь [this message]
2015-09-08 15:18 ` Rich Felker
2015-08-31 7:09 ` Adjustments to roadmap Rich Felker
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=20150907205119.5c6812e4@r2lynx \
--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).