nextcloud
[Bug]: Translation issues still unresolved
⚠️ Before submitting, please verify the following: ⚠️
- [x] This is a bug, not a question or a configuration issue.
- [x] This issue is not already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
- [x] I agree to follow Nextcloud's Code of Conduct
Bug description
I have updated to the latest version, but the language is still not updated to the language of my computer (Simplified Chinese). The language used by the software is still English after a certain update.
Steps to reproduce
No need to do anything
Expected behavior
Show Chinese
Which files are affected by this bug
None
Operating system
Windows
Which version of the operating system you are running.
Windows11
Package
Official Windows MSI
Nextcloud Server version
30.0.2
Nextcloud Desktop Client version
3.16.2
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
- [ ] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
Nextcloud Server logs
Additional info
thanks for reporting this issue again! the one that we resolved with #8081 was affecting macOS only.
in that PR I also added some extra logs at application startup to help with diagnosing issues regarding translations there. --> can you please try a daily build and post the first few log lines? (I'm interested in the ones that contain application.cpp:)
I installed the daily build. The version now displayed is: 3.17.0 alpha (Windows). I don't see the logs containing what you describe. @nilsding
@AinzLimuru thanks for providing the logs
I was interested in these two lines (found them in 20250329_2254_nextcloud.log.0.gz):
2025-03-29 22:54:23:142 [ info nextcloud.gui.application C:\Users\User\AppData\Local\Temp\windows-29568\client-building\desktop\src\gui\application.cpp:1006 ]: System UI languages are: QList("zh-Hans-CN", "zh-CN", "zh", "en-US", "en-Latn-US", "en")
2025-03-29 22:54:23:142 [ info nextcloud.gui.application C:\Users\User\AppData\Local\Temp\windows-29568\client-building\desktop\src\gui\application.cpp:1009 ]: selected application language: "zh_Hans_CN"
seems like we need to update the language substitution function used during application startup... I'll see what I can do
Also noticed on some macOS environment (English UI occurs despite the operating system language is in French). Two tests with desktop client 3.14 and 3.16 : same result.
@Jerome-Herbinet try a daily macOS build -- with #8081 merged this should work again.
will be part of ~~3.16.3 and~~ 3.17.0
@AinzLimuru for the time being if you're on a daily build >= 20250408 you can enforce the UI language by setting this in your %APPDATA%/Nextcloud/nextcloud.cfg:
[General]
language=zh_CN
This doesn't resolve the autodetection issue however, so I'll leave this issue open.
@nilsding Windows 11 is configured with language=zh_CN but it doesn't work. Maybe you need to explicitly add the language selection option in the settings.
3.16.3 same ,Could this be a compatibility issue with the older configuration?
I add language=zh_CN to nextcloud.cfg seems not worked
@ted423 Download it from here. https://download.nextcloud.com/desktop/daily/
@ted423 sorry for that, I got confused where this config change would end up in 😅
as it's already available in the daily builds it'll be part of 3.17.0
3.16.3 same ,Could this be a compatibility issue with the older configuration? I add
language=zh_CNto nextcloud.cfg seems not worked
3.17.2 I used the method provided by #8096 to edit %APPDATA%\Nextcloud\nextcloud.cfg and added language=zh_CN under [General], successfully setting the language to Chinese.
The Windows client version 4.01 still requires editing Nextcloud.cfg to specify a language that is consistent with the operating system.
@nilsding I tested the command line dism /online /get-intl and it returned the correct language information. Is it possible to improve the language selection process based on this?
@AinzRimuru while it would be possible in theory, it's rarely a good idea to invoke an external command just to e.g. determine the language/locale to be used.
@AinzRimuru while it would be possible in theory, it's rarely a good idea to invoke an external command just to e.g. determine the language/locale to be used.
My idea is whether it's possible to mimic the implementation of DISM to call system functions.
