Bug 518688 - macOS: digiKam cannot switch application language to Simplified Chinese (zh_CN)
Summary: macOS: digiKam cannot switch application language to Simplified Chinese (zh_CN)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Bundle-MacOS (other bugs)
Version First Reported In: unspecified
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-04-08 09:46 UTC by wsyxbcl
Modified: 2026-04-09 05:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 9.1.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description wsyxbcl 2026-04-08 09:46:52 UTC 
I receive this bug report from multiple macOS users, and I can't reproduce it myself as a linux user.

According to the affected users, digiKam does not switch its UI language to Simplified Chinese (zh_CN) on macOS. This has been reproduced by multiple users. And they are already using Chinese as their macOS system language, which doesn't appear to be the cause.

Related bug: https://bugs.kde.org/show_bug.cgi?id=407236
Comment 1 caulier.gilles 2026-04-08 10:17:35 UTC 
It work here, using current 9.1.0 pre-release.

https://www.flickr.com/photos/185465119@N02/55194937504/in/dateposted-public/

Chinese translations are certainly incomplete as you can see some parts still in English, but mostly 85% are translated here.
Comment 2 Maik Qualmann 2026-04-08 11:24:45 UTC 
The problem should be fixed with Bug 510941.

Maik
Comment 3 caulier.gilles 2026-04-08 11:39:27 UTC 
Please try with the 9.1.0 pre-release available here : https://files.kde.org/digikam/
Comment 4 wsyxbcl 2026-04-09 02:50:07 UTC 
(In reply to Maik Qualmann from comment #2)
> The problem should be fixed with Bug 510941.
> 
> Maik

Thanks for mentioning 510941, the issue was reported to me before that fix, so this should have been fixed.
Comment 5 wsyxbcl 2026-04-09 02:50:39 UTC 

*** This bug has been marked as a duplicate of bug 510941 ***