Sorry for the late response. I have
been asked for a similar request already for my plugin. Some people do
not want to be notified (warning icon) when a key is missing a translation. The
solution proposed was different than marking a key (comment or else) as DO NOT
TRANSLATE. What has been proposed to me (and this is how the Babel version is aiming
to implement this already), is to distinguish between empty keys and null keys
(key exists without a value or key does not exists at all in properties file).
Even though I have an implementation with such distinction, I am not suggesting
it is the best possible approach. I am open to ideas and if a “DO
NOT TRANSLATE” comment (or $NON_NLS-1$ to be consistent) is adopted, I
have no problem implementing that.
From:
babel-dev-bounces@xxxxxxxxxxx [mailto:babel-dev-bounces@xxxxxxxxxxx] On Behalf Of Kit Lo
Sent: November 26, 2007 1:34 PM
To: babel-dev@xxxxxxxxxxx
Subject: [babel-dev] DO NOT
TRANSLATE properties files and quote handling
A question for Paul, Dennis or Gabe: When we load the
translation server with translatable files, is there a way to mark a file, or
strings in a file as DO NOT TRANSLATE? I've seen a few cases where a file, or
strings in a file, should not be translated. Otherwise, the code logic will not
work.
If we don't have a way to do that now, we have to come up with a system, like a
special comment in the file, so we can skip translating the file or strings.
Maybe we can do something in Pascal's Message Editor side. Pascal, any comment?
We also need a way for the developer of the properties file to tell us if the
file will be processed by Java MessageFormat class. Depending on whether the
file would be processed by Java MessageFormat class, quotes need to be doubled
sometimes. Again, some special comment in the file will solve the problem. Any
other ideas?
Kit Lo
IBM Eclipse SDK Globalization Technical Lead
