From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Draft proposed locale changes
Date: Mon, 5 Mar 2018 13:54:00 -0500 [thread overview]
Message-ID: <20180305185400.GF1436@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAF1WSuzYsm81k=oCz9_O9+2_h5nLuQGzuZCEMb3Hg=dzb6tt5A@mail.gmail.com>
On Mon, Mar 05, 2018 at 09:42:49PM +0300, Konstantin P. wrote:
> Can you publish official po file for musl after proposed changes?
Do you mean a po template (pot) file showing what needs to be
translated? Or an example po file for a particular locale (maybe just
English preserving the error message text, if we go with "option zero"
and strip the English error text out of libc)?
Rich
next prev parent reply other threads:[~2018-03-05 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 18:39 Rich Felker
2018-03-05 18:42 ` Konstantin P.
2018-03-05 18:54 ` Rich Felker [this message]
2018-03-05 20:00 ` Konstantin P.
2018-03-05 21:25 ` Rich Felker
2018-03-06 1:54 ` Konstantin P.
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=20180305185400.GF1436@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).