From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Disabling locale at emerge output
Date: Sun, 24 Apr 2011 18:48:53 +0200 [thread overview]
Message-ID: <20110424184853.3312c774@epia.jer-c2.orkz.net> (raw)
In-Reply-To: <201104221953.36951.dilfridge@gentoo.org>
On Fri, 22 Apr 2011 19:53:36 +0200
"Andreas K. Huettel" <dilfridge@gentoo.org> wrote:
>
> How about a portage "feature" that is off by default? Like, "locale"
> meaning "build with locale"?
You mean we should settle for only slightly improved odds of getting a
build log we all can read?
> If it is on, and a build fails, the default error message could be
> extended with something like
>
> "Note that this build was using your system locale, i.e. the error
> messages are in your language and may not be understood by the
> developers or maintainers. If you want to file a bug, please
> re-emerge with FEATURE=-locale"
1) Hardly anyone is going to actually read that.
2) A good many of those who do read it, will ignore it.
3) It raises the bar for the bug to get filed in the first place. It's
definitely not a good idea to require users to go into another 10
hour session of, say, libreoffice or chromium compiling just to get
the proper LC_MESSAGES.
Again, slightly improved odds.
Also, with an interface that already forces users to read and write
English, and with the many commands not even using NLS or
lacking full translations coverage of all messages, it would probably
be in everyone's interest to see monolingual build output.
jer
next prev parent reply other threads:[~2011-04-24 16:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 11:31 [gentoo-dev] Disabling locale at emerge output Tomáš Chvátal
2011-04-22 12:31 ` ragavender rao
2011-04-22 17:53 ` Andreas K. Huettel
2011-04-24 16:48 ` Jeroen Roovers [this message]
2011-04-24 21:55 ` [gentoo-dev] " Duncan
2011-04-25 1:57 ` Jeroen Roovers
2011-04-25 5:24 ` Duncan
2011-04-25 4:05 ` Serkan Kaba
2011-04-25 6:14 ` Ulrich Mueller
2011-04-25 10:24 ` Jeroen Roovers
2011-04-25 13:40 ` ragavender rao
2011-04-22 12:37 ` [gentoo-dev] " Fabian Groffen
2011-04-22 12:57 ` Chí-Thanh Christopher Nguyễn
2011-04-26 2:06 ` [gentoo-dev] " Ryan Hill
2011-04-22 15:23 ` [gentoo-dev] " Jeroen Roovers
2011-04-22 17:50 ` Andreas K. Huettel
2011-04-22 15:40 ` Jeremy Olexa
2011-04-24 21:27 ` Andreas K. Huettel
2011-04-26 2:05 ` [gentoo-dev] " Ryan Hill
2011-04-26 4:02 ` Jeroen Roovers
2011-04-26 6:35 ` Michał Górny
2011-04-27 8:47 ` Ryan Hill
2011-04-27 16:26 ` Jeroen Roovers
2011-04-27 22:09 ` Chí-Thanh Christopher Nguyễn
2011-04-27 22:14 ` ross smith
2011-04-28 3:10 ` Ryan Hill
2011-04-28 12:00 ` Jeroen Roovers
2011-04-29 5:15 ` Ryan Hill
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=20110424184853.3312c774@epia.jer-c2.orkz.net \
--to=jer@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox