exiftool_vendored 9.41.2 → 9.45.0

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/TagNames/XMP.html

@@ -423,7 +423,7 @@ hear.)</p>
 <td class=c title=' / = Avoided'>string/</td>
 <td>&nbsp;</td></tr>
 <tr class=b>
-<td>Datetime</td>
+<td>DateTime</td>
 <td class=c title=' / = Avoided'>date/</td>
 <td>&nbsp;</td></tr>
 <tr>
@@ -7921,7 +7921,7 @@ XMP module for convenience.  (see <a href="http://www.w3.org/TR/SVG11/">http://w
 
 <hr>
 (This document generated automatically by Image::ExifTool::BuildTagLookup)
-<br><i>Last revised Oct 30, 2013</i>
+<br><i>Last revised Nov 25, 2013</i>
 <p class=lf><a href='index.html'>&lt;-- ExifTool Tag Names</a></p>
 </body>
 </html>

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/TagNames/index.html

@@ -187,11 +187,19 @@ find that some ExifTool tag names are different than expected.  The usual
 reason for this is to make the tag names more consistent across different
 types of meta information.  To determine a tag name, either consult this
 documentation or run <code>exiftool -s</code> on a file containing the information in
-question.
+question.</p>
+
+<p>(This documentation is the result of years of research, testing and reverse
+engineering, and is the most complete metadata tag list available anywhere
+on the internet.  It is provided not only for ExifTool users, but more
+importantly as a public service to help augment the collective knowledge,
+and is often used as a primary source of information in the development of
+other metadata software.  Please help keep this documentation as accurate
+and complete as possible, and feed back any new discoveries to the source.)
 </p>
 <hr>
 (This document generated automatically by Image::ExifTool::BuildTagLookup)
-<br><i>Last revised Oct 28, 2013</i>
+<br><i>Last revised Dec 8, 2013</i>
 <p class=lf><a href='../index.html'>&lt;-- Back to ExifTool home page</a></p>
 </body>
 </html>

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/ancient_history.html

@@ -2560,7 +2560,7 @@
     <li>ch_s  (thanks Haibing Zhong) [renamed 'zh_cn' in 7.75]
     <li>cz    (thanks Petr Mich&aacute;lek) [renamed 'cs' in 7.68]
     <li>de    (thanks Jens Duttke)
-    <li>en_ca (for those of us who like to see "colour" to be spelled properly)
+    <li>en_ca (for those of us who like to see "colour" spelled properly)
     <li>en_gb (correct "colour" plus a few other quirks)
     <li>es    (thanks Santiago del Br&iacute;o Gonz&aacute;lez)
     <li>fr    (thanks Bernard Guillotin)

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/exiftool_pod.html

@@ -364,14 +364,14 @@ maker notes.</p>
 <p>3) Changes to PDF files are reversible because the original information is
 never actually deleted from the file.  So ExifTool alone may not be used to
 securely edit metadata in PDF files.</p>
-<p>4) Specifying <code>-GROUP:all=</code> deletes the entire group as a block unless a
-family 2 group is specified, in which case the tags are deleted
-individually.  (Since the family 2 categories do not represent physical
-metadata blocks.)  So only in this case may individual tags be excluded from
-the mass delete.  For example, <code>-time:all --Exif:Time:All</code> removes all
-deletable Time tags except those in the EXIF.  This difference also applies
-when deleting all by family 2 group (ie. <code>-2all:all=</code>) which deletes tags
-individually, as opposed to <code>-all:all=</code> which deletes entire blocks.</p>
+<p>4) Specifying <code>-GROUP:all=</code> deletes the entire group as a block only if a
+single family 0 or 1 group is specified.  Otherwise all deletable tags in
+the specified group(s) are removed individually, and in this case is it
+possible to exclude individual tags from a mass delete.  For example,
+<code>-time:all --Exif:Time:All</code> removes all deletable Time tags except those in
+the EXIF.  This difference also applies if family 2 is specified when
+deleting all groups. For example, <code>-2all:all=</code> deletes tags individually,
+while <code>-all:all=</code> deletes entire blocks.</p>
 <p>5) The &quot;APP&quot; group names (&quot;APP0&quot; through &quot;APP15&quot;) are used to delete JPEG
 application segments which are not associated with another deletable group. 
 For example, specifying <code>-APP14:All=</code> will NOT delete the APP14 &quot;Adobe&quot;
