Summary: | russian tags wrong after batch recompression | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Kostya Sha <gentoo.integer> |
Component: | Plugin-Bqm-Convert | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | aspotashev, caulier.gilles |
Priority: | NOR | ||
Version: | 1.2.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Attachments: | screenshot |
Description
Kostya Sha
2010-05-22 21:48:30 UTC
Where are you storing your tags in the image? XMP? IPTC? EXIF? Michael Created attachment 43808 [details]
screenshot
don't know, where i can check ?
Michael, Sound like in Database only... Strange. Gilles Caulier Hmm for me neither tags nor captions / comments are saved when I process a file with BQM. Is this the default behavior? Andi, This is fixed in current implementation from svn. Gilles Caulier Kostya, Do you use "Tools/Recompress Images" menu entry from album GUI ? Gilles Caulier digiKam 1.6.0 is out: http://www.digikam.org/drupal/node/550 Please update and check if this entry still valid. Thanks in advance Gilles Caulier We need feedback using a recent version. 2.0.0 RC is out, please test... Thanks in advance Gilles Caulier Nothing wrong happens when I write text in Russian in the "Caption:" field in EXIF metadata editor and then use "Tools -> Recompress Images...". But there is a problem with IPTC: if you type in some text in Russian in the "Caption:" field and then click "Apply", all Russian letters immediately become question marks. There is of course a note that non-ascii characters shouldn't be used in IPTC tags, but I think that non-ascii characters should be blocked from entering (like in EXIF fields marked with an asterisk). I have digiKam 1.9.0. There is a bigger problem: if you write Russian text into "Caption" in EXIF and then restart digiKam, that text appears to be copied into "Caption" in IPTC tags, and it becomes question marks. yes caption is dispatched into Exif, iptc, and Xmp. There is an entry in bugzilla to add a new option to drop IPTC management for writting. https://bugs.kde.org/show_bug.cgi?id=214708 Gilles Caulier That's just a wish for an option. But what I'm talking about (and what was also described in the 2nd comment in bug#214708) is a _bug_ which leads to corrupt metadata when the user doesn't expect it. Alexander: Gilles proposes as a fix that IPTC is ignored and the comment is only written to Exif and XMP (as an option). What other solution do you think of, how does this bug differ? IPTC only supports Ascii, so with Russian, either question marks or nothing. What I suggest is to write IPTC caption only if it is ascii-only. If there is at least one non-ascii character, IPTC should be either cleared or kept unchanged. Official digiKam 2.6.0 release is out since few days now : http://www.digikam.org/drupal/node/656 Please, check if this entry still valid, or update report accordingly. Thanks in advance. Gilles Caulier Code has been added which checks for 7-bit and uses unicode otherwise New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? With digiKam 5.0.0 this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier |