Am Donnerstag, 18. Juli 2013, 19:44:44 schrieb Aahz Maruch: > On Thu, Jul 18, 2013, Tobias Ellinghaus wrote: > > So the first question that needs to be sorted out is "is supporting IPTC > > enough?" or do we also need all the exif and XMP fields? And if we decide > > that IPTC is all we need, are there standardized translations to/from > > exif and xmp? Because, if we get fed an image (or sidecar file) that > > contains relevant information in those metadata sets, we surely want to > > keep them. The alternative would be to support all possible data sets, > > however, that would mean that we > > 1) have to decide what to do when the user changes the "Author" value in > > exif. Shall it be changed for IPTC, too? > > 2) have to find a way to not make the GUI too cluttered and ugly, > > > > I personally would favour limiting ourselves to IPTC in the GUI and when > > finding some other data sets while reading the image we should translate > > these to IPTC. > > The one constraint I would add to this is that given an image with EXIF > data, the exported file should have the same EXIF data. Otherwise (and > particularly given the DT developers' reluctance to extend the file > management capabilities) it would be difficult to write tools that manage > sets of data.
Of course, all the exif stuff is completely separated and will keep working as it already does.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
