Re: [babel-dev] Adobe contribution import questions

[Kit Lo <kitlo@xxxxxxxxxx>]

Thanks Adobe and Margaret for the information!

Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead

Margaret Wong <ywong@xxxxxxxxx>
Sent by: babel-dev-bounces@xxxxxxxxxxx

11/19/2008 12:24 PM

Please respond to
Babel committers mailing list <babel-dev@xxxxxxxxxxx>

To	Babel committers mailing list <babel-dev@xxxxxxxxxxx>
cc
Subject	Re: [babel-dev] Adobe contribution import questions

Hi all,

Adobe has not yet tested these translations through a testing cycle.  We
do plan on doing this and contributing those changes at a later date.  This
testing would include the strings that are exposed in the Eclipse UI through
Adobe's Flex Builder application.

Margaret


On 11/19/08 12:12 AM, "Kit Lo" <kitlo@xxxxxxxxxx> wrote:


Here are my comments:

1. If the Translation == The English String, should we ignore it?
As I have mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=255700#c3
, leaving the translation in English serves one purpose: it means translator
has actually looked at this string and determined that it should not be
translated. I thought of one solution, not sure if it works, please comment.
If we see that the string has been left in English in the translated files
"in all languages", shouldn't we go back and mark the English
strings as non-translatable? (provided that we trust the professional translators
that these strings are not translatable.) Note that I highlighted "in
all languages". We have to be careful. If one language decided not
to translate a string, or, the translation happens to be the same as English,
it doesn't mean that it's not translatable.

2. Translation differences amongst professionals: who do we trust?
I have been worrying about the syncup script, but couldn't come up with
strong enough reasons or examples to reject the idea :-) The idea should
work 90% of the time, but one size does not fit all :-) Depending on whether
the context is a noun or a verb, the translation may be different. (That's
a different topic.)

Before we pick one of the options you listed, we may have to ask how Adobe
translate the files? Do their translators just translate the files off-line?
After translation, do they verify the translations in context by launching
Eclipse with all the translations, exercise the functions and verify the
translations?

IBM is very proud of the quality of the translations we contributed because
we do have a cycle to launch Eclipse with all the translations, exercise
the functions, verify all the translations, and make modifications to the
translations if needed before we release them.

Option #3 may not work very well. When a language champion goes back and
correct one translation, we currently have the logic to search for the
same translations and change them all, doesn't matter if the other strings
are a noun or a verb.

Option #2 may not be an answer to this question, but I think we should
do that anyway. We may need an annotation on where do we get the contributions
from when we import the strings.

Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead


"Antoine Toulme" <antoine@xxxxxxxxxxxxxxx>
Sent by: babel-dev-bounces@xxxxxxxxxxx 11/18/2008 04:43 PM

Please respond to
antoine@xxxxxxxxxxxxxxx; Please respond to
Babel committers mailing list <babel-dev@xxxxxxxxxxx>

To

"Babel committers mailing list" <babel-dev@xxxxxxxxxxx>

cc
Subject

Re: [babel-dev] Adobe contribution import questions






On Tue, Nov 18, 2008 at 10:19 PM, Denis Roy <denis.roy@xxxxxxxxxxx <mailto:denis.roy@xxxxxxxxxxx>
> wrote:
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
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=255700>
+1



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
<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.
I vote #3 as well.



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


Denis



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