| Summary: | Tags are not written to files on export or save when editing TIFF files | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Guillaume Paumier <guillom.pom> |
| Component: | Plugin-DImg-TIFF | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.0.0 | |
| Sentry Crash Report: | |||
|
Description
Guillaume Paumier
2011-06-19 17:47:38 UTC
No reproducible here. How do you check if tags are not written in file ? XMP contain relevant tags ! Gilles Caulier > Steps to Reproduce:
> 1. Add a tag to a TIF file
> 2. Open the TIF file in the image editor
> 3. Export or save the TIF file to another format (e.g. JPG)
> 4. Metadata and ratings are written to the exported file, but tags are not.
The relevant code would be ImageWindow::prepareImageToSave(), which is image
format agnostic.
You have double checked that the relevant field in the settings, to write tags
to metadata, is enabled?
This is why I would like to ask for confirmation for some of the specific
claims here:
- it happens only when editing a TIFF file, specifically not when editing a
JPG or PNG file
- it happens when saving to "another format", which means at least JPG and a
second format like PNG were tested
- digikam writes tags to fields in IPTC and XMP. All fields are empty.
Thanks
(In reply to comment #2) > > You have double checked that the relevant field in the settings, to write tags > to metadata, is enabled? Yes. I didn't check the output of exiv2 for the generated files; I noticed the tags were missing in the digikam interface, in the album view. Furthermore, when the generated image was exported to an online service (Flickr), no tags were added, even though the plugin option to "use tags from the host application" was checked. So I guess the problem was that the tags were not saved into the database. That said, I just compiled the latest trunk, and the problem seems to be fixed now. |