mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: libintl: stubs or working functions?
Date: Tue, 17 Mar 2015 11:38:57 -0400	[thread overview]
Message-ID: <20150317153857.GZ23507@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150317150234.GA16260@port70.net>

On Tue, Mar 17, 2015 at 04:02:34PM +0100, Szabolcs Nagy wrote:
> * ???????? <lynx@sibserver.ru> [2015-03-17 13:59:16 +0700]:
> > Attached is my draft of translated strings you mentioned to Russian.
> > Some strings I borrowed from glibc, but only few of them (things like
> > "Broken pipe" and similar). Certain translations may be inaccurate, but
> > mostly if I did not know context I did an additional quick research by
> > grepping man pages. I think this should be additionally reviewed by
> > russian subscribers.
> > 
> 
> i'm a bit worried about translated error messages, it's always a pain
> to understand bugreports with those
> 
> can we include the enum name?
> like
> 
> msgid "Permission denied"
> msgstr "asdf@# lkjk^& (EPERM)"

I'm a bit undecided on this. It's reasonable to ask people reporting
bugs to set their locale temporarily to something the project
maintainers understand (typically English). It's also pretty easy to
grep the .po files or use Google Translate to figure out what the
message says.

If users with a non-English locale would find those kind of messages
helpful and non-obtrusive (is latin text in the middle of non-latin
obtrusive? perhaps, depending on font?), I'm not opposed to having
them, but I don't think they should be added against the desire of
most users out of an interest in making it easier to interpret bug
reports for us or for other upstreams.

Rich


  reply	other threads:[~2015-03-17 15:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  9:36 Рысь
2015-03-06 22:24 ` Rich Felker
2015-03-08  9:22   ` Рысь
2015-03-09  0:56     ` Rich Felker
2015-03-15 12:33       ` Рысь
2015-03-15 23:54         ` Rich Felker
2015-03-16  4:18           ` Рысь
2015-03-16 13:04             ` Szabolcs Nagy
2015-03-16 13:35               ` Szabolcs Nagy
2015-03-16 13:41             ` Szabolcs Nagy
2015-03-17  1:40               ` Рысь
2015-03-17  2:01                 ` Rich Felker
2015-03-17  6:59                   ` Рысь
2015-03-17 15:02                     ` Szabolcs Nagy
2015-03-17 15:38                       ` Rich Felker [this message]
2015-03-17 18:51                         ` Wermut
2015-03-18 14:10                         ` u-wsnj
2015-03-18 14:26                           ` Jens Gustedt
2015-03-19  8:29                           ` Justin Cormack
2015-03-19  8:55                             ` Jens Gustedt
2015-03-19 12:41                             ` u-wsnj
2015-03-19 17:25                               ` stephen Turner
2015-03-20  1:58                                 ` Weldon Goree
2015-03-20  3:11                                   ` Rich Felker
2015-03-19 17:54                               ` Rich Felker
2015-03-20  9:20                                 ` u-wsnj
2015-03-20 20:27                                   ` Rich Felker
2015-03-18  7:15                       ` Рысь
2015-03-24  3:59                     ` Рысь
2015-03-16  9:27           ` Szabolcs Nagy

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=20150317153857.GZ23507@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).