@@ -828,7 +828,7 @@ are ignored.  For example, this format file:</p>
     exiftool -p test.fmt a.jpg b.jpg</pre>
 <p>produces output like this:</p>
 <pre>
-    -- Generated by ExifTool 9.41 --
+    -- Generated by ExifTool 9.45 --
     File: a.jpg - 2003:10:31 15:44:19
     (f/5.6, 1/60s, ISO 100)
     File: b.jpg - 2006:05:23 11:57:38
@@ -860,9 +860,10 @@ and null from the printed value.</p>
 
 <dd>
 <p>Format output as a PHP Array.  The <strong>-g</strong>, <strong>-G</strong>, <strong>-D</strong>, <strong>-H</strong>, <strong>-l</strong>,
-<strong>-sep</strong> and <strong>-struct</strong> options combine with <strong>-php</strong> in the same way as with
-<strong>-json</strong>. As well, the <strong>-b</strong> option may be added to output binary data. 
-Here is a simple example showing how this could be used in a PHP script:</p>
+<strong>-sep</strong> and <strong>-struct</strong> options combine with <strong>-php</strong>, and duplicate tags are
+handled in the same way as with the <strong>-json</strong> option.  As well, the <strong>-b</strong>
+option may be added to output binary data.  Here is a simple example showing
+how this could be used in a PHP script:</p>
 <pre>
     &lt;?php
     eval('$array=' . `exiftool -php -q image.jpg`);
@@ -895,6 +896,9 @@ default is to join list items with &quot;, &quot;.  When writing, this option ca
 values assigned to list-type tags to be split into individual items at each
 substring matching <em>STR</em> (otherwise they are not split by default).  Space
 characters in <em>STR</em> match zero or more whitespace characters in the value.</p>
+<p>Note that an empty separator (&quot;&quot;) is allowed, and will join items with no
+separator when reading, or split the value into individual characters when
+writing.</p>
 </dd>
 <dt><strong><a name="sort" class="item"><strong>-sort</strong></a></strong></dt>
 
@@ -1068,8 +1072,8 @@ append feature, provides a method to write metadata from multiple source
 files to a single output file without the need for shell redirection.</p>
 <p>4) Adding the <strong>-v</strong> option to <strong>-W</strong> generates a list of the tags and output
 file names instead of giving a verbose dump of the entire file.  (Unless
-appending all output to one file for each source file by using <strong>-W+</strong> and an
-output file <em>FMT</em> that does not contain %t, $g or %s.)</p>
+appending all output to one file for each source file by using <strong>-W+</strong> with
+an output file <em>FMT</em> that does not contain %t, $g or %s.)</p>
 <p>5) Individual list items are stored in separate files when <strong>-W</strong> is combined
 with <strong>-b</strong>, but note that for separate files to be created %c must be used
 in <em>FMT</em> to give the files unique names.</p>
@@ -1312,12 +1316,12 @@ file was successfully written (ie. the file is moved instead of copied).</p>
 <p>Similar to <strong>-overwrite_original</strong> except that an extra step is added to
 allow the original file attributes to be preserved.  For example, on a Mac
 this causes the original file creation date, type, creator, label color,
-icon and hard links to the file to be preserved (but note that the Mac OS
-resource fork is always preserved unless specifically deleted with
-<code>-rsrc:all=</code>).  This is implemented by opening the original file in update
-mode and replacing its data with a copy of a temporary file before deleting
-the temporary.  The extra step results in slower performance, so the
-<strong>-overwrite_original</strong> option should be used instead unless necessary.</p>
+icon, Finder tags and hard links to the file to be preserved (but note that
+the Mac OS resource fork is always preserved unless specifically deleted
+with <code>-rsrc:all=</code>).  This is implemented by opening the original file in
+update mode and replacing its data with a copy of a temporary file before
+deleting the temporary.  The extra step results in slower performance, so
+the <strong>-overwrite_original</strong> option should be used instead unless necessary.</p>
 </dd>
 <dt><strong><a name="p" class="item"><strong>-P</strong> (<strong>-preserve</strong>)</a></strong></dt>
 

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/geotag.html

