Community
Participate
Working Groups
The Babel runtime plug-in allows users to provide translations from within the target application. These translations need to be sent to the Babel server. Also, the runtime plug-in should fetch the latest translations from the server before showing the translation dialog because users may not have the latest language packs. There may also be other uses for an API into the babel server. The API should allow a plug-in to fetch data given a key that consists of the following components: bundle symbolic name file path of the properties file key locale The API should also allow us to put a value. This is a little more complex because data can only be submitted within the context of a bugzilla account. The Babel runtime plug-in allows users to translate all messages that appear in an editor, view, or dialog. Therefore it will typically request a number of messages at once, but most if not all are likely to be in a single property file. Therefore it would improve performance if the API allowed multiple keys to be passed.
The API calls need to include the bugzilla login and password, at least for those calls that do writes to the database.
To integrate nicely with the Messages Editor, here is a wish list for the runtime API: - Being able to get all keys for a resource bundle at once. - Being able to get all values for a given key at once (all locales). - Capability to rename/delete/add a key. - Being able to save just one key/value. If the idea of "batch" mode is to be supported, then a being able to read/write a stream that represents a resource bundle (expected Java Properties format) would work great as well (not sure how individual changes would be tracked efficiently).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
