Reviewed: https://review.opendev.org/c/openstack/horizon/+/940297 Committed: https://opendev.org/openstack/horizon/commit/d79022eb33f639ca4e3657388ea8f2181de02960 Submitter: "Zuul (22348)" Branch: master
commit d79022eb33f639ca4e3657388ea8f2181de02960 Author: Radomir Dopieralski <[email protected]> Date: Tue Jan 28 12:05:27 2025 +0100 Do column name translations at runtime, not at import The column's verbose_name was forced to a string from a lazy translation at the object's creation time, which happens when the table definitions are imported, and when the user language preference is not set yet. Instead force it to a string at the very last moment, when it is used in a template. Fixes-bug: 2093276 Change-Id: I9cd3bc2535915a858aa380287fccd89d0f19cf7d ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/2093276 Title: problems with translation Status in OpenStack Dashboard (Horizon): Fix Released Bug description: OpenStack version: 2024.2 (Dalmatian) OS version: AlmaLinux 9.5 There are some strange issues with translation on other languages besides (English(en)). After switching to other languages following column names stays untranslated. Only images (both in project and admin sections), key pairs and server groups sections have translated text in it's table columns. See attached screenshot. What can cause this issue? All the corresponding msgid's are included LC_MESSAGES/django.mo files. These names somehow stay the same. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/2093276/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
