-
Notifications
You must be signed in to change notification settings - Fork 17
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.
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
Add comment functions #41
Comments
Thanks for the suggestion! It looks like they are already exposed via the underlying (It also means that if you need this right now, a temporary workaround might be to call these functions directly) I think (but don't really remember) that I originally didn't expose them because I saw the comment you mentioned that suggests these are just wrappers for bulk-operating on fields that are already individually accessible… but you note that
Can you elaborate on that? What is not possible to do currently that only these wrappers provide? |
For example, if you take the dirty.jpg test file from mat2, it contains a "Created with GIMP" comment. If you try each of the fields mentioned in the docs, none of them return the comment. However, |
There is a JPEG comment, which is stored in the JPEG meta data along with width, height, depth information. This has nothing to do with Exif, XMP and IPTC metadata and is thus no accessible by It would be nice to have these functions wrapped to access the JPEG comment as well. Not all jpeg decoders for rust support reading the comment. |
Thanks for the clarification of where that extra metadata was coming from. In principle I agree it would be very desirable to be able to set/unset JPEG comments through this library as well, so I'm on board with the general goal here. Do you happen to know if there's any other JPEG metadata other than these comments that we should generalize this to? What I'm worried about is that exposing I wonder if upstream gexiv2 would be open to a PR implementing a set of functions for JPEG comments specifically (and/or any other JPEG metadata, if any such exists)... How would you feel about that approach? |
Well I don't see that gexiv2 is deprecating the use of It may be nice indeed to have specific functions for accessing only the comment, but if they are accepted, it will take time before downstreams are updated. Having the already existing functions available in rexiv2 would be great. |
GExiv2 has three functions to manipulate comments:
gexiv2_metadata_get_comment()
gexiv2_metadata_set_comment()
gexiv2_metadata_clear_comment()
It would be nice to have them as, contrary to what the
gexiv2_metadata_get_comment()
doc says, it can return metadata not accessible otherwise.The text was updated successfully, but these errors were encountered: