launchpad-translators team mailing list archive

[Adi Roiban <adi@xxxxxxxxx>]

On Mon, 2010-05-31 at 12:33 +0300, Yaron Shahrabani wrote:
> I really like where this discussion is going
> 
> Adi, do you think its feasible?
You are using top posting and I don't know what are you actually asking.
Can you please expand the above question?

> This feature should use the comments so the po files that return to
> the upstream will include the comments

> The problem is that some of the bad suggestions enter the TM and some
> unexperienced users might use these suggestions, marking and
> commenting may help avoid this issue

>From what I understood this topic is about helping new translators not
making the same errors over and over again.

>From my point of view, having "bad" suggestions in the translation
memory is a different issue and they can be also generated by
experienced translators (Errare humanum est perseverare autem
diabolicum). If you want to discuss this problem, I think it is better
to start a new thread.

Regarding commenting and tagging of translations, transforming Launchpad
Translations in a discussion board/forum is not feasible.

It would be nice to allow translators to edit the Gettext POFile
comments for their translations.

One think that maybe we can improve to mitigate suggesting the same bad
suggestion over and over again, is to signal/tag a suggestion as being
dismissed by someone in some date. 

Just like we can see that the current translations was done by X in May
and reviewed by Y in June, we could see that a translations was done by
Z in May and dimissed by W in June.

> About composing a document that apply to all translators this is
> non-realistic since the translators use other systems and believe in
> different approaches and most of them don't want to unite into a
> translators community (although we keep on trying and won't give up)

Then just create that document with comment error for Launchpad
Translators rules/guidelines.

Like I said, I find those "common errors" a good way to learn from
examples and I think they should be included in all guidelines.

> Do you want me to add parts of our discussion to the bug report?

Feel free to add what do you think could be useful for solving that bug.
Just keep in mind that Launchpad Translations should be simple to use
and that each problem should be handled in a different bug.

Cheers,

> Kind regards and thank you all for your support!
> Yaron Shahrabani
> 
> 
> On Mon, May 31, 2010 at 12:10 PM, Adi Roiban <adi@xxxxxxxxx> wrote:
>         On Sat, 2010-05-29 at 11:16 +0300, Yaron Shahrabani wrote:
>         > I want to raise a slightly disturbing issue
>         >
>         >
>         > there are many translators who are really confident about
>         their work
>         > but practically doing an awful work, the problem is that
>         when I fix
>         > their mistakes they usually don't see it and keep on
>         translating the
>         > same way
>         
>         
>         Each team can inform Launchpad for the web address of the used
>         guidelines [1]
>         
>         For the Romanian team (GNOME, KDE, Mozilla, OO.org ... etc) we
>         have a
>         wiki page with a list of "Frequent/common errors" and in the
>         team
>         guidelines there is a link to that page [2].
>         
>         New translators are require to read that page of common errors
>         and by
>         reading that page a new translator can learn from examples.
>         
>         Rather than sending personal emails to new translators and
>         explaining
>         the grammar and orographic Romanian, we just point them to
>         that wiki
>         page.
>         
>         If we see those common errors in new translations, we stop
>         reviewing and
>         ask the new translator to: 1- read the guidelines, 2- review
>         his/her
>         previous translation , 3- Let us know when the his/her own
>         review is
>         done.
>         
>         >From my experience, most of the new translators submitting
>         bad
>         translators, are "drive-by translators" and they don't care to
>         much
>         about the translation quality. I always send an email to let
>         them know
>         that they are submitting bad translations, and only 5% of them
>         are
>         getting back to acknowledge that they have not read the
>         guidelines and
>         that I can do a new review for their new suggestions. This is
>         one of the
>         reasons why I don't want to waste to much resources with those
>         new
>         translators.
>         
>         I think that fixing bug 25 (Allow discussion/commenting on
>         translations ) [3] should help a bit with this issue.
>         
>         [1] https://help.launchpad.net/Translations/Guidelines
>         [2] http://i18n.ro/Greseli_frecvente [3]
>         https://bugs.edge.launchpad.net/rosetta/+bug/25
>         
>         
>         --
>         Adi Roiban
>         
>         
>         
>         _______________________________________________
>         Mailing list: https://launchpad.net/~launchpad-translators
>         Post to     : launchpad-translators@xxxxxxxxxxxxxxxxxxx
>         Unsubscribe : https://launchpad.net/~launchpad-translators
>         More help   : https://help.launchpad.net/ListHelp
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~launchpad-translators
> Post to     : launchpad-translators@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~launchpad-translators
> More help   : https://help.launchpad.net/ListHelp


-- 
Adi Roiban