Bug 120995 - Digikam complains about GNOME locale settings, even after correcting them
Summary: Digikam complains about GNOME locale settings, even after correcting them
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Usability-i18n (show other bugs)
Version: 0.8.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-29 19:51 UTC by Dik Takken
Modified: 2022-01-23 09:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dik Takken 2006-01-29 19:51:25 UTC
Version:           0.8.0-beta2 (using KDE KDE 3.5.0)
Installed from:    Gentoo Packages
OS:                Linux

After changing the locale settings for the GNOME applications on my system, DigiKam complained that this could lead to problems. So, I changed the GNOME locale back to the original setting. But DigiKam still complains, claiming that the locale setting is still not wat it used to be.

By the way: Why on earth does DigiKam complain about locale settings that only apply outside of KDE??
Comment 1 Tom Albers 2006-02-04 20:10:06 UTC
digikam checks the locale which is used for digikam, mostly that will be the systems locale. If you need digikam to launch with a specific locale, then you can start the program with:
LC_ALL=ISO8859-15 digikam   

By the way, I think you change the system locale in GNOME, not only the locale used for GNOME apps.
Comment 2 Dik Takken 2006-02-05 13:20:05 UTC
I changed the LC_ALL environment variable, which changes the locale of all applications, except for KDE applications.

So, why is DigiKam an exception? Why can I not change the system locale without the risk of breaking DigiKam? Switching locale has never been a problem before.

Comment 3 Achim Bohnet 2006-02-08 02:06:27 UTC
Hi Dik,

the only reason I know is that folder/albums and filenames with non-ascii
chars could not be found anymore.   And digikam would (after asking the user)
delete them from the database.   So one would lose tags and comments for
all files and the complete subtree of folder/albums with non ascii chars
in them.

Ah, btw once apon a time digikam stored <lang>_<country>.<encoding>.
Now only <encoding> is stored (as it should be).   So if you get
something like

 old: de_DE.UTF-8  new: UTF-8

you can ignore the message.  At least I did ;)  (nevertheless make sure you have
a backup copy of you images)

Developers: If this is really the only reason, maybe we could enhance the error
message to explain this? (with a reference to a more complete explanation& howto-fix)

Achim

Comment 4 Dik Takken 2006-02-08 10:42:23 UTC
> maybe we could enhance the error message to explain this?

That would be a Good Thing. The message may scare some users to death, especially if they don't know how to switch character encoding, or what a character encoding is.

Is it technically possible for DigiKam to actually check if all albums are still accessible using the new encoding? This will cause the message to popup *only* in cases where real trouble is to be expected, like when the user switches from chinese to english or something.