From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] i18n project
Date: Sun, 11 Jun 2006 13:08:14 +0200 [thread overview]
Message-ID: <448BF99E.3000300@gentoo.org> (raw)
In-Reply-To: <20060611021604.1412291b@sven.genone.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Marius Mauch wrote:
> <genone> and my point is that users often don't even realize that
> their post contains non-english text
Make Portage add a line with "Some of the previous errors were reported
in non-English language. If you want to get support from official
channel, please run `LC_ALL=C command`." when it detects a non-English
locale.
> Basically I don't think the benefit is rather dubious or maybe it's
> just that I had some rather bad experiences with translated versions of
> FOSS applications, but I'm quite opposed to this part of the project
> unless you have a way to remove my concerns.
Sure, translating GCC output is *not* good, but why don't provide
localized version of Portage messages like, for example, those when
Portage complains about unsatisfied dependency?
Cheers,
-jkt
--
cd /local/pub && more beer > /dev/mouth
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2006-06-11 11:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 23:37 [gentoo-dev] [RFC] i18n project Diego 'Flameeyes' Pettenò
2006-06-10 13:11 ` Jan Kundrát
2006-06-11 0:16 ` Marius Mauch
2006-06-11 8:25 ` Peter Volkov (pva)
2006-06-11 11:08 ` Jan Kundrát [this message]
2006-06-19 15:12 ` Paul de Vrieze
2006-06-19 16:39 ` Jan Kundrát
2006-06-19 17:16 ` Flammie Pirinen
2006-06-20 21:35 ` Mike Frysinger
2006-06-11 7:57 ` Peter Volkov (pva)
2006-06-11 11:17 ` Jan Kundrát
2006-06-11 8:37 ` Nguyễn Thái Ngọc Duy
2006-06-11 11:20 ` Jan Kundrát
2006-06-12 6:43 ` Flammie Pirinen
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=448BF99E.3000300@gentoo.org \
--to=jkt@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