at:i18n was taking care of that, but it always uses the default i18n literals.
It's weird, but I only got working the i18n in the plugin xml file (e.g.
i18n-name-key), but I may have something wrong in my plugin...
Beside the resource tag with the file, you also need a transformation in the web-resource and the component-import.
<transformation extension="js"> <transformer key="jsI18n"/> </transformation>
<component-import key="i18nResolver" interface="com.atlassian.sal.api.message.I18nResolver"/>
Hope this helps,
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
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!
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