To be precise:
How do I include multiple langage resources in one single plugin?
Honestly, we did not really think of that yet.
Would you want trying - provide 2 message bundles for EN and another language and put it into the resources/ folder of the plugin source. Then change the text to use this properties.
Also for stuff within the plugin descriptor (rhq-plugin.xml) you need to be careful, as some stuff is not only shown to the user, but also an internal keyword to the plugin executable.
Thanks for the comment.
I'm trying to compose Japanese message resources.
I'll look into it and will file a jira issue with a patch attached.
That would be very cool!
We actually have thought about this (i18n'ing the plugins) - but not implemented anything.
We need a way to figure out how, for example, we can provide translations for things like DisplayName but yet be able to default the actual display strings in case no translations are available. We were thinking something along the lines of using the DisplayName as both the key to the resource bundle but also the default string. I dunno - if anyone has any good ideas and want to look into proposing a design/implementation, we are willing to listen.
Has there been any progress on this issue? All the rhq plugins used in EAP will need to be i18n compliant.