[Digikam-devel] [Bug 195006] national charaters not accepted in database file path
Marcel Wiesweg
marcel.wiesweg at gmx.de
Sun Mar 18 17:22:01 GMT 2012
https://bugs.kde.org/show_bug.cgi?id=195006
--- Comment #25 from Marcel Wiesweg <marcel.wiesweg at gmx.de> ---
If you have a look at
http://sqlite.org/c3ref/open.html
passing the filename as UTF-8 to sqlite_open_v2 is explicitly required, any
other attempt would be a violation of the API documentation. See the note at
the bottom of the page, even though it is only directed at Windows users: "The
encoding used for the filename argument of sqlite3_open() and sqlite3_open_v2()
must be UTF-8, not whatever codepage is currently defined. Filenames containing
international characters must be converted to UTF-8 prior to passing them into
sqlite3_open() or sqlite3_open_v2()"
This is what I mean: we have a 100% unicode passthrough of the filename through
digikam and Qt, and obviously the data we have in digikam is correct.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Digikam-devel
mailing list