Eclipse Community Forums: Babel » What's the right/best process for raising and discussing a translation issue in a Europa nl plug-in?

Home » Eclipse Projects » Babel » What's the right/best process for raising and discussing a translation issue in a Europa nl plug-in?

Show: Today's Messages :: Show Polls :: Message Navigator

What's the right/best process for raising and discussing a translation issue in a Europa nl plug-in? [message #10039]

Mon, 09 June 2008 18:25

Eclipse User

Originally posted by: nospam_kowalskilee.gmail.com

Hello, I just want to raise this issue in the right place. :-) My
apologies for the length of this posting.

What's the right or best process for raising and discussing a
translation issue seen in a Babel Europa nl plug-in?

Should I use Bugzilla to open a bug, or first post to the babel
developers mailing list?

------------------------
This is the situation:
First, this posting was made to the eclipse.platform.ua newsgroup:
http://www.eclipse.org/newsportal/article.php?id=526&gro up=eclipse.platform.ua#526

I investigated the French, as I have a small knowledge to read that
language. I found that in the 3.2.1 NL Pack, the file
WebappResources_fr.properties in the org.eclipse.help.webapp.nl_fr
plug-in contains the following lines:
Search=Rec&hercher
and *both*:
selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes
SelectWorkingSet=S\u00E9lectionner la port\u00E9e de la recherche

But, when I get the Babel Europa update for my 3.3.2 Platform SDK and
look into the org.eclipse.help.webapp.nl_fr plug-in and into its
WebappResources_fr.properties file, I do *not* see these two:
Search=Rec&hercher
selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes

And when I run the 3.3.2 infocenter from my Platform SDK with a French
UI, I reproduce the issue that Marcus reported in the
eclipse.platform.ua newsgroup.

Then, I updated the WebappResources_fr.properties file by adding those
two lines, and updated the org.eclipse.help.webapp jar that was added
from updating with Babel Europa, and lo and behold, when I run my 3.3.2
infocenter now, the labels show up properly translated.

So, I have some additional questions:
a. Why weren't those two lines/tokens carried through from the 3.2.1 NL
Pack to the Babel Europa package? Did they accidentally get dropped?
b. How to make sure a fix gets into the Babel Europa and Babel Ganymede
(if needed) packages?

I don't see a way on the Babel web site to add a new externalized token
to the file in question, if that's the right thing to do.

Thanks!
Lee Anne Kowalski

Report message to a moderator

Additional info: Re: What's the right/best process for raising and discussing a translation issue in [message #10063 is a reply to message #10039]

Mon, 09 June 2008 18:35

Eclipse User

Originally posted by: nospam_kowalskilee.gmail.com

Some additional info:
When I look at the Babel Project translation interface and select
French, 3.4, and
org.eclipse.help.webapp/src/org/eclipse/help/internal/webapp /WebappResources.properties
file, I see an anomaly:

In the Translatable String section, there are two lines that look identical:
Search Results Resultats de la recherche
Search Results Resultats de la recherche

But, if you select the first one, the String Translation shows the first
one has English String = Search Results and Externalized Token = search
and the history of translations says Eclipse Genie changed it from
Rec&hercher to the Resultats text.

Was that an approved change somehow? Because now we have two
externalized tokens (search and SearchResults) that look like they are
set to the same translated phrase. And I don't see that they should be
the same in the Eclipse UI. Somehow, the externalized token=search got
associated with the English String = Search Results, and I suspect that
is incorrect.

--Lee Anne

