Re: [platform-core-dev] New platform NLS support

[Bob Foster <bob@xxxxxxxxxx>]

The primary issue seems to be one of developer convenience. The current 
work mode (for me and I suspect many others) is that a developer can 
first write a getString() call that will, if the key is not found, 
simply return the key. This allows the code to be run immediately. A 
follow-up pass with a tool converts the string argument to a key and 
puts the key and argument in the resource bundle.

I read the part about "opportunity for tooling." The difference is, it 
seems the tooling now must act immediately, or the file will not compile.

Could you please explain the steps one has to go through with the new 
feature, without further tooling, when one, say, needs to format an 
exception message?

Bob Foster

John Arthorne wrote:
> Eclipse 3.1 M5 has introduced a new resource bundle mechanism that is 
> significantly more efficient than the standard Java property resource 
> bundle mechanism.  This new mechanism stores each messages as a static 
> field whose value is bound at runtime based on the current locale.  The 
> result is that message keys are no longer stored in memory as strings, 
> and the overhead of the Hashtable used by property resource bundle is 
> eliminated.  More details on the new API, along with analysis of its 
> performance and a conversion tool for those using property resource 
> bundles, is found here:
>
> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/documents/3.1/message_bundles.html 
>
>
> Questions on this new API are welcome on the platform-core-dev mailing 
> list.