Eclipse Community Forums: Babel » non translatable Strings

Help

Home

Home » Eclipse Projects » Babel » non translatable Strings

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

non translatable Strings [message #23402]

Thu, 04 December 2008 11:08

Laurent Goubet

Messages: 1902
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------090907040001000405040904
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi translators,

I often maintain a single .properties file in my plugins to hold both
translatable and untranslatable (as in "do not translate") Strings. The
latter are located below comments warning the translators _not_ to
translate any further such as

#############################################
# END OF TRANSLATED PROPERTIES #
# do not translate values beyond this point #
#############################################

Needless to say, when using the babel UI translators won't see these
warnings and translate anyway when the key has a value that is valid
english and hence translatable... Granted, there is a way to mark
Strings as being untranslatable in the babel UI, yet I'd rather have
them automatically marked as such or better yet, totally hidden from the
translation UI.

Are there specific comments we can add to properties files so that babel
will not mark them for translation? AFAIK, with babel as it is now, we
cannot even create a config.properties file since it walks the entire
plugin tree and parses all properties file for translation.

Laurent Goubet
Obeo

--------------090907040001000405040904
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="laurent_goubet.vcf"

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

--------------090907040001000405040904--

Report message to a moderator

Re: non translatable Strings [message #23489 is a reply to message #23402]

Thu, 04 December 2008 12:32

Eclipse User

Originally posted by: atoulme.intalio.com

No, but we have an open bug about it I think.

We couldn't really come to terms as to what should be the flag to mark a
string as untranslatable.

Good news is though, that you can flag a straing as untranslatable in
the Babel UI.

Just login, go to the string, and check non-translatable.

It's a bit bothersome, but it is the workaround for now.

Thanks,

Antoine

laurent Goubet wrote:
> Hi translators,
>
> I often maintain a single .properties file in my plugins to hold both
> translatable and untranslatable (as in "do not translate") Strings. The
> latter are located below comments warning the translators _not_ to
> translate any further such as
>
> #############################################
> # END OF TRANSLATED PROPERTIES #
> # do not translate values beyond this point #
> #############################################
>
> Needless to say, when using the babel UI translators won't see these
> warnings and translate anyway when the key has a value that is valid
> english and hence translatable... Granted, there is a way to mark
> Strings as being untranslatable in the babel UI, yet I'd rather have
> them automatically marked as such or better yet, totally hidden from the
> translation UI.
>
> Are there specific comments we can add to properties files so that babel
> will not mark them for translation? AFAIK, with babel as it is now, we
> cannot even create a config.properties file since it walks the entire
> plugin tree and parses all properties file for translation.
>
> Laurent Goubet
> Obeo

Report message to a moderator

Re: non translatable Strings [message #23575 is a reply to message #23489]

Thu, 04 December 2008 12:45

Laurent Goubet

Messages: 1902
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------020601060104070103040703
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Antoine,

Yes, as mentionned in the previous mail I saw this as a potential
workaround too. Still remains the problem that anyone can also "just
login, uncheck the box and translate the string" since "untranslatable"
doesn't bear the same meaning as "shouldn't be translated".

If I go in the babel UI and see a String "Compare" marked as
"untranslatable", I'm bound to think "hey wait! But this is translatable
in any language?"... An option would be to prevent anyone to uncheck the
"untranslatable" box if he is not the one who checked it in the first
place (save for Eclipse Genie), but this remains a bothersome option :).

Since you've confirmed that there is no other option for now, I'll try
and find a bug report or raise one myself for this;

Thanks

Laurent Goubet
Obeo

Antoine Toulme a

Report message to a moderator

Re: non translatable Strings [message #23618 is a reply to message #23575]

Thu, 04 December 2008 13:41

Eclipse User

Originally posted by: atoulme.intalio.com

Laurent, the bug reference: 226378

Thanks,

Antoine

laurent Goubet wrote:
> Antoine,
>
> Yes, as mentionned in the previous mail I saw this as a potential
> workaround too. Still remains the problem that anyone can also "just
> login, uncheck the box and translate the string" since "untranslatable"
> doesn't bear the same meaning as "shouldn't be translated".
>
> If I go in the babel UI and see a String "Compare" marked as
> "untranslatable", I'm bound to think "hey wait! But this is translatable
> in any language?"... An option would be to prevent anyone to uncheck the
> "untranslatable" box if he is not the one who checked it in the first
> place (save for Eclipse Genie), but this remains a bothersome option :).
>
> Since you've confirmed that there is no other option for now, I'll try
> and find a bug report or raise one myself for this;
>
> Thanks
>
> Laurent Goubet
> Obeo
>
> Antoine Toulme a écrit :
>> No, but we have an open bug about it I think.
>>
>> We couldn't really come to terms as to what should be the flag to mark
>> a string as untranslatable.
>>
>> Good news is though, that you can flag a straing as untranslatable in
>> the Babel UI.
>>
>> Just login, go to the string, and check non-translatable.
>>
>> It's a bit bothersome, but it is the workaround for now.
>>
>> Thanks,
>>
>> Antoine
>>
>> laurent Goubet wrote:
>>> Hi translators,
>>>
>>> I often maintain a single .properties file in my plugins to hold both
>>> translatable and untranslatable (as in "do not translate") Strings. The
>>> latter are located below comments warning the translators _not_ to
>>> translate any further such as
>>>
>>> #############################################
>>> # END OF TRANSLATED PROPERTIES #
>>> # do not translate values beyond this point #
>>> #############################################
>>>
>>> Needless to say, when using the babel UI translators won't see these
>>> warnings and translate anyway when the key has a value that is valid
>>> english and hence translatable... Granted, there is a way to mark
>>> Strings as being untranslatable in the babel UI, yet I'd rather have
>>> them automatically marked as such or better yet, totally hidden from the
>>> translation UI.
>>>
>>> Are there specific comments we can add to properties files so that babel
>>> will not mark them for translation? AFAIK, with babel as it is now, we
>>> cannot even create a config.properties file since it walks the entire
>>> plugin tree and parses all properties file for translation.
>>>
>>> Laurent Goubet
>>> Obeo
>>
>

Report message to a moderator

Re: non translatable Strings [message #23661 is a reply to message #23618]

Thu, 04 December 2008 14:08

Laurent Goubet

Messages: 1902
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------080300080401010700050405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Thanks, cced myself on it when you told about a bug earlier ;).

Laurent Goubet
Obeo

Antoine Toulme a

Report message to a moderator