Lee Anne wrote:
> Hello, I just want to raise this issue in the right place. :-) My
> apologies for the length of this posting.
>
> What's the right or best process for raising and discussing a
> translation issue seen in a Babel Europa nl plug-in?
>
> Should I use Bugzilla to open a bug, or first post to the babel
> developers mailing list?
>
> ------------------------
> This is the situation:
> First, this posting was made to the eclipse.platform.ua newsgroup:
> http://www.eclipse.org/newsportal/article.php?id=526&gro up=eclipse.platform.ua#526
>
>
> I investigated the French, as I have a small knowledge to read that
> language. I found that in the 3.2.1 NL Pack, the file
> WebappResources_fr.properties in the org.eclipse.help.webapp.nl_fr
> plug-in contains the following lines:
> Search=Rec&hercher
> and *both*:
> selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes
> SelectWorkingSet=S\u00E9lectionner la port\u00E9e de la recherche
>
> But, when I get the Babel Europa update for my 3.3.2 Platform SDK and
> look into the org.eclipse.help.webapp.nl_fr plug-in and into its
> WebappResources_fr.properties file, I do *not* see these two:
> Search=Rec&hercher
> selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes
>
> And when I run the 3.3.2 infocenter from my Platform SDK with a French
> UI, I reproduce the issue that Marcus reported in the
> eclipse.platform.ua newsgroup.
>
> Then, I updated the WebappResources_fr.properties file by adding those
> two lines, and updated the org.eclipse.help.webapp jar that was added
> from updating with Babel Europa, and lo and behold, when I run my 3.3.2
> infocenter now, the labels show up properly translated.
>
> So, I have some additional questions:
> a. Why weren't those two lines/tokens carried through from the 3.2.1 NL
> Pack to the Babel Europa package? Did they accidentally get dropped?
> b. How to make sure a fix gets into the Babel Europa and Babel Ganymede
> (if needed) packages?
>
> I don't see a way on the Babel web site to add a new externalized token
> to the file in question, if that's the right thing to do.
>
> Thanks!
> Lee Anne Kowalski

Report message to a moderator

Re: What's the right/best process for raising and discussing a translation issue in a Europa nl plug [message #10133 is a reply to message #10039]

Tue, 10 June 2008 15:16

Eclipse Webmaster

Messages: 607343
Registered: July 2009

Senior Member

Lee Anne wrote:
> Hello, I just want to raise this issue in the right place. :-) My
> apologies for the length of this posting.
>
> What's the right or best process for raising and discussing a
> translation issue seen in a Babel Europa nl plug-in?

If it's a *translation* issue (incorrect terminology, etc) the best way
is to use the babel-translators mailing list, and talk to the folks
translating directly. Prefix mail messages with the [xx] language code.

https://dev.eclipse.org/mailman/listinfo/babel-translators

Also, please note that the Babel translation tool is open to everyone,
so if some terminology is incorrect, people can simply log in and fix it.

http://babel.eclipse.org/

> Should I use Bugzilla to open a bug, or first post to the babel
> developers mailing list?
>
> ------------------------
> This is the situation:
> First, this posting was made to the eclipse.platform.ua newsgroup:
> http://www.eclipse.org/newsportal/article.php?id=526&gro up=eclipse.platform.ua#526

In the case above, I would refer them to the translation tool so they
can fix the translation directly.

http://babel.eclipse.org/

> I investigated the French, as I have a small knowledge to read that
> language. I found that in the 3.2.1 NL Pack, the file
> WebappResources_fr.properties in the org.eclipse.help.webapp.nl_fr
> plug-in contains the following lines:
> Search=Rec&hercher
> and *both*:
> selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes
> SelectWorkingSet=S\u00E9lectionner la port\u00E9e de la recherche
>
> But, when I get the Babel Europa update for my 3.3.2 Platform SDK and
> look into the org.eclipse.help.webapp.nl_fr plug-in and into its
> WebappResources_fr.properties file, I do *not* see these two:
> Search=Rec&hercher
> selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes

Perhaps the SelectWorkingSet= tag has simply not been translated, or it
is no longer in the 3.3.2 English strings?

> And when I run the 3.3.2 infocenter from my Platform SDK with a French
> UI, I reproduce the issue that Marcus reported in the
> eclipse.platform.ua newsgroup.
>
> Then, I updated the WebappResources_fr.properties file by adding those
> two lines, and updated the org.eclipse.help.webapp jar that was added
> from updating with Babel Europa, and lo and behold, when I run my 3.3.2
> infocenter now, the labels show up properly translated.
>
> So, I have some additional questions:
> a. Why weren't those two lines/tokens carried through from the 3.2.1 NL
> Pack to the Babel Europa package? Did they accidentally get dropped?
> b. How to make sure a fix gets into the Babel Europa and Babel Ganymede
> (if needed) packages?
>
> I don't see a way on the Babel web site to add a new externalized token
> to the file in question, if that's the right thing to do.

