[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [babel-translators] Adobe contribution import questions

Hi,

I'd vote for a mix of #2 and #3 : override Genie's translations _and_ run further sync with a non-genie user since that particular String is indeed fuzzy and will have to be reverted later. Avoiding the Genie user might prevent this very same issue to happen again.

Hendrik Maryns a écrit :
Denis Roy schreef:
Babel team, Babel Translators,

I'm working on importing the Adobe contribution, and I'm encountering
some 'what if's that I'd like to discuss:



1. If the Translation == The English String, should we ignore it?
==========================================

My guess is 'yes', but please see (and comment on) this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=255700



2. Translation differences amongst professionals: who do we trust?
===========================================

I happened to stumble upon this gem, in *French:*
http://babel.eclipse.org/staging/translate.php?project=eclipse&version=3.4&file=org.eclipse.search/new%20search/org/eclipse/search2/internal/ui/SearchMessages.properties&string=MatchFilterSelectionDialog_label

The Key is *MatchFilterSelectionDialog_label*, and the English value is
*Search Filters*.  Of course, without context [1], "search" could be a
noun or a verb, but in this case, I think it means "Filters of Search"
(noun), not "Please Search the Filters" (verb).

Genie had a translation value of:"*Filtres de recherche*" (Filters of
Search, noun), which likely came from the IBM 3.2 lang packs and, IMO,
is correct.  However, it was overwritten by the Adobe value "*Rechercher
les filtres*" (Search the Filters, verb).

So my question is: how do we deal with this?  Here are some options I
think can be useful:

1. We could tell the importer to not overwrite values that were
translated by Genie. This could be bad, as since we've been running the
syncup script, Genie's translations may not necessarily be correct, and
in that case, the Adobe value should overwrite it.

2. We could tell the importer to not overwrite values that were
translated by Genie and run future syncup as a non-Genie user account to
distinguish both import and syncup actions.

3. We simply let Genie's values be overwritten, and consider this an
isolated case.  The language champions, and the general public, will
notice the error and use the Server tool to revert the translation.

I vote #3.


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=246199 would be useful
here.

I vote for #3, but with the added proviso I discussed in the bug: those strings should be marked ‘fuzzy’. And see bug 254847.

I think 2 might be a good idea too, independently.

H.
------------------------------------------------------------------------


_______________________________________________
babel-translators mailing list
babel-translators@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-translators

begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr/";>Obeo</a>
email;internet:laurent.goubet@xxxxxxx
url:http://www.obeo.fr
version:2.1
end:vcard