Translation failed caused by unicode verbose_name when a table is init
Bug #962417 reported by
Jim Yeh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Jim Yeh |
Bug Description
As you change your language in the setting panel,
you will find that the translation will be failed in tables.
I think it is because the instantiation of HorizonSite generate each table class.
Then, the verbose_name is fixed in its __metaclass__.
There is a similar bug. https:/
But, I think the bug is just because the translation is not finished.
Changed in horizon: | |
milestone: | none → essex-rc2 |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Nebula (nebula) |
Changed in horizon: | |
assignee: | Nebula (nebula) → Jim Yeh (lemonlatte) |
status: | Confirmed → In Progress |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | essex-rc2 → 2012.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/5700 github. com/openstack/ horizon/ commit/ 8e83bc8bc406a70 432ea52084010f0 3765c3aa1c
Committed: http://
Submitter: Jenkins
Branch: master
commit 8e83bc8bc406a70 432ea52084010f0 3765c3aa1c
Author: Jim Yeh <email address hidden>
Date: Thu Mar 22 21:15:56 2012 +0800
Use ugettext_lazy for verbose_texts instead of unicode.
* Fix bug 962417
DataTableOption is initialize will
* Change the ugettext to ugettext_lazy
* Unicode the verbose_name while the
make the translation fixed.
* Similar scenario in Column class and Action class.
Change-Id: I69ce9f89b0f0c2 afb32b26e15ea8d b84828d840f