the .mo format used by gettext and related tools, and a simple .csv format. An application will generally call either tornado.locale. load_translations or tornado.locale.load_gettext_translations once at one of load_translations (which uses a simple CSV format) or load_gettext_translations (which uses the .mo format supported by gettext and related tools). If nei- ther method is called, the Locale.translate detection, UTF- 16, and UTF-8-with-BOM. tornado.locale.load_gettext_translations(directory: str, domain: str) → None Loads translations from gettext’s locale tree Locale tree is similar to system’s /usr/share/locale

supports loading translations in two formats: the .mo format used by gettext [https://docs.python.org/3/library/gettext.html#module-gettext] and related tools, and a simple .csv format. An application will will generally call either tornado.locale.load_translations or tornado.locale.load_gettext_translations once at startup; see those methods for more details on the supported formats. You can get the list tornado.locale — Internationalization support get() set_default_locale() load_translations() load_gettext_translations() get_supported_locales() Locale Locale.get_closest() Locale.get() Locale.translate()