On Mon, Dec 06, 2010 at 02:31:12PM +0100, Mike Hommey wrote:
>
> Wouldn't a translated reportbug be an invitation for non-english bug
> reports? That would surely be helpful for users, but otoh, a maintainer
> who can't read the bug reports can't do anything for theses users...

If backed up by a proper patch an automatic translation might make sense.
What about some intermediate step like:

The recipient of your export does most probably not understand your
mother language $LANG and thus the report should be sended in English
language. If you are not able to describe the problem properly in
English please send a mail to $USER_MAILING_LIST_FOR_LANG and ask
for a proxy bug reporter.

(or something in this sense). If this will not lead to a proper bug
report but some user who gets help on the mailing list (learns about the
mailing list as a way to get help) this is also a positive effect.

I also have the impression that some bug reporters can somehow describe
a problem but do not understand things like severities etc - so it might
be that translating this can be helpful for some people.

> The only way I can see this working would be to have a sort of staging
> bts, where users could send their bugs in their mother tongue, and where
> some i18n teams could translate and forward to the actual bts. That's a
> long way before that happening, and I'm not certain it would work well.

Contacting the native language mailinglist could be such "staging BTS".

And yes, I'm aware that this is not really optimal and that's why I
hesitated to simply fire up reportbug and file a bug report against it.

Kind regards

Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20101206134819.GB29656@an3as.eu">http://lists.debian.org/20101206134819.GB29656@an3as.eu

Andreas Tille writes ("Re: Reportbug not translated (Was: Bug#605892: please state that mails will be publically archived)"):
> If backed up by a proper patch an automatic translation might make sense.
> What about some intermediate step like:
>
> The recipient of your export does most probably not understand your
> mother language $LANG and thus the report should be sended in English
> language. If you are not able to describe the problem properly in
> English please send a mail to $USER_MAILING_LIST_FOR_LANG and ask
> for a proxy bug reporter.

This is all a very nice idea but I'm sad to say that I think mostly we
would be inviting the submitter (and perhaps the proxy bug reporter)
to waste their time.

The odds of this approach producing good enough interaction that an
actual bug would be found, understood and then fixed by a developer
seem quite low to me.

Ian.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 19709.4835.539514.977485@chiark.greenend.org.uk">h ttp://lists.debian.org/19709.4835.539514.977485@chiark.greenend.org.uk

On Mon, Dec 06, 2010 at 03:34:02PM +0100, Sandro Tosi wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384287

Ahhh, thanks for the pointer (I missed this). So at least no additional
action is needed (except sending a patch).

> BTS is in english, and all bug reports have to be in english (to have
> a chance to be resolved), so I don't see too much pressure in
> translating it + what all the other replies already said.

I think there were two pro translation arguments:

1. (mentioned by Tolimar) was in the line with my suggestion to
point to the relevant user list
2. (mentioned by bubulle) enabling correct understanding of the
reportbug menu even if the potential reporter does not speak
proper English might be helpful

Kind regards

Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20101206200631.GC11372@an3as.eu">http://lists.debian.org/20101206200631.GC11372@an3as.eu