[news.eclipse.platform.rcp] Re: Getting i18n setting from database

[jsetya@xxxxxxxxx (Setya)]

Thanks Alex for your response,

> 2) Storing the translations of the individual labels that are currently 
stored in the various .properties files that are used by your application

Yes, this is exactly what I'm trying to achieve.

> What I'd recommend is that you have the translated entries stored in the 
database for ease of storage/management, and then use that to automatically 
generate the plugin.properties for each plugin as part of the build process.

> You would also be able to automatically extract these translations from your 
DB to generate fragments, much like the RCP NL pack is distributed today.

> Using a build-time process to extract translations into appropriate 
properties files is going to be a much more sensible suggestion than trying to 
hack the Eclipse code to do lookups when the application starts.

Thanks, these are good ideas. Now my questions here :

1. When does this 'build process' occur, is it when I export my plugin 
through Export Wizard in the manifest editor ?
2. How can I hook my own process to generate plugin.properties during 
build process ?
3. From your suggestions, does it mean I won't have plugin.properties 
ready during development until I go through build process ? If that's so 
how can I test my application with various i18n settings during 
development ?


Thanks in advanced.


Regards,

Setya