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: Thu, 19 Mar 2015 13:54:43 -0400	[thread overview]
Message-ID: <20150319175443.GF23507@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150319124105.GJ23636@example.net>

On Thu, Mar 19, 2015 at 01:41:05PM +0100, u-wsnj@aetey.se wrote:
> On Thu, Mar 19, 2015 at 08:29:41AM +0000, Justin Cormack wrote:
> > On Mar 18, 2015 11:10 PM, <u-wsnj@aetey.se> wrote:
> > > IOW I'd like to always have the canonical errname in the output,
> > > in English too.
> 
> > Would it make sense for the canonical names to be the output in the C
> > locale and English if you set an English locale?
> 
> What I am after is seeing "EXXXXX" as a part of the message with any LANG,
> including English:
> 
> LANG=en:  "No such file or directory (ENOENT)"
> LANG=xx:  "&((/&=(/%&/(&%/(/)(/&/ ENOENT"
>  ...
> 
> It could be nice to have a common convention for all languages
> about the formatting of the error reference, like parentheses
> around the name and/or placing it rightmost, but this is probably
> impossible with some languages.

The issues I'm somewhat concerned with are:

- Does this interfere with proper flow of RTL text? In absence of bidi
  nesting chars, I would think the answer might be yes.

- Does it result in ugly mix of unmatching fonts in UI, possibly even
  alterring line spacing?

Keep in mind that error messages are not necessarily bugs to be
reported upstream but may be informative to users directly. For
example a GUI app could be reporting to the user that they file they
tried to open is not accessible.

Rich


  parent reply	other threads:[~2015-03-19 17:54 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
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 [this message]
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=20150319175443.GF23507@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).