l10n bugs
Claude Paroz
paroz at email.ch
Mon Aug 29 16:10:18 CDT 2005
Le lundi 29 août 2005 à 13:03 +0200, Carlos Perelló Marín a écrit :
> On Fri, 2005-08-26 at 21:32 +0200, Claude Paroz wrote:
> [...]
> > > >
> > > If it's a problem with a specific translation, then the best would be to
> > > hop into Rosetta and fix it there, if it's been imported into Rosetta.
> >
> > It was not my question ;-) A user which see a translation error doesn't
> > always have the ability to translate himself. We cannot either told him
> > to create an account on Rosetta, find the correct package, the correct
> > string, and translate. It's too much.
>
> That's why breezy will come with an extra functionality that will let
> you find the URL from where you can translate that application. We will
> give a brief introduction to the system and how to do all those steps
> that you say it's not easy to do.
>
> >
> > Instead I want a simpler way, like giving an url where people can
> > directly submit a bug against a language package, that is fill a form
> > and click submit !
>
> Well, the translations live inside a language pack but the translation
> comes from the application so with the bug tracker integration (just
> like the translation integration I just talked), this issue will also be
> solved as you will have a direct link to file a bug report on that
> application.
Thanks for the news, I still didn't take time to install Breezy :(
The difficulty with a translation bug is that it depends on two parts :
application to which the string belongs and language in wich the string
is translated. But who cares ?
The maintainer doesn't really care. He can't do anything for that (apart
from reassigning the task to someone else).
The user just want to say : "This string is not in my language and I
don't understand it, so please do something about that". He should be
able to *simply* report it. If he can do more, by translating in
Rosetta, great, but we can't assume that. And even if he does, a sort of
quality check should be made.
Translator team really cares :) So they should absolutely be aware of
the report.
> >
> > Translation team leader(s) should then cope with the bug report.
> > What do you think about that ?
>
> Yeah, that's a good thing and perhaps should be noted in our launchpad
> integration page so maintainers don't need to reassign the bugs to those
> language packs...
>
> Could you add that suggestion as a bug report, please?
What do you mean by "launchpad integration page" ? I have to understand
the whole picture before being able to do a good suggestion.
Claude
More information about the rosetta-users
mailing list