Strings in local_settings.py.example are not translated

[Akihiro Motoki]

Strings in local_settings.py.example are not translated because local_settings.py.example is not recognized as python file and the strings are not contained in PO file.

One idea in my mind is to rename local_settings.py.example to local_settings_example.py so that "run_test.sh --makemessages" can recognize it as Python file. This way brings another merit that local_settings.py example file will be checked by pep8.

[Julie Pichon (jpichon)]

There are more general issues and questions around having translatable strings in the settings in general too. If a deployer changes them, translations don't exist and it seems difficult for a deployer to fix that. It also causes problems (or could be considered "resolved by", I suppose :-)) for a blueprint like https://blueprints.launchpad.net/horizon/+spec/ini-based-configuration .

[Akihiro Motoki (amotoki)]

I agree that translatable strings in the settings have more problems in general.

IMHO if a deployer introduces new strings, they need to update message catalogs
if they want to use translated strings. It is a common thing when deployers need
to provide new strings/messages with multiple languages.

I was not aware of blueprint ini-based-configuration. I am a fun of the blueprint
but I am not confident whether we should customize menu through ini files.

[Rob Cresswell (robcresswell-deactivatedaccount)]

Hey Akihiro,

If it is okay with you, I'll move this out of RC1. There doesn't seem to be a solid plan for how to solve this for now.

[Akihiro Motoki (amotoki)]

I am okay to move it to Mitaka. I remove my assignee too.

We don't have a concrete plan.
For the default value defined in our settings, the migration to support oslo.config in Horizon may help us.

[Akihiro Motoki (amotoki)]

This bug can be addressed as part of https://blueprints.launchpad.net/horizon/+spec/ini-based-configuration
Once options are defined in the main horizon code, strings in default values can be extracted.