i18n plugin localization

Hi,

I want to use own i18n plugin localization. When I wrote loc_cs_CZ.properties file as equivalent to english localization in loc.properties everything looks fine, but if user change language profile back to english (or the other language), original english labels will not populate back.

What Im doing wrong, or need register some additional resources?

Thx for help,

RK

5 answers

1 accepted

Accepted Answer
0 votes

It is my own plugin for JIRA 4.1.2, where in atlassian-plugin.xml I have

<resource type="i18n" name="i18n" location="i18n.messages" />

and in resources folder I have localization files

i18n/messages.properties

i18n/messages_cs_CZ.properties

If I remove cs, english labels are shown, but Im not albe to have these two localizations together.

Problem solved.

In what product (JIRA, Confluence) and what kind of plugin are you trying to localize? Without that information, we can only guess, what you are trying to do.

Can you show me how ?

It was some issue/bug in JIRA 4.1. If I installed JIRA with selecting cs_CZ as my default location in instalation process and than try change to en, it used my cs_CZ properties as primary. Try over-ride the default locale used by the JVM: -Duser.language=en -Duser.country=US (add into the some setenv, properties startup JIRA file) The other way is reinstal all application.

In resources folder I have 2 files

note_plugin_en.properties

note_plugin_fr.properties

And I have 2 button for users to change the language. I dont know how to change the display language when users click on buttons. Can you give me some suggestion ?

Im working on JIRA 5.0.

Thank you.

Just stumbled over the same problem in JIRA 4.4.

  • My system is locale is German (de).
  • The default locale configured in JIRA is English (UK).
  • I have two propertiy files: messages.properties (default/fallback) and messages_de.properties (German)
  • When selecting, e.g. French, JIRA would not fall back to the default properties (messages.properties) but, in my case, to the german ones (messages_de.properties). So instead of using the configured English locale, the German locale was used.

Changing the locale used by the JVM as described here fixed the problem.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 11 hours ago in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

158 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you