On Sun, 4 Dec 2011 00:21:42 -0500
Mike Frysinger <vapier@gentoo.org> 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 <jer@gentoo.org> wrote:
> On Sun, 4 Dec 2011 00:21:42 -0500
> Mike Frysinger <vapier@gentoo.org> 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 <antarus@gentoo.org> 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

On Sun, Dec 4, 2011 at 1:14 AM, Alec Warner <antarus@gentoo.org> wrote:
> Can we *just translate the error messages?
>

That seems pretty impractical to me. Google Translate is about your
only option here, and somehow I doubt it is up to parsing build logs.
Hand translation could work if we increases the understaffed bug
wrangling team to the size of the UN...

Rich

On Sun, 4 Dec 2011 02:14:15 -0600
Ryan Hill <dirtyepic@gentoo.org> wrote:

> > Many dozens of times, and a magnitude more dozens of times,
>
> So a comparatively small number then.

You seem to argue that the time I spend on getting bug reports
right isn't essential or beneficial to your bugzilla work. Let's
actually act on that.

The alternative action I am now putting in place is to just allow the
foreign language build logs. One side effect is that the Summary, which
I tend to make more specific to the reported bug (replacing "refuses to
build", "failes[sic] on[sic] compile" and so on) by appending the
actual error, will now start seeing a multitude of untranslated output
messages. This makes bugs harder to find by searching, but by then
they're assigned anyway, so that's not my problem any longer.


jer

On Monday 05 December 2011 17:12:44 ChÃ*-Thanh Christopher Nguyá»…n wrote:
> 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.

assuming you have the same version of the package issuing the error message
installed locally, and you haven't restricted your LINGUAS in anyway (so you
have them all installed), then yes
-mike