mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: Re: libintl: stubs or working functions?
Date: Thu, 19 Mar 2015 08:29:41 +0000	[thread overview]
Message-ID: <CAK4o1Wwmpe+E38YU53eXEZ1TPu8PZVcej1XJovZV7ewmN=ogAA@mail.gmail.com> (raw)
In-Reply-To: <20150318141020.GH23636@example.net>

[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]

On Mar 18, 2015 11:10 PM, <u-wsnj@aetey.se> wrote:
>
> On Tue, Mar 17, 2015 at 11:38:57AM -0400, Rich Felker wrote:
> > > 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.
>
> As an application user I am motivated to be able to report problems as
> exactly as possible.
>
> As a "library user" (either as a packager, application developer,
> support staff or something else) I find it unfortunate/disturbing to
> have to "guess" the actual error name, even when a message is in a well
> known language like English.
>
> This is mostly very easy but sometimes less certain, with less usual
> errors and/or different C libraries which may contain different English
> strings/spellings too.
>
> An error-specific indentifier should IMHO always be present
> in every message, not translated to a "natural" language with the
> intention to be translatable back with more or less pain.
>
> IOW I'd like to always have the canonical errname in the output,
> in English too.
>
> This would make error messages easier and more robust to interpret.
>

Would it make sense for the canonical names to be the output in the C
locale and English if you set an English locale?

Justin

[-- Attachment #2: Type: text/html, Size: 2390 bytes --]

  parent reply	other threads:[~2015-03-19  8:29 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
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 [this message]
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='CAK4o1Wwmpe+E38YU53eXEZ1TPu8PZVcej1XJovZV7ewmN=ogAA@mail.gmail.com' \
    --to=justin@specialbusservice.com \
    --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).