public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  et_EE locale and language of error messages
Date: Fri, 19 May 2006 14:49:26 +0200	[thread overview]
Message-ID: <20060519124926.GA14551@gentoo.org> (raw)
In-Reply-To: <e4k3lu$6ar$1@sea.gmane.org>

On Fri, May 19, 2006 at 11:38:06AM +0200, Stefan Schweizer wrote:
> Hi,
> 
> there are at least two problems with how portage currently handles locales:
> 
> - Firstly some packages fail to build with obscure LC_* settings
> The continuous stream of et_EE bugs is annoying: http://tinyurl.com/jsqzb
> 
> - and secondly I get my gcc output in german when I have a german locale
> set. This makes it really hard to report bugs or the bugreports are useless
> for most developers that do not understand the language.
> 
> Those problems cannot be easily workarounded since portage does not use
> LC_ALL and LANG settings from /etc/make.conf
> 
> I propose to have the portage build environment set the language to English
> or LC_ALL=C by default. That would significantly reduce the bugs with
> unreadable error messages+ solve all the et_EE bugs at once.
> 
> One problem could be that packages depend on LC_* to install the correct
> language. But that is a real bug then in my opinion, because ebuilds should
> only honour LINGUAS and not LC_* during build time. Those bugs should be
> detected and fixed.
> 
> What do you think? LC_ALL=C in portage or not?

No, it's needlessly unfriendly to users, and encourages broken packages.
et_EE breakage should be fixed, and slowly but surely is, and as for
unreadable error messages, getting German gcc output in a German locale
is a feature, not a bug. It can indeed be a problem in bugreports, but
it's a much milder one, since it's trivial to look up what any
particular message is translated from.
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-05-19 12:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  9:38 [gentoo-dev] et_EE locale and language of error messages Stefan Schweizer
2006-05-19 10:22 ` Marc Hildebrand
2006-05-19 13:13   ` [gentoo-dev] " Stefan Schweizer
2006-05-19 13:30     ` Harald van Dijk
2006-05-19 16:01     ` Duncan
2006-05-19 17:14     ` Marius Mauch
2006-05-19 17:27       ` [gentoo-dev] " Stefan Schweizer
2006-05-19 18:10         ` Marius Mauch
2006-05-19 17:45       ` [gentoo-dev] " Zac Medico
2006-05-22 16:57   ` Wiktor Wandachowicz
2006-05-19 12:49 ` Harald van Dijk [this message]
2006-05-19 13:02   ` [gentoo-dev] " Jakub Moc
2006-05-19 13:09   ` Patrick McLean
2006-05-19 13:24     ` Harald van Dijk
2006-05-19 13:55       ` Carsten Lohrke
2006-05-19 13:44   ` Daniel Drake
2006-05-19 13:40     ` Harald van Dijk
2006-05-19 15:44   ` [gentoo-dev] " Stefan Schweizer
2006-05-19 16:05     ` Harald van Dijk
2006-05-24  0:59 ` [gentoo-dev] " Mike Frysinger
2006-05-24 10:36 ` Kevin F. Quinn
2006-05-24 11:17   ` Harald van Dijk
2006-05-24 12:58     ` Kevin F. Quinn
2006-05-24 11:42   ` Jakub Moc
2006-05-24 13:12     ` Kevin F. Quinn
2006-05-25 21:09     ` Mike Frysinger
2006-05-26  7:37     ` Mike Frysinger

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=20060519124926.GA14551@gentoo.org \
    --to=truedfx@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