https://bugs.kde.org/show_bug.cgi?id=382362 Bug ID: 382362
Summary: Locale database mismatch between Windows and Linux
Product: digikam
Version: 5.6.0
Platform: Other
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Portability
Assignee:
[hidden email]
Reporter:
[hidden email]
Target Milestone: ---
Created attachment 106638
-->
https://bugs.kde.org/attachment.cgi?id=106638&action=editdigiKam complaining Linux's locale “UTF-8” mismatch Windows' “System” one
I'm hosting a database for some digiKam users. Current digiKam users are
running digiKam 5.6.0 on Windows because they also use some special
Windows-only tools that are unavailable on Linux. So, the database has never
seen any Linux client yet and was entirely populated by Windows digiKam
instances.
It would be possible in the future to have digiKam users running Linux, so I
tried to connect a digiKam 5.6.0 (appImage build) on Debian Stretch. But once I
entered the MySQL database credentials, digiKam raises a pop-up window saying
me my “locale changed since this album was last opened”, saying my current
locale is UTF-8 and the current database one is “System” (probably an internal
Windows name). See the screenshot attached.
So, as a precaution, I canceled the configuration and haven't opened the
Database from Linux.
Do you think there is some corruption risk if opening from Linux a MySQL
digiKam databases created from digiKam running on Window10?
Also, even if there would not been any risk for the database content itself, it
would be very annoying for users if anytime a Linux user got the pop-up warning
after a Windows user, and the Windows user having the warning anytime after a
Linux user.
It looks like the databases are currently using the “latin1_swedish_ci”
collation for everything including file paths and tags, something that is not
making me happy because I wonder if digiKam would handle correctly tags like
“Lætitia « mémé » Çitöl” (including the non-breakable thin space you wouldn't
notice). But that's probably another issue.
--
You are receiving this mail because:
You are the assignee for the bug.
Locked
