# Add a new language to Indico 2.2

**URL:** <https://talk.getindico.io/t/add-a-new-language-to-indico-2-2/1874>\
**Category:** Administrators\
**Created:** [July 26, 2020, 6:35am UTC](https://talk.getindico.io/t/add-a-new-language-to-indico-2-2/1874 "2020-07-26T06:35:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ThiefMaster](https://talk.getindico.io/user_avatar/talk.getindico.io/thiefmaster/32/509_2.png) [@ThiefMaster](https://talk.getindico.io/u/ThiefMaster)\
**Post date:** [July 26, 2020, 6:59am UTC](https://talk.getindico.io/t/add-a-new-language-to-indico-2-2/1874/2 "2020-07-26T06:59:38Z")

</div>

The `es_ES` errors are safe to ignore. For chinese to work properly you need to rename `zh_CN.GB2312` to `zh_Hans_CN`.

After `indico i18n compile-catalog` the `indico/translations/zh_Hans_CN/LC_MESSAGES/` folder should contain `messages.mo` plus the other files (`messages.po`, `messages-js.po`, `messages-react.po`, [`messages-react.json`]). Once `messages.mo` exists restarting uwsgi should be enough for the language to show up in Indico.

PS: Usually you should compile the i18n files locally on a dev setup and then copy the folder. Doing it on a production system will likely work (but I don’t think any of us tested it!) for the Python/Jinja translations (`indico i18n compile-catalog` for messages.po to messages.mo), and for the classic JS translations (messages-js.po - nothing to compile there), but NOT for the new React translations (`indico i18n compile-catalog-react` for messages-react.po to messages-react.json), since the tools for this are only available on a dev setup!

---

_[View the full topic](https://talk.getindico.io/t/add-a-new-language-to-indico-2-2/1874)._
