Bug #10525
closedChinese (taiwan) / HK Translation using incorrect identifier on 2.4.5
100%
Description
When I using pfsense 2.4.4 upgrade to 2.4.5 the language change Chinese(Taiwan) or HK has error.
When I want change language to Chinese(Taiwan) or HK has error. It always in English.
I found 2.4.4 is using zh_TW or zh_HK
But 2.4.5 is using zh_Hant_TW or zh_Hant_HK
and 2.4.5 /usr/local/share/locale does't have directories zh_Hant_TW or zh_Hant_HK
(When I using cp -R zh_TW zh_Hant_TW seems nothing to change , just only edit /cf/conf/config.xml , with zh_Hant_TW replace to zh_TW just ok)
Updated by Jim Pingle over 4 years ago
- Subject changed from When using pfsense 2.4.4 upgrade to 2.4.5 the language change chinese(taiwan) or HK has error to Chinese (taiwan) / HK Translation using incorrect identifier on 2.4.5
- Category set to Translations
- Assignee set to Renato Botelho
- Target version set to 2.4.5-p1
- Affected Version set to 2.4.5
- Affected Architecture All added
Updated by Renato Botelho over 4 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 249a0757d5f86c7f0c4229dd45b634c83dfeccd4.
Updated by Jim Pingle over 4 years ago
- Status changed from Feedback to In Progress
There is still some discrepancy here.
For HK the GUI is setting zh_Hans_HK and for TW the GUI is setting zh_Hant_TW. The upgrade code changes zh_HK and zh_TW to those names, but the files are actually in zh_HK and zh_TW.
Renato said there is still one more step left to do here.
Updated by Renato Botelho over 4 years ago
- Status changed from In Progress to Feedback
Applied in changeset 70b7144719d4ba6782bdd4f90af51ed736c9008e.
Updated by Jim Pingle over 4 years ago
- Status changed from Feedback to Resolved
The identifiers now match the language files on the filesystem, and changing to the language works as expected.
Unrelated to this, but using console options 16 and 11 to restart PHP-FPM and the GUI web server after changing the language may be necessary to ensure a consistent experience. Alternately, reboot after changing the language.
Since that quirk isn't related to this issue, and this issue is solved, I'm closing this out.