or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module supports loading translations in two formats: the .mo format used by gettext [https://docs.python.org/3.6/library/gettext.html#module-gettext] and related tools, and a simple .csv csv format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders supports loading translations in two formats: 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 tornado.locale.load_gettext_translations once at startup; see those methods for more details on the supported formats.. You can get the list of supported locales in your application with tornado.locale. ge

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module supports loading translations in two formats: the .mo format used by gettext [https://docs.python.org/3.6/library/gettext.html#module-gettext] and related tools, and a simple .csv csv format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module supports loading translations in two formats: the .mo format used by gettext [https://docs.python.org/3.5/library/gettext.html#module-gettext] and related tools, and a simple .csv csv format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module supports loading translations in two formats: the .mo format used by gettext [https://docs.python.org/3.6/library/gettext.html#module-gettext] and related tools, and a simple .csv csv format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module 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 format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module 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 format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module 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 format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module 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 format. An application 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

or a translation of the second string will be returned otherwise. The most common pattern for translations is to use Python named placeholders for variables (the %(num)d in the example above) since placeholders tornado.locale module 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 format. An application 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