Could you please share more information about your plugin? Is it opensource or commercial? We are the active contributors of the Spanish Pack and can help you with the internationalization...
I think you should start taking a look at:
If your plugin is independent, it must embed its own bundles.
Let me know if you need any help.
2015-01-28 16:37 GMT+01:00 El alaoui Mohamed Reda <[hidden email]>:
I followed the documentation to embed my own bundles in a language different from english (org/sonar/l10n/<plugin key>_<language>.properties) but I'm facing another problem.
How do I change the language of my sonarqube instance?
I tried to install the targeted language pack, thinking it would change the language of the whole application. But it is not the case. It is a mix between the language of the pack I installed and the default language of my plugin, i.e english. I conclude my bundle is ignored.
Is there an option somewhere I missed?
On 29/01/2015 12:29, Antonio Calero wrote:
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Server does not have such configuration. Language is sent by browser.
Administration pages are not translated and are always in English. If there are still some mixes of languages in other pages, that means that the installed language bundle is not complete.
My plugin internationalization works well in the two languages with sonar version 3.7.4 but not works with the last sonar version 4.5.2
there is any way to solve it ?
2015-02-01 19:56 GMT+01:00 Simon Brandhof <[hidden email]>:
No answer ?!!!
2015-02-11 16:59 GMT+01:00 El alaoui Mohamed Reda <[hidden email]>:
You should provide more contextual information to help us understand the problem.
On 16 February 2015 at 16:41, El alaoui Mohamed Reda <[hidden email]> wrote:
I'm working on a plugin that embeds its own i18n context, regarding the documentation here :
Here is my folder structure under src/main/resources :
The internationalisation works as well, in sonar 3.7.4 version (I only test with LTS versions). The change of the browser language changes the language of my rule messages.
But for a reason that I ignore, it doesn't work with 4.5.2 version. Whatever the language of my browser, the language of my rule message is always the default one, i.e english.
Furthermore, the documentation describes how to deal with the rule description for version prior to 4.2. As I mentionned, the internationalisation works well, for the rule description in version 3.7.4.
But the assessment is the same as the one for the rule messages for version 4.5.2 : the change of the browser language is
without effect, the language is still the default one. Is the mechanism still available for the latest versions?
Is there something I missed ?
Thanks for your help
2015-02-16 20:14 GMT+01:00 Simon Brandhof <[hidden email]>:
You're not doing anything wrong. i18n has been deprecated for rules.
On Tue, Feb 17, 2015 at 9:14 AM, El alaoui Mohamed Reda <[hidden email]> wrote:
Rather, i18n has been removed for rules.
On Tue, Feb 17, 2015 at 9:51 AM, G. Ann Campbell <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|