| non translatable Strings [message #575980] |
Thu, 04 December 2008 11:08 |
|
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--
|
|
|
Powered by
FUDForum. Page generated in 0.03006 seconds
] 
Search
Help
Register
Login
Home
