Bug 22900

If BR is in other language someone needs to translate it and I'm afraid that there are many languages without active translators. So it won't be fixed as there will be no interpreter.

I once worked in a Java shop which had internationalized apps.  This involves having multiple message text files, one per supported language.  Since they didn't have budget for translators, their build system would run the English message file through Google Translate to create the others.

I'm not familiar with the Translate API, but the UI has a capability to auto-determine the source language, so it might be possible to run each comment through a "translate whatever to English" call and get something at least usable.

CC: (none) => ftg

(In reply to Frank Griffin from comment #2)
>..... so it might be possible to run each
> comment through a "translate whatever to English" call and get something at
> least usable.

And for the developer etc. replying to one of these reports, would he then reply in English, or use translate in reverse, not knowing if the translation made sense or not?
I think the replies would have to be in English with a link to the translator site for the OP to use if needed.

CC: (none) => zen25000

I'd say include both the original non-English post followed by the English translation (with a suitable disclaimer) as the following comment.  When a developer replies, do the same in reverse: include the English response followed by a translation to the poster's language.

Obviously this won't be correct in every situation, but there's always the option to close it as INVALID (or INCOMPREHENSIBLE :-) ) if a particular case just isn't working.

It's easier to rely on "user api" :)

Tell people to use google translate when they dont understand, and we stay at english as default

CC: (none) => tmb

Well, technically the "easiest" is to do nothing, but I don't think that was the OP's point :)

(In reply to Thomas Backlund from comment #5)
> Tell people to use google translate when they dont understand, and we stay
> at english as default

I agree +1 (which means closing this bug as WONTFIX)

(In reply to Kristoffer Grundström from comment #0)
> Description of problem: I know that it's not prohibited to make a bugreport
> in other languages than English, 
> Portuguese and in French here even though English is the most spoken
> language I really find it odd that there's no reports written in more
> languages. 

We do ask for English reports:

https://wiki.mageia.org/en/How_to_report_a_bug_properly 

     Important note: The common language used is English, so please refrain
     from reporting bugs in other languages. Feel free to ask in the IRC
     channels or forums if you need someone to help you with this. 

Despite that request, reports did get filed in more languages than you think, I remember German and Romanian.

> We might get a bigger user base if we allowed (perhaps even
> invited) people to write reports in their own mothertongue for those who
> can't write in English.
> 

As Filip said, we don't have translators for many languages. Also, the existing translation engines aren't reliable enough.


(In reply to Frédéric Buclin from comment #7)
> (In reply to Thomas Backlund from comment #5)
> > Tell people to use google translate when they dont understand,

Or, preferably: to find someone in their community, who knows English well

> > and we stay at english as default
> 
> I agree +1 (which means closing this bug as WONTFIX)

Closing

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => WONTFIX

(In reply to Marja van Waes from comment #8)
 
> As Filip said, we don't have translators for many languages. Also, the
> existing translation engines aren't reliable enough.


Is there nothing we can do about that?