[Digikam-devel] [Bug 114211] image comments encoding unreadable after moving an album

[Marcel Wiesweg]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=114211         




------- Additional Comments From marcel.wiesweg gmx de  2006-05-02 18:36 -------
So we can do something about 1) and 2), not 3). Most important is 1), because the JFIF comment is read first, so when digikam reads any comment written by digikam, this one is used.

1) JFIF comment: Konqueror (the Jpeg KFilePlugin from kdegraphics) reads the JFIF comment as utf8.
I could not find any spec, and I do not know how other apps do it, but reading and writing utf8 here is the most easy solution.

2) EXIF comment: We need to interpret charset information from exiv2, I have some code for this on my computer. 
One question is what we do with the undefined charset: Ascii or local8Bit? Spec is just as specific on the question ("Although the possibility of unreadable characters exists, display of these characters is left as a matter of reader implementation.")
Second question is whether we write the EXIF comment as Unicode (I think ucs2, not utf8). Other choices are Ascii or Undefined. Said KFilePlugin does not support unicode (reading ascii, but the value is not used at all I think). Which other apps could I test this with?