[Localization] Problem: 2 translations for 1 string

Gerhard Steiner gd.steiner at gmx.at
Fri Mar 21 15:13:10 EDT 2008


Korakurider schrieb:
> On Fri, Mar 21, 2008 at 6:48 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>   
>> On Mar 20, 2008, at 18:48 , Alexander Todorov wrote:
>>  > http://www.gnu.org/software/gettext/manual/gettext.html#Contexts
>>
>>
>>  This describes exactly the problem we're facing with Etoys. Looks like
>>  we need to support contexts in Squeak ... unless someone has a better
>>  idea?
>>     
>    Not better idea , but we would need to rethink of dividing 'etoys'
> translation domain into smaller (and not too small !!) pieces, that
> could makes the conflict less likely (I am not sure if no conflict we
> have).
> And that should make life easier for many of translators and Sayamindu
> as a pootle admin :-)
>   
Yes please !!!!!!!!!!!!!

A small but very useful help for translater would be:
At the moment, it is really hard to find out in Pootle how often a 
translation string is used.
The text which describes the places is written in one line, also when 
the string is used more often.
If there is a line  for each place a string is used, the translator sees 
"oh, ok I have to be carefully"


>    To me, while the run-time behavior of gettext looking up
> translation by context is fine,
>    how and what to specify for context in source code actually seems not clear.
>
>   + At the time when source code is being written by developer with
> limited insight on various languages,
>   it would be difficult for developer to decide whether context is
> really needed for some phrase to distinguish it against other
> occurrence.
>   But I don't think we want to specify context to every phrases.
>   + We can specify any string as context, but some etoys specific
> guideline would be needed for what to specify.
>
>    I would like to hear insight from someone with actual experience...
>
>   
At the moment I'm trying to prepare a list with ambiguous strings from 
the etoys.po on Pootle. Will need a little bit time as I have to do by 
manually going through a file with 3700 strings.

Dangerous strings are
1. all which are used in more than one place.
2. Basic/General strings as "copy", "clear", "none", "quit", "save"

More will come

But what I can see now, to really solve the translation problems in 
etoys, we need both
1. Splitting of etoys.po into smaller pieces
2. Context based translation for some double used strings and basic strings
> Cheers,
>  /Korakurider
>
>   
>>  Gerhard, could you open a ticket and attach the list of ambiguous
>>  strings? Thanks!
>>
>>  - Bert -
>>
>>
>>
>>
>>  _______________________________________________
>>  Localization mailing list
>>  Localization at lists.laptop.org
>>  http://lists.laptop.org/listinfo/localization
>>
>>     
> _______________________________________________
> Localization mailing list
> Localization at lists.laptop.org
> http://lists.laptop.org/listinfo/localization
>
>   



More information about the Localization mailing list