Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Chí-Thanh Christopher Nguyễn <chithanh@g.o>
Subject: Re: So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?
Date: Mon, 05 Dec 2011 23:12:44 +0100
Rich Freeman schrieb:
>> Can we  just translate the error messages?
> That seems pretty impractical to me.  Google Translate is about your
> only option here,

Actually the translation already exists in /usr/share/locale/ and just
needs to be looked up, so it appears not entirely impractical. Still,
probably not worth the effort.


Best regards,
Chí-Thanh Christopher Nguyễn


Replies:
Re: So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?
-- Mike Frysinger
References:
So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
-- Jeroen Roovers
Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
-- Mike Frysinger
Re: So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?
-- Jeroen Roovers
Re: So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?
-- Rich Freeman
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?
Next by thread:
Re: So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?
Previous by date:
Re: We need *you* for a USE="selinux" dependency
Next by date:
Re: sources.gentoo.org instability


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.