RubyGems - exiftool_vendored - Versions diffs - 9.78.0 → 9.99.0 - Mend

exiftool_vendored 9.78.0 → 9.99.0

Potentially problematic release.

This version of exiftool_vendored might be problematic. Click here for more details.

Files changed (1409) hide show

data/bin/Image-ExifTool-9.99/html/install.html ADDED Viewed

@@ -0,0 +1,251 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+        "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
+<html>
+<head>
+<title>Installing ExifTool</title>
+<link rel=stylesheet type='text/css' href='style.css' title='Style'>
+<style type="text/css">
+<!--
+li      { margin-top: .5em }
+.attn   { padding: 0.5em; border: 1px solid gray; background: #fee }
+-->
+</style></head>
+<body>
+<h1 class='up'>Installing ExifTool</h1>
+<blockquote class=attn><b class=red>Note:</b> ExifTool <b>does <u>not</u> need
+to be installed</b> to run.  Just download and extract either the full Perl
+distribution on Mac/Linux, or the Windows EXE version on Windows, and run it
+directly.  <i class=lt>[But note that if you move the Perl "exiftool"
+application, you must also move its "lib" directory to the same location. This
+doesn't apply to the Windows version which unpacks the libraries into a
+temporary directory.]</i><br><br>However, the benefits of installation are:
+<ul><li>Makes ExifTool available to all users.</li>
+<li>Saves typing on the command line (by placing "exiftool" in your PATH).</li>
+<li>Installs the ExifTool documentation and API libraries (full Perl version only).</li>
+</ul></blockquote>
+<p>See the appropriate section below with instructions for installing or
+uninstalling ExifTool on your specific platform:</p>
+<ul>
+<li><a href="#Windows">Windows</a></li>
+<li><a href="#OSX">Macintosh OS X</a></li>
+<li><a href="#Unix">Unix Platforms</a></li>
+</ul>
+<p>Also see <a href="index.html#running">these instructions</a> for help running
+ExifTool.</p>
+<hr>
+<h2><a name="Windows">Windows</a></h2>
+<p>In Windows, there is a choice of two different versions of ExifTool to
+install.  The Perl distribution requires Perl to be installed on your system.
+(A good, free Perl interpreter can be downloaded from
+<a href="http://www.activestate.com/activeperl/">activeperl.com</a>.)</p>
+<p>If you don't already have Perl, it is easier to install the stand-alone ExifTool
+executable, but note that the stand-alone version doesn't include the HTML
+documentation or some other files of the full distribution.</p>
+<h3>Stand-Alone Executable</h3>
+<ol>
+<li><b>Download</b> the <b>Windows Executable</b> from the <a href="index.html">ExifTool home page</a>.
+<br><span class=lt>(The file you download will have a name like "<code>exiftool-#.##.zip</code>".)</span></li>
+<li><b>Extract "<code>exiftool(-k).exe</code>"</b> from the
+"<code>.zip</code>" file, and place it <b>on your Desktop</b>.
+<br><span class=lt>(Double-click on "<code>exiftool-#.##.zip</code>" to open
+the archive, then drag "<code>exiftool(-k).exe</code>" to your Desktop.)</span></li>
+</ol>
+<p>You can now double-click on "<code>exiftool(-k).exe</code>" to read the
+application documentation, or drag-and-drop files and folders to run exiftool on
+selected files. To install exiftool for <b>use from the command line</b>,
+continue with the following steps:</p>
+<ol start=3>
+<li><b>Rename</b> "<code>exiftool(-k).exe</code>" to <b>"<code>exiftool.exe</code>"</b>.
+<br><span class=lt>(or "<code>exiftool(-k)</code>" to "<code>exiftool</code>" if file name
+extensions are hidden on your system)</span></li>
+<li><b>Move "<code>exiftool.exe</code>"</b> to the "<code>C:\WINDOWS</code>" directory
+(or any other directory in your PATH).</li>
+</ol>
+<p>You can now run exiftool by typing "<code>exiftool</code>" at the command
+prompt.  (To get to the command prompt, select "Run..." from the Windows "Start"
+menu, then type "<code>cmd</code>" and press Return.)</p>
+<p><b>Notes:</b>
+<ol type='a'>
+<li>In Windows 7, running exiftool requires administrator privileges.  If
+necessary, this may be enabled by right clicking on exiftool, then selecting
+<b>"Run this program as administrator"</b> from the Compatibility settings.</li>
+<li>Occasionally users have reported that exiftool gives errors when running
+this version for this first time.  It is possible this may happen if a file gets
+corrupted during the download/installation process.  In this case, follow the
+Uninstalling instructions below then re-install exiftool. Be sure that you have
+sufficient disk space in your TEMP directory for exiftool to unpack about 12 MB
+of temporary files -- these are the Perl libraries used by the exiftool
+application which are unpacked the first time exiftool is run.</li>
+</ol></p>
+<p><b>Uninstalling:</b></p>
+<ol type='i'>
+<li>Drag "<code>exiftool(-k).exe</code>" (or "<code>C:\WINDOWS\exiftool.exe</code>")
+into the Recycle bin.</li>
+<li>Drag the directory "<code>par-USER</code>" from your temporary directory to
+the Recycle bin.  Here "<code>USER</code>" is your Windows user name and the
+location of the temporary directory depends on the value of the TEMP environment
+variable (typically "<code>C:\Documents and Settings\USER\Local Settings\Temp</code>"
+for Windows XP, or "<code>C:\Users\USER\AppData\Local\Temp</code>" for Windows 7).</li>
+</ol>
+<h3>Full Perl Distribution</h3>
+<p>You must have Perl installed to use this version.  (A free version of Perl
+can be downloaded from
+<a href="http://www.activestate.com/activeperl/">activeperl.com</a>.)</p>
+<ol>
+<li><b>Download</b> the <b>Image-ExifTool distribution</b> from the <a href="index.html">ExifTool home page</a>
+<br><span class=lt>(The file you download will have a name like "<code>Image-ExifTool-#.##.tar.gz</code>".)</span></li>
+<li><b>Extract the ExifTool files</b> from the archive.
+<br><span class=lt>(The archive is a gzipped tar file, and can be opened with
+various Windows utilities, including WinZip.)</span></li>
+<li><b>Rename</b> "<code>exiftool</code>" to <b>"<code>exiftool.pl</code>"</b>
+in the exiftool distribution.</li>
+<li><b>Move "<code>exiftool.pl</code>"</b> and the <b>"<code>lib</code>"</b>
+directory from the exiftool distribution to "<code>C:\WINDOWS</code>"
+(or any other directory in your PATH).</li>
+</ol>
+<p>Now, if you have made the proper Windows associations for the
+"<code>.pl</code>" extension (an option in the ActivePerl installation), you
+can run exiftool by typing "<code>exiftool.pl</code>" at the
+"<code>cmd.exe</code>" prompt.  Otherwise you should type
+"<code>perl c:\windows\exiftool.pl</code>".</p>
+<p><b>Uninstalling:</b></p>
+<ol type='i'>
+<li>Drag "<code>C:\WINDOWS\exiftool.pl</code>" and
+"<code>C:\WINDOWS\lib</code>" into the Recycle bin.  You should first confirm
+that "<code>C:\WINDOWS\lib</code>" contains only the "<code>File</code>"
+and "<code>Image</code>" sub-directories.  Do not delete it if it
+contains anything else.</li>
+</ol>
+<hr>
+<h2><a name="OSX">Macintosh OS X</a></h2>
+<p>If you have installed the BSDSDK package from the Xcode Developer Tools
+(<i>ie. if you have the</i> "<code>make</code>" <i>utility</i>), you should
+follow the install procedure for <a href="#Unix">Unix platforms</a> in the next
+section instead of the steps below. The Unix install has the advantage of making
+the ExifTool library available for your Perl scripts, as well as installing the
+man pages and POD documentation.</p>
+<p>Otherwise, you have a choice of two packages to install: The OS X package, or
+the full Perl distribution.  Both of the procedures below install the ExifTool
+files in the same location.  Installing from the OS X package is easier, but the
+full distribution includes HTML documentation and some other files not included
+in the OS X package.  Both versions run natively on PPC and Intel Macs.</p>
+<h3>OS X Package</h3>
+<ol>
+<li><b>Download</b> the <b>ExifTool OS X Package</b> from the <a href="index.html">ExifTool home page</a>.
+<br><span class=lt>(The file you download will have a name like "<code>ExifTool-#.##.dmg</code>".)</span></li>
+<li><b>Install</b> as a normal <b>OS X package</b>.
+<br><span class=lt>(Open the disk image, double-click on the install package, and follow the instructions.)
+</span></li>
+</ol>
+<p>You can now run exiftool by typing "<code>exiftool</code>" in a Terminal window.</p>
+<h3>Full Perl Distribution</h3>
+<ol>
+<li><b>Download</b> the <b>Image-ExifTool distribution</b> from the <a href="index.html">ExifTool home page</a>
+to your Desktop.
+<br><span class=lt>(The file you download will have a name like "<code>Image-ExifTool-#.##.tar.gz</code>".)</span></li>
+<li><b>Launch</b> the <b>Terminal</b> application from the Utilities folder in your Applications folder.</li>
+<li>In the Terminal window, <b>type the following</b>:
+<pre class='code'>    cd ~/Desktop
+    tar -xzf Image-ExifTool-#.##.tar.gz
+    cd Image-ExifTool-#.##
+    sudo cp -r exiftool lib /usr/local/bin
+</pre>
+where "<code>#.##</code>" is the version number of the ExifTool you downloaded.
+<br><span class=lt>(Note: The last step above will require you to enter your
+password.)</span></li>
+</ol>
+<p>You can now run exiftool by typing "<code>exiftool</code>" in a Terminal window.</p>
+<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/local/bin, while the standard Unix
+"<code>make install</code>" described below puts "<code>exiftool</code>" in
+/usr/local/bin and the individual libraries in /Library/Perl/#.#.#, where "#.#.#" is
+your Perl version. If both sets of libraries exist, /usr/local/bin/lib takes
+precedence for exiftool, but /Library/Perl/#.#.# is the default for any other
+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'>
+<li>Launch the "Terminal" application from the Applications Utilities folder.</li>
+<li>Type "<code>open /usr/local/bin</code>" (without the quotes) in the Terminal
+window, then press RETURN. (This opens a folder that you normally can't access
+from OS X.)</li>
+<li>Drag "<code>exiftool</code>" and "<code>lib</code>" into the trash from the
+"<code>bin</code>" folder you opened. You should first confirm that
+"<code>lib</code>" contains only two sub-folders: "<code>File</code>" and
+"<code>Image</code>". If it contains anything else, don't trash it because you
+have the wrong "<code>lib</code>" folder.</li>
+</ol>
+<hr>
+<h2><a name="Unix">Unix Platforms</a></h2>
+<ol>
+<li><b>Download</b> the <b>Image-ExifTool distribution</b> from the <a href="index.html">ExifTool home page</a>
+<br><span class=lt>(The file you download will have a name like "<code>Image-ExifTool-#.##.tar.gz</code>".)</span></li>
+<li><b>Unpack the distribution</b> and <b>make it your current directory</b> by typing:
+<pre class='code'>    cd <i>&lt;your download directory&gt;</i>
+    gzip -dc Image-ExifTool-#.##.tar.gz | tar -xf -
+    cd Image-ExifTool-#.##
+</pre>
+where "<code>#.##</code>" is the version number of the ExifTool you downloaded.
+<br><span class=lt>(At this point you may run exiftool by typing
+"<code>exiftool <i>&lt;image file name&gt;</i></code>".)</span></li>
+<li><b>Test and install ExifTool</b> by typing:
+<pre class='code'>
+    perl Makefile.PL
+    make test
+    sudo make install
+</pre>
+<span class=lt>(Note: The "<code>make test</code>" step is not required, but
+useful because it runs a full suite of tests to verify that ExifTool is working
+properly on your system.  The "<code>sudo make install</code>" command requires
+that you have su access, and will prompt for your password.  This will make
+ExifTool and its documentation accessible to all users on your system. If you
+don't have su access, you can run ExifTool in your own account by moving
+"<code>exiftool</code>" and its "<code>lib</code>" directory to any convienient
+location, preferably somewhere in your PATH.)</span></li>
+</ol>
+<p>You can now run exiftool by typing "<code>exiftool</code>".  Also, you can
+consult the ExifTool documentation with commands like:</p>
+<blockquote><pre class='code'>perldoc exiftool
+perldoc Image::ExifTool
+perldoc Image::ExifTool::TagNames
+</pre></blockquote>
+<p>or</p>
+<blockquote><pre class='code'>man exiftool
+man Image::ExifTool
+man Image::ExifTool::TagNames
+</pre></blockquote>
+<h3>Uninstalling</h3>
+<ol type='i'>
+<li>Type "<code>sudo make uninstall</code>" from the distribution directory.
+<br><span class=lt>(Note: Unfortunately, newer systems may give an <i>"Uninstall
+is unsafe and deprecated"</i> message even though uninstalling ExifTool is safe
+because it has no dependencies.  If this happens, the necessary commands to
+remove the installed files will be listed, and these commands must be run
+manually.)</span></li>
+</ol>
+<hr>
+<p class='lf'><a href="index.html">&lt;-- Back to ExifTool home page</a></p>
+</body>
+</html>

data/bin/{Image-ExifTool-9.78 → Image-ExifTool-9.99}/html/metafiles.html RENAMED Viewed

File without changes

data/bin/{Image-ExifTool-9.78 → Image-ExifTool-9.99}/html/overview.png RENAMED Viewed

File without changes

data/bin/Image-ExifTool-9.99/html/standards.html ADDED Viewed

@@ -0,0 +1,286 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+        "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
+<html>
+<head>
+  <title>Problems with current Metadata Standards</title>
+<link rel=stylesheet type='text/css' href='style.css' title='Style'>
+<style type="text/css">
+<!--
+a.ref   { text-decoration: none; font-size: x-small;
+          font-weight: normal; vertical-align: super; }
+-->
+</style>
+</head>
+<body>
+<div class='index'>
+<a href="#TIFF">TIFF 6.0</a>
+<br><a href="#DNG">DNG 1.3</a>
+<br><a href="#EXIF">EXIF 2.3</a>
+<br><a href="#PhotoInfo">OffsetSchema</a>
+<br><a href="#JPEG">JPEG</a>
+<br><a href="#MPF">MPF</a>
+<br><a href="#refs">References</a>
+</div>
+<h1 class=up>Problems with current Metadata Standards</h1>
+<p>It seems that all metadata standards have their own unique problems. This
+page documents some significant structural problems found in some current
+metadata and file format specifications, and gives possible solutions to these
+problems.  <i>[Also see my <a href="commentary.html">Commentary on Meta
+Information Formats</a>.]</i></p>
+<a name="TIFF"></a>
+<h3>TIFF 6.0 <a class=ref href="#ref1">[1]</a></h3>
+<p>A significant problem of the 1992 TIFF 6.0 specification is that there is no
+way to distinguish an IFD (image file directory) offset from a simple integer
+value.  As a result, new IFD's may not be created without risking corruption of
+the files by unaware software.  This is not only a problem for proprietary maker
+notes which commonly use a TIFF IFD structure, but is also a problem for
+extensibility of TIFF-based RAW image formats (as demonstrated by the DNG 1.3
+specification -- see below).</p>
+<p><b>A simple solution:</b></p>
+<p>Use a TIFF field type of 13 (IFD) instead of 4 (LONG) for IFD offsets.
+This was first proposed in 1995 by Adobe in their PageMaker
+6.0 TIFF Technical Notes<a class=ref href="#ref2">[2]</a>,
+but unfortunately it never found its way into the TIFF specification.  Even so,
+Olympus Optical Co. has shown some intelligence and is using this field type in
+the maker notes of their recent digital cameras.
+</p>
+<p><b>Another useful addition:</b> <i>(added 2009-09-27)</i></p>
+<p>A number of camera and cell phone manufacturers (Concord, Kodak, Motorola,
+Nokia, Olympus, Pentax, Ricoh, Samsung and Sony) leave blank IFD entries in the
+maker notes of images from some models. Presumably this simplifies the embedded
+software by allowing the output file structure to be kept constant even when the
+number of maker note IFD entries changes.  It could be useful if this feature
+was added explicitly to the offical TIFF specification by defining a field type
+of 0 as a "free IFD entry" to be ignored.  (Note that this ability already
+exists implicitly at a certain level in the specification, which states:
+<i>"Readers should skip over fields containing an unexpected field
+type"</i>.)</p>
+<a name="DNG"></a>
+<h3>DNG 1.3 <a class=ref href="#ref3">[3]</a></h3>
+<p>With the DNG 1.3 specification of June 2009, Adobe added a new Camera Profile
+IFD referenced by an offset using the standard (and unfortunate) TIFF LONG field
+type.  This means that the new Profile IFD will be lost if the file is rewritten
+by any software which does not have explicit knowledge of the 1.3 specification.
+But to make things worse, Adobe didn't even use a standard IFD format for the
+data. Instead, the IFD begins with a TIFF-style header and uses relative instead
+of absolute offsets.  This would have been a good idea if the IFD was stored as
+the value of an UNDEFINED tag rather than referenced from a LONG offset. (If
+done this way, the new information would have been preserved if the file was
+rewritten by unaware software.) But as implemented it just adds to the pain of
+parsing the file by requiring even more specialized code to be written in
+support of the DNG 1.3 format.</p>
+<p><b>A simple solution:</b></p>
+<p>Sack the Adobe developers who were responsible for this, and use field type
+13 (as recommended above for TIFF 6.0) and a standard TIFF IFD structure when
+adding new IFD's in the future.</p>
+<a name="EXIF"></a>
+<h3>EXIF 2.3 <a class=ref href="#ref4">[4]</a></h3>
+<p>The EXIF specification has been the standard for digital camera metadata for
+many years, and while the digital camera technology has advanced significantly
+in these years, the EXIF specification has not.  There are a number of
+significant problems with the EXIF specification which have never been
+addressed.</p>
+<p>Some current problems with the EXIF specification are:</p>
+<ol>
+<li>Maker note data structure has no restrictions and is easily invalidated when
+editing EXIF.</li>
+<li>No facility for storing the time zone for date/time values.</li>
+<li>Very limited support for alternate character sets (essentially only the
+UserComment tag has this feature).</li>
+<li>No alternate language support.</li>
+<li>Byte ordering for "Unicode" text strings, and the meaning of "Unicode"
+itself is not clearly specified.</li>
+<li>Mandatory tags are unnecessary and painful to implement.</li>
+<li>ApertureValue and MaxApertureValue are stored as unsigned RATIONAL, which
+means that lenses with F numbers faster than 1.0 (with equivalent APEX values of
+less than zero) can not be represented.</li>
+<li>MaxApertureValue is defined as "The smallest F number of the lens".  This
+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 (eg. camera pitch/roll
+angles, sensor temperature, face detection, auto-focus points, image
+stabilization, flash exposure compensation, etc).</li>
+</ol>
+<p><b>Simple solutions:</b></p>
+<ol>
+<li>Specify that maker note data must be self-contained (ie. must not exceed the
+bounds of the maker note value data), and must be relocatable (ie. must not use
+absolute offsets).  <i>[I would have suggested defining a new maker note tag
+with field type 13 (IFD) which references a standard format IFD, but I am afraid
+that no camera maker would ever jump on board with this suggestion now that they
+have already been seduced by the dark side.]</i></li>
+<li>Change the specification to allow an optional time zone of the format
+"-05:00" to be appended to the date/time string values.</li>
+<li>Change the specification to allow UTF-8 in ASCII-type values as recommended
+by the MWG<a class=ref href="#ref5">[5]</a>.</li>
+<li>No simple solution for this.  XMP<a class=ref href="#ref6">[6]</a>
+is the only reasonable alternative if alternate language support is
+required.</li>
+<li>Specify that the Unicode byte order must be the same as the EXIF byte
+ordering. (This is the only reasonable choice, but for some reason both
+Microsoft and Apple seem to write Unicode using the native processor byte
+ordering. regardless of the EXIF byte order.)  Also, it should be made clear
+that by "Unicode" the EXIF specification actually means UCS-2, although updating
+this to allow UTF-16 surrogate pairs may be a good idea.</li>
+<li>Define reasonable fallback values for required tags which are missing.</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>
+<h3>Microsoft "OffsetSchema" Tag <a class=ref href="#ref7">[7]</a></h3>
+<p>In February 2007 Microsoft proposed a new PhotoInfo tag called "OffsetSchema"
+(hex. 0xEA1D, dec. 59933) in an attempt to patch a deficiency in the EXIF maker
+note specification (see point 1 in EXIF 2.2 section above).  This tag represents
+the offset difference between the original maker note location in the EXIF and
+the new location after editing, and is designed to allow the maker note tag
+values to be accessed after the location of the maker notes is changed by
+editing the EXIF. <i>[Bless their little hearts for trying to improve this
+situation, but while the idea is good the implementation is flawed and
+ultimately unworkable.]</i></p>
+<p>There are two main problems with the implementation, and the second is a show
+stopper:</p>
+<blockquote>1. For this new tag to be available to a single-pass metadata reader, it
+must come <i>before</i> the maker note data (hex. 0x927C, dec. 37500).  But
+since the EXIF/TIFF format specifies that tags must be stored in numerical
+order, the maker note tag (hex. 0x927C) comes before the OffsetSchema tag
+(hex. 0xEA1D).</blockquote>
+<blockquote>2. The OffsetSchema tag will be invalidated by any software that
+rewrites the EXIF and moves the maker notes without properly updating the tag.
+In an ideal world all application developers would release an updated version
+of their software which treats the OffsetSchema properly, and all users would
+update to this new version.  But since this is the real world it just won't
+happen, which makes the value of OffsetSchema unreliable.  Too bad, because this
+wouldn't have been a problem if Microsoft had specified that the new tag
+represented the original offset of the maker notes instead of the difference
+from the original position. With this change, the tag wouldn't need updating
+when the EXIF is edited, and the information would be much more reliable.  The
+only problem here would be editing software that explicitly changes the maker
+note offsets.  However, software with this ability is rare, and it is more
+reasonable to ask that the OffsetSchema tag simply be deleted by any software
+that updates the maker note offsets.  (Software must be fairly advanced in the
+first place if it parses the proprietary maker note data structures and changes
+these offsets.)</blockquote>
+<p><b>A simple solution:</b></p>
+<p>Create a new tag which comes before the maker notes (hex. 0x927B, dec. 37499
+would be good) and represents the original offset of the maker notes.</p>
+<a name="JPEG"></a>
+<h3>JPEG File Interchange Format <a class=ref href="#ref8">[8]</a></h3>
+<p>The JPEG File Interchange Format version 1.02 was released in 1992.  The
+biggest structural problem with this standard is that metadata in these files in
+is stored in segments which have a maximum size of 65533 bytes.  This limit has
+necessitated a number of creative solutions, each creating complications and
+problems of their own.  <i>[See my comments on the <a
+href="writing.html#Preview">PreviewImage problem</a> for example.]</i></p>
+<p><b>A simple solution:</b></p>
+<p>Since the value of the segment size word includes the 2 bytes of the segment
+size word itself, a value of 0 or 1 is not allowed by the current JPEG standard.
+The standard could be enhanced so a value of 1 indicates an extended JPEG
+segment where the 2-byte size word (with value 0x0001) is followed immediately
+by a 4-byte integer giving the size of the extended JPEG segment.  This would
+allow segment sizes of up to 4294967291 bytes (assuming the size includes these
+4 bytes). Further, a value of 0 could be defined for an 8-byte integer if one
+really wanted to support huge metadata segments.  Either change to an existing
+JPEG would break all current JPEG reader/writers, but the change is trivial and
+could easily be implemented.</p>
+<p><b>An alternative solution:</b></p>
+<p>Define a new application marker segment which uses a 4-byte size word.  This
+technique is already used for the extended JPEG2000 codestream MCT, MCC and MIC
+marker segments.</p>
+<a name="MPF"></a>
+<h3>Multi-Picture Format (MPF) <a class=ref href="#ref9">[9]</a></h3>
+<p>In February 2009 CIPA<a class=ref href="#ref10">[10]</a> released a
+"Multi-Picture Format" standard for storing large images in JPEG files.  This
+format is yet another attempt to bypass the JPEG segment-size limit (see above)
+to store large preview images.  But again, there is a significant problem with
+this standard:  Pointers in the new APP2 MPF segment use offsets relative to the
+start of the MPF header in this segment to reference image data after the JPEG
+EOI.  Unfortunately, these offsets are quickly broken if any data after the MPF
+segment changes length.  This problem could have been avoided if offsets had
+been specified relative to the end of file, but it is too late for this now that
+the specification is public.  However, another problem is that information after
+the JPEG EOI is often discarded by software when the file is edited.</p>
+<p><b>A possible work-around:</b></p>
+<p>Enforce the rule that the MPF APP2 segment must come after all other APP
+segments.  (It would have been smart if this was specified in the CIPA standard,
+but sadly this wasn't the case.)  If this is done, then metadata in the remaining
+APP segments (EXIF, IPTC, XMP, etc) can safely be edited without breaking the
+MPF offsets.  I suggest that all metadata editors employ this strategy,
+regardless of the segment order specified in the standard (which says that the
+MPF APP2 segment must come immediately after the EXIF APP1 segment).</p>
+<p>Unfortunately this work-around has the same problems as the Microsoft
+OffsetSchema tag because the MPF information may easily be invalidated by an
+unaware editor, and it doesn't address the problem of losing data stored after
+the JPEG EOI.</p>
+<p><b>A simple solution:</b></p>
+<p>Change the JPEG specification to allow larger segments (as mentioned above in
+the JPEG section), and change the MPF specification to store all information
+inside a JPEG segment.</p>
+<p><i>[2014-04-29: CIPA has changed the location of these standards documents,
+so the URL's referenced here are now broken.]</i></p>
+<a name="refs"></a>
+<h3>References</h3>
+<ol>
+<li><a name="ref1" href="http://partners.adobe.com/public/developer/en/tiff/TIFF6.pdf">http://partners.adobe.com/public/developer/en/tiff/TIFF6.pdf</a></li>
+<li><a name="ref2" href="http://partners.adobe.com/public/developer/en/tiff/TIFFPM6.pdf">http://partners.adobe.com/public/developer/en/tiff/TIFFPM6.pdf</a></li>
+<li><a name="ref3" href="http://www.adobe.com/products/dng/pdfs/dng_spec_1_3_0_0.pdf">http://www.adobe.com/products/dng/pdfs/dng_spec_1_3_0_0.pdf</a></li>
+<li><a name="ref4" href="http://www.cipa.jp/english/hyoujunka/kikaku/pdf/DC-008-2010_E.pdf">http://www.cipa.jp/english/hyoujunka/kikaku/pdf/DC-008-2010_E.pdf</a></li>
+<li><a name="ref5" href="http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf">http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf</a></li>
+<li><a name="ref6" href="http://www.adobe.com/devnet/xmp/">http://www.adobe.com/devnet/xmp/</a></li>
+<li><a name="ref7" href="http://support.microsoft.com/kb/927527">http://support.microsoft.com/kb/927527</a></li>
+<li><a name="ref8" href="http://www.jpeg.org/public/jfif.pdf">http://www.jpeg.org/public/jfif.pdf</a></li>
+<li><a name="ref9" href="http://www.cipa.jp/english/hyoujunka/kikaku/pdf/DC-X007-KEY_E.pdf">http://www.cipa.jp/english/hyoujunka/kikaku/pdf/DC-X007-KEY_E.pdf</a></li>
+<li><a name="ref10" href="http://www.cipa.jp/english/hyoujunka/kikaku/cipa_e_kikaku_list.html">http://www.cipa.jp/english/hyoujunka/kikaku/cipa_e_kikaku_list.html</a></li>
+</ol>
+<hr>
+<i>Created Sep 17, 2009</i><br>
+<i>Last revised Apr 23, 2015</i>
+<p class='lf'><a href="index.html">&lt;-- Back to ExifTool home page</a></p>
+</body>
+</html>