Bug 126199 - Nikon D70 comments in jpegs are all shown as "charset="Ascii" "
Summary: Nikon D70 comments in jpegs are all shown as "charset="Ascii" "
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Unclassified
Component: Metadata-Engine (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-24 23:07 UTC by Dennis Gnad
Modified: 2017-07-12 14:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 0.9.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Gnad 2006-04-24 23:07:04 UTC
Version:           0.9 svn 2006-04-24 (using KDE KDE 3.5.2)

With the Nikon D70 you have the option to add a comment to the files, if they are in the .NEF they aren't shown at all in digikam, which doesnt really annoy so much. But if you put one in a jpeg, the jpeg shows following as the comment in digikam:
charset="Ascii" (there are also a lot of spaces after that)
which is probably something that comes before the real comment in the file, and describes its.
Even exiftool seems not to be able to read the comment out of those jpeg.. somewhat strange ...
I wish I could attach such a jpeg, but it is over the allowed filesize I can upload. So if you want it, give me your email, or tell me some location where I could upload it.
Thanks,
 Dennis
Comment 1 Marcel Wiesweg 2006-05-31 19:55:03 UTC
Please send me a jpeg, marcel.wiesweg@gmx.de
Comment 3 Marcel Wiesweg 2006-06-03 19:02:02 UTC
The comments in these JPEGs are 36 spaces. The charset is specified as ASCII, and here this string (which comes from libexiv2) is correctly parsed and not shown.

If there actually is a comment, then libexiv2 does not find it.
If the "charset=ascii" is shown on your computer, please check that you are using the latest svn version, at least later than May 21.
Comment 4 Dennis Gnad 2006-06-05 23:54:04 UTC
Exiv2 from now on doesn't show the charset=ascii anymore.
Though there is a new bug for .NEFs now, it shows also some cryptic stuff. I will fill a bug report at exiv2's bug tracking (if I will finally receive that confirmation email to login there).
Comment 5 F.J. Cruz 2006-06-06 08:54:23 UTC
---- Dennis Gnad <bluedrago@web.de> escribió: 
[bugs.kde.org quoted mail]
The "cryptic stuff" is the raw content of some field from makernotes, but I've not detected which field is.

Paco.