Open GoogleCodeExporter opened 8 years ago
face tags saved as a metadata *tag.
Original comment by Supreme1...@gmail.com
on 9 Sep 2010 at 3:04
I thought about implementing this when I made my old patches. While this should
be up to the user, I strongly suggest _not_ doing it. The reason is if/when the
user re-shares these photos all the tags and comments will be sent to the third
party thus raising privacy concerns.
Ideally the best option would be to create and follow a standard for placing
photo metadata in the photo's folder such that it can be integrated into other
applications such as photo editors, and even the electronic photo frame
displays.
Original comment by bbzbryce
on 14 Sep 2010 at 10:21
[deleted comment]
most photohosting sites do not save or display the images metadata. but beyond
that, not being able to have the comments and tags displayed in my photo editor
is a definite drawback of how it is now. Saving the metadata directly to the
image would be the only solution afaik.
Original comment by Supreme1...@gmail.com
on 19 Sep 2010 at 7:06
I'm not too familiar with the jpeg metadata format(s) but I believe that there
is just a basic "comment" field for text. This would be suitable for the
description of the photo but I believe it would be a misuse of the standard to
include the comments/tags in that field.
I think it would be a good idea to include the description in the jpeg's
metadata but that an external program (to import the extra metadata into your
photo viewer of choice) is the best way to manage the tag/comment data.
The json file in the album folder holds all this info and can be parsed by a
script to export the data. I'm pretty proud of my HTML viewer and so I'm not
too interested in writing the code to export the data to Picasa or iPhoto or
whatever.
Thanks for the suggestion. I think the photo description could (should?) be
included in the jpeg metadata, but beyond that an export script for your
specific photo viewer is needed. I can confidently say that it will be January
before I get around to working on any new features like this so don't hold your
breath.
Original comment by tommy.mu...@gmail.com
on 20 Sep 2010 at 7:05
Original issue reported on code.google.com by
Supreme1...@gmail.com
on 8 Sep 2010 at 8:09