https://bugs.kde.org/show_bug.cgi?id=495939
--- Comment #3 from mir-...@web.de --- Thank you for the information. The facts have become a little clearer to me. In the DB Browser for SQLite program, the entry UTF-8 is output as the value in the table under settings for keyword locale. Similarly, in the same database using SQL PRAGMA encoding; UTF-16le is output. This apparently caused Digikam to get confused and this constellation resulted in messages when Digikan was started. If I have understood you correctly, however, the SQL PRAGMA encoding; query is decisive for the database and the settings for keyword locale (which can theoretically also be changed via the database) are probably only important as a display function. -- You are receiving this mail because: You are watching all bug changes.
