[babel-dev] DO NOT TRANSLATE / $NON-NLS-1$ in .properties files?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[babel-dev] DO NOT TRANSLATE / $NON-NLS-1$ in .properties files?

From: Sean Flanigan <sflaniga@xxxxxxxxxx>
Date: Fri, 16 Jan 2009 15:38:33 +1000
Delivered-to: babel-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/babel-dev>
List-help: <mailto:babel-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/babel-dev>, <mailto:babel-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/babel-dev>, <mailto:babel-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Thunderbird 2.0.0.19 (X11/20090105)

Hi,

I found an old thread < http://markmail.org/message/b7gnc6o3rq6o7v6o >
about creating a "well-known" convention for marking strings as
untranslatable in the .properties files.

Was any decision ever made on this?  I'm finding I have a similar need
in JBoss Tools: .properties files just get used for too many different
things!

Sean.

-- 
Sean Flanigan

Senior Software Engineer
Engineering - Internationalisation
Red Hat

Attachment: signature.asc
Description: OpenPGP digital signature

Follow-Ups:
- Re: [babel-dev] DO NOT TRANSLATE / $NON-NLS-1$ in .properties files?
  - From: Antoine Toulme

Prev by Date: RE: [babel-dev] Babel Server Nightly mysqldump --- importing failed.
Next by Date: Re: [babel-dev] DO NOT TRANSLATE / $NON-NLS-1$ in .properties files?
Previous by thread: [babel-dev] Identifying (and externalising) untranslated strings
Next by thread: Re: [babel-dev] DO NOT TRANSLATE / $NON-NLS-1$ in .properties files?
Index(es):
- Date
- Thread

Breadcrumbs