Total Commander

tbeu · Posted: Mon Feb 13, 2012 2:28 pm Post subject:

I remembered some old conversation with developer of Exiv2 when I asked for IPTC encoding. He told me that the character set is defined by the Iptc.Envelope.CharacterSet tag which however is often missing. Then all that can be done is to guess encoding like recommended by MWG in http://www.metadataworkinggroup.com/pdf/mwg_guidance.pdf, page 31.

Thus the default jpg-comment.ini was wrong having both ft_string and ft_stringw data types that are handled differently by the plugin. Currently ft_string uses default code page for reading/writing whereas ft_stringw assums UTF-8 (even if Iptc.Envelope.CharacterSet does not state UTF-8). I am going to fix both issues.

Please check FAQ 10 of exiftool http://www.sno.phy.queensu.ca/~phil/exiftool/faq.html#Q10 how exiftool handles IPTC encodings. Thus you can see how to use charset iptc option to define the used IPTC character set.

I believe that UTF-8 encoding for IPTC is not supported by XnView. Only default code page is used.
_________________
My plugins: Autodesk 3ds Max Preview, Blat Mailer, ImageMetaData (JPG Comment/EXIF/IPTC/XMP) , MATLAB MAT-file Viewer, SolidWorks Preview and more

Peter · Posted: Mon Feb 13, 2012 4:07 pm Post subject:

Thanks Thomas for the clarification. As said above I am content with the fixes you promised.

Greetings

Peter
_________________
TC 8.01 / #266191
Windows XP 32 Professional & Win 7 x64

Hakker · Junior Member Joined: 01 Mar 2009 Posts: 18

I used an older plugin first to get resolution data of images like width, height and color depth however since that one isn't updated anymore ImgSize and I transfered to x64 I found your plugin. However for some reason it finds the resolution only partly. Sometimes it can get them other times it doesn't get it.

Is it possible to add an option that it can get that data more reliable? Not every image comes from an camera for instance so that might be a part of the problem.

tbeu · Posted: Tue Feb 21, 2012 1:45 am Post subject:

Peter · Posted: Tue Feb 21, 2012 3:54 am Post subject:

The plugin offers different entries for "resolution". Did you try all of them?

Peter
_________________
TC 8.01 / #266191
Windows XP 32 Professional & Win 7 x64

Hakker · Junior Member Joined: 01 Mar 2009 Posts: 18

mariasaleem · New Member Joined: 19 Apr 2012 Posts: 1

Nice work peter, Very Happy

_________________
content writing jobs

tbeu · Posted: Thu Jun 07, 2012 3:50 pm Post subject: ImageMetaData plugin 2.3.2.0

Plugin Version 2.3.2.0 is released:
• replaced Exiv2 library 0.22 (r2643) by 0.23 (r2749)
• replaced Expat 2.0.1 by Expat 2.1.0
• replaced zlib library 1.2.5 by 1.2.7
• fixed trailing wide string conversion for ft_numeric_floating fields
• fixed: trailing wide string for ft_numeric_floating fields displays max. 5 decimal places
• fixed code page issues for reading/writing metadata
• fixed run-time exception when writing an empty/invalid time/date format
• renamed/shortened and resorted all strings in default jpg-comment.ini (breaking compatibility)
• set ShowErrors in default jpg-comment.ini to off
• added CodePage option to section [Settings] of jpg-comment.ini,i.e.

tbeu · Posted: Tue Jun 12, 2012 2:20 pm Post subject: ImageMetaData plugin 2.3.3.0

Plugin Version 2.3.3.0 is released:
• fixed access violations for invalid string conversions
• removed CodePage option from section [Settings] of jpg-comment.ini
• added JPEG_CodePage, EXIF_CodePage, IPTC_CodePage and XMP_CodePage options to section [Settings] of jpg-comment.ini, i.e.

tbeu · Posted: Sun Oct 07, 2012 1:34 pm Post subject: ImageMetaData plugin 2.3.4.1

Plugin Version 2.3.4.1 is released:
• replaced Exiv2 library 0.23 (r2749) by 0.23 (r2895)
• fixed Exif date stamp: forward slash (besides colon) is also allowed as separator
• added experimental support of metadata dump as full text fields, to enable add the new dump fields at the end of section [Metadata] of jpg-comment.ini,i.e.