@@ -513,6 +513,8 @@ one or more geotagged images:</p>
 #
 # Usage:        exiftool -p gpx.fmt -d %Y-%m-%dT%H:%M:%SZ FILE [...] > out.gpx
 #
+# Requires:     ExifTool version 8.10 or later
+#
 # Revisions:    2010/02/05 - P. Harvey created
 #
 # Notes:     1) All input files must contain GPSLatitude and GPSLongitude.
@@ -589,6 +591,8 @@ file from a collection of geotagged images:</p>
 #
 # Usage:        exiftool -p kml.fmt FILE [...] > out.kml
 #
+# Requires:     ExifTool version 8.10 or later
+#
 # Revisions:    2010/02/05 - P. Harvey created
 #               2013/02/05 - PH Fixed camera icon to work with new Google Earth
 #

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/history.html

@@ -17,6 +17,56 @@ considered development releases, and are not uploaded to <a href="http://search.
 <!-- Use line width of 80 -->
 <!-- *********************************************************************** -->
 
+<a name='v9.45'><b>Dec. 21, 2013 - Version 9.45</b></a>
+<ul>
+<li>Added details about movie data offset in MOV verbose dump
+<li>Added a new Pentax WhiteBalance value
+<li>Added a new Sony/Minolta LensType (thanks Jos Roost)
+<li>Decode a new QuickTime tag
+<li>Prevent illegal tag names to be generated from user-defined XMP tags
+<li>Patched to allow reading some improperly formatted EXIF UserComment values
+<li>Fixed problem where reading some large M2TS files could take a loooong time
+</ul>
+
+<a name='v9.44'><b>Dec. 11, 2013 - Version 9.44</b></a>
+<ul>
+<li>Added a new Pentax WhiteBalance value
+<li>Added back the K-3 SRResult tag, but make it Unknown and with no print
+    conversion
+<li>Fixed problem copying the maker notes of some recent Pentax models
+</ul>
+
+<a name='v9.43'><b>Dec. 8, 2013 - Version 9.43</b></a>
+<ul>
+<li>Added a new Olympus CameraType
+<li>Added new Canon and Pentax LensType values
+<li>Added a new Panasonic ShootingMode
+<li>Added a new CanonModelID
+<li>Decode a number of new Sony Tags (thanks Jos Roost)
+<li>Decode a new Pentax tag
+<li>Fixed decoding of a few Pentax tags for newer models
+<li>Fixed decoding of CameraTemperature for Olympus Stylus 1
+<li>Fixed bug when writing QuickTime date/time tags with QuickTimeUTC option set
+</ul>
+
+<a name='v9.42'><b>Dec. 1, 2013 - Version 9.42</b></a>
+<ul>
+<li>Added a new Canon LensType (thanks Norbert Wasser)
+<li>Added a new Pentax LensType (thanks Louis Granboulan)
+<li>Added a new Sony LensType (thanks Fredrik Agert)
+<li>Added a new Nikon LensID (thanks LibRaw)
+<li>Added a new Olympus CameraType
+<li>Decode a number of new Sony tags (thanks Jos Roost)
+<li>Decode a number of new Panasonic tags (thanks Thomas Modes)
+<li>Decode a few new Pentax tags (thanks Klaus Homeister and others)
+<li>Improved Olympus SensorTemperature calibration (thanks Eric Sibert)
+<li>Patched decoding of EXIF:UserComment to tolerate invalid character code
+    written by Canon Zoombrowser EX 4.5
+<li>Patched to allow GPS information to be extracted from incorrectly formatted
+    EXIF written by Windows Phone OS 7.5 (observed in some HTC and Nokia phones)
+<li>Fixed runtime warnings which could occur when -j or -php combined with -f
+</ul>
+
 <a name='v9.41'><b>Nov. 16, 2013 - Version 9.41</b></a>
 <ul>
 <li>Added the ability to use multiple group qualifiers on tag names when writing
@@ -26,7 +76,7 @@ considered development releases, and are not uploaded to <a href="http://search.
 <li>Added a new Canon LensType (thanks David Monro)
 <li>Added a new Sony LensType2 (thanks Jos Roost)
 <li>Decode a bunch more Nikon, Canon, Sony and FujiFilm WhiteBalance tags
