[SCM] exiv2 packaging branch, master, updated. debian/0.25-3.1-3734-gdcbc29a

Thu Jul 13 17:36:42 UTC 2017

Gitweb-URL: http://git.debian.org/?p=pkg-kde/kde-extras/exiv2.git;a=commitdiff;h=7ee2b5a

The following commit has been merged in the master branch:
commit 7ee2b5a7a0ff2ecd7da6a45d9d1a8bc02a8b069d
Author: Andreas Huggel <ahuggel at gmx.net>
Date:   Sun Oct 31 08:27:48 2004 +0000

    Updated according to website
---
 doc/makernote.html | 92 +++++++++++++++++++++++++++++++++++++++---------------
 1 file changed, 66 insertions(+), 26 deletions(-)

diff --git a/doc/makernote.html b/doc/makernote.html
index a00daf9..f228cbd 100644
--- a/doc/makernote.html
+++ b/doc/makernote.html
@@ -5,14 +5,54 @@
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   <link type="text/css" rel="stylesheet" href="include/sortabletable.css">
   <script type="text/javascript" src="include/sortabletable.js"></script>
+  <script type="text/javascript">
+  <!--
+  var preload = new Array('include/blank.png', 
+                          'include/ascending.png', 
+                          'include/descending.png');
+  var loader = new Array();
+  for(var i = 0; i < preload.length; i++) {
+    loader[i] = new Image();
+    loader[i].src = preload[i];
+  }
+  //-->
+  </script>
 </head>
 <body>
 
 <h1>Exif and Iptc metadata manipulation library and tools</h1>
 
 <h2>MakerNote Formats and Specifications</h2>
-<p>According to the <a title="The Exif 2.2 standard (PDF)" href="http://tsc.jeita.or.jp/avs/data/cp3451.pdf">Exif 2.2 standard</a>, the makernote is <i>"a tag for manufacturers of Exif writers to record any desired information. The contents are up to the manufacturer, but this tag should not be used for any other than its intended purpose."</i> Many (but not all) vendors write the makernote in IFD (Image File Directory) format, i.e., in the same format as the rest of the Exif information is encoded. Many manufacturers apparently store a lot of information in the makernote field but unfortunately, most vendors do not publish their specifications.</p>
-<p>The following table summarizes the structures of the MakerNote field used by some vendors.</p>
+
+<p>
+The MakerNote is tag 0x927c in the Exif IFD. According to the 
+<a title="The Exif 2.2 standard (PDF)" href="http://tsc.jeita.or.jp/avs/data/cp3451.pdf">
+Exif 2.2 standard</a>, the makernote is <i>"a tag for manufacturers of
+Exif writers to record any desired information. The contents are up to
+the manufacturer, but this tag should not be used for any other than
+its intended purpose."</i></p> 
+
+<p>Unfortunately, most vendors do not publish their makernote specifications. (Why not?) 
+Most of the <a href="#R0">specifications available on the Internet</a> 
+were reverse-engineered. Judging from the size of many makernote fields, manufacturers 
+apparently store a lot of information there and from the available specifications, 
+some of this is certainly quite interesting. For example, makernotes may contain 
+information about the lens used, contrast, saturation and sharpness settings, image 
+quality settings, etc.</p>
+
+<p>Many (but not all) vendors write the makernote in TIFF IFD (Image File Directory) format, 
+i.e., in the same format as the rest of the Exif information is encoded. Although this may 
+appear to make sense at first glance, it actually complicates the situation for programs that 
+attempt to write to the Exif data. The problem is that IFDs contain offsets relative to the 
+start of the Exif data. That implies that if an Exif writer moves a makernote field encoded in 
+IFD format to a different location within the Exif data, it gets corrupted. The reason to
+write to the Exif data could be as simple as to add copyright information, an Exif comment, 
+etc. In my opinion, this is a bug in the specification. In fact, some vendors seem to have
+recognized this problem and use offsets relative to somewhere at the beginning of the makernote 
+field for the makernote IFD.</p>
+
+<p>The following table summarizes the structures of the MakerNote field used by some vendors. 
+Please let me know if you find further specifications on the Internet.</p>
 <table class="ReportTable" id="report-1" cellspacing="0">
   <colgroup>
     <col>
@@ -31,14 +71,14 @@
    </tr>
   </thead>
   <tbody>
-   <tr> 
+   <tr class="OddRow"> 
     <td>Canon</td>
     <td> </td>
     <td>IFD</td>
-    <td> <a href="#R2">[2]</a></td>
+    <td><a href="#R2">[2]</a></td>
     <td> </td>
    </tr>
-   <tr> 
+   <tr class="EvenRow"> 
     <td>Casio</td>
     <td>QV-3000EX, QV-2000UX, QV-8000SX</td>
     <td>IFD</td>
@@ -46,7 +86,7 @@
     <td>"Early" versions of QV-2000UX and QV-8000SX only 
       have 4 bytes in the MakerNote field.</td>
    </tr>
-   <tr> 
+   <tr class="OddRow"> 
     <td>Fujifilm</td>
     <td> </td>
     <td>IFD; starts with string "FUJIFILM" and an offset 
@@ -55,30 +95,30 @@
     <td>Fujifilm's Exif data uses big endian (MM) byte order, but the MakerNote 
       uses little endian (II) alignment</td>
    </tr>
-   <tr> 
+   <tr class="EvenRow"> 
     <td>Minolta</td>
     <td> </td>
     <td>IFD</td>
     <td><a href="#R5">[5]</a></td>
     <td>MakerNote numbers are always stored in big endian (MM) byte order</td>
    </tr>
-   <tr> 
-    <td>Nikon</td>
+   <tr class="OddRow"> 
+    <td>Nikon (1)</td>
     <td>E990, D1</td>
     <td>IFD (from offset 0x00)</td>
     <td><a href="#R3">[3]</a></td>
     <td> </td>
    </tr>
-   <tr> 
-    <td>Nikon</td>
+   <tr class="EvenRow"> 
+    <td>Nikon (2)</td>
     <td>E700, E800, E900, E900S, E910, E950</td>
     <td>IFD; starts with string "Nikon

-- 
exiv2 packaging

