[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 17 Mar 2015 19:51:58 +0100
From: Wermut <wermut@...il.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: libintl: stubs or working functions?
If you like to include these enum names, then they should also be
present in the source message. A typical translator, will not now all
enum names and the relationship with the msgid.
msgid "Permission denied"
msgstr "asdf@# lkjk^& (EPERM)"
should then be:
msgid "Permission denied (EPERM)"
msgstr "asdf@# lkjk^& (EPERM)"
On Tue, Mar 17, 2015 at 4:38 PM, Rich Felker <dalias@...c.org> wrote:
> On Tue, Mar 17, 2015 at 04:02:34PM +0100, Szabolcs Nagy wrote:
>> * ???????? <lynx@...server.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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
