Bug 367970 - Allow copy of EXIF, IPTC and XMP from one to another image
Summary: Allow copy of EXIF, IPTC and XMP from one to another image
Status: RESOLVED DUPLICATE of bug 155384
Alias: None
Product: digikam
Classification: Applications
Component: Usability-Clipboard (show other bugs)
Version: 5.1.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-29 17:52 UTC by Hans-Peter
Modified: 2023-05-20 21:44 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter 2016-08-29 17:52:45 UTC 
Digikam 4.14 and older had a feature to import EXIF and other meta data from another image. Please implement this in 5.x as well.

Reproducible: Always
Comment 1 caulier.gilles 2016-09-06 05:20:23 UTC 

*** This bug has been marked as a duplicate of bug 155384 ***
Comment 2 b3nmore 2016-12-01 17:34:17 UTC 
(In reply to caulier.gilles from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 155384 ***

Not sure why this is a duplicate. Bug 155384 seems to be a request for general enhancement, which may or may not be implemented at some point. This bug is more like a regression, because exif, iptc and xmp import was already possible with digikam <5 and no replacement exist like in the bqm (or I have not found it ;)).
Comment 3 Hans-Peter 2016-12-01 20:53:10 UTC 
(In reply to b3nmore from comment #2)
> (In reply to caulier.gilles from comment #1)
> > 
> > *** This bug has been marked as a duplicate of bug 155384 ***
> 
> Not sure why this is a duplicate. Bug 155384 seems to be a request for
> general enhancement, which may or may not be implemented at some point. This
> bug is more like a regression, because exif, iptc and xmp import was already
> possible with digikam <5 and no replacement exist like in the bqm (or I have
> not found it ;)).

Thats correct, its a feature which has been lost during 5.x development, not an old bug.