Requirements: - metadata go with the image, preferably in the image - no data loss, no legacy data loss - automatically migrate legacy data to XMP - XMP sidecar can override exif values stored in unwritable raw file - cooperation with metadata editors that don't support XMP - preserve originals - handle photos on read-only filesystems reasonably well
Another thing to consider is security properties of filesystems, althought this is much more critical with thumbnails. Somtimes people keep images in a cryptographic file system (perhaps to comply with nondisclosure agreements for commercial customers, or some other reason). It might be that the location of images is sensitive. As a general rule, I think programs like geeqie should not read data from an image file and write it in another location unless the user explicitly opts in to that behavior, perhaps per source filesystem. So XMP sidecars in the same directory seem fine. Geeqie now uses text files for storing keywords and comments. This format should be used only for compatibility and when the XMP via Exiv2 is not I think you should consider simply requiring exiv2, period, and not building without it. Maintaining a separate path seems like far more work than fixing exiv2 on some platform, and less useful.
pgptdOM9i8Leu.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