-    (thanks Iliah Borg)
+    (thanks LibRaw)
 <li>Extract information from the new Pentax APP7 segment
 </ul>
 

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/index.html

@@ -72,9 +72,9 @@ table.dl td     { padding: .4em .8em }
 </div>
 
 <blockquote><table class='dl lg'><tr><td><b>
-<a href="Image-ExifTool-9.41.tar.gz">
-Download        Version 9.41</a> (3.5 MB) -
-<a href="history.html">Nov. 16, 2013</a></b></td></tr></table></blockquote>
+<a href="Image-ExifTool-9.45.tar.gz">
+Download        Version 9.45</a> (3.6 MB) -
+<a href="history.html">Dec. 21, 2013</a></b></td></tr></table></blockquote>
 
 <p><b>ExifTool is a platform-independent <a href="ExifTool.html">Perl
 library</a> plus a <a href="exiftool_pod.html">command-line application</a> for
@@ -122,8 +122,8 @@ distribution above.)</i></p>
 
 <blockquote><table class='dl lg'><tr><td><b>
 <a name="alone">Windows Executable:</a>
-<a href="exiftool-9.41.zip">
-         exiftool-9.41.zip</a> (3.6 MB)</b></td></tr></table></blockquote>
+<a href="exiftool-9.45.zip">
+         exiftool-9.45.zip</a> (3.6 MB)</b></td></tr></table></blockquote>
 
 <p><b>The stand-alone Windows executable</b> does not require Perl. Just
 download and un-zip the archive then double-click on
@@ -134,8 +134,8 @@ of Windows (including Windows 7).</p>
 
 <blockquote><table class='dl lg'><tr><td><b>
 Mac OS X Package:
-<a href="ExifTool-9.41.dmg">
-         ExifTool-9.41.dmg</a> (2.3 MB)</b></td></tr></table></blockquote>
+<a href="ExifTool-9.45.dmg">
+         ExifTool-9.45.dmg</a> (2.3 MB)</b></td></tr></table></blockquote>
 
 <p><b>The OS X package</b> installs the ExifTool command-line application and
 libraries in /usr/bin. After installing, type "<code>exiftool</code>" in a
@@ -878,7 +878,7 @@ arguments like <code>"-DSTTAG&lt;SRCTAG"</code>) have the ability to execute
 Perl code from within command-line arguments.  This may be a security problem if
 ExifTool is executed from another application that blindly passes untrusted file
 names on the command line (since they may be interpreted as ExifTool options if
-they contain a leading dash).  To be secure, the calling application must ensure
+they have a leading dash).  To be secure, the calling application must ensure
 that input file names do not start with a dash (U+002D) or a Unicode minus sign
 (U+2212).  The easiest way to accomplish this is to prefix input file names with
 a known directory name, ie) <code>"./FILENAME"</code>.</p>
@@ -1034,9 +1034,10 @@ binary data.  The simple script above does not handle this case.</p>
 
 <p><b><a name="user_docs">User-contributed Documentation</a></b></p>
 <ul>
+<li><a href="http://www.youtube.com/results?search_query=avpreserve+exiftool">ExifTool Tutorial</a> (video in 4 parts by <a href="http://www.avpreserve.com">AVPreserve</a>)</li>
+<li><a href="http://www.youtube.com/watch?v=K9PAD7GqUag">Using the ExifTool on Linux to read/write Exif Tags to your photo collection</a> (video by <a href="http://www.linuxbyexample.org">Linux By Example</a>)</li>
+<li><a href="http://www.youtube.com/watch?v=WchknYwbFJY">Working with jpg Metadata Comments - Exiftool - BASH - Linux Command Line</a> (video by <a href="http://www.linuxbyexample.org">Linux By Example</a>)</li>
 <li><a href="http://sourceforge.net/projects/exiftool1line/files/">Useful one-line ExifTool commands</a> (.txt file)</li>
-<li><a href="http://www.youtube.com/watch?v=K9PAD7GqUag">Using the ExifTool on Linux to read/write Exif Tags to your photo collection</a> (video)</li>
-<li><a href="http://www.youtube.com/watch?v=WchknYwbFJY">Working with jpg Metadata Comments - Exiftool - BASH - Linux Command Line</a> (video)</li>
 </ul>
 
 <h3><a name="related">Related Utilities</a></h3>
