-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.440 on Ubuntu, Java 11
To reproduce:
- open Jenkins using the Czech localization
Expected
- correctly encoded links in side panel (e.g. People=Lidé)
Actual
- wrong encoding for items supplied by Core (People=Lidé)
- correct encoding for items supplied by plugins (e.g. https://github.com/jenkinsci/lockable-resources-plugin/blob/346d600eea2422ac91d6aa41d91a37723508cfe4/src/main/resources/org/jenkins/plugins/lockableresources/actions/LockableResourcesRootAction/index_cs.properties#L24 )
- localization coming from the `Messages` classes generated by Localizer seems OK
- correct result in ScriptConsole with
ResourceBundle.getBundle("hudson.model.View.sidepanel").getString("People")
[JENKINS-72832] Wrong string encoding in jelly files
Basil Crow
added a comment - I can't reproduce this problem on latest weekly. I installed the Locale plugin and set the default language to "cs" in Manage Jenkins and checked "Ignore browser preference and force this language to all users". Everything is displayed correctly, including Lidé and Uzamykatelné zdroje. I am running Java 11 and Firefox 123.0.1 on Linux. I think there were previously some problems with the "Localization Support" (not to be confused with "Locale") plugin, but those should have been fixed already.
Basil Crow
added a comment - I can't reproduce this problem on latest weekly. I installed the Locale plugin and set the default language to "cs" in Manage Jenkins and checked "Ignore browser preference and force this language to all users". Everything is displayed correctly, including Lidé and Uzamykatelné zdroje. I am running Java 11 and Firefox 123.0.1 on Linux. I think there were previously some problems with the "Localization Support" (not to be confused with "Locale") plugin, but those should have been fixed already.
basil I saw you've done the UTF conversion of core properties files, do you have some idea how to debug this?