Closed GoogleCodeExporter closed 9 years ago
comment are stored in "jpeg comment", not in "exif comment"
Original comment by manat...@gmail.com
on 26 Jan 2009 at 7:52
Sorry I got confused. I had a look at the different jpeg metadata definitions a
little while ago. I know it's fairly complicated with all norms out there, but
still,
I sent pictures to my parents and couldn't see the comments, either in windows
photo
something or in ACDSee (old version 3.0)...
Original comment by chartier...@gmail.com
on 26 Jan 2009 at 8:12
@chartier.francois: I had the same idea, but on second thought, this idea has an
issue: what would jBrout do if he found a picture where the jpeg comment and
the iptc
description were both non-empty and different?
Original comment by davito...@gmail.com
on 26 Jan 2009 at 8:44
@chartier.francois: anyhow, this issue is now flagged invalid, I don't know if
it can
be re-opened. Maybe you should create a new issue with the correct terms.
@manatlan; what do you think?
Original comment by davito...@gmail.com
on 26 Jan 2009 at 9:04
I thought about the issue too, and I guess overwriting other comments would be a
little... not the jbrout's respectful way.
Maybe an optional mode ? like automatic renaming and rotating ?
and while thinking again, maybe it was exif comment I wanted... I'll have to
look
back into it.
Original comment by chartier...@gmail.com
on 26 Jan 2009 at 2:17
You are not alone with this problem, so I guess it is worth investigating.
Currently, jBrout stores what he names (at least in French) a "comment" which he
stores in the general JPEG comment zone. There is also the IPTC
Caption/Description.
We'll forget about the Microsoft.Comment tag ;-)
It could be done in an "intelligent" way: if jBrout finds the IPTC
Caption/Description empty or if it is identical to the JPEG comment, he can
update it
too. If he finds something in both these fields and they are different, jBout
could
display their contents, ask which one should be kept, even offer to merge them.
Original comment by davito...@gmail.com
on 26 Jan 2009 at 3:25
Original issue reported on code.google.com by
chartier...@gmail.com
on 26 Jan 2009 at 7:36