Re: [babel-dev] Project source location not being picked up

[Kit Lo <kitlo@xxxxxxxxxx>]

Mid-air collision with Denis!

Denis explained the idea already. I will also add my remarks here:

Andreas, that's the current design of Babel. We assume that strings with exact matches should be translated the same way and therefore synchronize them automatically. You can review the other changes by clicking on the "RECENT TRANSLATIONS" link under the banner (http://babel.eclipse.org/babel/recent.php). If you really think that two strings should have different meanings, you can either contact the project (via Bugzilla) to come up with better different English descriptions. Or, we can work together to enter different translations for specific strings in the Babel translation database.

Denis, "php5 process_project_source_locations.php" should be the right command to be added to the crontab. Thanks!

Regards,
Kit Lo
Eclipse Babel Project Lead
IBM Eclipse SDK (IES) Globalization Technical Lead
IBM Rational solution for Collaborative Lifecycle Management (CLM) Globalization Technical Lead

Denis Roy ---03/12/2014 09:39:44 AM---On 03/12/2014 04:46 AM, Andreas Sewe wrote: > Kit Lo wrote:

From: Denis Roy <denis.roy@xxxxxxxxxxx>
To: babel-dev@xxxxxxxxxxx,
Date: 03/12/2014 09:39 AM
Subject: Re: [babel-dev] Project source location not being picked up
Sent by: babel-dev-bounces@xxxxxxxxxxx

---

On 03/12/2014 04:46 AM, Andreas Sewe wrote:
> Kit Lo wrote:
>> We used to have a background job that runs daily to process the map
>> files. It may not be running. I manually started the process.
>> Translatable strings for technology.recommenders 2.0.6 are now available
>> for translation.
Thanks, Kit.  I think we had lost genie's crontab some time ago.  Is the 
process "php5 process_project_source_locations.php" ?  If so, I've added 
it to the crontab.  It will run every hour.


> Great. Thank you.
>
> Follow-up question: I just started with a translation of
> technology.recommenders 2.0.6 into German, as gain some first-hand
> experience of the whole Babel workflow. During that, I came across the
> following message wenn translating a single key: "Translated 2 strings
> across all Babel projects."
>
> Does that mean when I translate, say, the string "always" to "immer"
> that other projects besides technology.recommenders 2.0.6 receive that
> translation as a side-effect? That seems dangerous to me, as I don't
> know their translation context, so I assume I misunderstood the above
> message.

That's exactly what it means, and over the years we've discovered that 
it's not dangerous at all.  In fact, it's quite beneficial, since any 
localized version of a string is likely to be more accurate to the end 
user than the default English string.  Should an automatically 
translated string be incorrect, it can be changed in the UI afterwards.

In fact, don't be surprised if your project soon inherits many 
translated strings across all the languages we support as our Babel 
Syncup genie applies exact-matches from other projects to yours. Again, 
the idea is to accelerate translation by providing "something" instead 
of nothing, even if it's not entirely accurate. But again, in most 
cases, it is quite accurate.

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