@@ -1113,6 +1114,7 @@ three droplets to extract information [exiftool must be installed] (thanks to Ro
 <li><a href="http://www.resourcespace.org/">ResourceSpace</a>: Open source digital asset management system</li>
 <li><a href="http://owl.phy.queensu.ca/~phil/exiftool/fix_corrupted_nef.html">fix_corrupted_nef</a>: Utility to fix Nikon D4/D600/D800/D800E NEF images corrupted by Nikon Transfer 1</li>
 <li><a href="http://panorama.dyndns.org/index.php?lang=en&subject=pyExifToolGUI&texttag=pyExifToolGUI">pyExifToolGUI</a>: Python-based graphical frontend for ExifTool</li>
+<li><a href="https://github.com/avpreserve/mdqc">MDQC</a>: <a href="http://www.avpreserve.com/avpsresources/tools/">AVPreserve tool</a> for metadata quality control across large numbers of digital assets</li>
 </ul>
 
 <p><b><a name="related_online">Online</a></b></p>
@@ -1125,6 +1127,7 @@ three droplets to extract information [exiftool must be installed] (thanks to Ro
 <ul>
 <li><a href="http://regex.info/blog/lightroom-goodies/gps">Jeffrey's Geoencoding Plugin for Lightroom</a>: Geoencode your photos from within Lightroom</li>
 <li><a href="http://regex.info/blog/lightroom-goodies/metadata-wrangler/">Metadata Wrangler</a>: Strip selected metadata components from images as they are exported</li>
+<li><a href="http://www.robcole.com/Rob/ProductsAndServices/ExifMetaLrPlugin/">ExifMeta</a>: Make all exif metadata available in Lightroom for lib filtering and smart collections</li>
 <li><a href="http://chaoliu12.wordpress.com/fullmetaexport-lightroom-plugin/">FullMetaExport</a>: Export JPEG images from Lightroom with full metadata</li>
 <li><a href="http://www.essl.de/wp/2012/05/24/lenstagger-now-with-analog-camera-film-support/">LensTagger</a>:  Add EXIF information like aperture and focal length for manual lenses</li>
 <li><a href="http://tim.jagenberg.info/projects/deaspect/">DeAspect:</a> Remove aspect ratio information from DNG, CR2 and ORF images to restore full image</li>
@@ -1132,6 +1135,7 @@ three droplets to extract information [exiftool must be installed] (thanks to Ro
 
 <p><b><a name="related_prog">Programming</a></b></p>
 <ul>
+<li><a href="http://owl.phy.queensu.ca/~phil/cpp_exiftool/">C++ ExifTool</a>: Performance-oriented C++ interface for the exiftool application (by Phil Harvey)</li>
 <li><a href="http://owl.phy.queensu.ca/~phil/exiftool/get_tags.sit">Download</a> sample AppleScript to extract tags into AppleScript record (thanks to Rob Lewis)</li>
 <li><a href="http://owl.phy.queensu.ca/~phil/exiftool/ExifToolWrapper.zip">Download</a> example of a simple Visual C++ wrapper for exiftool (thanks Mark Borg and &#40643;&#29790;&#26124;)</li>
 <li><a href="http://owl.phy.queensu.ca/~phil/exiftool/ExifToolWrapper_cs.zip">Download</a> C# version of simple exiftool wrapper (thanks Willem Semmelink)</li>
@@ -1150,11 +1154,6 @@ three droplets to extract information [exiftool must be installed] (thanks to Ro
 <li><a href="http://u88.n24.queensu.ca/~bogdan/articles/delphi01.html">How to call ExifTool from Delphi</a>, by Bogdan Hrastnik</li>
 </ul>
 
-<p>Also notable, but not directly based on ExifTool:</p>
-
-<ul><li><a href="http://www.photome.de/">PhotoME</a>: Windows utility to read/write meta information</li>
-</ul>
-
 <h3><a name="references">References</a></h3>
 
 <p>The following sources were very useful in helping to decode various types of

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/install.html

@@ -161,13 +161,19 @@ password.)</span></li>
 </ol>
 <p>You can now run exiftool by typing "<code>exiftool</code>" in a Terminal window.</p>
 
-<p class=lt>(Note: Both OS X installation techniques outlined above place
+<p class=lt><b>Notes:</b></p><ul class=lt><li>Both OS X installation techniques outlined above place
 exiftool and its lib directory in /usr/bin, while the standard Unix
 "<code>make install</code>" described below puts "<code>exiftool</code>" in
 /usr/bin and the individual libraries in /Library/Perl/#.#.#, where "#.#.#" is
 your Perl version. If both sets of libraries exist, /usr/bin/lib takes
 precedence for exiftool, but /Library/Perl/#.#.# is the default for any other
-Perl scripts.)</p>
+Perl scripts.</li>
+<li>In OS X 10.8 or later, you may see this message when you try to open the install package:
+<blockquote class=red>"ExifTool-#.##.pkg" can't be opened because it is from an
+unidentified developer.</blockquote> The solution is to set "Allow applications downloaded
+from" to "Anywhere" in the General "Security &amp; Privacy" System Preferences.
+(<a href="http://news.softpedia.com/news/Fix-OS-X-Error-Application-Can-t-Be-Opened-Because-it-Is-from-an-Unidentified-Developer-407375.shtml">Read
+here</a> for a full description.)</li></ul>
 
 <h3>Uninstalling</h3>
 <ol type='i'>

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/html/standards.html

@@ -115,6 +115,10 @@ definition is unclear in the case of zoom lenses where the maximum aperture
 varies across the zoom range.  Some manufacturers (Canon, Nikon, Sony) store the
 maximum aperture at the specific focal length, but others (Olympus, Pentax)
 store the absolute maximum aperture of the lens.</li>
+<li>EXIF is not extensible, and is missing definitions for storing some
+information that could be very useful to camera owners (ie. camera orientation,
+sensor temperature, face detection, auto-focus points, image stabilization,
+flash exposure compensation, etc).</li>
 </ol>
 
 <p><b>Simple solutions:</b></p>
@@ -143,6 +147,8 @@ this to allow UTF-16 surrogate pairs may be a good idea.</li>
 <li>Allow ApertureValue and MaxApertureValue to be stored as signed SRATIONAL.</li>
 <li>Define whether MaxApertureValue is taken at the current focal length of
 a zoom lens, or over the entire zoom range.</li>
+<li>Expand the standard to include additional useful information available from
+modern digital cameras.</li>
 </ol>
 
 <a name="PhotoInfo"></a>
@@ -271,7 +277,7 @@ inside a JPEG segment.</p>
 </ol>
 <hr>
 <i>Created Sep 17, 2009</i><br>
-<i>Last revised Jan 8, 2013</i>
+<i>Last revised Dec 7, 2013</i>
 <p class='lf'><a href="index.html">&lt;-- Back to ExifTool home page</a></p>
 </body>
 </html>

data/bin/{Image-ExifTool-9.41 → Image-ExifTool-9.45}/lib/Image/ExifTool.pm

@@ -27,7 +27,7 @@ use vars qw($VERSION $RELEASE @ISA @EXPORT_OK %EXPORT_TAGS $AUTOLOAD @fileTypes
             %mimeType $swapBytes $swapWords $currentByteOrder %unpackStd
             %jpegMarker %specialTags);
 
-$VERSION = '9.41';
+$VERSION = '9.45';
 $RELEASE = '';
 @ISA = qw(Exporter);
 %EXPORT_TAGS = (
@@ -1284,6 +1284,7 @@ sub DummyWriteProc { return 1; }
         Name => 'JFIFVersion',
         Format => 'int8u[2]',
         PrintConv => 'sprintf("%d.%.2d", split(" ",$val))',
+        Mandatory => 1,
     },
     2 => {
         Name => 'ResolutionUnit',
@@ -1295,6 +1296,7 @@ sub DummyWriteProc { return 1; }
             2 => 'cm',
         },
         Priority => -1,
+        Mandatory => 1,
     },
     3 => {
         Name => 'XResolution',
@@ -1302,6 +1304,7 @@ sub DummyWriteProc { return 1; }
         Writable => 1,
         Priority => -1,
         RawConv => '$$self{JFIFXResolution} = $val',
+        Mandatory => 1,
     },
     5 => {
         Name => 'YResolution',
@@ -1309,6 +1312,7 @@ sub DummyWriteProc { return 1; }
         Writable => 1,
         Priority => -1,
         RawConv => '$$self{JFIFYResolution} = $val',
+        Mandatory => 1,
     },
 );
 %Image::ExifTool::JFIF::Extension = (
@@ -3585,12 +3589,7 @@ sub SetupTagTable($)
         foreach $tagInfo (@infoArray) {
             $$tagInfo{Table} = $tagTablePtr;
             $$tagInfo{TagID} = $tagID;
-            my $tag = $$tagInfo{Name};
-            unless (defined $tag) {
-                # generate name equal to tag ID if 'Name' doesn't exist
-                $tag = $tagID;
-                $$tagInfo{Name} = ucfirst($tag); # make first char uppercase
-            }
+            $$tagInfo{Name} or $$tagInfo{Name} = MakeTagName($tagID);
             $$tagInfo{Flags} and ExpandFlags($tagInfo);
         }
         next unless @infoArray > 1;
@@ -4093,6 +4092,19 @@ sub ValidateImage($$$)
     return $imagePt;
 }
 
+#------------------------------------------------------------------------------
+# Generate a valid tag name based on the tag ID or name
+# Inputs: 0) tag ID or name
+# Returns: valid tag name
+sub MakeTagName($)
+{
+    my $name = shift;
+    $name =~ tr/-_a-zA-Z0-9//dc;    # remove illegal characters
+    $name = ucfirst $name;          # capitalize first letter
+    $name = "Tag$name" if length($name) < 2; # must at least 2 characters long
+    return $name;
+}
+
 #------------------------------------------------------------------------------
 # Make description from a tag name
 # Inputs: 0) tag name 1) optional tagID to add at end of description
@@ -5967,7 +5979,8 @@ sub ProcessDirectory($$$;$)
         my $addr = $$dirInfo{DirStart} + $$dirInfo{DataPos} + ($$dirInfo{Base}||0);
         if ($$self{PROCESSED}{$addr}) {
             $self->Warn("$dirName pointer references previous $$self{PROCESSED}{$addr} directory");
-            return 0;
+            # patch for bug in Windows phone 7.5 O/S that writes incorrect InteropIFD pointer
+            return 0 unless $dirName eq 'GPS' and $$self{PROCESSED}{$addr} eq 'InteropIFD';
         }
         $$self{PROCESSED}{$addr} = $dirName;
     }
@@ -6145,7 +6158,7 @@ sub AddTagToTable($$;$$)
         $name = $tagID;
         $name =~ tr/-_a-zA-Z0-9//dc;    # remove illegal characters
         $name = ucfirst $name;          # start with uppercase
-        # make sure name is a reasonable length
+        # add prefix if specified
         my $prefix = $$tagTablePtr{TAG_PREFIX};
         if ($prefix and not $noPrefix) {
             # make description to prevent tagID from getting mangled by MakeDescription()
@@ -6153,8 +6166,8 @@ sub AddTagToTable($$;$$)
             $name = "${prefix}_$name";
         }
     }
-    # tag names must be at least 2 characters long and begin with a letter
-    $name = "Tag$name" if length($name) <= 1 or $name !~ /^[A-Z]/i;
+    # tag names must be at least 2 characters long and prefer them to start with a letter
+    $name = "Tag$name" if length($name) < 2 or $name !~ /^[A-Z]/i;
     $$tagInfo{Name} = $name;
     # add tag to table, but never overwrite existing entries (could potentially happen
     # if someone thinks there isn't any tagInfo because a condition wasn't satisfied)
@@ -6754,7 +6767,7 @@ sub ProcessBinaryData($$$)
         }
         # hook to allow format, etc to be set dynamically
         if (defined $$tagInfo{Hook}) {
-            #### eval Hook ($format, $varSize)
+            #### eval Hook ($format, $varSize, $size)
             eval $$tagInfo{Hook};
             # save variable size data if required for writing (in case changed by Hook)
             if ($$dirInfo{VarFormatData}) {