Summary: | Nikon D70 comments in jpegs are all shown as "charset="Ascii" " | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Dennis Gnad <bluedrago> |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | caulier.gilles, cniehaus |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.9.0 | |
Sentry Crash Report: |
Description
Dennis Gnad
2006-04-24 23:07:04 UTC
Please send me a jpeg, marcel.wiesweg@gmx.de Marcel, try with these items : http://digikam3rdparty.free.fr/TEST_IMAGES/JPEG/Horizontal/NIKON-D70-01.JPG http://digikam3rdparty.free.fr/TEST_IMAGES/JPEG/Horizontal/NIKON-D70-02.JPG http://digikam3rdparty.free.fr/TEST_IMAGES/JPEG/Horizontal/NIKON-D70-03.JPG http://digikam3rdparty.free.fr/TEST_IMAGES/JPEG/Horizontal/NIKON-D100.JPG http://digikam3rdparty.free.fr/TEST_IMAGES/JPEG/Horizontal/NIKON-D200-02.JPG Gilles 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. 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). ---- 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. |