# What's the new ui\_i18n?

**URL:** https://discuss.elastic.co/t/whats-the-new-ui-i18n/166372
**Category:** Kibana
**Created:** [January 30, 2019, 2:11pm UTC](https://discuss.elastic.co/t/whats-the-new-ui-i18n/166372 "2019-01-30T14:11:41Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![whoami](https://avatars.discourse-cdn.com/v4/letter/w/a9a28c/32.png) [@whoami](https://discuss.elastic.co/u/whoami)
#### Post date: [January 30, 2019, 2:11pm UTC](https://discuss.elastic.co/t/whats-the-new-ui-i18n/166372/1 "2019-01-30T14:11:41Z")

</div>

seems kibana6.6 remove ui\_i18n.js, and there is no translations anymore.

```auto
return new kibana.Plugin({

  uiExports: {
    translations: [
      resolve(__dirname, './translations/zh_CN.json')
    ]
  },
});

```

what's the replacement in kibana6.6, I do not see the breaking change in release log

---

<div class="post-metadata">

### Author: ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)
#### Post date: [January 30, 2019, 3:01pm UTC](https://discuss.elastic.co/t/whats-the-new-ui-i18n/166372/2 "2019-01-30T15:01:30Z")

</div>

@whoami this seems to be an internal implementation change, and probably the reason why it isn't listed in the breaking changes doc.

---

<div class="post-metadata">

### Author: ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [January 30, 2019, 4:26pm UTC](https://discuss.elastic.co/t/whats-the-new-ui-i18n/166372/3 "2019-01-30T16:26:15Z")

</div>

Hey @whoami,

Yep, we changed the way Kibana and i18n work together. Before 6.6 the i18n approach was never fully supported, so that's probably why it wasn't mentioned in the release notes as a breaking change. But that has changed, please read [this](https://github.com/elastic/kibana/blob/6.6/packages/kbn-i18n/README.md) and [this](https://github.com/elastic/kibana/blob/6.6/packages/kbn-i18n/GUIDELINE.md) to know how to use i18n framework Kibana provides.

In short you don't need to define `uiExports.translations` anymore, just place `zh-CN.json` inside of `your-plugin-folder/translations` folder and it will be picked up automatically.

**Note:** please use BCP47 compatible locale name for both `i18n.locale` and JSON file name i.e. use dash instead of underscore.

Let me know if you have any questions regarding i18n.

Best,  
Oleg

---

<div class="post-metadata">

### Author: ![whoami](https://avatars.discourse-cdn.com/v4/letter/w/a9a28c/32.png) [@whoami](https://discuss.elastic.co/u/whoami)
#### Post date: [January 31, 2019, 7:32am UTC](https://discuss.elastic.co/t/whats-the-new-ui-i18n/166372/4 "2019-01-31T07:32:08Z")

</div>

awesome

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 28, 2019, 7:32am UTC](https://discuss.elastic.co/t/whats-the-new-ui-i18n/166372/5 "2019-02-28T07:32:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
