Localization in murano doesn't work

Bug #1377883 reported by Dmytro Dovbii on 2014-10-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Alexey Khivin

Bug Description

Gettext machinery doesn't work fully.
It correctly collects all marked strings and compiles message catalogs, but it doesn't load and activate the appropriate message catalog at runtime.
The issue is probably lies in TranslatorFactory's constructor. It's trying to get a value that does not exist:

> localedir = os.environ.get(domain.upper() + '_LOCALEDIR')

Dmytro Dovbii (ddovbii) on 2014-10-06
summary: - Localization in murano-api doesn't work
+ Localization in murano doesn't work
Changed in murano:
importance: Undecided → Medium
Ekaterina Chernova (efedorova) wrote :

Need to use oslo translation machinery and test after it

Changed in murano:
status: New → Confirmed
milestone: none → liberty-1
Alexey Khivin (akhivin) on 2015-05-19
Changed in murano:
assignee: nobody → Alex Khivin (akhivin)
Changed in murano:
milestone: liberty-1 → liberty-2
Changed in murano:
milestone: liberty-2 → liberty-3
Changed in murano:
milestone: liberty-3 → liberty-rc1
Changed in murano:
milestone: liberty-rc1 → next
Alexey Khivin (akhivin) wrote :

looks like localization in murano implemented exactly the same way as others openstack components do.
There are no translated messages yet but there is the blueprint on murano localization https://blueprints.launchpad.net/murano/+spec/murano-i18n

Changed in murano:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers