Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Keeping metadata #26

Open
javiergutierrezchamorro opened this issue Oct 30, 2016 · 4 comments
Open

Keeping metadata #26

javiergutierrezchamorro opened this issue Oct 30, 2016 · 4 comments
Labels
feature request

Comments

@javiergutierrezchamorro
Copy link

It is documented that most metadata is removed from most formats, with the exception of keep-exif swith.

Would be nice having a global flag to not remove any metadata at all, or to selectively keep it as keep-iptc, ...
TPS referenced this issue in svn2github/nikkhokkho Nov 9, 2016
Disabled Leanify from the JPEG toolchain when copy metadata is enable…
f4d24b8 
…d, because it removed IPTC information (ZonaCasio).

git-svn-id: svn://svn.code.sf.net/p/nikkhokkho/code/trunk@608 ddd8a7e7-04a1-4c0d-ae79-48073a28b335
TPS referenced this issue in svn2github/nikkhokkho Nov 9, 2016
Disable Leanify in PNG and ICO when Copy Metadata is checked (ZonaCasio)
d30d69e 
git-svn-id: svn://svn.code.sf.net/p/nikkhokkho/code/trunk@610 ddd8a7e7-04a1-4c0d-ae79-48073a28b335
@JayXon
Copy link
Owner

JayXon commented Dec 3, 2016

I don't think I can have a global flag anytime soon since leanify is designed to remove all metadata from the beginning, but I could add some flags like keep-iptc and keep-icc-profile for jpeg and png.

@javiergutierrezchamorro
Copy link
Author

Thanks. That would be enough for starting.

JayXon added a commit that referenced this issue Dec 4, 2016
@JayXon
Add --keep-icc-profile and --jpeg-keep-all-metadata #26
866d4ad
@TPS
Copy link

TPS commented Dec 4, 2016

As an intermediate to a --keep-all-metadata, wouldn't it be reasonable to have a --keep-all-known-metadata (-kakm, for short, maybe), which simply combines all current & future --*keep* switches?

@JayXon
Copy link
Owner

JayXon commented Dec 4, 2016

I don't like the idea of a vaguely defined switch, I want all the switches to have a well defined expected behavior that doesn't depend on the implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@TPS @JayXon @javiergutierrezchamorro