[gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?

On Sat, Dec 3, 2011 at 7:50 PM, Jeroen Roovers wrote:

Subject says it all. More and more bug attachments appear that have
been generated with non-English locales, and it's a nuisance for both
bug reporters and bug wranglers to request/provide the sane alternative
that every developer should be able to read.

I think forcing LC_ALL=C is crazy.

-A

    jer

On Saturday 03 December 2011 22:50:00 Jeroen Roovers wrote:

Subject says it all. More and more bug attachments appear that have
been generated with non-English locales, and it's a nuisance for both
bug reporters and bug wranglers to request/provide the sane alternative
that every developer should be able to read.

non C locales triggers real bugs i think we should be fixing

and in reality, you're complaining only about LC_MESSAGES, not LC_ALL or any
other locale category ...
-mike

On Sun, 4 Dec 2011 00:21:42 -0500
Mike Frysinger wrote:

and in reality, you're complaining only about LC_MESSAGES, not LC_ALL
or any other locale category ...

Fine.


jer

On Sat, Dec 3, 2011 at 10:03 PM, Jeroen Roovers wrote:

On Sun, 4 Dec 2011 00:21:42 -0500
Mike Frysinger wrote:

and in reality, you're complaining only about LC_MESSAGES, not LC_ALL
or any other locale category ...

Fine.

Can we just translate the error messages?

-A

    jer

On Sat, 3 Dec 2011 22:14:16 -0800
Alec Warner wrote:

Can we just translate the error messages?

*I* sure can but it takes time and effort, and for ever developer who
looks at this, the process is repeated unless bug wranglers or other
handy users happen to provide the translation.

Just think of looking into a large build log, checking that the
"error:" should now be "Fehler:" or something in an altogether
different script you can't even read, and then searching backwards
through the log to find the first occurrence. Do the same for "No such
file or directory", "undefined reference" and so on - the things that
most commonly get translated.

Or do you mean automate translation whenever something is attached to a
bug report? I think we'd be doing things the wrong way round then, but
feel free to donate the machine translation server farm to do it. Also,
make sure the result uses the same (original) strings and that you don't
get funny "google translate" surprises.


jer