Actually, the maps processor should pick these up. My guess is that,
because both tokens are identical (case-insensitive), there is a bug in
the processor.

I've opened this bug to track the investigation:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=236454

--

Eclipse WebMaster - webmaster@eclipse.org
Questions? Consult the WebMaster FAQ at
http://wiki.eclipse.org/index.php/Webmaster_FAQ
View my status at http://wiki.eclipse.org/index.php/WebMaster

Report message to a moderator

Re: What's the right/best process for raising and discussing a translation issue in a Europa nl plug [message #10155 is a reply to message #10133]

Tue, 10 June 2008 15:33

Eclipse User

Originally posted by: nospam_kowalskilee.gmail.com

Hi Denis,

Thank you so much for opening the bug to track the investigation.

And I had reposted the question to the babel-translators list before I
saw your response here, so my apologies in advance if that causes you
any problems--or is otherwise annoying. I think the Babel project is
great and you and your team are doing an amazing job of it all.

Thanks again!
Lee Anne

Denis Roy wrote:
> Lee Anne wrote:
>> Hello, I just want to raise this issue in the right place. :-) My
>> apologies for the length of this posting.
>>
>> What's the right or best process for raising and discussing a
>> translation issue seen in a Babel Europa nl plug-in?
>
> If it's a *translation* issue (incorrect terminology, etc) the best way
> is to use the babel-translators mailing list, and talk to the folks
> translating directly. Prefix mail messages with the [xx] language code.
>
> https://dev.eclipse.org/mailman/listinfo/babel-translators
>
> Also, please note that the Babel translation tool is open to everyone,
> so if some terminology is incorrect, people can simply log in and fix it.
>
> http://babel.eclipse.org/
>
>> Should I use Bugzilla to open a bug, or first post to the babel
>> developers mailing list?
>>
>> ------------------------
>> This is the situation:
>> First, this posting was made to the eclipse.platform.ua newsgroup:
>> http://www.eclipse.org/newsportal/article.php?id=526&gro up=eclipse.platform.ua#526
>
>
> In the case above, I would refer them to the translation tool so they
> can fix the translation directly.
>
> http://babel.eclipse.org/
>
>
>> I investigated the French, as I have a small knowledge to read that
>> language. I found that in the 3.2.1 NL Pack, the file
>> WebappResources_fr.properties in the org.eclipse.help.webapp.nl_fr
>> plug-in contains the following lines:
>> Search=Rec&hercher
>> and *both*:
>> selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes
>> SelectWorkingSet=S\u00E9lectionner la port\u00E9e de la recherche
>>
>> But, when I get the Babel Europa update for my 3.3.2 Platform SDK and
>> look into the org.eclipse.help.webapp.nl_fr plug-in and into its
>> WebappResources_fr.properties file, I do *not* see these two:
>> Search=Rec&hercher
>> selectWorkingSet=Rechercher uni&quement dans les rubriques suivantes
>
> Perhaps the SelectWorkingSet= tag has simply not been translated, or it
> is no longer in the 3.3.2 English strings?
>
>
>> And when I run the 3.3.2 infocenter from my Platform SDK with a French
>> UI, I reproduce the issue that Marcus reported in the
>> eclipse.platform.ua newsgroup.
>>
>> Then, I updated the WebappResources_fr.properties file by adding those
>> two lines, and updated the org.eclipse.help.webapp jar that was added
>> from updating with Babel Europa, and lo and behold, when I run my
>> 3.3.2 infocenter now, the labels show up properly translated.
>>
>> So, I have some additional questions:
>> a. Why weren't those two lines/tokens carried through from the 3.2.1
>> NL Pack to the Babel Europa package? Did they accidentally get dropped?
>> b. How to make sure a fix gets into the Babel Europa and Babel
>> Ganymede (if needed) packages?
>>
>> I don't see a way on the Babel web site to add a new externalized
>> token to the file in question, if that's the right thing to do.
>
> Actually, the maps processor should pick these up. My guess is that,
> because both tokens are identical (case-insensitive), there is a bug in
> the processor.
>
> I've opened this bug to track the investigation:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=236454
>
>

Report message to a moderator