Unlocalized locale menu

[Yuko Katabami]

It would be nice if the list of locales are localized into corresponding languages.

[Julie Pichon (jpichon)]

Thank you for all the i18n bug reports Yuko.

With regard to the locale menu, it's actually a conscious decision to leave them in English. I remember when this was discussed in Horizon (bug 1254488), if a user ends up with the interface in a language they don't understand, they won't be able to recognise their language from the list if they are also translated. Then there are two options, either keep the languages list in English or keep every language name the way it's said in the language itself... The English list is the easiest to maintain so we decided to go this way, which I believe Horizon is still doing as well.

[Yuko Katabami (ykatabam)]

Hi Julie,

Thank you very much for explaining the reason behind.
It makes sense to me and I don't think any non-English users have issues with choosing a desired language from the English list, but Horizon still uses translated locale names.
See attached screenshot.

[Yuko Katabami (ykatabam)]

Hi Julie,

Thank you very much for explaining the reason behind.
It makes sense to me and I don't think any non-English users have issues with choosing a desired language from the English list, but Horizon still uses translated locale names.
See attached screenshot.

[Julie Pichon (jpichon)]

Oh I see, so they went with keeping each name in the original language. I'm not sure about doing this in tripleo-ui at the moment, the language name is kept in a user-configurable variable (so deployers could change the language names if they wished) but I'm happy to let the bug be reopened if people think it's a good idea- I see advantages to both ways.

[Yuko Katabami (ykatabam)]

Thank you very much, Julie.

[Julie Pichon (jpichon)]

As part of bug 1682452, the language names are being moved from a user setting back into a regular variable. Now that the two reasons I brought up in comment #2 & #5 are invalid, perhaps it would be worthwhile re-investigating doing something similar to the screenshot in comment #4 for localised language names.

[sandeep_s (sandeep-shedmake)]

Just a note that, reported problem persists with Pike.

bug 1732875 comment 1, lists non i18ned strings (in json).

Example:
"http://192.168.24.1:3000/login": ["British English", "English", "French", "German", "Indonesian", "Japanese", "Korean", "Simplified Chinese", "Spanish", "Turkish"]

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE