Consider an event model. Allow the user to define export post process hooks. When export done call the desired post process hook with the file as a parameter. Initial release could just be a blank box. Later releases could offer predefined commands, such as remove all exit data via the exiftool.
Further in a future release this could be extended to allow for automatic exporting when any attribute or condition on the image has changed. Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Pascal Obry <pas...@obry.net> Sent: Tuesday, January 1, 2019 11:57:19 AM To: Timur Irikovich Davletshin; darktable-user@lists.darktable.org Subject: Re: [darktable-user] Exporting tags → JPEG keywords Le mardi 01 janvier 2019 à 22:23 +0300, Timur Irikovich Davletshin a écrit : > System-wide settings will do fine too :) Just few lines to add new > checkbox in settings and additional check in common/exif.cc lines 2472- > 2473 (is it the one which constructs XMP structure?)... Don't like the system wide setting here. There is case where you want to export with tags and case where you don't want depending for who you export (yourself, client for the Web...). -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.or
