exiftool_vendored 9.33.0

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.

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

Files changed (864) hide show
  1. checksums.yaml +15 -0
  2. data/bin/Image-ExifTool-9.33/Changes +6241 -0
  3. data/bin/Image-ExifTool-9.33/MANIFEST +859 -0
  4. data/bin/Image-ExifTool-9.33/META.yml +27 -0
  5. data/bin/Image-ExifTool-9.33/Makefile.PL +41 -0
  6. data/bin/Image-ExifTool-9.33/README +227 -0
  7. data/bin/Image-ExifTool-9.33/arg_files/exif2iptc.args +24 -0
  8. data/bin/Image-ExifTool-9.33/arg_files/exif2xmp.args +38 -0
  9. data/bin/Image-ExifTool-9.33/arg_files/gps2xmp.args +20 -0
  10. data/bin/Image-ExifTool-9.33/arg_files/iptc2exif.args +17 -0
  11. data/bin/Image-ExifTool-9.33/arg_files/iptc2xmp.args +53 -0
  12. data/bin/Image-ExifTool-9.33/arg_files/iptcCore.args +172 -0
  13. data/bin/Image-ExifTool-9.33/arg_files/pdf2xmp.args +23 -0
  14. data/bin/Image-ExifTool-9.33/arg_files/xmp2exif.args +39 -0
  15. data/bin/Image-ExifTool-9.33/arg_files/xmp2gps.args +24 -0
  16. data/bin/Image-ExifTool-9.33/arg_files/xmp2iptc.args +62 -0
  17. data/bin/Image-ExifTool-9.33/arg_files/xmp2pdf.args +23 -0
  18. data/bin/Image-ExifTool-9.33/config_files/ExifTool_config +299 -0
  19. data/bin/Image-ExifTool-9.33/config_files/convert_regions.config +81 -0
  20. data/bin/Image-ExifTool-9.33/exiftool +5715 -0
  21. data/bin/Image-ExifTool-9.33/fmt_files/gpx.fmt +29 -0
  22. data/bin/Image-ExifTool-9.33/fmt_files/gpx_wpt.fmt +33 -0
  23. data/bin/Image-ExifTool-9.33/fmt_files/kml.fmt +53 -0
  24. data/bin/Image-ExifTool-9.33/html/ExifTool.html +1959 -0
  25. data/bin/Image-ExifTool-9.33/html/MIE1.1-20070121.pdf +0 -0
  26. data/bin/Image-ExifTool-9.33/html/Shift.html +173 -0
  27. data/bin/Image-ExifTool-9.33/html/TagNames/AFCP.html +53 -0
  28. data/bin/Image-ExifTool-9.33/html/TagNames/AIFF.html +146 -0
  29. data/bin/Image-ExifTool-9.33/html/TagNames/APE.html +149 -0
  30. data/bin/Image-ExifTool-9.33/html/TagNames/APP12.html +188 -0
  31. data/bin/Image-ExifTool-9.33/html/TagNames/ASF.html +1066 -0
  32. data/bin/Image-ExifTool-9.33/html/TagNames/BMP.html +110 -0
  33. data/bin/Image-ExifTool-9.33/html/TagNames/Canon.html +8062 -0
  34. data/bin/Image-ExifTool-9.33/html/TagNames/CanonCustom.html +2044 -0
  35. data/bin/Image-ExifTool-9.33/html/TagNames/CanonRaw.html +561 -0
  36. data/bin/Image-ExifTool-9.33/html/TagNames/CanonVRD.html +1222 -0
  37. data/bin/Image-ExifTool-9.33/html/TagNames/Casio.html +1569 -0
  38. data/bin/Image-ExifTool-9.33/html/TagNames/Composite.html +665 -0
  39. data/bin/Image-ExifTool-9.33/html/TagNames/DICOM.html +15762 -0
  40. data/bin/Image-ExifTool-9.33/html/TagNames/DNG.html +273 -0
  41. data/bin/Image-ExifTool-9.33/html/TagNames/DV.html +75 -0
  42. data/bin/Image-ExifTool-9.33/html/TagNames/DarwinCore.html +1445 -0
  43. data/bin/Image-ExifTool-9.33/html/TagNames/DjVu.html +313 -0
  44. data/bin/Image-ExifTool-9.33/html/TagNames/EXE.html +697 -0
  45. data/bin/Image-ExifTool-9.33/html/TagNames/EXIF.html +3244 -0
  46. data/bin/Image-ExifTool-9.33/html/TagNames/Extra.html +301 -0
  47. data/bin/Image-ExifTool-9.33/html/TagNames/FLAC.html +183 -0
  48. data/bin/Image-ExifTool-9.33/html/TagNames/FLIR.html +931 -0
  49. data/bin/Image-ExifTool-9.33/html/TagNames/Flash.html +419 -0
  50. data/bin/Image-ExifTool-9.33/html/TagNames/FlashPix.html +1435 -0
  51. data/bin/Image-ExifTool-9.33/html/TagNames/Font.html +485 -0
  52. data/bin/Image-ExifTool-9.33/html/TagNames/FotoStation.html +103 -0
  53. data/bin/Image-ExifTool-9.33/html/TagNames/FujiFilm.html +637 -0
  54. data/bin/Image-ExifTool-9.33/html/TagNames/GE.html +40 -0
  55. data/bin/Image-ExifTool-9.33/html/TagNames/GIF.html +116 -0
  56. data/bin/Image-ExifTool-9.33/html/TagNames/GIMP.html +140 -0
  57. data/bin/Image-ExifTool-9.33/html/TagNames/GPS.html +222 -0
  58. data/bin/Image-ExifTool-9.33/html/TagNames/GeoTiff.html +2177 -0
  59. data/bin/Image-ExifTool-9.33/html/TagNames/H264.html +393 -0
  60. data/bin/Image-ExifTool-9.33/html/TagNames/HP.html +155 -0
  61. data/bin/Image-ExifTool-9.33/html/TagNames/HTML.html +666 -0
  62. data/bin/Image-ExifTool-9.33/html/TagNames/ICC_Profile.html +710 -0
  63. data/bin/Image-ExifTool-9.33/html/TagNames/ID3.html +1473 -0
  64. data/bin/Image-ExifTool-9.33/html/TagNames/IPTC.html +895 -0
  65. data/bin/Image-ExifTool-9.33/html/TagNames/ITC.html +90 -0
  66. data/bin/Image-ExifTool-9.33/html/TagNames/JFIF.html +61 -0
  67. data/bin/Image-ExifTool-9.33/html/TagNames/JPEG.html +523 -0
  68. data/bin/Image-ExifTool-9.33/html/TagNames/JVC.html +56 -0
  69. data/bin/Image-ExifTool-9.33/html/TagNames/Jpeg2000.html +464 -0
  70. data/bin/Image-ExifTool-9.33/html/TagNames/Kodak.html +1759 -0
  71. data/bin/Image-ExifTool-9.33/html/TagNames/KyoceraRaw.html +92 -0
  72. data/bin/Image-ExifTool-9.33/html/TagNames/LNK.html +478 -0
  73. data/bin/Image-ExifTool-9.33/html/TagNames/Leaf.html +870 -0
  74. data/bin/Image-ExifTool-9.33/html/TagNames/M2TS.html +133 -0
  75. data/bin/Image-ExifTool-9.33/html/TagNames/MIE.html +1026 -0
  76. data/bin/Image-ExifTool-9.33/html/TagNames/MIFF.html +196 -0
  77. data/bin/Image-ExifTool-9.33/html/TagNames/MNG.html +847 -0
  78. data/bin/Image-ExifTool-9.33/html/TagNames/MPC.html +97 -0
  79. data/bin/Image-ExifTool-9.33/html/TagNames/MPEG.html +249 -0
  80. data/bin/Image-ExifTool-9.33/html/TagNames/MPF.html +199 -0
  81. data/bin/Image-ExifTool-9.33/html/TagNames/MWG.html +563 -0
  82. data/bin/Image-ExifTool-9.33/html/TagNames/MXF.html +6673 -0
  83. data/bin/Image-ExifTool-9.33/html/TagNames/Matroska.html +1069 -0
  84. data/bin/Image-ExifTool-9.33/html/TagNames/Microsoft.html +2066 -0
  85. data/bin/Image-ExifTool-9.33/html/TagNames/Minolta.html +2555 -0
  86. data/bin/Image-ExifTool-9.33/html/TagNames/MinoltaRaw.html +326 -0
  87. data/bin/Image-ExifTool-9.33/html/TagNames/Nikon.html +4467 -0
  88. data/bin/Image-ExifTool-9.33/html/TagNames/NikonCapture.html +776 -0
  89. data/bin/Image-ExifTool-9.33/html/TagNames/NikonCustom.html +3835 -0
  90. data/bin/Image-ExifTool-9.33/html/TagNames/OOXML.html +280 -0
  91. data/bin/Image-ExifTool-9.33/html/TagNames/Ogg.html +44 -0
  92. data/bin/Image-ExifTool-9.33/html/TagNames/Olympus.html +3386 -0
  93. data/bin/Image-ExifTool-9.33/html/TagNames/OpenEXR.html +222 -0
  94. data/bin/Image-ExifTool-9.33/html/TagNames/PDF.html +745 -0
  95. data/bin/Image-ExifTool-9.33/html/TagNames/PGF.html +80 -0
  96. data/bin/Image-ExifTool-9.33/html/TagNames/PICT.html +753 -0
  97. data/bin/Image-ExifTool-9.33/html/TagNames/PLIST.html +86 -0
  98. data/bin/Image-ExifTool-9.33/html/TagNames/PNG.html +515 -0
  99. data/bin/Image-ExifTool-9.33/html/TagNames/PSP.html +160 -0
  100. data/bin/Image-ExifTool-9.33/html/TagNames/Panasonic.html +1452 -0
  101. data/bin/Image-ExifTool-9.33/html/TagNames/PanasonicRaw.html +214 -0
  102. data/bin/Image-ExifTool-9.33/html/TagNames/Pentax.html +4332 -0
  103. data/bin/Image-ExifTool-9.33/html/TagNames/PhaseOne.html +258 -0
  104. data/bin/Image-ExifTool-9.33/html/TagNames/PhotoCD.html +402 -0
  105. data/bin/Image-ExifTool-9.33/html/TagNames/PhotoMechanic.html +196 -0
  106. data/bin/Image-ExifTool-9.33/html/TagNames/Photoshop.html +555 -0
  107. data/bin/Image-ExifTool-9.33/html/TagNames/PostScript.html +125 -0
  108. data/bin/Image-ExifTool-9.33/html/TagNames/PrintIM.html +31 -0
  109. data/bin/Image-ExifTool-9.33/html/TagNames/Qualcomm.html +4778 -0
  110. data/bin/Image-ExifTool-9.33/html/TagNames/QuickTime.html +3104 -0
  111. data/bin/Image-ExifTool-9.33/html/TagNames/RIFF.html +1164 -0
  112. data/bin/Image-ExifTool-9.33/html/TagNames/RSRC.html +74 -0
  113. data/bin/Image-ExifTool-9.33/html/TagNames/RTF.html +150 -0
  114. data/bin/Image-ExifTool-9.33/html/TagNames/Radiance.html +87 -0
  115. data/bin/Image-ExifTool-9.33/html/TagNames/Rawzor.html +45 -0
  116. data/bin/Image-ExifTool-9.33/html/TagNames/Real.html +780 -0
  117. data/bin/Image-ExifTool-9.33/html/TagNames/Reconyx.html +132 -0
  118. data/bin/Image-ExifTool-9.33/html/TagNames/Ricoh.html +456 -0
  119. data/bin/Image-ExifTool-9.33/html/TagNames/Samsung.html +419 -0
  120. data/bin/Image-ExifTool-9.33/html/TagNames/Sanyo.html +366 -0
  121. data/bin/Image-ExifTool-9.33/html/TagNames/Shortcuts.html +237 -0
  122. data/bin/Image-ExifTool-9.33/html/TagNames/Sigma.html +372 -0
  123. data/bin/Image-ExifTool-9.33/html/TagNames/SigmaRaw.html +403 -0
  124. data/bin/Image-ExifTool-9.33/html/TagNames/Sony.html +4279 -0
  125. data/bin/Image-ExifTool-9.33/html/TagNames/SonyIDC.html +267 -0
  126. data/bin/Image-ExifTool-9.33/html/TagNames/Stim.html +200 -0
  127. data/bin/Image-ExifTool-9.33/html/TagNames/Theora.html +102 -0
  128. data/bin/Image-ExifTool-9.33/html/TagNames/Unknown.html +31 -0
  129. data/bin/Image-ExifTool-9.33/html/TagNames/Vorbis.html +228 -0
  130. data/bin/Image-ExifTool-9.33/html/TagNames/XMP.html +7234 -0
  131. data/bin/Image-ExifTool-9.33/html/TagNames/ZIP.html +204 -0
  132. data/bin/Image-ExifTool-9.33/html/TagNames/iWork.html +49 -0
  133. data/bin/Image-ExifTool-9.33/html/TagNames/index.html +192 -0
  134. data/bin/Image-ExifTool-9.33/html/TagNames/style.css +31 -0
  135. data/bin/Image-ExifTool-9.33/html/ancient_history.html +6727 -0
  136. data/bin/Image-ExifTool-9.33/html/canon_raw.html +366 -0
  137. data/bin/Image-ExifTool-9.33/html/commentary.html +319 -0
  138. data/bin/Image-ExifTool-9.33/html/config.html +312 -0
  139. data/bin/Image-ExifTool-9.33/html/data_members.html +265 -0
  140. data/bin/Image-ExifTool-9.33/html/exiftool_pod.html +2338 -0
  141. data/bin/Image-ExifTool-9.33/html/faq.html +1434 -0
  142. data/bin/Image-ExifTool-9.33/html/filename.html +281 -0
  143. data/bin/Image-ExifTool-9.33/html/geotag.html +642 -0
  144. data/bin/Image-ExifTool-9.33/html/history.html +358 -0
  145. data/bin/Image-ExifTool-9.33/html/htmldump.html +732 -0
  146. data/bin/Image-ExifTool-9.33/html/idiosyncracies.html +251 -0
  147. data/bin/Image-ExifTool-9.33/html/index.html +1271 -0
  148. data/bin/Image-ExifTool-9.33/html/install.html +239 -0
  149. data/bin/Image-ExifTool-9.33/html/metafiles.html +266 -0
  150. data/bin/Image-ExifTool-9.33/html/overview.png +0 -0
  151. data/bin/Image-ExifTool-9.33/html/standards.html +277 -0
  152. data/bin/Image-ExifTool-9.33/html/struct.html +342 -0
  153. data/bin/Image-ExifTool-9.33/html/style.css +31 -0
  154. data/bin/Image-ExifTool-9.33/html/under.html +124 -0
  155. data/bin/Image-ExifTool-9.33/html/verbose.html +195 -0
  156. data/bin/Image-ExifTool-9.33/html/writing.html +239 -0
  157. data/bin/Image-ExifTool-9.33/lib/File/RandomAccess.pm +378 -0
  158. data/bin/Image-ExifTool-9.33/lib/File/RandomAccess.pod +231 -0
  159. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool.pm +6815 -0
  160. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool.pod +2385 -0
  161. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/AES.pm +501 -0
  162. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/AFCP.pm +284 -0
  163. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/AIFF.pm +271 -0
  164. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/APE.pm +262 -0
  165. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/APP12.pm +322 -0
  166. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/ASF.pm +884 -0
  167. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/BMP.pm +179 -0
  168. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/BZZ.pm +472 -0
  169. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/BigTIFF.pm +282 -0
  170. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/BuildTagLookup.pm +2400 -0
  171. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Canon.pm +7794 -0
  172. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/CanonCustom.pm +2523 -0
  173. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/CanonRaw.pm +931 -0
  174. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/CanonVRD.pm +1481 -0
  175. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/CaptureOne.pm +235 -0
  176. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Casio.pm +2013 -0
  177. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset.pm +396 -0
  178. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Arabic.pm +39 -0
  179. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Baltic.pm +35 -0
  180. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Cyrillic.pm +45 -0
  181. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Greek.pm +40 -0
  182. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Hebrew.pm +36 -0
  183. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/JIS.pm +1735 -0
  184. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Latin.pm +24 -0
  185. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Latin2.pm +36 -0
  186. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacArabic.pm +47 -0
  187. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacChineseCN.pm +2088 -0
  188. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacChineseTW.pm +3623 -0
  189. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacCroatian.pm +43 -0
  190. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacCyrillic.pm +47 -0
  191. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacGreek.pm +45 -0
  192. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacHebrew.pm +47 -0
  193. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacIceland.pm +42 -0
  194. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacJapanese.pm +1933 -0
  195. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacKorean.pm +2720 -0
  196. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacLatin2.pm +44 -0
  197. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacRSymbol.pm +2087 -0
  198. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacRoman.pm +42 -0
  199. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacRomanian.pm +42 -0
  200. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacThai.pm +49 -0
  201. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/MacTurkish.pm +42 -0
  202. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/PDFDoc.pm +28 -0
  203. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/ShiftJIS.pm +1835 -0
  204. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Symbol.pm +54 -0
  205. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Thai.pm +41 -0
  206. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Turkish.pm +25 -0
  207. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Charset/Vietnam.pm +27 -0
  208. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/DICOM.pm +3835 -0
  209. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/DNG.pm +835 -0
  210. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/DV.pm +319 -0
  211. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/DarwinCore.pm +317 -0
  212. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/DjVu.pm +376 -0
  213. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/EXE.pm +1228 -0
  214. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Exif.pm +4542 -0
  215. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/FLAC.pm +296 -0
  216. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/FLIR.pm +972 -0
  217. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Fixup.pm +354 -0
  218. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Flash.pm +755 -0
  219. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/FlashPix.pm +1882 -0
  220. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Font.pm +643 -0
  221. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/FotoStation.pm +258 -0
  222. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/FujiFilm.pm +1020 -0
  223. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/GE.pm +80 -0
  224. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/GIF.pm +542 -0
  225. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/GIMP.pm +258 -0
  226. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/GPS.pm +511 -0
  227. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/GeoTiff.pm +2187 -0
  228. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Geotag.pm +1173 -0
  229. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/H264.pm +1102 -0
  230. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/HP.pm +262 -0
  231. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/HTML.pm +576 -0
  232. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/HtmlDump.pm +895 -0
  233. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/ICC_Profile.pm +999 -0
  234. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/ID3.pm +1532 -0
  235. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/IPTC.pm +1244 -0
  236. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/ITC.pm +215 -0
  237. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Import.pm +308 -0
  238. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/InDesign.pm +277 -0
  239. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/JPEG.pm +588 -0
  240. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/JPEGDigest.pm +2511 -0
  241. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/JVC.pm +130 -0
  242. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Jpeg2000.pm +881 -0
  243. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Kodak.pm +2014 -0
  244. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/KyoceraRaw.pm +173 -0
  245. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/LNK.pm +723 -0
  246. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/cs.pm +1586 -0
  247. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/de.pm +7356 -0
  248. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/en_ca.pm +557 -0
  249. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/en_gb.pm +572 -0
  250. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/es.pm +4016 -0
  251. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/fi.pm +2856 -0
  252. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/fr.pm +4720 -0
  253. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/it.pm +7917 -0
  254. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/ja.pm +5815 -0
  255. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/ko.pm +2332 -0
  256. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/nl.pm +3220 -0
  257. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/pl.pm +1140 -0
  258. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/ru.pm +769 -0
  259. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/sv.pm +639 -0
  260. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/tr.pm +544 -0
  261. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/zh_cn.pm +1329 -0
  262. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Lang/zh_tw.pm +802 -0
  263. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Leaf.pm +515 -0
  264. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/M2TS.pm +729 -0
  265. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MIE.pm +2561 -0
  266. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MIEUnits.pod +377 -0
  267. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MIFF.pm +279 -0
  268. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MNG.pm +684 -0
  269. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MPC.pm +156 -0
  270. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MPEG.pm +736 -0
  271. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MPF.pm +289 -0
  272. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MWG.pm +736 -0
  273. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MXF.pm +3032 -0
  274. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MakerNotes.pm +1573 -0
  275. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Matroska.pm +891 -0
  276. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Microsoft.pm +879 -0
  277. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Minolta.pm +2833 -0
  278. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/MinoltaRaw.pm +534 -0
  279. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Nikon.pm +6116 -0
  280. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/NikonCapture.pm +911 -0
  281. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/NikonCustom.pm +4405 -0
  282. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/OOXML.pm +409 -0
  283. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Ogg.pm +237 -0
  284. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Olympus.pm +3582 -0
  285. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/OpenEXR.pm +324 -0
  286. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PDF.pm +2327 -0
  287. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PGF.pm +143 -0
  288. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PICT.pm +1260 -0
  289. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PLIST.pm +449 -0
  290. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PNG.pm +1100 -0
  291. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PPM.pm +169 -0
  292. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PSP.pm +305 -0
  293. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Panasonic.pm +1995 -0
  294. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PanasonicRaw.pm +535 -0
  295. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Pentax.pm +5489 -0
  296. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PhaseOne.pm +557 -0
  297. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PhotoCD.pm +507 -0
  298. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PhotoMechanic.pm +256 -0
  299. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Photoshop.pm +629 -0
  300. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PostScript.pm +693 -0
  301. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/PrintIM.pm +125 -0
  302. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Qualcomm.pm +1344 -0
  303. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/QuickTime.pm +3519 -0
  304. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/README +944 -0
  305. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/RIFF.pm +1322 -0
  306. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/RSRC.pm +241 -0
  307. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/RTF.pm +383 -0
  308. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Radiance.pm +144 -0
  309. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Rawzor.pm +190 -0
  310. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Real.pm +736 -0
  311. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Reconyx.pm +190 -0
  312. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Ricoh.pm +741 -0
  313. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Samsung.pm +820 -0
  314. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Sanyo.pm +439 -0
  315. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Shift.pl +594 -0
  316. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Shortcuts.pm +291 -0
  317. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Sigma.pm +574 -0
  318. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/SigmaRaw.pm +649 -0
  319. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Sony.pm +5722 -0
  320. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/SonyIDC.pm +330 -0
  321. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Stim.pm +196 -0
  322. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/TagInfoXML.pm +792 -0
  323. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/TagLookup.pm +8005 -0
  324. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/TagNames.pod +25950 -0
  325. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Theora.pm +145 -0
  326. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Unknown.pm +66 -0
  327. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Vorbis.pm +237 -0
  328. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WriteCanonRaw.pl +637 -0
  329. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WriteExif.pl +3674 -0
  330. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WriteIPTC.pl +702 -0
  331. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WritePDF.pl +759 -0
  332. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WritePNG.pl +330 -0
  333. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WritePhotoshop.pl +266 -0
  334. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WritePostScript.pl +777 -0
  335. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/WriteXMP.pl +1318 -0
  336. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/Writer.pl +5779 -0
  337. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/XMP.pm +3634 -0
  338. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/XMP2.pl +1298 -0
  339. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/XMPStruct.pl +813 -0
  340. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/ZIP.pm +623 -0
  341. data/bin/Image-ExifTool-9.33/lib/Image/ExifTool/iWork.pm +223 -0
  342. data/bin/Image-ExifTool-9.33/perl-Image-ExifTool.spec +104 -0
  343. data/bin/Image-ExifTool-9.33/t/AFCP.t +44 -0
  344. data/bin/Image-ExifTool-9.33/t/AFCP_2.out +37 -0
  345. data/bin/Image-ExifTool-9.33/t/AFCP_3.out +20 -0
  346. data/bin/Image-ExifTool-9.33/t/AIFF.t +28 -0
  347. data/bin/Image-ExifTool-9.33/t/AIFF_2.out +31 -0
  348. data/bin/Image-ExifTool-9.33/t/APE.t +38 -0
  349. data/bin/Image-ExifTool-9.33/t/APE_2.out +28 -0
  350. data/bin/Image-ExifTool-9.33/t/APE_3.out +57 -0
  351. data/bin/Image-ExifTool-9.33/t/ASF.t +28 -0
  352. data/bin/Image-ExifTool-9.33/t/ASF_2.out +54 -0
  353. data/bin/Image-ExifTool-9.33/t/BMP.t +28 -0
  354. data/bin/Image-ExifTool-9.33/t/BMP_2.out +21 -0
  355. data/bin/Image-ExifTool-9.33/t/BigTIFF.t +28 -0
  356. data/bin/Image-ExifTool-9.33/t/BigTIFF_2.out +19 -0
  357. data/bin/Image-ExifTool-9.33/t/Canon.t +41 -0
  358. data/bin/Image-ExifTool-9.33/t/CanonRaw.t +126 -0
  359. data/bin/Image-ExifTool-9.33/t/CanonRaw_2.out +165 -0
  360. data/bin/Image-ExifTool-9.33/t/CanonRaw_4.out +217 -0
  361. data/bin/Image-ExifTool-9.33/t/CanonRaw_5.out +207 -0
  362. data/bin/Image-ExifTool-9.33/t/CanonRaw_6.out +231 -0
  363. data/bin/Image-ExifTool-9.33/t/CanonRaw_7.out +247 -0
  364. data/bin/Image-ExifTool-9.33/t/CanonVRD.t +129 -0
  365. data/bin/Image-ExifTool-9.33/t/CanonVRD_11.out +118 -0
  366. data/bin/Image-ExifTool-9.33/t/CanonVRD_12.out +12 -0
  367. data/bin/Image-ExifTool-9.33/t/CanonVRD_2.out +116 -0
  368. data/bin/Image-ExifTool-9.33/t/CanonVRD_3.out +116 -0
  369. data/bin/Image-ExifTool-9.33/t/CanonVRD_4.out +2 -0
  370. data/bin/Image-ExifTool-9.33/t/CanonVRD_5.out +3 -0
  371. data/bin/Image-ExifTool-9.33/t/CanonVRD_6.out +3 -0
  372. data/bin/Image-ExifTool-9.33/t/CanonVRD_7.out +2 -0
  373. data/bin/Image-ExifTool-9.33/t/CanonVRD_8.out +2 -0
  374. data/bin/Image-ExifTool-9.33/t/CanonVRD_9.out +1 -0
  375. data/bin/Image-ExifTool-9.33/t/Canon_2.out +350 -0
  376. data/bin/Image-ExifTool-9.33/t/Canon_3.out +3 -0
  377. data/bin/Image-ExifTool-9.33/t/Casio.t +54 -0
  378. data/bin/Image-ExifTool-9.33/t/Casio_2.out +70 -0
  379. data/bin/Image-ExifTool-9.33/t/Casio_3.out +100 -0
  380. data/bin/Image-ExifTool-9.33/t/Casio_4.out +26 -0
  381. data/bin/Image-ExifTool-9.33/t/Casio_5.out +78 -0
  382. data/bin/Image-ExifTool-9.33/t/Casio_6.out +115 -0
  383. data/bin/Image-ExifTool-9.33/t/DICOM.t +28 -0
  384. data/bin/Image-ExifTool-9.33/t/DICOM_2.out +108 -0
  385. data/bin/Image-ExifTool-9.33/t/DNG.t +39 -0
  386. data/bin/Image-ExifTool-9.33/t/DNG_2.out +326 -0
  387. data/bin/Image-ExifTool-9.33/t/DNG_3.out +4 -0
  388. data/bin/Image-ExifTool-9.33/t/DV.t +27 -0
  389. data/bin/Image-ExifTool-9.33/t/DV_2.out +24 -0
  390. data/bin/Image-ExifTool-9.33/t/DjVu.t +28 -0
  391. data/bin/Image-ExifTool-9.33/t/DjVu_2.out +44 -0
  392. data/bin/Image-ExifTool-9.33/t/EXE.t +31 -0
  393. data/bin/Image-ExifTool-9.33/t/EXE_2.out +40 -0
  394. data/bin/Image-ExifTool-9.33/t/EXE_3.out +15 -0
  395. data/bin/Image-ExifTool-9.33/t/EXE_4.out +14 -0
  396. data/bin/Image-ExifTool-9.33/t/ExifTool.t +284 -0
  397. data/bin/Image-ExifTool-9.33/t/ExifTool_16.out +180 -0
  398. data/bin/Image-ExifTool-9.33/t/ExifTool_17.out +594 -0
  399. data/bin/Image-ExifTool-9.33/t/ExifTool_2.out +399 -0
  400. data/bin/Image-ExifTool-9.33/t/ExifTool_20.out +1 -0
  401. data/bin/Image-ExifTool-9.33/t/ExifTool_21.out +1 -0
  402. data/bin/Image-ExifTool-9.33/t/ExifTool_22.out +1 -0
  403. data/bin/Image-ExifTool-9.33/t/ExifTool_23.out +6 -0
  404. data/bin/Image-ExifTool-9.33/t/ExifTool_24.out +3 -0
  405. data/bin/Image-ExifTool-9.33/t/ExifTool_25.out +13 -0
  406. data/bin/Image-ExifTool-9.33/t/ExifTool_26.out +12 -0
  407. data/bin/Image-ExifTool-9.33/t/ExifTool_3.out +87 -0
  408. data/bin/Image-ExifTool-9.33/t/ExifTool_4.out +41 -0
  409. data/bin/Image-ExifTool-9.33/t/ExifTool_5.out +6 -0
  410. data/bin/Image-ExifTool-9.33/t/ExifTool_6.out +68 -0
  411. data/bin/Image-ExifTool-9.33/t/ExifTool_7.out +125 -0
  412. data/bin/Image-ExifTool-9.33/t/ExifTool_8.out +125 -0
  413. data/bin/Image-ExifTool-9.33/t/ExifTool_9.out +33 -0
  414. data/bin/Image-ExifTool-9.33/t/FLAC.t +37 -0
  415. data/bin/Image-ExifTool-9.33/t/FLAC_2.out +25 -0
  416. data/bin/Image-ExifTool-9.33/t/FLAC_3.out +19 -0
  417. data/bin/Image-ExifTool-9.33/t/FLIR.t +30 -0
  418. data/bin/Image-ExifTool-9.33/t/FLIR_2.out +104 -0
  419. data/bin/Image-ExifTool-9.33/t/FLIR_3.out +47 -0
  420. data/bin/Image-ExifTool-9.33/t/Flash.t +37 -0
  421. data/bin/Image-ExifTool-9.33/t/FlashPix.t +30 -0
  422. data/bin/Image-ExifTool-9.33/t/FlashPix_2.out +48 -0
  423. data/bin/Image-ExifTool-9.33/t/Flash_2.out +20 -0
  424. data/bin/Image-ExifTool-9.33/t/Flash_3.out +53 -0
  425. data/bin/Image-ExifTool-9.33/t/Font.t +30 -0
  426. data/bin/Image-ExifTool-9.33/t/Font_2.out +23 -0
  427. data/bin/Image-ExifTool-9.33/t/Font_3.out +35 -0
  428. data/bin/Image-ExifTool-9.33/t/Font_4.out +26 -0
  429. data/bin/Image-ExifTool-9.33/t/Font_5.out +26 -0
  430. data/bin/Image-ExifTool-9.33/t/Font_6.out +36 -0
  431. data/bin/Image-ExifTool-9.33/t/Font_7.out +36 -0
  432. data/bin/Image-ExifTool-9.33/t/FotoStation.t +38 -0
  433. data/bin/Image-ExifTool-9.33/t/FotoStation_2.out +39 -0
  434. data/bin/Image-ExifTool-9.33/t/FotoStation_3.out +3 -0
  435. data/bin/Image-ExifTool-9.33/t/FujiFilm.t +78 -0
  436. data/bin/Image-ExifTool-9.33/t/FujiFilm_2.out +87 -0
  437. data/bin/Image-ExifTool-9.33/t/FujiFilm_3.out +88 -0
  438. data/bin/Image-ExifTool-9.33/t/FujiFilm_4.out +117 -0
  439. data/bin/Image-ExifTool-9.33/t/FujiFilm_5.out +1 -0
  440. data/bin/Image-ExifTool-9.33/t/GE.t +46 -0
  441. data/bin/Image-ExifTool-9.33/t/GE_2.out +84 -0
  442. data/bin/Image-ExifTool-9.33/t/GE_3.out +84 -0
  443. data/bin/Image-ExifTool-9.33/t/GIF.t +83 -0
  444. data/bin/Image-ExifTool-9.33/t/GIF_2.out +40 -0
  445. data/bin/Image-ExifTool-9.33/t/GIF_3.out +41 -0
  446. data/bin/Image-ExifTool-9.33/t/GIF_4.out +16 -0
  447. data/bin/Image-ExifTool-9.33/t/GIMP.t +27 -0
  448. data/bin/Image-ExifTool-9.33/t/GIMP_2.out +63 -0
  449. data/bin/Image-ExifTool-9.33/t/GPS.t +42 -0
  450. data/bin/Image-ExifTool-9.33/t/GPS_2.out +94 -0
  451. data/bin/Image-ExifTool-9.33/t/GPS_3.out +96 -0
  452. data/bin/Image-ExifTool-9.33/t/GeoTiff.t +36 -0
  453. data/bin/Image-ExifTool-9.33/t/GeoTiff_2.out +36 -0
  454. data/bin/Image-ExifTool-9.33/t/GeoTiff_3.out +36 -0
  455. data/bin/Image-ExifTool-9.33/t/Geotag.t +164 -0
  456. data/bin/Image-ExifTool-9.33/t/Geotag_2.out +9 -0
  457. data/bin/Image-ExifTool-9.33/t/Geotag_3.out +6 -0
  458. data/bin/Image-ExifTool-9.33/t/Geotag_5.out +1 -0
  459. data/bin/Image-ExifTool-9.33/t/Geotag_6.out +9 -0
  460. data/bin/Image-ExifTool-9.33/t/Geotag_7.out +53 -0
  461. data/bin/Image-ExifTool-9.33/t/Geotag_8.out +15 -0
  462. data/bin/Image-ExifTool-9.33/t/HTML.t +28 -0
  463. data/bin/Image-ExifTool-9.33/t/HTML_2.out +68 -0
  464. data/bin/Image-ExifTool-9.33/t/IPTC.t +157 -0
  465. data/bin/Image-ExifTool-9.33/t/IPTC_2.out +58 -0
  466. data/bin/Image-ExifTool-9.33/t/IPTC_4.out +56 -0
  467. data/bin/Image-ExifTool-9.33/t/IPTC_5.out +1 -0
  468. data/bin/Image-ExifTool-9.33/t/IPTC_6.out +2 -0
  469. data/bin/Image-ExifTool-9.33/t/IPTC_7.out +1 -0
  470. data/bin/Image-ExifTool-9.33/t/IPTC_8.out +20 -0
  471. data/bin/Image-ExifTool-9.33/t/ITC.t +28 -0
  472. data/bin/Image-ExifTool-9.33/t/ITC_2.out +19 -0
  473. data/bin/Image-ExifTool-9.33/t/InDesign.t +61 -0
  474. data/bin/Image-ExifTool-9.33/t/InDesign_2.out +19 -0
  475. data/bin/Image-ExifTool-9.33/t/InDesign_3.out +21 -0
  476. data/bin/Image-ExifTool-9.33/t/InDesign_4.out +11 -0
  477. data/bin/Image-ExifTool-9.33/t/JVC.t +36 -0
  478. data/bin/Image-ExifTool-9.33/t/JVC_2.out +3 -0
  479. data/bin/Image-ExifTool-9.33/t/JVC_3.out +3 -0
  480. data/bin/Image-ExifTool-9.33/t/Jpeg2000.t +49 -0
  481. data/bin/Image-ExifTool-9.33/t/Jpeg2000_2.out +63 -0
  482. data/bin/Image-ExifTool-9.33/t/Jpeg2000_3.out +51 -0
  483. data/bin/Image-ExifTool-9.33/t/Jpeg2000_4.out +15 -0
  484. data/bin/Image-ExifTool-9.33/t/Kodak.t +40 -0
  485. data/bin/Image-ExifTool-9.33/t/Kodak_2.out +109 -0
  486. data/bin/Image-ExifTool-9.33/t/Kodak_3.out +119 -0
  487. data/bin/Image-ExifTool-9.33/t/KyoceraRaw.t +28 -0
  488. data/bin/Image-ExifTool-9.33/t/KyoceraRaw_2.out +27 -0
  489. data/bin/Image-ExifTool-9.33/t/LNK.t +28 -0
  490. data/bin/Image-ExifTool-9.33/t/LNK_2.out +45 -0
  491. data/bin/Image-ExifTool-9.33/t/Lang.t +40 -0
  492. data/bin/Image-ExifTool-9.33/t/Lang_1.out +1 -0
  493. data/bin/Image-ExifTool-9.33/t/Lang_10.out +46 -0
  494. data/bin/Image-ExifTool-9.33/t/Lang_11.out +46 -0
  495. data/bin/Image-ExifTool-9.33/t/Lang_12.out +46 -0
  496. data/bin/Image-ExifTool-9.33/t/Lang_13.out +46 -0
  497. data/bin/Image-ExifTool-9.33/t/Lang_14.out +46 -0
  498. data/bin/Image-ExifTool-9.33/t/Lang_15.out +46 -0
  499. data/bin/Image-ExifTool-9.33/t/Lang_16.out +46 -0
  500. data/bin/Image-ExifTool-9.33/t/Lang_17.out +46 -0
  501. data/bin/Image-ExifTool-9.33/t/Lang_18.out +46 -0
  502. data/bin/Image-ExifTool-9.33/t/Lang_2.out +46 -0
  503. data/bin/Image-ExifTool-9.33/t/Lang_3.out +46 -0
  504. data/bin/Image-ExifTool-9.33/t/Lang_4.out +46 -0
  505. data/bin/Image-ExifTool-9.33/t/Lang_5.out +46 -0
  506. data/bin/Image-ExifTool-9.33/t/Lang_6.out +46 -0
  507. data/bin/Image-ExifTool-9.33/t/Lang_7.out +46 -0
  508. data/bin/Image-ExifTool-9.33/t/Lang_8.out +46 -0
  509. data/bin/Image-ExifTool-9.33/t/Lang_9.out +46 -0
  510. data/bin/Image-ExifTool-9.33/t/M2TS.t +29 -0
  511. data/bin/Image-ExifTool-9.33/t/M2TS_2.out +27 -0
  512. data/bin/Image-ExifTool-9.33/t/MIE.t +82 -0
  513. data/bin/Image-ExifTool-9.33/t/MIE_2.out +67 -0
  514. data/bin/Image-ExifTool-9.33/t/MIE_3.out +134 -0
  515. data/bin/Image-ExifTool-9.33/t/MIE_5.out +1 -0
  516. data/bin/Image-ExifTool-9.33/t/MIE_6.out +1 -0
  517. data/bin/Image-ExifTool-9.33/t/MIFF.t +28 -0
  518. data/bin/Image-ExifTool-9.33/t/MIFF_2.out +108 -0
  519. data/bin/Image-ExifTool-9.33/t/MP3.t +29 -0
  520. data/bin/Image-ExifTool-9.33/t/MP3_2.out +45 -0
  521. data/bin/Image-ExifTool-9.33/t/MWG.t +72 -0
  522. data/bin/Image-ExifTool-9.33/t/MWG_2.out +13 -0
  523. data/bin/Image-ExifTool-9.33/t/MWG_3.out +8 -0
  524. data/bin/Image-ExifTool-9.33/t/MWG_4.out +5 -0
  525. data/bin/Image-ExifTool-9.33/t/MWG_5.out +22 -0
  526. data/bin/Image-ExifTool-9.33/t/MXF.t +27 -0
  527. data/bin/Image-ExifTool-9.33/t/MXF_2.out +78 -0
  528. data/bin/Image-ExifTool-9.33/t/Matroska.t +29 -0
  529. data/bin/Image-ExifTool-9.33/t/Matroska_2.out +64 -0
  530. data/bin/Image-ExifTool-9.33/t/Minolta.t +50 -0
  531. data/bin/Image-ExifTool-9.33/t/Minolta_2.out +133 -0
  532. data/bin/Image-ExifTool-9.33/t/Minolta_3.out +146 -0
  533. data/bin/Image-ExifTool-9.33/t/Minolta_4.out +148 -0
  534. data/bin/Image-ExifTool-9.33/t/Nikon.t +114 -0
  535. data/bin/Image-ExifTool-9.33/t/Nikon_2.out +82 -0
  536. data/bin/Image-ExifTool-9.33/t/Nikon_3.out +98 -0
  537. data/bin/Image-ExifTool-9.33/t/Nikon_4.out +174 -0
  538. data/bin/Image-ExifTool-9.33/t/Nikon_5.out +167 -0
  539. data/bin/Image-ExifTool-9.33/t/Nikon_7.out +260 -0
  540. data/bin/Image-ExifTool-9.33/t/Nikon_8.out +4 -0
  541. data/bin/Image-ExifTool-9.33/t/Olympus.t +85 -0
  542. data/bin/Image-ExifTool-9.33/t/Olympus_2.out +79 -0
  543. data/bin/Image-ExifTool-9.33/t/Olympus_3.out +81 -0
  544. data/bin/Image-ExifTool-9.33/t/Olympus_4.out +192 -0
  545. data/bin/Image-ExifTool-9.33/t/Olympus_5.out +264 -0
  546. data/bin/Image-ExifTool-9.33/t/Olympus_6.out +151 -0
  547. data/bin/Image-ExifTool-9.33/t/Olympus_7.out +482 -0
  548. data/bin/Image-ExifTool-9.33/t/OpenEXR.t +28 -0
  549. data/bin/Image-ExifTool-9.33/t/OpenEXR_2.out +23 -0
  550. data/bin/Image-ExifTool-9.33/t/PDF.t +295 -0
  551. data/bin/Image-ExifTool-9.33/t/PDF_10.out +10 -0
  552. data/bin/Image-ExifTool-9.33/t/PDF_11.out +10 -0
  553. data/bin/Image-ExifTool-9.33/t/PDF_12.out +9 -0
  554. data/bin/Image-ExifTool-9.33/t/PDF_14.out +5 -0
  555. data/bin/Image-ExifTool-9.33/t/PDF_15.out +6 -0
  556. data/bin/Image-ExifTool-9.33/t/PDF_16.out +4 -0
  557. data/bin/Image-ExifTool-9.33/t/PDF_17.out +4 -0
  558. data/bin/Image-ExifTool-9.33/t/PDF_18.out +5 -0
  559. data/bin/Image-ExifTool-9.33/t/PDF_19.out +6 -0
  560. data/bin/Image-ExifTool-9.33/t/PDF_2.out +117 -0
  561. data/bin/Image-ExifTool-9.33/t/PDF_20.out +4 -0
  562. data/bin/Image-ExifTool-9.33/t/PDF_22.out +3 -0
  563. data/bin/Image-ExifTool-9.33/t/PDF_4.out +12 -0
  564. data/bin/Image-ExifTool-9.33/t/PDF_5.out +8 -0
  565. data/bin/Image-ExifTool-9.33/t/PDF_6.out +9 -0
  566. data/bin/Image-ExifTool-9.33/t/PDF_7.out +11 -0
  567. data/bin/Image-ExifTool-9.33/t/PDF_8.out +9 -0
  568. data/bin/Image-ExifTool-9.33/t/PDF_9.out +9 -0
  569. data/bin/Image-ExifTool-9.33/t/PGF.t +28 -0
  570. data/bin/Image-ExifTool-9.33/t/PGF_2.out +32 -0
  571. data/bin/Image-ExifTool-9.33/t/PICT.t +28 -0
  572. data/bin/Image-ExifTool-9.33/t/PICT_2.out +15 -0
  573. data/bin/Image-ExifTool-9.33/t/PLIST.t +31 -0
  574. data/bin/Image-ExifTool-9.33/t/PLIST_2.out +20 -0
  575. data/bin/Image-ExifTool-9.33/t/PLIST_3.out +20 -0
  576. data/bin/Image-ExifTool-9.33/t/PNG.t +75 -0
  577. data/bin/Image-ExifTool-9.33/t/PNG_2.out +22 -0
  578. data/bin/Image-ExifTool-9.33/t/PNG_3.out +118 -0
  579. data/bin/Image-ExifTool-9.33/t/PNG_4.out +12 -0
  580. data/bin/Image-ExifTool-9.33/t/PPM.t +40 -0
  581. data/bin/Image-ExifTool-9.33/t/PPM_2.out +15 -0
  582. data/bin/Image-ExifTool-9.33/t/PPM_3.out +9 -0
  583. data/bin/Image-ExifTool-9.33/t/PSP.t +28 -0
  584. data/bin/Image-ExifTool-9.33/t/PSP_2.out +32 -0
  585. data/bin/Image-ExifTool-9.33/t/Panasonic.t +60 -0
  586. data/bin/Image-ExifTool-9.33/t/Panasonic_2.out +99 -0
  587. data/bin/Image-ExifTool-9.33/t/Panasonic_3.out +119 -0
  588. data/bin/Image-ExifTool-9.33/t/Panasonic_4.out +177 -0
  589. data/bin/Image-ExifTool-9.33/t/Panasonic_5.out +228 -0
  590. data/bin/Image-ExifTool-9.33/t/Pentax.t +50 -0
  591. data/bin/Image-ExifTool-9.33/t/Pentax_2.out +219 -0
  592. data/bin/Image-ExifTool-9.33/t/Pentax_3.out +262 -0
  593. data/bin/Image-ExifTool-9.33/t/Pentax_4.out +123 -0
  594. data/bin/Image-ExifTool-9.33/t/PhotoCD.t +28 -0
  595. data/bin/Image-ExifTool-9.33/t/PhotoCD_2.out +35 -0
  596. data/bin/Image-ExifTool-9.33/t/PhotoMechanic.t +38 -0
  597. data/bin/Image-ExifTool-9.33/t/PhotoMechanic_2.out +81 -0
  598. data/bin/Image-ExifTool-9.33/t/PhotoMechanic_3.out +2 -0
  599. data/bin/Image-ExifTool-9.33/t/Photoshop.t +42 -0
  600. data/bin/Image-ExifTool-9.33/t/Photoshop_2.out +96 -0
  601. data/bin/Image-ExifTool-9.33/t/Photoshop_3.out +108 -0
  602. data/bin/Image-ExifTool-9.33/t/PostScript.t +49 -0
  603. data/bin/Image-ExifTool-9.33/t/PostScript_2.out +64 -0
  604. data/bin/Image-ExifTool-9.33/t/PostScript_3.out +132 -0
  605. data/bin/Image-ExifTool-9.33/t/QuickTime.t +31 -0
  606. data/bin/Image-ExifTool-9.33/t/QuickTime_2.out +128 -0
  607. data/bin/Image-ExifTool-9.33/t/QuickTime_3.out +69 -0
  608. data/bin/Image-ExifTool-9.33/t/RIFF.t +31 -0
  609. data/bin/Image-ExifTool-9.33/t/RIFF_2.out +24 -0
  610. data/bin/Image-ExifTool-9.33/t/RIFF_3.out +52 -0
  611. data/bin/Image-ExifTool-9.33/t/RIFF_4.out +16 -0
  612. data/bin/Image-ExifTool-9.33/t/RTF.t +27 -0
  613. data/bin/Image-ExifTool-9.33/t/RTF_2.out +20 -0
  614. data/bin/Image-ExifTool-9.33/t/Radiance.t +28 -0
  615. data/bin/Image-ExifTool-9.33/t/Radiance_2.out +22 -0
  616. data/bin/Image-ExifTool-9.33/t/Real.t +46 -0
  617. data/bin/Image-ExifTool-9.33/t/Real_2.out +68 -0
  618. data/bin/Image-ExifTool-9.33/t/Real_3.out +18 -0
  619. data/bin/Image-ExifTool-9.33/t/Real_4.out +11 -0
  620. data/bin/Image-ExifTool-9.33/t/Ricoh.t +47 -0
  621. data/bin/Image-ExifTool-9.33/t/Ricoh_2.out +70 -0
  622. data/bin/Image-ExifTool-9.33/t/Ricoh_3.out +98 -0
  623. data/bin/Image-ExifTool-9.33/t/Ricoh_4.out +112 -0
  624. data/bin/Image-ExifTool-9.33/t/Sanyo.t +39 -0
  625. data/bin/Image-ExifTool-9.33/t/Sanyo_2.out +101 -0
  626. data/bin/Image-ExifTool-9.33/t/Sanyo_3.out +111 -0
  627. data/bin/Image-ExifTool-9.33/t/Sigma.t +60 -0
  628. data/bin/Image-ExifTool-9.33/t/Sigma_2.out +91 -0
  629. data/bin/Image-ExifTool-9.33/t/Sigma_3.out +94 -0
  630. data/bin/Image-ExifTool-9.33/t/Sigma_4.out +63 -0
  631. data/bin/Image-ExifTool-9.33/t/Sigma_5.out +192 -0
  632. data/bin/Image-ExifTool-9.33/t/Sony.t +62 -0
  633. data/bin/Image-ExifTool-9.33/t/Sony_2.out +84 -0
  634. data/bin/Image-ExifTool-9.33/t/Sony_3.out +85 -0
  635. data/bin/Image-ExifTool-9.33/t/Sony_5.out +32 -0
  636. data/bin/Image-ExifTool-9.33/t/TestLib.pm +417 -0
  637. data/bin/Image-ExifTool-9.33/t/Unknown.t +36 -0
  638. data/bin/Image-ExifTool-9.33/t/Unknown_2.out +90 -0
  639. data/bin/Image-ExifTool-9.33/t/Unknown_3.out +90 -0
  640. data/bin/Image-ExifTool-9.33/t/Vorbis.t +28 -0
  641. data/bin/Image-ExifTool-9.33/t/Vorbis_2.out +28 -0
  642. data/bin/Image-ExifTool-9.33/t/Writer.t +913 -0
  643. data/bin/Image-ExifTool-9.33/t/Writer_10.out +240 -0
  644. data/bin/Image-ExifTool-9.33/t/Writer_11.out +37 -0
  645. data/bin/Image-ExifTool-9.33/t/Writer_13.out +160 -0
  646. data/bin/Image-ExifTool-9.33/t/Writer_14.out +67 -0
  647. data/bin/Image-ExifTool-9.33/t/Writer_15.out +171 -0
  648. data/bin/Image-ExifTool-9.33/t/Writer_16.out +1 -0
  649. data/bin/Image-ExifTool-9.33/t/Writer_17.out +1 -0
  650. data/bin/Image-ExifTool-9.33/t/Writer_18.out +3 -0
  651. data/bin/Image-ExifTool-9.33/t/Writer_19.out +34 -0
  652. data/bin/Image-ExifTool-9.33/t/Writer_2.out +168 -0
  653. data/bin/Image-ExifTool-9.33/t/Writer_22.out +4 -0
  654. data/bin/Image-ExifTool-9.33/t/Writer_24.out +1 -0
  655. data/bin/Image-ExifTool-9.33/t/Writer_25.out +38 -0
  656. data/bin/Image-ExifTool-9.33/t/Writer_26.out +32 -0
  657. data/bin/Image-ExifTool-9.33/t/Writer_27.out +14 -0
  658. data/bin/Image-ExifTool-9.33/t/Writer_28.out +1 -0
  659. data/bin/Image-ExifTool-9.33/t/Writer_29.out +2 -0
  660. data/bin/Image-ExifTool-9.33/t/Writer_30.out +2 -0
  661. data/bin/Image-ExifTool-9.33/t/Writer_31.out +97 -0
  662. data/bin/Image-ExifTool-9.33/t/Writer_32.out +3 -0
  663. data/bin/Image-ExifTool-9.33/t/Writer_33.out +3 -0
  664. data/bin/Image-ExifTool-9.33/t/Writer_34.out +3 -0
  665. data/bin/Image-ExifTool-9.33/t/Writer_35.out +187 -0
  666. data/bin/Image-ExifTool-9.33/t/Writer_36.out +2 -0
  667. data/bin/Image-ExifTool-9.33/t/Writer_37.out +2 -0
  668. data/bin/Image-ExifTool-9.33/t/Writer_38.out +62 -0
  669. data/bin/Image-ExifTool-9.33/t/Writer_39.out +4 -0
  670. data/bin/Image-ExifTool-9.33/t/Writer_4.out +85 -0
  671. data/bin/Image-ExifTool-9.33/t/Writer_40.out +4 -0
  672. data/bin/Image-ExifTool-9.33/t/Writer_41.out +3 -0
  673. data/bin/Image-ExifTool-9.33/t/Writer_42.out +5 -0
  674. data/bin/Image-ExifTool-9.33/t/Writer_43.out +5 -0
  675. data/bin/Image-ExifTool-9.33/t/Writer_44.out +2 -0
  676. data/bin/Image-ExifTool-9.33/t/Writer_45.out +1 -0
  677. data/bin/Image-ExifTool-9.33/t/Writer_46.out +77 -0
  678. data/bin/Image-ExifTool-9.33/t/Writer_47.out +56 -0
  679. data/bin/Image-ExifTool-9.33/t/Writer_48.out +29 -0
  680. data/bin/Image-ExifTool-9.33/t/Writer_50.out +3 -0
  681. data/bin/Image-ExifTool-9.33/t/Writer_51.out +386 -0
  682. data/bin/Image-ExifTool-9.33/t/Writer_6.out +182 -0
  683. data/bin/Image-ExifTool-9.33/t/Writer_7.out +149 -0
  684. data/bin/Image-ExifTool-9.33/t/Writer_9.out +237 -0
  685. data/bin/Image-ExifTool-9.33/t/XMP.t +521 -0
  686. data/bin/Image-ExifTool-9.33/t/XMP_10.out +33 -0
  687. data/bin/Image-ExifTool-9.33/t/XMP_11.out +59 -0
  688. data/bin/Image-ExifTool-9.33/t/XMP_12.out +4 -0
  689. data/bin/Image-ExifTool-9.33/t/XMP_13.out +5 -0
  690. data/bin/Image-ExifTool-9.33/t/XMP_14.out +3 -0
  691. data/bin/Image-ExifTool-9.33/t/XMP_15.out +3 -0
  692. data/bin/Image-ExifTool-9.33/t/XMP_16.out +5 -0
  693. data/bin/Image-ExifTool-9.33/t/XMP_17.out +6 -0
  694. data/bin/Image-ExifTool-9.33/t/XMP_18.out +10 -0
  695. data/bin/Image-ExifTool-9.33/t/XMP_19.out +35 -0
  696. data/bin/Image-ExifTool-9.33/t/XMP_2.out +138 -0
  697. data/bin/Image-ExifTool-9.33/t/XMP_20.out +35 -0
  698. data/bin/Image-ExifTool-9.33/t/XMP_21.out +38 -0
  699. data/bin/Image-ExifTool-9.33/t/XMP_22.out +38 -0
  700. data/bin/Image-ExifTool-9.33/t/XMP_23.out +9 -0
  701. data/bin/Image-ExifTool-9.33/t/XMP_24.out +31 -0
  702. data/bin/Image-ExifTool-9.33/t/XMP_25.out +28 -0
  703. data/bin/Image-ExifTool-9.33/t/XMP_26.out +52 -0
  704. data/bin/Image-ExifTool-9.33/t/XMP_27.out +93 -0
  705. data/bin/Image-ExifTool-9.33/t/XMP_28.out +44 -0
  706. data/bin/Image-ExifTool-9.33/t/XMP_29.out +24 -0
  707. data/bin/Image-ExifTool-9.33/t/XMP_3.out +136 -0
  708. data/bin/Image-ExifTool-9.33/t/XMP_30.out +90 -0
  709. data/bin/Image-ExifTool-9.33/t/XMP_31.out +19 -0
  710. data/bin/Image-ExifTool-9.33/t/XMP_32.out +2 -0
  711. data/bin/Image-ExifTool-9.33/t/XMP_34.out +2 -0
  712. data/bin/Image-ExifTool-9.33/t/XMP_36.out +18 -0
  713. data/bin/Image-ExifTool-9.33/t/XMP_37.out +35 -0
  714. data/bin/Image-ExifTool-9.33/t/XMP_39.out +44 -0
  715. data/bin/Image-ExifTool-9.33/t/XMP_40.out +3 -0
  716. data/bin/Image-ExifTool-9.33/t/XMP_41.out +175 -0
  717. data/bin/Image-ExifTool-9.33/t/XMP_5.out +29 -0
  718. data/bin/Image-ExifTool-9.33/t/XMP_6.out +87 -0
  719. data/bin/Image-ExifTool-9.33/t/XMP_7.out +118 -0
  720. data/bin/Image-ExifTool-9.33/t/XMP_8.out +17 -0
  721. data/bin/Image-ExifTool-9.33/t/XMP_9.out +36 -0
  722. data/bin/Image-ExifTool-9.33/t/ZIP.t +69 -0
  723. data/bin/Image-ExifTool-9.33/t/ZIP_2.out +18 -0
  724. data/bin/Image-ExifTool-9.33/t/ZIP_3.out +17 -0
  725. data/bin/Image-ExifTool-9.33/t/ZIP_4.out +213 -0
  726. data/bin/Image-ExifTool-9.33/t/ZIP_5.out +134 -0
  727. data/bin/Image-ExifTool-9.33/t/ZIP_6.out +49 -0
  728. data/bin/Image-ExifTool-9.33/t/ZIP_7.out +28 -0
  729. data/bin/Image-ExifTool-9.33/t/images/AFCP.jpg +0 -0
  730. data/bin/Image-ExifTool-9.33/t/images/AIFF.aif +0 -0
  731. data/bin/Image-ExifTool-9.33/t/images/APE.ape +0 -0
  732. data/bin/Image-ExifTool-9.33/t/images/APE.mpc +0 -0
  733. data/bin/Image-ExifTool-9.33/t/images/ASF.wmv +0 -0
  734. data/bin/Image-ExifTool-9.33/t/images/BMP.bmp +0 -0
  735. data/bin/Image-ExifTool-9.33/t/images/BigTIFF.btf +0 -0
  736. data/bin/Image-ExifTool-9.33/t/images/Canon.jpg +0 -0
  737. data/bin/Image-ExifTool-9.33/t/images/Canon1DmkIII.jpg +0 -0
  738. data/bin/Image-ExifTool-9.33/t/images/CanonRaw.cr2 +0 -0
  739. data/bin/Image-ExifTool-9.33/t/images/CanonRaw.crw +0 -0
  740. data/bin/Image-ExifTool-9.33/t/images/CanonVRD.vrd +0 -0
  741. data/bin/Image-ExifTool-9.33/t/images/CaptureOne.eip +0 -0
  742. data/bin/Image-ExifTool-9.33/t/images/Casio.jpg +0 -0
  743. data/bin/Image-ExifTool-9.33/t/images/Casio2.jpg +0 -0
  744. data/bin/Image-ExifTool-9.33/t/images/CasioQVCI.jpg +0 -0
  745. data/bin/Image-ExifTool-9.33/t/images/DICOM.dcm +0 -0
  746. data/bin/Image-ExifTool-9.33/t/images/DNG.dng +0 -0
  747. data/bin/Image-ExifTool-9.33/t/images/DV.dv +0 -0
  748. data/bin/Image-ExifTool-9.33/t/images/DjVu.djvu +0 -0
  749. data/bin/Image-ExifTool-9.33/t/images/EXE.elf +0 -0
  750. data/bin/Image-ExifTool-9.33/t/images/EXE.exe +0 -0
  751. data/bin/Image-ExifTool-9.33/t/images/EXE.macho +0 -0
  752. data/bin/Image-ExifTool-9.33/t/images/ExifTool.jpg +0 -0
  753. data/bin/Image-ExifTool-9.33/t/images/ExifTool.tif +0 -0
  754. data/bin/Image-ExifTool-9.33/t/images/ExtendedXMP.jpg +0 -0
  755. data/bin/Image-ExifTool-9.33/t/images/FLAC.flac +0 -0
  756. data/bin/Image-ExifTool-9.33/t/images/FLAC.ogg +0 -0
  757. data/bin/Image-ExifTool-9.33/t/images/FLIR.fpf +0 -0
  758. data/bin/Image-ExifTool-9.33/t/images/FLIR.jpg +0 -0
  759. data/bin/Image-ExifTool-9.33/t/images/Flash.flv +0 -0
  760. data/bin/Image-ExifTool-9.33/t/images/Flash.swf +0 -0
  761. data/bin/Image-ExifTool-9.33/t/images/FlashPix.ppt +0 -0
  762. data/bin/Image-ExifTool-9.33/t/images/Font.afm +28 -0
  763. data/bin/Image-ExifTool-9.33/t/images/Font.dfont +0 -0
  764. data/bin/Image-ExifTool-9.33/t/images/Font.pfa +38 -0
  765. data/bin/Image-ExifTool-9.33/t/images/Font.pfb +0 -0
  766. data/bin/Image-ExifTool-9.33/t/images/Font.pfm +0 -0
  767. data/bin/Image-ExifTool-9.33/t/images/Font.ttf +0 -0
  768. data/bin/Image-ExifTool-9.33/t/images/FotoStation.jpg +0 -0
  769. data/bin/Image-ExifTool-9.33/t/images/FujiFilm.jpg +0 -0
  770. data/bin/Image-ExifTool-9.33/t/images/FujiFilm.raf +0 -0
  771. data/bin/Image-ExifTool-9.33/t/images/GE.jpg +0 -0
  772. data/bin/Image-ExifTool-9.33/t/images/GIF.gif +0 -0
  773. data/bin/Image-ExifTool-9.33/t/images/GIMP.xcf +0 -0
  774. data/bin/Image-ExifTool-9.33/t/images/GPS.jpg +0 -0
  775. data/bin/Image-ExifTool-9.33/t/images/GeoTiff.tif +0 -0
  776. data/bin/Image-ExifTool-9.33/t/images/Geotag.gpx +23 -0
  777. data/bin/Image-ExifTool-9.33/t/images/Geotag.igc +24 -0
  778. data/bin/Image-ExifTool-9.33/t/images/Geotag.log +13 -0
  779. data/bin/Image-ExifTool-9.33/t/images/Geotag.xml +23 -0
  780. data/bin/Image-ExifTool-9.33/t/images/Geotag2.log +7 -0
  781. data/bin/Image-ExifTool-9.33/t/images/HTML.html +77 -0
  782. data/bin/Image-ExifTool-9.33/t/images/IPTC.jpg +0 -0
  783. data/bin/Image-ExifTool-9.33/t/images/ITC.itc +0 -0
  784. data/bin/Image-ExifTool-9.33/t/images/InDesign.indd +0 -0
  785. data/bin/Image-ExifTool-9.33/t/images/JVC.jpg +0 -0
  786. data/bin/Image-ExifTool-9.33/t/images/JVC2.jpg +0 -0
  787. data/bin/Image-ExifTool-9.33/t/images/Jpeg2000.j2c +0 -0
  788. data/bin/Image-ExifTool-9.33/t/images/Jpeg2000.jp2 +0 -0
  789. data/bin/Image-ExifTool-9.33/t/images/Kodak.jpg +0 -0
  790. data/bin/Image-ExifTool-9.33/t/images/KyoceraRaw.raw +0 -0
  791. data/bin/Image-ExifTool-9.33/t/images/LNK.lnk +0 -0
  792. data/bin/Image-ExifTool-9.33/t/images/M2TS.mts +0 -0
  793. data/bin/Image-ExifTool-9.33/t/images/MIE.mie +0 -0
  794. data/bin/Image-ExifTool-9.33/t/images/MIFF.miff +0 -0
  795. data/bin/Image-ExifTool-9.33/t/images/MP3.mp3 +0 -0
  796. data/bin/Image-ExifTool-9.33/t/images/MWG.jpg +0 -0
  797. data/bin/Image-ExifTool-9.33/t/images/MXF.mxf +0 -0
  798. data/bin/Image-ExifTool-9.33/t/images/Matroska.mkv +0 -0
  799. data/bin/Image-ExifTool-9.33/t/images/Minolta.jpg +0 -0
  800. data/bin/Image-ExifTool-9.33/t/images/Minolta.mrw +0 -0
  801. data/bin/Image-ExifTool-9.33/t/images/Nikon.jpg +0 -0
  802. data/bin/Image-ExifTool-9.33/t/images/Nikon.nef +0 -0
  803. data/bin/Image-ExifTool-9.33/t/images/NikonD2Hs.jpg +0 -0
  804. data/bin/Image-ExifTool-9.33/t/images/NikonD70.jpg +0 -0
  805. data/bin/Image-ExifTool-9.33/t/images/OOXML.docx +0 -0
  806. data/bin/Image-ExifTool-9.33/t/images/Olympus.jpg +0 -0
  807. data/bin/Image-ExifTool-9.33/t/images/Olympus2.jpg +0 -0
  808. data/bin/Image-ExifTool-9.33/t/images/OlympusE1.jpg +0 -0
  809. data/bin/Image-ExifTool-9.33/t/images/OpenDoc.ods +0 -0
  810. data/bin/Image-ExifTool-9.33/t/images/OpenEXR.exr +0 -0
  811. data/bin/Image-ExifTool-9.33/t/images/PDF.pdf +0 -0
  812. data/bin/Image-ExifTool-9.33/t/images/PDF2.pdf +0 -0
  813. data/bin/Image-ExifTool-9.33/t/images/PGF.pgf +0 -0
  814. data/bin/Image-ExifTool-9.33/t/images/PICT.pict +0 -0
  815. data/bin/Image-ExifTool-9.33/t/images/PLIST-bin.plist +0 -0
  816. data/bin/Image-ExifTool-9.33/t/images/PLIST-xml.plist +35 -0
  817. data/bin/Image-ExifTool-9.33/t/images/PNG.png +0 -0
  818. data/bin/Image-ExifTool-9.33/t/images/PPM.ppm +5 -0
  819. data/bin/Image-ExifTool-9.33/t/images/PSP.psp +0 -0
  820. data/bin/Image-ExifTool-9.33/t/images/Panasonic.jpg +0 -0
  821. data/bin/Image-ExifTool-9.33/t/images/Panasonic.rw2 +0 -0
  822. data/bin/Image-ExifTool-9.33/t/images/Pentax.avi +0 -0
  823. data/bin/Image-ExifTool-9.33/t/images/Pentax.jpg +0 -0
  824. data/bin/Image-ExifTool-9.33/t/images/PhotoCD.pcd +0 -0
  825. data/bin/Image-ExifTool-9.33/t/images/PhotoMechanic.jpg +0 -0
  826. data/bin/Image-ExifTool-9.33/t/images/Photoshop.psd +0 -0
  827. data/bin/Image-ExifTool-9.33/t/images/PostScript.eps +108 -0
  828. data/bin/Image-ExifTool-9.33/t/images/QuickTime.m4a +0 -0
  829. data/bin/Image-ExifTool-9.33/t/images/QuickTime.mov +0 -0
  830. data/bin/Image-ExifTool-9.33/t/images/RIFF.avi +0 -0
  831. data/bin/Image-ExifTool-9.33/t/images/RIFF.wav +0 -0
  832. data/bin/Image-ExifTool-9.33/t/images/RIFF.webp +0 -0
  833. data/bin/Image-ExifTool-9.33/t/images/RTF.rtf +25 -0
  834. data/bin/Image-ExifTool-9.33/t/images/Radiance.hdr +0 -0
  835. data/bin/Image-ExifTool-9.33/t/images/Real.ra +0 -0
  836. data/bin/Image-ExifTool-9.33/t/images/Real.ram +1 -0
  837. data/bin/Image-ExifTool-9.33/t/images/Real.rm +0 -0
  838. data/bin/Image-ExifTool-9.33/t/images/Ricoh.jpg +0 -0
  839. data/bin/Image-ExifTool-9.33/t/images/Ricoh2.jpg +0 -0
  840. data/bin/Image-ExifTool-9.33/t/images/Sanyo.jpg +0 -0
  841. data/bin/Image-ExifTool-9.33/t/images/Sigma.jpg +0 -0
  842. data/bin/Image-ExifTool-9.33/t/images/Sigma.x3f +0 -0
  843. data/bin/Image-ExifTool-9.33/t/images/SigmaDP2.x3f +0 -0
  844. data/bin/Image-ExifTool-9.33/t/images/Sony.jpg +0 -0
  845. data/bin/Image-ExifTool-9.33/t/images/Sony.pmp +0 -0
  846. data/bin/Image-ExifTool-9.33/t/images/Unknown.jpg +0 -0
  847. data/bin/Image-ExifTool-9.33/t/images/Vorbis.ogg +0 -0
  848. data/bin/Image-ExifTool-9.33/t/images/Writer.jpg +0 -0
  849. data/bin/Image-ExifTool-9.33/t/images/XMP.inx +108 -0
  850. data/bin/Image-ExifTool-9.33/t/images/XMP.jpg +0 -0
  851. data/bin/Image-ExifTool-9.33/t/images/XMP.svg +33 -0
  852. data/bin/Image-ExifTool-9.33/t/images/XMP.xml +98 -0
  853. data/bin/Image-ExifTool-9.33/t/images/XMP.xmp +99 -0
  854. data/bin/Image-ExifTool-9.33/t/images/XMP2.xmp +25 -0
  855. data/bin/Image-ExifTool-9.33/t/images/XMP3.xmp +43 -0
  856. data/bin/Image-ExifTool-9.33/t/images/XMP4.xmp +93 -0
  857. data/bin/Image-ExifTool-9.33/t/images/XMP5.xmp +158 -0
  858. data/bin/Image-ExifTool-9.33/t/images/ZIP.gz +0 -0
  859. data/bin/Image-ExifTool-9.33/t/images/ZIP.zip +0 -0
  860. data/bin/Image-ExifTool-9.33/t/images/iWork.numbers +0 -0
  861. data/lib/exiftool_vendored.rb +10 -0
  862. data/lib/exiftool_vendored/version.rb +3 -0
  863. data/lib/exiftool_vendored/version_extractor.rb +17 -0
  864. metadata +977 -0
data/bin/Image-ExifTool-9.33/html/faq.html ADDED
@@ -0,0 +1,1434 @@
1
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2
+ "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
3
+ <html>
4
+ <head>
5
+ <title>ExifTool FAQ</title>
6
+ <link rel=stylesheet type='text/css' href='style.css' title='Style'>
7
+ <style type="text/css">
8
+ <!--
9
+ pre { color: #800; margin-left: 2em }
10
+ ol.index { margin: 0; padding: 0 0 0 2em }
11
+ .U { color: #c84 } /* unused data block */
12
+ .prog { padding: 0.5em; border: 1px solid gray; background: #fee }
13
+ -->
14
+ </style>
15
+ </head>
16
+ <body>
17
+ <div class='index'>
18
+ <ol class='index'>
19
+ <li><a href="#Q1">Discussion forum</a></li>
20
+ <li><a href="#Q2">Determining tag names</a></li>
21
+ <li><a href="#Q3">ExifTool doesn't read/write properly</a></li>
22
+ <li><a href="#Q4">Aperture and shutter speed</a></li>
23
+ <li><a href="#Q5">Date and time formats</a></li>
24
+ <li><a href="#Q6">"Can't convert TAG" errors</a></li>
25
+ <li><a href="#Q7">Deleting all EXIF from a TIFF</a></li>
26
+ <li><a href="#Q8">Writing Make, Model &amp; MakerNotes</a></li>
27
+ <li><a href="#Q9">Tag locations when copying</a></li>
28
+ <li><a href="#Q10">Coded character sets</a></li>
29
+ <li><a href="#Q11">User-defined tags</a></li>
30
+ <li><a href="#Q12">Export to database</a></li>
31
+ <li><a href="#Q13">Output file size</a></li>
32
+ <li><a href="#Q14">GPS coordinate format</a></li>
33
+ <li><a href="#Q15">MakerNote errors</a></li>
34
+ <li><a href="#Q16">Some files not renamed</a></li>
35
+ <li><a href="#Q17">List-type tags</a></li>
36
+ <li><a href="#Q18">Windows character encoding</a></li>
37
+ <li><a href="#Q19">Formatting tag values</a></li>
38
+ <li><a href="#Q20">Write errors (repair corrupted EXIF)</a></li>
39
+ <li><a href="#Q21">Newlines in values</a></li>
40
+ <li><a href="#Q22">Order of operations</a></li>
41
+ <li><a href="#Q23">"0 image files updated"</a></li>
42
+ <li><a href="#Q24">Date/time gets reset to today</a></li>
43
+ <li><a href="#Q25">Image validation</a></li>
44
+ </ol>
45
+ </div>
46
+
47
+ <h1 class='up'>ExifTool FAQ</h1>
48
+
49
+ <a name="Q1"></a>
50
+ <p>1. <b>"Is there a forum for discussing ExifTool issues?"</b></p>
51
+
52
+ <blockquote>
53
+ ExifTool issues can be discussed on the ExifTool forum at
54
+ <a href="http://u88.n24.queensu.ca/exiftool/forum/">http://u88.n24.queensu.ca/exiftool/forum/</a>
55
+ </blockquote>
56
+
57
+ <a name="Q2"></a>
58
+ <p>2. <b>"How do I determine the tag name for some information?"</b></p>
59
+
60
+ <blockquote>When you run exiftool, by default it prints descriptions, not tag
61
+ names, for the information it extracts. These descriptions are in English
62
+ unless the <code>-lang</code> option is used to select another language. Note
63
+ that descriptions often contain spaces between words but tag names never do. To
64
+ print the tag names instead instead of descriptions, use the <code>-s</code>
65
+ option when extracting information. Valid characters in tag names are
66
+ <code>A-Z</code>, <code>a-z</code>, <code>0-9</code>, <code>_</code> and
67
+ <code>-</code>. See the <a href="TagNames/index.html">tag name
68
+ documentation</a> for a complete list of available tag names.</blockquote>
69
+
70
+ <blockquote>Tag names may be optionally prefixed by a family 0 or 1 group name
71
+ to specify a particular information type or location. Use the
72
+ <code>-g0</code> and <code>-g1</code> (or
73
+ <code>-G0</code> and <code>-G1</code>) options when extracting
74
+ information to see the corresponding group names.
75
+ </blockquote>
76
+
77
+ <a name="Q3"></a>
78
+ <p>3a. <b>"ExifTool reports the wrong value or doesn't extract a tag"</b>,
79
+ <br>3b. <b>"ExifTool doesn't write a tag properly"</b>, or
80
+ <br>3c. <b>"Other software can't read information written by ExifTool"</b></p>
81
+
82
+ <blockquote><i>[Also see <a href="#Q23">FAQ number 23</a> for reasons why
83
+ ExifTool may not write some tags to certain file types.]</i></blockquote>
84
+
85
+ <blockquote>First, make sure you are looking at the right information. Use
86
+ ExifTool with a command like this to extract all information from the file,
87
+ along with the location it was written:
88
+
89
+ <pre>exiftool -a -G1 -s c:\images\test.jpg</pre>
90
+
91
+ In this command, <code>-a</code> allows duplicate tags to be extracted,
92
+ <code>-G1</code> shows the family 1 group name (ie. the location) of each tag,
93
+ and <code>-s</code> shows the tag names instead of their descriptions.
94
+ (Substitute the path name of your file in place of
95
+ "<code>c:\images\test.jpg</code>".)</blockquote>
96
+
97
+ <blockquote>When duplicate tags exist, only one is extracted unless the
98
+ <code>-a</code> option is used. Beware that options like <code>-EXIF:all</code>
99
+ select all EXIF tags from the extracted tags, so EXIF tags hidden by duplicate
100
+ tags in other locations will not appear in the output for
101
+ <code>-EXIF:all</code>. For example, the command
102
+
103
+ <pre>exiftool -gps:all image.jpg</pre>
104
+
105
+ will NOT necessarily extract all GPS tags because some GPS tags may have been
106
+ suppressed by same-named tags in other groups. To be sure all GPS tags are
107
+ extracted, the <code>-a</code> option must be used:
108
+
109
+ <pre>exiftool -a -gps:all image.jpg</pre>
110
+
111
+ If you are having problems with other software reading information written by
112
+ ExifTool, if possible try first writing the information from the other software,
113
+ then use ExifTool (with the <code>-a</code> and <code>-G1</code> options) to
114
+ determine where the information was written. Once you know where it should go,
115
+ you can use ExifTool to write to this location. You can read or write
116
+ information in a specific location by prefixing the tag name on the command line
117
+ with the desired group name. ie) "<code>-ExifIFD:DateTimeOriginal</code>"
118
+ </blockquote>
119
+
120
+ <blockquote>This problem may also occur if contradictory information exists in
121
+ different meta information formats within the same file. For example, often XMP
122
+ will be ignored if IPTC exists and the Photoshop:IPTCDigest does not agree with
123
+ the IPTC content. The
124
+ <a href="http://www.metadataworkinggroup.org/">Metadata Working Group</a>
125
+ recommends techniques to keep the EXIF, IPTC and XMP metadata synchronized.
126
+ These recommendations are implemented by the ExifTool
127
+ <a href="TagNames/MWG.html">MWG tags</a>. For maximum compatibility with the
128
+ widest range of applications, it is suggested that these MWG tags be used
129
+ whenever possible.</blockquote>
130
+
131
+ <blockquote>One final note: When writing, the <code>-v2</code> option may be
132
+ useful because it provides details about what ExifTool is writing, and where.
133
+ </blockquote>
134
+
135
+ <a name="Q4"></a>
136
+ <p>4. <b>"ExifTool reports more than one shutter speed or aperture value, and
137
+ they are slightly different"</b></p>
138
+
139
+ <blockquote>
140
+ There are a number of different ways that aperture and shutter speed information
141
+ are stored in many images. The standard EXIF values (EXIF:FNumber and
142
+ EXIF:ExposureTime) should correspond to the values displayed by your camera,
143
+ but these values may have been rounded off. The corresponding EXIF APEX
144
+ values (EXIF:ApertureValue and EXIF:ShutterSpeedValue) may be different due
145
+ to their own round-off errors. If available, the MakerNotes values may be
146
+ the most accurate because they haven't been rounded off to nice even values
147
+ for display, so with these you may see odd values like 1/102 instead of
148
+ 1/100, etc.
149
+ </blockquote>
150
+
151
+ <a name="Q5"></a>
152
+ <p>5. <b>"How do I format date and time information for writing?"</b></p>
153
+
154
+ <blockquote>All information (including date/time information) is written in the
155
+ same format as it is read out. When reading, ExifTool converts all date and
156
+ time information to standard EXIF format, so this is also the way it is
157
+ specified when writing. The standard EXIF date/time format is
158
+ "<code>YYYY:mm:dd HH:MM:SS</code>", and some meta information formats such as
159
+ XMP also allow sub-seconds and a timezone to be specified. The timezone format
160
+ is "<code>+HH:MM</code>", "<code>-HH:MM</code>" or "<code>Z</code>". For
161
+ example:
162
+
163
+ <pre>exiftool -xmp:dateTimeOriginal="2005:10:23 20:06:34.33-05:00" a.jpg
164
+ </pre>
165
+
166
+ When writing XMP or other information types which allow incomplete date/time
167
+ values, the following input formats are also accepted:
168
+
169
+ <pre>YYYY
170
+ YYYY:mm
171
+ YYYY:mm:dd
172
+ YYYY:mm:dd HH:MM
173
+ </pre>
174
+
175
+ Having said this, ExifTool is very flexible about the actual format of input
176
+ date/time values when writing, and will attempt to reformat any values into the
177
+ standard format unless the <code>-n</code> option is used. Any separators may
178
+ be used (or in fact, none at all). The first 4 consecutive digits found in the
179
+ value are interpreted as the year, then next 2 digits are the month, and so on.
180
+ <i class=lt>[The year must be 4 digits. Other fields are expected to be 2
181
+ digits, but a single digit is allowed if the subsequent character is a
182
+ non-digit.]</i> For EXIF date/time values, all 6 date/time fields must exist
183
+ ("<code>YYYYmmddHHMMSS</code>"), but XMP date/time values require only the year
184
+ ("<code>YYYY</code>"). This feature facilitates useful operations such as
185
+ setting date/time tags from a date embedded in the file name. For example, the
186
+ command
187
+
188
+ <pre>exiftool "-alldates&lt;filename" c:\images</pre>
189
+
190
+ will set the common date/time tags from the file name for all images in the
191
+ directory "<code>c:\images</code>". This will work for any file name which
192
+ matches the above criteria (ie. "IMG_20110927_103000.jpg").
193
+ <i class=lt>[AllDates is a shortcut for 3 tag names: DateTimeOriginal,
194
+ CreateDate and ModifyDate. See the <a href="TagNames/Shortcuts.html">Shortcuts
195
+ Tags documentation</a> for more information.]</i></blockquote>
196
+
197
+ <blockquote>The <code>-d</code> option allows full control over the format of
198
+ date/time values when reading. However, the effect of the <code>-d</code>
199
+ option is not reversible, so date/time values must be written using the format
200
+ described above, even when the <code>-d</code> option is used. Note that when
201
+ reading, the effect of the <code>-n</code> option on date/time values is only to
202
+ disable the <code>-d</code> formatting.</blockquote>
203
+
204
+ <blockquote><b>Special feature</b>: A value of "<code>now</code>" may be used to
205
+ represent the current time when writing any date/time tag. For example:
206
+ <pre>exiftool -xmp:dateTimeOriginal=now a.jpg</pre>
207
+ <i class=lt>[There is also a <a href="TagNames/Extra.html">Now tag</a> which may
208
+ be used for a similar purpose by copying its value to another tag, but copying
209
+ tags adds an extra read stage to the processing which is best avoided if
210
+ performance is an issue.]</i>
211
+ </blockquote>
212
+
213
+ <a name="Q6"></a>
214
+ <p>6. <b>"I get '<code>Can't convert TAG (not in PrintConv)</code>' errors when
215
+ writing a tag"</b></p>
216
+
217
+ <blockquote>
218
+ By default, ExifTool applies a print conversion (PrintConv) to extracted
219
+ information to make the output more human-readable. Some conversions involve
220
+ lookup tables which are documented in the <b>Values</b> column of the
221
+ <a href="TagNames/index.html">tag name documentation</a>. For example, the
222
+ GPSAltitudeRef tag defines the following conversions:
223
+ <pre>0 = Above Sea Level
224
+ 1 = Below Sea Level
225
+ </pre>
226
+ For this tag, a value of '0' is printed as 'Above Sea Level', and '1' is printed
227
+ as 'Below Sea Level'. Reading and writing with ExifTool is symmetrical <i>[with
228
+ the possible exception of list-type tags -- see <a href="#Q17">FAQ number 17</a>
229
+ below]</i>, so a value that is printed as 'Above Sea Level' must also be written in
230
+ that form. (In other words, the inverse print conversion is applied when writing
231
+ values.) For example, to write GPSAltitudeRef you can type:
232
+ <pre>exiftool -gpsaltituderef="Above Sea Level" image.jpg
233
+ </pre>
234
+ or any unambiguous short form may be used and ExifTool will know what you mean, ie)
235
+ <pre>exiftool -gpsaltituderef=above image.jpg
236
+ </pre>
237
+ Alternatively, the print conversion can be disabled for all tags with the
238
+ <code>-n</code> option, or for individual tags by suffixing the tag name with a
239
+ '<code>#</code>' character. In either case the printed value of GPSAltitudeRef
240
+ will be '0' or '1' when extracting information, and the value is written in the
241
+ same way. So following two commands have exactly the same effect as above:
242
+ <pre>exiftool -gpsaltituderef=0 -n image.jpg
243
+ exiftool -gpsaltituderef#=0 image.jpg
244
+ </pre>
245
+ Integer values may also be specified in hexadecimal (with a leading '0x'). For
246
+ example, the following commands are all equivalent:
247
+ <pre>exiftool -flash=1 -n image.jpg
248
+ exiftool -flash=0x1 -n image.jpg
249
+ exiftool -flash#=1 image.jpg
250
+ exiftool -flash#=0x1 image.jpg
251
+ exiftool -flash=fired image.jpg
252
+ </pre></blockquote><blockquote class=prog>
253
+ <b>Programmers</b>: These techniques look like this when calling Image::ExifTool
254
+ functions from a Perl script:
255
+ <pre>$exifTool->SetNewValue(flash => 1, Type => 'ValueConv');
256
+ $exifTool->SetNewValue(flash => 0x1, Type => 'ValueConv');
257
+ $exifTool->SetNewValue('flash#' => 1);
258
+ $exifTool->SetNewValue('flash#' => 0x1);
259
+ $exifTool->SetNewValue(flash => 'fired');
260
+ </pre></blockquote>
261
+
262
+ <a name="Q7"></a>
263
+ <p>7. <b>"I can't delete all EXIF information from a TIFF file using
264
+ '<code>exiftool -exif:all= img.tif</code>'"</b></p>
265
+
266
+ <blockquote>This is because of the way a TIFF file is structured. With a JPEG
267
+ image, this command removes IFD0 (the main Image File Directory) as well as any
268
+ subdirectories, thus removing all EXIF information. But with the TIFF format,
269
+ the main image itself is stored in IFD0, so deleting this directory would
270
+ destroy the image. The same is true for any TIFF-based RAW file such as DNG,
271
+ CR2, NEF, etc. For these types of files, ExifTool just deletes the ExifIFD
272
+ subdirectory, so any information stored in other directories is preserved.
273
+ </blockquote>
274
+
275
+ <blockquote>Use "<code>exiftool -a -G1 -s img.tif</code>" to see where the
276
+ information is stored. Any tags remaining in other IFD's must be deleted
277
+ individually from a TIFF-format file if desired. For convenience, a
278
+ <a href="TagNames/Shortcuts.html">shortcut tag</a> is provided to simplify the
279
+ deletion of common metadata tags from IFD0 by adding "<code>-CommonIFD0=</code>"
280
+ to the command line.
281
+ </blockquote>
282
+
283
+ <a name="Q8"></a>
284
+ <p>8a. <b>"All maker note information is lost if I change the Make or Model tag"</b>, or
285
+ <br>8b. <b>"I can't copy maker note information to an image"</b></p>
286
+
287
+ <blockquote>
288
+ The Make and Model tags are used by some image utilities (including ExifTool) to
289
+ determine the format of the maker note information. Deleting or changing either
290
+ of these tags may prevent these utilities from recognizing or properly
291
+ interpreting the maker notes. Also beware that the maker notes information may
292
+ be damaged if an image is edited when the maker notes are not properly
293
+ recognized. So it is a good idea not to edit the Make and Model tags in the
294
+ first place.</blockquote>
295
+
296
+ <blockquote>If you really want to delete the Make and Model information, you
297
+ might as well delete the maker notes too. You can do this with either of the
298
+ following commands:
299
+ <pre>exiftool -make= -model= -makernotes:all= image.jpg
300
+ exiftool -make= -model= -makernotes= image.jpg
301
+ </pre>
302
+ For the same reason, maker notes can not be copied to an image with an
303
+ incompatible Make or Model. To do this, the Make and Model tags must also be
304
+ copied. ie)
305
+ <pre>exiftool -tagsfromfile src.jpg -makernotes -make -model dst.jpg
306
+ </pre>
307
+ (Note that in this case the "<code>-makernotes:all</code>" syntax does not work
308
+ because it attempts to copy the maker note tags individually. Since maker note
309
+ tags may not be created individually, they must instead be copied as a block
310
+ with "<code>-makernotes</code>".)
311
+ </blockquote>
312
+
313
+ <a name="Q9"></a>
314
+ <p>9a. <b>"The information is different when I copy all tags to a new file"</b>, or
315
+ <br>9b. <b>"The tag locations change when I use <code>-tagsfromfile</code>
316
+ to copy information"</b></p>
317
+
318
+ <blockquote>
319
+ This feature is explained under the <code>-tagsFromFile</code> option in
320
+ the <a href="exiftool_pod.html">exiftool application documentation</a>, but the
321
+ question is common enough that it is discussed here in more detail.</blockquote>
322
+
323
+ <blockquote>By default, ExifTool will store information in preferred locations
324
+ when either writing new information or copying information between files. This
325
+ freedom allows ExifTool to write or copy information to files of different
326
+ formats without requiring the user to know details about where the information
327
+ is stored.</blockquote>
328
+
329
+ <blockquote>The preferred general locations for information written to JPEG
330
+ images are 1) EXIF, 2) IPTC and 3) XMP. As an example, information extracted
331
+ from the maker notes will be preferentially written (on a tag-by-tag basis) in
332
+ EXIF format when copying information between two JPEG images. But if a specific
333
+ tag doesn't exist in EXIF, then the tag is written to the first valid group in
334
+ the order specified above. The advantage of "translating" the information to
335
+ EXIF is that it then becomes readable by applications which only support
336
+ standard EXIF. The disadvantage is that you don't get an exact copy of the
337
+ original information structure.</blockquote>
338
+
339
+ <blockquote>But ExifTool gives you the ability to customize this behaviour to
340
+ write the information to wherever you want. This is done by specifying a group
341
+ name for the tag(s) to be copied. This applies even if the group name is
342
+ "<code>all</code>", in which case the original family 1 group is preserved. So
343
+ to copy all information and preserve the original structure, use this syntax:
344
+
345
+ <pre>exiftool -tagsfromfile src.jpg -all:all dst.jpg
346
+ </pre>
347
+
348
+ In this command, since no destination tag was specified, the destination is the
349
+ same as the source (ie. "<code>-all:all>all:all</code>"), so the information is
350
+ copied to the same family 1 group.</blockquote>
351
+
352
+ <blockquote>Here are some examples to show you the type of control you have over
353
+ where the information is written. All commands in each example are equivalent:
354
+
355
+ <pre><span class='blk'># copy all tags to preferred groups (no destination group)</span>
356
+ exiftool -tagsfromfile src.jpg dst.jpg
357
+ exiftool -tagsfromfile src.jpg -all dst.jpg
358
+ exiftool -tagsfromfile src.jpg "-all&gt;all" dst.jpg
359
+ exiftool -tagsfromfile src.jpg "-all:all&gt;all" dst.jpg
360
+
361
+ <span class='blk'># copy all tags, preserving family 1 group (destination group 'all')</span>
362
+ exiftool -tagsfromfile src.jpg -all:all dst.jpg
363
+ exiftool -tagsfromfile src.jpg "-all&gt;all:all" dst.jpg
364
+ exiftool -tagsfromfile src.jpg "-all:all&gt;all:all" dst.jpg
365
+
366
+ <span class='blk'># copy all tags to EXIF group (destination group 'exif')
367
+ # [the destination family 1 group is the preferred EXIF IFD]</span>
368
+ exiftool -tagsfromfile src.jpg "-all&gt;exif:all" dst.jpg
369
+ exiftool -tagsfromfile src.jpg "-all:all&gt;exif:all" dst.jpg
370
+
371
+ <span class='blk'># copy XMP tags to XMP group (destination group 'xmp')
372
+ # [the destination family 1 group is the preferred XMP namespace]</span>
373
+ exiftool -tagsfromfile src.jpg "-xmp:all" dst.jpg
374
+ exiftool -tagsfromfile src.jpg "-xmp:all&gt;xmp:all" dst.jpg
375
+
376
+ <span class='blk'># copy XMP tags, preserving family 1 group (destination group 'all')</span>
377
+ exiftool -tagsfromfile src.jpg "-xmp:all&gt;all:all" dst.jpg
378
+
379
+ <span class='blk'># copy XMP tags to preferred groups (no destination group)</span>
380
+ exiftool -tagsfromfile src.jpg "-xmp:all&gt;all" dst.jpg
381
+
382
+ <span class='blk'># copy XMP tags to EXIF only (destination group 'exif')
383
+ # [the destination family 1 group is the preferred EXIF IFD]</span>
384
+ exiftool -tagsfromfile src.jpg "-xmp:all&gt;exif:all" dst.jpg
385
+ </pre>
386
+
387
+ The same rules illustrated above also apply when copying individual tags.</blockquote>
388
+
389
+ <blockquote>Note: If no destination group is specified, a new tag is created if
390
+ necessary only in the preferred group, but if the same tag already exists in
391
+ another group, then this information is also updated. (Otherwise inconsistent
392
+ values for the same information would exist in different locations. Of course,
393
+ you can always generate inconsistencies like this if you really want to by
394
+ specifically writing contradictory information to different groups.)
395
+ </blockquote>
396
+
397
+ <blockquote>Certain types of meta information (such as EXIF, IPTC, XMP and
398
+ ICC_Profile) may also be <b>copied as a block</b>. This technique copies all
399
+ meta information, even if ExifTool doesn't have the ability to write some
400
+ individual tags contained in the block. For all block types except EXIF, the
401
+ metadata is copied byte-for-byte from the original image. With EXIF however,
402
+ the metadata may be restructured to ensure that it is self-contained. Also note
403
+ that EXIF may not be written as a block to TIFF-based file formats. Beware that
404
+ <b>any existing metadata</b> of this type in the distination file <b>will be
405
+ overwritten</b> by the new block.
406
+
407
+ <pre><span class='blk'># copy EXIF as a block between same-named JPG files in different directories</span>
408
+ exiftool -tagsfromfile SRCDIR/%f.%e -ext jpg DSTDIR
409
+
410
+ <span class='blk'># copy XMP as a block from one file to another</span>
411
+ exiftool -tagsfromfile src.jpg -xmp dst.cr2
412
+ </pre></blockquote>
413
+
414
+ <a name="Q10"></a>
415
+ <p>10. <b>"How does ExifTool handle coded character sets?"</b></p>
416
+
417
+ <!-- vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv -->
418
+ <!-- NOTE: CHANGES TO FAQ 10 MUST ALSO BE REFLECTED IN ExifTool.pod! -->
419
+
420
+ <blockquote><i>[Also see <a href="#Q18">FAQ number 18</a> for help on displaying
421
+ special characters in a Windows console.]</i></blockquote>
422
+
423
+ <blockquote>Certain meta information formats allow coded character sets other
424
+ than plain ASCII. When reading, most known encodings are converted to the
425
+ external character set according to the exiftool "<code>-charset CHARSET</code>"
426
+ or <code>-L</code> option, or to UTF&#8209;8 by default. When writing, the
427
+ inverse conversion is performed. Alternatively, special characters may be
428
+ converted to/from HTML character entities with the <code>-E</code> option.
429
+ </blockquote>
430
+
431
+ <blockquote>A distinction is made between the <b>external</b> character set
432
+ visible to the ExifTool user, and the <b>internal</b> character used to store
433
+ text in the metadata of a file. These character sets may be specified
434
+ separately as follows:
435
+ <ol><li>The <b>external</b> character set for strings passed to/from ExifTool
436
+ is UTF&#8209;8 by default, but it may be changed through any of these
437
+ command-line options:
438
+ <blockquote><code>-charset CHARSET</code> &nbsp; or &nbsp;
439
+ <code>-charset exiftool=CHARSET</code> &nbsp; or &nbsp; <code>-L</code>
440
+ </blockquote></li>
441
+ <li>The <b>internal</b> character set for strings stored in file metadata may be
442
+ specified for some metadata types:
443
+ <blockquote><code>-charset TYPE=CHARSET</code></blockquote>
444
+ (where <code>TYPE</code> is "<code>exif</code>", "<code>iptc</code>",
445
+ "<code>id3</code>", "<code>photoshop</code>" or "<code>quicktime</code>")</li></ol>
446
+
447
+ Valid <code>CHARSET</code> values are (with aliases given in brackets):
448
+
449
+ <blockquote><table class=clear>
450
+ <tr><td>UTF8</td><td>(cp65001, UTF&#8209;8)</td><td>Thai</td><td>(cp874)</td></tr>
451
+ <tr><td>Latin</td><td>(cp1252, Latin1)</td><td>MacRoman</td><td>(cp10000, Mac, Roman)</td></tr>
452
+ <tr><td>Latin2</td><td>(cp1250)</td><td>MacLatin2</td><td>(cp10029)</td></tr>
453
+ <tr><td>Cyrillic</td><td>(cp1251,&nbsp;Russian)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td>MacCyrillic</td><td>(cp10007)</td></tr>
454
+ <tr><td>Greek</td><td>(cp1253)</td><td>MacGreek</td><td>(cp10006)</td></tr>
455
+ <tr><td>Turkish</td><td>(cp1254)</td><td>MacTurkish</td><td>(cp10081)</td></tr>
456
+ <tr><td>Hebrew</td><td>(cp1255)</td><td>MacRomanian</td><td>(cp10010)</td></tr>
457
+ <tr><td>Arabic</td><td>(cp1256)</td><td>MacIceland</td><td>(cp10079)</td></tr>
458
+ <tr><td>Baltic</td><td>(cp1257)</td><td>MacCroatian</td><td>(cp10082)</td></tr>
459
+ <tr><td>Vietnam</td><td>(cp1258)</td></tr>
460
+ </table></blockquote>
461
+
462
+ The <code>-L</code> option is equivalent to "<code>-charset Latin</code>",
463
+ "<code>-charset Latin1</code>" and "<code>-charset cp1252</code>".</blockquote>
464
+
465
+ <blockquote>Type-specific details are given below about the special character
466
+ handling for EXIF, IPTC, XMP, PNG, ID3, PDF, Photoshop, QuickTime, AIFF, MIE and
467
+ Vorbis information:</blockquote>
468
+
469
+ <!-- NOTE: CHANGES TO FAQ 10 MUST ALSO BE REFLECTED IN ExifTool.pod! -->
470
+
471
+ <blockquote><b>EXIF</b>: Most textual information in EXIF is stored in "ASCII"
472
+ format (called "string" in the <a href="TagNames/index.html">ExifTool tag name
473
+ documentation</a>). By default ExifTool does not convert these strings.
474
+ However, it is not uncommon for applications to write UTF&#8209;8 or other
475
+ encodings where ASCII is expected. To deal with these, ExifTool allows the
476
+ internal EXIF string encoding to be specified with
477
+ "<code>-charset exif=CHARSET</code>", which causes EXIF string values to be
478
+ converted from the specified character set when reading, and stored with this
479
+ character set when writing. (The
480
+ <a href="http://www.metadataworkinggroup.org/">MWG</a> recommends using
481
+ UTF&#8209;8 encoding for EXIF strings, and in keeping with this the
482
+ "<code>-use mwg</code>" feature sets the default internal EXIF string encoding
483
+ to UTF&#8209;8, but note that this will have no effect unless the external
484
+ encoding is also set to something other than the default of UTF&#8209;8.)</blockquote>
485
+
486
+ <blockquote>A few EXIF tags (UserComment, GPSProcessingMethod and
487
+ GPSAreaInformation) support a designated internal text encoding, with values
488
+ stored as ASCII, Unicode (UCS-2) or JIS. When reading these tags, ExifTool
489
+ converts Unicode and JIS to the external character set specified by the
490
+ <code>-charset</code> or <code>-L</code> option, or to UTF&#8209;8 by default.
491
+ ASCII text is not converted. When writing, text is stored as ASCII unless the
492
+ string contains special characters, in which case it is converted from the
493
+ external character set (UTF&#8209;8 by default), and stored as Unicode. ExifTool
494
+ writes Unicode in native EXIF byte ordering by default, but the byte order may
495
+ be specified by setting the ExifUnicodeByteOrder tag (see the
496
+ <a href="TagNames/Extra.html">Extra Tags</a> documentation).</blockquote>
497
+
498
+ <blockquote>The EXIF "XP" tags (XPTitle, XPComment, etc) are always stored
499
+ internally as little-endian Unicode (UCS&#8209;2), and are read and written
500
+ using the specified external character set.</blockquote>
501
+
502
+ <!-- NOTE: CHANGES TO FAQ 10 MUST ALSO BE REFLECTED IN ExifTool.pod! -->
503
+
504
+ <blockquote><b>IPTC</b><span class='sm'><sup>&dagger;</sup></span>: The
505
+ value of the IPTC:CodedCharacterSet tag determines how the internal IPTC string
506
+ values are interpreted. If CodedCharacterSet exists and has a value of
507
+ "<code>UTF8</code>" (or "<code>ESC&nbsp;%&nbsp;G</code>") then string values are
508
+ assumed to be stored as UTF&#8209;8. Otherwise the internal IPTC encoding is
509
+ assumed to be Windows Latin1 (cp1252), but this can be changed with
510
+ "<code>-charset iptc=CHARSET</code>". When reading, these strings are converted
511
+ to UTF&#8209;8 by default, or to the character set specified by the
512
+ <code>-charset</code> or <code>-L</code> option. When writing, the inverse
513
+ conversions are performed. No conversion is done if the internal (IPTC) and
514
+ external (ExifTool) character sets are the same. Note that ISO 2022 character
515
+ set shifting is not supported. Instead, a warning is issued and the string is
516
+ not converted if an ISO 2022 shift code is encountered. See the
517
+ <a href="http://www.iptc.org/std/IIM/4.1/specification/IIMV4.1.pdf">IPTC IIM
518
+ specification</a> for more information about IPTC character coding.</blockquote>
519
+
520
+ <blockquote>ExifTool may be used to convert IPTC values to a different internal
521
+ encoding. To do this, all IPTC tags must be rewritten along with the desired
522
+ value of CodedCharacterSet. For example, the following command changes the
523
+ internal IPTC encoding to UTF&#8209;8 (from Windows Latin1 unless
524
+ CodedCharacterSet was already "UTF8"):
525
+ <pre>exiftool -tagsfromfile @ -iptc:all -codedcharacterset=utf8 a.jpg
526
+ </pre>or from Windows Latin2 (cp1250) to UTF&#8209;8:
527
+ <pre>exiftool -tagsfromfile @ -iptc:all -codedcharacterset=utf8 -charset iptc=latin2 a.jpg
528
+ </pre>and this command changes it back from UTF&#8209;8 to Windows Latin1 (cp1252):
529
+ <pre>exiftool -tagsfromfile @ -iptc:all -codedcharacterset= a.jpg
530
+ </pre>or to Windows Latin2:
531
+ <pre>exiftool -tagsfromfile @ -iptc:all -codedcharacterset= -charset iptc=latin2 a.jpg
532
+ </pre>Note that unless CodedCharacterSet is 'UTF&#8209;8', applications
533
+ have no reliable way to determine the IPTC character encoding. For this reason,
534
+ it is recommended that CodedCharacterSet be set to "<code>UTF8</code>" when
535
+ creating new IPTC.</blockquote>
536
+
537
+ <blockquote class='sm'><sup>&dagger;</sup> <span class=lt>Refers to the older
538
+ <a href="http://www.iptc.org/site/News_Exchange_Formats/IIM/">IPTC IIM</a> format.
539
+ The more recent
540
+ <a href="http://iptc.cms.apa.at/site/Photo_Metadata/IPTC_Core_&amp;_Extension/">IPTC
541
+ Core and Extension specifications</a> actually use the XMP format (see below).</span>
542
+ </blockquote>
543
+
544
+ <!-- NOTE: CHANGES TO FAQ 10 MUST ALSO BE REFLECTED IN ExifTool.pod! -->
545
+
546
+ <blockquote><b>XMP</b>: Exiftool reads XMP encoded as UTF&#8209;8, UTF&#8209;16
547
+ or UTF&#8209;32, and converts them all to UTF&#8209;8 internally. Also, all XML
548
+ character entity references and numeric character references are converted.
549
+ When writing, ExifTool always encodes XMP as UTF&#8209;8, converting the
550
+ following 5 characters to XML character references: <code>&amp; &lt; &gt; &#39;
551
+ &quot;</code>. By default no further conversion is performed, however the
552
+ <code>-charset</code> or <code>-L</code> option may be used used to convert
553
+ text to/from a specified character set when reading/writing.</blockquote>
554
+
555
+ <blockquote><b>PNG</b>: <a href="TagNames/PNG.html#TextualData">PNG TextualData
556
+ tags</a> are stored as tEXt, zTXt and iTXt chunks in PNG images. The tEXt and
557
+ zTXt chunks use ISO 8859-1 encoding, while iTXt uses UTF&#8209;8. When reading,
558
+ ExifTool converts all PNG textual data to the character set specified by the
559
+ <code>-charset</code> or <code>-L</code> option, or to UTF&#8209;8 by default.
560
+ When writing, ExifTool generates a tEXt chunk (or zTXt with the <code>-z</code>
561
+ option) if the text doesn't contain special characters or if Latin encoding is
562
+ specified (<code>-L</code> or <code>-charset latin</code>); otherwise an iTXt
563
+ chunk is used and the text is converted from the specified character set and
564
+ stored as UTF&#8209;8.</blockquote>
565
+
566
+ <blockquote><b>ID3</b>: The ID3v1 specification officially supports only ISO
567
+ 8859&#8209;1 encoding (a subset of Windows Latin1), although some applications
568
+ may incorrectly use other character sets. By default ExifTool converts ID3v1
569
+ text from Latin to the character set specified by the <code>-charset</code> or
570
+ <code>-L</code> option, or to UTF&#8209;8 by default. However, the internal
571
+ ID3v1 charset may be specified with "<code>-charset id3=CHARSET</code>". The
572
+ encoding for ID3v2 information is stored in the file, so ExifTool converts
573
+ ID3v2 text from this encoding to the character set specified by
574
+ <code>-charset</code> or <code>-L</code>, or to UTF&#8209;8 by default. ExifTool
575
+ does not currently write ID3 information.</blockquote>
576
+
577
+ <blockquote><b>PDF</b>: PDF text strings are stored in either PDFDocEncoding
578
+ (similar to Windows Latin1) or Unicode (UCS&#8209;2). When reading, ExifTool
579
+ converts to the character set specified by the <code>-charset</code> or
580
+ <code>-L</code> option, or to UTF&#8209;8 by default. When writing, ExifTool
581
+ encodes input text from the specified character set as Unicode only if the
582
+ string contains special characters, otherwise PDFDocEncoding is
583
+ used.</blockquote>
584
+
585
+ <blockquote><b>Photoshop</b>: Some Photoshop resource names are stored as
586
+ Pascal strings with unknown encoding. By default, ExifTool assumes MacRoman
587
+ encoding and converts this to UTF&#8209;8, but the internal and external
588
+ character sets may be specified with <code>-charset Photoshop=CHARSET</code>
589
+ and <code>-charset CHARSET</code> respectively.</blockquote>
590
+
591
+ <blockquote><b>QuickTime</b>: QuickTime text strings may be stored in a
592
+ variety of poorly documented formats, and ExifTool does its best to decode
593
+ these according to the <code>-charset</code> option setting. For some
594
+ QuickTime strings where the internal encoding is not known, ExifTool assumes
595
+ a default encoding of MacRoman, but this may be changed with
596
+ "<code>-charset QuickTime=CHARSET</code>".</blockquote>
597
+
598
+ <blockquote><b>AIFF</b>: AIFF strings are assumed to be stored in MacRoman, and
599
+ are converted according to the <code>-charset</code> option when reading.
600
+ </blockquote>
601
+
602
+ <blockquote><b>MIE</b>: MIE strings are stored as either UTF&#8209;8 or ISO
603
+ 8859&#8209;1. When reading, UTF&#8209;8 strings are converted according to
604
+ the <code>-charset</code> or <code>-L</code> option, and ISO 8859&#8209;1
605
+ strings are never converted. When writing, input strings are converted from
606
+ the specified character set to UTF&#8209;8. The resulting strings are stored as
607
+ UTF&#8209;8 if they contain multi-byte UTF&#8209;8 character sequences,
608
+ otherwise they are stored as ISO 8859&#8209;1.</blockquote>
609
+
610
+ <blockquote><b>Vorbis</b>: Vorbis comments are stored as UTF&#8209;8,
611
+ and are converted to the character set specified by <code>-charset</code> or
612
+ <code>-L</code> when reading.</blockquote>
613
+
614
+ <blockquote class=prog>
615
+ <b>Programmers</b>: ExifTool returns all values as byte strings of encoded
616
+ characters. Perl wide characters are not used. The encoding is UTF&#8209;8 by
617
+ default, but valid UTF&#8209;8 can not be guaranteed for all values, so the
618
+ caller must validate the encoding if necessary. The encodings described above
619
+ are set by the various <a href="ExifTool.html#Charset">Charset options</a> of
620
+ the API.
621
+ <br><br><b>Note</b>: Some settings of the system PERL_UNICODE environment
622
+ variable may be incompatible with ExifTool's character handling.
623
+ </blockquote>
624
+
625
+ <!-- NOTE: CHANGES TO FAQ 10 MUST ALSO BE REFLECTED IN ExifTool.pod! -->
626
+ <!-- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -->
627
+
628
+ <a name="Q11"></a>
629
+ <p>11. <b>"My user-defined tags don't work"</b></p>
630
+
631
+ <blockquote>
632
+ For examples of how to add user-defined tags, see the
633
+ <a href="config.html">ExifTool_config</a> file in the ExifTool distribution.
634
+ It may be useful to activate this file as a test before trying to implement
635
+ your own config file. To activate this file, copy it to your <b>HOME</b>
636
+ directory then rename it to "<code>.ExifTool_config</code>".
637
+ <blockquote class=lt><b>Note</b>: The config file must be renamed at the
638
+ command line because neither the Windows nor Mac GUI allow a file name to
639
+ begin with a "<code>.</code>". To do this in Windows, run "cmd.exe" and type
640
+ the following (pressing <i>RETURN</i> at the end of each line):
641
+ <pre>cd %HOMEPATH%
642
+ rename ExifTool_config .ExifTool_config
643
+ </pre>
644
+ or on a Mac, open the "Terminal" application (from the /Applications/Utilities
645
+ folder) and type this command then press <i>RETURN</i>:
646
+ <pre>mv ExifTool_config .ExifTool_config
647
+ </pre></blockquote>
648
+
649
+ With the sample config file installed, you should be able to write the example
650
+ tags. A command like this:
651
+ <pre>exiftool -v2 -NewXMPxmpTag=test <i>FILE</i></pre>
652
+ should print this as the first line of its output:
653
+ <pre>Writing XMP-xmp:NewXMPxmpTag
654
+ </pre>
655
+ If this doesn't work, the most common problem is that the
656
+ "<code>.ExifTool_config</code>" configuration file isn't getting loaded. In
657
+ this case, there are a few things you can try:
658
+ <ol>
659
+ <li>Make sure the config file name is correct. It must be
660
+ "<code>.ExifTool_config</code>" (note the leading "<code>.</code>", and the
661
+ capital "<code>T</code>").</li>
662
+ <li>Set either the <b>HOME</b> or the <b>EXIFTOOL_HOME</b> environment variable
663
+ to the name of the directory where you put your "<code>.ExifTool_config</code>"
664
+ file.</li>
665
+ <li>Put the config file in the same directory as the exiftool script. (Also, be
666
+ sure the config filename starts with a dot! See the note above for help
667
+ renaming the config file.)</li>
668
+ <li>If you can't get the config file to load automatically, you can try loading
669
+ it manually with the exiftool <code>-config <i>CFGFILE</i></code> option. (Note:
670
+ This must be the first option on the command line.) This allows loading
671
+ of a config file with any name.</li>
672
+ </ol>
673
+ </blockquote>
674
+
675
+ <blockquote>If necessary, you can verify that ExifTool is loading your config
676
+ file by adding the following line to your file:
677
+
678
+ <pre>print "LOADED!\n";
679
+ </pre>
680
+
681
+ If you see a "<code>LOADED!</code>" message when you run exiftool, but your new
682
+ tags still don't work, make sure you are using the proper tag name and that the
683
+ file you are writing can support this type of information.</blockquote>
684
+
685
+ <blockquote class=prog><b>Programmers</b>: To specify the config file directory from within
686
+ a Perl script when using the ExifTool API, set the <b>EXIFTOOL_HOME</b>
687
+ environment variable before loading the ExifTool module:
688
+ <pre>BEGIN { $ENV{EXIFTOOL_HOME} = '/config_file_directory' }
689
+ use Image::ExifTool;
690
+ </pre>
691
+ Also see the <a href="ExifTool.html#Config">Configuration section of the
692
+ ExifTool API documentation</a> for techniques to use a config file with another
693
+ name, or to disable the config file feature.
694
+ </blockquote>
695
+
696
+ <a name="Q12"></a>
697
+ <p>12. <b>"How do I export information from exiftool to a database?"</b></p>
698
+
699
+ <blockquote>
700
+ It is often easiest to export information formatted as a tab-delimited or
701
+ comma-separated list of values using the exiftool <code>-T</code> or
702
+ <code>-csv</code> option. As well, the <code>-r</code> option is useful for
703
+ recursing through all images in a hierarchy of directories. For example:
704
+
705
+ <pre>exiftool -T -r -filename -exposuremode -ISO t/images &gt; out.txt
706
+ </pre>
707
+
708
+ This command recursively processes all images in the "<code>t/images</code>"
709
+ directory, extracting FileName, ExposureMode and ISO tags, and writing the
710
+ output to a tab-delimited text file called "<code>out.txt</code>". After the
711
+ command has executed, "<code>out.txt</code>" will look something like this:
712
+
713
+ <pre>Canon.jpg Manual 100
714
+ Casio.jpg - 64
715
+ Nikon.jpg - 100
716
+ OlympusE1.jpg Auto 400
717
+ </pre>
718
+
719
+ One limitation of the <code>-T</code> option is that a list of tags to extract
720
+ must be specified. Otherwise, all information is extracted from each input
721
+ file, and the columns would contain values from random tags.</blockquote>
722
+
723
+ <blockquote> The <code>-csv</code> (comma separated values) option solves this
724
+ dilemma by pre-extracting information from all input files, then producing a
725
+ sorted list of available tag names as the first row of the output, and
726
+ organizing the information into columns for each tag. As well, a first column
727
+ labelled "SourceFile" is generated. These features make it practical to use the
728
+ <code>-csv</code> option for extracting all information from multiple images.
729
+ For example, this command:
730
+
731
+ <pre>exiftool -csv -r t/images > out.csv</pre>
732
+
733
+ gives an output like this:
734
+
735
+ <pre>SourceFile,AEBBracketValue,AELock,AFAreaHeight,AFAreaMode,AFAreas,[...]
736
+ t/images/Canon.jpg,0,,151,,,[...]
737
+ t/images/Casio.jpg,,,,,,[...]
738
+ t/images/Nikon.jpg,,,,Single Area,,[...]
739
+ t/images/OlympusE1.jpg,,Off,,,"Center (121,121)-(133,133)",[...]
740
+ </pre>
741
+
742
+ Note that the number of columns in the <code>-csv</code> output may be very
743
+ large if all information is extracted. Missing tags are indicated by empty
744
+ strings as in the example above, or by dashes if the <code>-f</code> option is
745
+ used.</blockquote>
746
+
747
+ <blockquote> It should be possible to import these files directly into most
748
+ database applications. On the command line, any list of tag names may be used,
749
+ and any number of file or directory names may be specified. (Hint: If your
750
+ command line starts to get too long, you may want to look into using the
751
+ <code>-@</code> option and/or the <a href="index.html#shortcut">ShortCut</a>
752
+ feature).</blockquote>
753
+
754
+ <blockquote>In Windows, a .BAT file containing the exiftool command may be used
755
+ to give drag and drop functionality. Dropping a folder on the following .BAT
756
+ file will create "out.txt" in the folder:
757
+
758
+ <pre>echo "FileName&lt;tab&gt;Aperture&lt;tab&gt;ISO" &gt; %1\out.txt
759
+ exiftool -T -r -filename -aperture -ISO %1 &gt;&gt; %1\out.txt
760
+ </pre>
761
+
762
+ The "<code>echo</code>" command was included to add column headings to the
763
+ output. (The tab character in the echo command, indicated by
764
+ "<code>&lt;tab&gt;</code>", may be generated in Mac/Linux shells with CTRL-v
765
+ then TAB, or in a Windows cmd shell with TAB when cmd.exe is run with the
766
+ <code>/f:off</code> option to disable tab completion.)
767
+ </blockquote>
768
+
769
+ <blockquote>Other possible export formats include RDF/XML (with the the
770
+ <code>-X</code> option), or JSON (with the <code>-j</code> option). These
771
+ methods allow transfer of more complex data sets (including structured
772
+ information with the <code>-struct</code> option), but require that the
773
+ importing software supports these formats.</blockquote>
774
+
775
+ <blockquote>Finally, the <code>-p</code> option may be used to generate any
776
+ arbitrary output format. For example, the following format file
777
+ (let's call it "<code>my.fmt</code>") may be used to emulate a CSV-formatted
778
+ output:
779
+
780
+ <pre>#[HEAD]FileName, Aperture, ISO
781
+ $filename, $aperture, $iso
782
+ </pre>
783
+
784
+ with a command like this:
785
+
786
+ <pre>exiftool -f -r -p my.fmt t/images &gt; out.csv
787
+ </pre>
788
+
789
+ Alternatively, the <code>-p</code> option may be used with a format string instead
790
+ of a file name. The following command has the same effect as above except that
791
+ the row of headings is not printed (Note: Use single quotes as below on Mac/Linux,
792
+ or double quotes instead on Windows):
793
+
794
+ <pre>exiftool -f -r -p '$filename, $aperture, $iso' t/images &gt; out.csv
795
+ </pre>
796
+
797
+ With the <code>-f</code> option, the value of any missing tag is printed as a
798
+ dash. Without this option, missing tags generate a minor warning and the
799
+ line in the <code>-p</code> output is not printed. The <code>-m</code> option
800
+ may be used to ignore minor warnings, which causes these lines to be printed
801
+ with an empty value for missing tags.</blockquote>
802
+
803
+ <blockquote>
804
+ See the <code>-p</code> option in the <a href="exiftool_pod.html">application
805
+ documentation</a> for more information about this feature.
806
+ </blockquote>
807
+
808
+ <blockquote><b>Note</b>: Information may be <b>imported</b> from CSV or JSON files for
809
+ writing to images by specifying an input file name with the <code>-csv</code> or
810
+ <code>-j</code> option. See the <a href="exiftool_pod.html">exiftool
811
+ application documentation</a> for more details.</blockquote>
812
+
813
+ <a name="Q13"></a>
814
+ <p>13. <b>"Why is my file smaller after I use ExifTool to write information?"</b></p>
815
+
816
+ <blockquote>
817
+ There are various specific reasons why this can happen, but the general answer
818
+ is: When ExifTool writes an image, the meta information may be restructured in
819
+ such a way that it takes less space than in the original file.</blockquote>
820
+
821
+ <blockquote>For instance, the EXIF/TIFF standard allows for blocks of
822
+ unreferenced data to exist in an image. Some digital cameras write JPEG or
823
+ TIFF-based RAW files which contain large blocks of unused data, usually filled
824
+ with binary zeros. The reason for this could be to simplify camera algorithms
825
+ by allowing variable-sized information to be written at fixed offsets in the
826
+ output image. When ExifTool rewrites an image it does not copy these unused
827
+ blocks. This can result in a significant reduction in file size for some
828
+ images. <i>[The <code>-htmlDump</code> option may be used to view the file
829
+ structure if you are interested in seeing these unused data blocks -- use a
830
+ command like "<code>exiftool -htmlDump a.jpg &gt; out.html</code>", then open
831
+ <code>out.html</code> in your web browser. Unused data blocks are
832
+ <span class=U>brown</span> in this output.]</i>
833
+ </blockquote>
834
+
835
+ <blockquote>Also, the size of an XMP record may easily shrink or grow when it is
836
+ rewritten, even if no meta information is changed. This is partly due to the
837
+ fact that the XMP specification recommends a few KB of padding at the end of the
838
+ record (ExifTool adds 2424 bytes by default, but this padding is omitted if the
839
+ <code>-z</code> option is used), and partly due to the flexibility of the XMP
840
+ format which allows the information to be written in various styles, some of
841
+ which are more compact than others.
842
+ </blockquote>
843
+
844
+ <blockquote>You may also notice that the values of some "offset" tags (like
845
+ ThumbnailOffset and PreviewImageStart) may change when the file is rewritten.
846
+ This is normal, and simply indicates that the associated data is now stored at a
847
+ different position within the file.</blockquote>
848
+
849
+ <blockquote>ExifTool does not modify the image data itself, so editing a file is
850
+ "lossless" as far as the image is concerned.</blockquote>
851
+
852
+ <a name="Q14"></a>
853
+ <p>14. <b>"What format do I use for writing GPS coordinates?"</b></p>
854
+
855
+ <blockquote>ExifTool is very flexible in the formats allowed for entering GPS
856
+ coordinates. Any string containing between 1 and 3 floating point numbers is
857
+ valid. The numbers represent degrees, (and optionally) minutes and
858
+ seconds.</blockquote>
859
+
860
+ <blockquote>For EXIF GPS coordinates, the reference direction is specified
861
+ separately with the EXIF:GPSLatitudeRef or EXIF:GPSLongitudeRef
862
+ tag.</blockquote>
863
+
864
+ <blockquote>For XMP GPS coordinates, the reference direction is specified within
865
+ the XMP:GPSLatitude or XMP:GPSLongitude value, with west longitudes and south
866
+ latitudes being specified either by negative coordinate values or by ending the
867
+ string with "<code>W</code>" or "<code>S</code>". </blockquote>
868
+
869
+ <blockquote>Here are some examples of equivalent ways to specify a GPS
870
+ latitude in both EXIF and XMP:
871
+
872
+ <pre>exiftool -exif:gpslatitude="42 30 0.00" -exif:gpslatituderef=S a.jpg
873
+ exiftool -exif:gpslatitude="42 deg 30.00 min" -exif:gpslatituderef=S a.jpg
874
+ exiftool -exif:gpslatitude=42.5 -exif:gpslatituderef=S a.jpg
875
+
876
+ exiftool -xmp:gpslatitude="42 30 0.00 S" a.jpg
877
+ exiftool -xmp:gpslatitude=42.50S a.jpg
878
+ exiftool -xmp:gpslatitude=-42.5 a.jpg
879
+ </pre>
880
+
881
+ Similar styles may be used for longitude. ExifTool will convert any of these
882
+ coordinate styles to the proper format for the specific tag used.
883
+ </blockquote>
884
+
885
+ <a name="Q15"></a>
886
+ <p>15. <b>"I get MakerNote warnings or errors when reading or writing information"</b></p>
887
+
888
+ <blockquote>Problems like this may be caused by image editing software which
889
+ doesn't properly update offsets in the MakerNotes when rewriting an image. These
890
+ offsets are used as pointers to reference tag values and structures within the
891
+ metadata, and errors like this may lead to missing or incorrect values for some
892
+ MakerNotes tags. In many cases, ExifTool will detect this type of problem and
893
+ issue a warning like this when reading (or an error when writing):
894
+
895
+ <pre>Warning: [minor] Possibly incorrect maker notes offsets (fix by -340?)
896
+ </pre>
897
+
898
+ <i class=lt>[Be aware that if multiple warnings occur, the <code>-a</code>
899
+ option must be used to see them all, since by default only one warning is
900
+ displayed per file.]</i> </blockquote>
901
+
902
+ <blockquote>This is a particularly insidious problem that is sometimes difficult
903
+ for ExifTool to correct automagically, so it requires some operator
904
+ intervention. If this warning occurs, you have a few alternatives:</blockquote>
905
+
906
+ <blockquote>1) Use the <code>-F</code> option to allow ExifTool to attempt to
907
+ fix the incorrect offsets. If ExifTool was correct in its diagnosis, then this
908
+ option will fix the incorrect offsets. This is usually the appropriate choice
909
+ if this problem was caused by editing the image with other
910
+ software.</blockquote>
911
+
912
+ <blockquote>2) Use the <code>-m</code> option to ignore the warning (or downgrade
913
+ the error to a warning when writing). This causes ExifTool to honour the
914
+ existing maker note offsets, and may be the correct choice if images straight
915
+ out of the camera have this problem.</blockquote>
916
+
917
+ <blockquote>Often, the first choice (<code>-F</code>) is the right thing to do,
918
+ but this depends on many factors, so it is best to try both methods then compare
919
+ the resulting maker note information to see which works best for your
920
+ situation.</blockquote>
921
+
922
+ <blockquote>When writing, <code>-F</code> applies a permanent correction to the
923
+ maker notes. Note that <u>some MakerNote information may be lost permanently
924
+ if the proper correction is not applied when writing images with this
925
+ problem</u>.</blockquote>
926
+
927
+ <blockquote>3) The third alternative is to adjust the maker note offsets by a
928
+ specific amount. This is done by appending an integer to the <code>-F</code>
929
+ option. For example, with the warning above (where ExifTool suggests "fix by
930
+ -340?"), <code>-F</code> would be equivalent to <code>-F-340</code>. See the
931
+ <a href="exiftool_pod.html#f_offset_fixbase">-F option documentation</a> for
932
+ more details. This advanced feature may require some technical knowledge about
933
+ the structure of EXIF information (and here, ExifTool's <code>-htmlDump</code>
934
+ feature may be very useful for visualizing this structure).</blockquote>
935
+
936
+ <blockquote>Other types of MakerNote errors may also prevent the file from
937
+ being written. However, most MakerNote errors are designated as <b>minor</b>,
938
+ which allows them to be ignored by using the <code>-m</code> option. For
939
+ example:
940
+
941
+ <pre>Error: [minor] Bad format (65535) for MakerNotes entry 17
942
+ </pre>
943
+
944
+ Using <code>-m</code> will downgrade the minor error to a warning, allowing the
945
+ file to be written, but <u>some MakerNote information may be lost when ignoring
946
+ certain types of errors like this</u>. </blockquote>
947
+
948
+ <a name="Q16"></a>
949
+ <p>16. <b>"Why doesn't ExifTool rename my AVI files?"</b></p>
950
+
951
+ <blockquote>By default, ExifTool only processes <u>writable file
952
+ types</u><span class='sm'><sup>&dagger;</sup></span> when <u>any
953
+ tag</u><span class='sm'><sup>&Dagger;</sup></span> is being written and a
954
+ directory name is specified on the command line. To force exiftool to process
955
+ other files, they must either be listed on the command line by name, or be
956
+ specified using the <code>-ext</code> option, something like this:
957
+
958
+ <pre>exiftool -ext AVI -ext JPG -d pics/%Y/%m "-directory&lt;dateTimeOriginal" DIR
959
+ </pre>
960
+
961
+ When a single <code>-ext</code> option is used, only files of the specified type
962
+ are processed. However, multiple <code>-ext</code> options may be used in the
963
+ same command (as in the example above) to process any number of different file
964
+ types.
965
+ </blockquote>
966
+
967
+ <blockquote class='sm'><sup>&dagger;</sup> <span class=lt>The
968
+ <code>-listwf</code> option may be used to list the extensions of all writable file types.</span>
969
+ <br><sup>&Dagger;</sup> <span class=lt>This includes "pseudo" tags like
970
+ FileName, Directory, FileModifyDate and FileCreateDate.</span></blockquote>
971
+
972
+ <a name="Q17"></a>
973
+ <p>17. <b>"List-type tags do not behave as expected"</b></p>
974
+
975
+ <blockquote>Tags indicated by a plus sign (<code>+</code>) in the
976
+ <a href="TagNames/index.html">tag name documentation</a> are list-type tags.
977
+ Two examples of common list-type tags are
978
+ <a href="TagNames/IPTC.html#ApplicationRecord">IPTC:Keywords</a> and
979
+ <a href="TagNames/XMP.html#dc">XMP:Subject</a>. These tags may contain multiple
980
+ items which are combined into a single string when reading. (By default,
981
+ extracted list items are separated by a comma and a space, but the
982
+ <code>-sep</code> option may be used to change this.) When writing, separate
983
+ items are assigned individually. For example, the following command writes
984
+ three keywords to all writable files in directory <code>DIR</code>, replacing
985
+ any previously existing keywords:
986
+
987
+ <pre>exiftool -keywords=one -keywords=two -keywords=three DIR
988
+ </pre>
989
+
990
+ List items are assigned separately, NOT all together, because this would
991
+ represent a single keyword:
992
+
993
+ <pre>exiftool -keywords="one, two, three" test.jpg <span class=blk>(WRONG!)</span>
994
+ </pre>
995
+
996
+ With exiftool version 7.56 or later, the <code>-sep</code> option may be used to
997
+ split values of list-type tags into separate items when writing. For example,
998
+
999
+ <pre>exiftool -sep ", " -keywords="one, two, three" DIR
1000
+ </pre>
1001
+
1002
+ will store three separate keywords, the same as the first example above. This
1003
+ feature may also be used to split a tag value into separate items if it was
1004
+ originally stored incorrectly as a single string:
1005
+
1006
+ <pre>exiftool -sep ", " -tagsfromfile @ -keywords test.jpg
1007
+ </pre>
1008
+
1009
+ However, sometimes it is desirable to have list items which contain a comma, and
1010
+ this is allowed:
1011
+
1012
+ <pre>exiftool -contributor="Harvey, Phil" -contributor="Marley, Bob" a.jpg
1013
+ </pre>
1014
+
1015
+ But to distinguish these entries when extracting information, a different list
1016
+ separator or a different output format must be used. For instance, the
1017
+ following command uses "<code>//</code>" to separate list items,
1018
+
1019
+ <pre>exiftool -contributor -sep "//" a.jpg
1020
+ </pre>
1021
+
1022
+ and produces an output like this:
1023
+
1024
+ <pre class=blk>Contributor : Harvey, Phil//Marley, Bob
1025
+ </pre>
1026
+
1027
+ Alternatively, the <code>-j</code>, <code>-php</code> and <code>-X</code>
1028
+ options use an output format which preserves the structure of a
1029
+ list (if <code>-sep</code> is NOT used).</blockquote>
1030
+
1031
+ <blockquote>Note that the writing examples above overwrite any values which
1032
+ already existed in the original file for these tags. Instead, to add or delete
1033
+ items from an existing list, use "<code>+=</code>" or "<code>-=</code>" in place
1034
+ of "<code>=</code>". For example:
1035
+
1036
+ <pre>exiftool -keywords+="add this" -keywords-="remove this" DIR
1037
+ </pre>
1038
+
1039
+ With commands like this, new items are added to the list in place of the first
1040
+ deleted item, or at the end of the list if no items were removed.</blockquote>
1041
+
1042
+ <blockquote>Note: Using "<code>=</code>" is equivalent to "<code>+=</code>" in
1043
+ any command where the same tag is set with "<code>+=</code>" or
1044
+ "<code>-=</code>" in another assignment. (ie. existing items will be preserved
1045
+ unless specifically deleted with "<code>-=</code>".)</blockquote>
1046
+
1047
+ <blockquote>To prevent duplication when adding new items, specific items can be
1048
+ deleted then added back again in the same command. For example, the following
1049
+ command adds the keywords "one" and "two", ensuring that they are not duplicated
1050
+ if they already existed in the keywords of an image:
1051
+
1052
+ <pre>exiftool -keywords-=one -keywords+=one -keywords-=two -keywords+=two DIR
1053
+ </pre>
1054
+
1055
+ When copying list tags using the <code>-tagsFromFile</code> option, items are
1056
+ copied individually to form proper lists. However, there is a complication when
1057
+ copying multiple tags to a single list tag: Here, any assignment to a tag
1058
+ overrides earlier assignments to the same tag in the command. For instance,
1059
+ this command
1060
+
1061
+ <pre>exiftool "-keywords&lt;filename" "-keywords&lt;comment" DIR
1062
+ </pre>
1063
+
1064
+ writes only the value from the Comment tag. (Note that <code>-tagsFromFile @</code>
1065
+ is implied by the "<code>&lt;</code>" operation in this command, causing tags to
1066
+ be copied from the original file.) This may seem strange, but it prevents
1067
+ duplicate items from being added to a list when copying a group of tags from a
1068
+ file containing duplicate information. Alternatively, the
1069
+ <code>-addTagsFromFile</code> option may be used to accumulate items when
1070
+ copying from multiple tags:
1071
+
1072
+ <pre>exiftool -addTagsFromFile @ "-keywords&lt;filename" "-keywords&lt;comment" DIR
1073
+ </pre>
1074
+
1075
+ Note that as with "<code>=</code>" in the first three examples above, the
1076
+ "<code>&lt;</code>" operation of this command overwrites any Keywords that
1077
+ existed previously in the original file. To add to or remove from the existing
1078
+ keywords, use "<code>+&lt;</code>" or "<code>-&lt;</code>".
1079
+ </blockquote>
1080
+
1081
+ <a name="Q18"></a>
1082
+ <p>18. <b>"Special characters don't display properly in my Windows console"</b></p>
1083
+
1084
+ <blockquote>The Windows cmd.exe console uses an MS-DOS encoding by default
1085
+ (cp437 or something similar, depending on your region). The exiftool
1086
+ <code>-charset</code> option may be used to encode the exiftool output for a
1087
+ specific Windows code page, which may help display some special characters, but
1088
+ instead it may be better to switch the console to UTF&#8209;8 (the native
1089
+ ExifTool character encoding). This is especially useful if you are using the
1090
+ <code>-lang</code> option to translate exiftool output to another language. To
1091
+ change the the Windows console to UTF&#8209;8, follow these steps:
1092
+
1093
+ <ol><li>Run "cmd.exe" to open a Windows console (select "Run..." from the
1094
+ Start menu and enter "cmd").</li>
1095
+ <li>Change the font in the console Properties to any True Type font (ie. "TT
1096
+ Lucida Console").</li>
1097
+ <li>Type "<code>chcp 65001</code>" then press RETURN at the command prompt.</li>
1098
+ </ol>
1099
+
1100
+ The console should now be able to display UTF&#8209;8 characters (cp65001). But
1101
+ note that the TT Lucida Console font shipped with Windows, at least my version,
1102
+ may not be very complete, and doesn't seem to contain Japanese or Chinese
1103
+ characters.</blockquote>
1104
+
1105
+ <blockquote>To permanently set the font, select "Save properties for future
1106
+ windows" when changing the font Properties. Also, you can automatically run
1107
+ "<code>chcp 65001</code>" every time "cmd.exe" is launched by changing the
1108
+ Windows Registry for the Command Processor: Run "regedit" and put "<code>chcp
1109
+ 65001</code>" into Data field for "HKEY_LOCAL_MACHINE\Software\Microsoft\Command
1110
+ Processor\Autorun". (Unfortunately, I haven't been able to figure out how to
1111
+ change the code page for exiftool when launched via the Windows GUI. If anyone
1112
+ can figure out how to do this, please let me know.)
1113
+ </blockquote>
1114
+
1115
+ <blockquote>On some Windows systems, using UTF&#8209;8 doesn't seem to work. In
1116
+ this case, a Windows character set may be the best alternative: For instance,
1117
+ for Windows Latin1 (cp1252) type "<code>chcp 1252</code>" in the console to
1118
+ switch to cp1252, then run exiftool with "<code>-charset cp1252</code>" (or
1119
+ <code>-L</code>). This same technique can be used for other supported Windows
1120
+ code pages.</blockquote>
1121
+
1122
+ <a name="Q19"></a>
1123
+ <p>19. <b>"How do I change the format of an extracted tag value?"</b></p>
1124
+
1125
+ <blockquote>The exiftool application has built-in options which allow you to
1126
+ display numeric values (<code>-n</code>), escape special HTML characters
1127
+ (<code>-E</code>), and change the date/time (<code>-d</code>) and GPS coordinate
1128
+ (<code>-c</code>) formats, but sometimes more control is needed over the
1129
+ formatting of a value...</blockquote>
1130
+
1131
+ <blockquote>The <code>-p</code> and <code>-tagsFromFile</code> options provide
1132
+ an advanced translation feature that allows arbitrary Perl expressions to be
1133
+ used to modify tag values. The basic syntax is this:
1134
+
1135
+ <pre>${TAG;EXPR}</pre>
1136
+
1137
+ where <code>TAG</code> is the tag name, and <code>EXPR</code> is a Perl
1138
+ expression acting on the default input variable (<code>$_</code>), which is
1139
+ initially the original value of the tag. For example, the following command
1140
+ sets the FileName from Artist, translating spaces to underlines:
1141
+
1142
+ <pre>exiftool '-filename&lt;${artist;tr/ /_/}.%e' image.jpg</pre>
1143
+
1144
+ (Note: Use single quotes as above in Mac/Linux, or double quotes instead
1145
+ in Windows.)</blockquote>
1146
+
1147
+ <blockquote>Another technique is to create a user-defined Composite tag to do
1148
+ the reformatting. Here is a basic config file that reformats the Artist tag to
1149
+ provide a new MyArtist tag with the same character translation as the example
1150
+ above:
1151
+
1152
+ <pre>%Image::ExifTool::UserDefined = (
1153
+ 'Image::ExifTool::Composite' => {
1154
+ MyArtist => {
1155
+ Require => 'Artist',
1156
+ ValueConv => '$val =~ tr/ /_/; $val',
1157
+ },
1158
+ },
1159
+ );
1160
+ 1; # end
1161
+ </pre>
1162
+
1163
+ With this config file, an Artist value of "Phil Harvey" yields a corresponding
1164
+ MyArtist value of "Phil_Harvey". The ValueConv string may be any valid Perl
1165
+ expression, and is evaluated to obtain the value for the new tag. In this
1166
+ expression, <code>$val</code> represents the ValueConv value of the Require'd
1167
+ tag. </blockquote>
1168
+
1169
+ <blockquote>To activate the config file, it must be named
1170
+ "<code>.ExifTool_config</code>" and placed either in your home directory or in
1171
+ the same directory as the exiftool application. Note that the file name begins
1172
+ with a "<code>.</code>", so if you are in Windows or on a Mac you may need to
1173
+ rename the file from the command line since the GUI might not like file names
1174
+ beginning with a "<code>.</code>".</blockquote>
1175
+
1176
+ <blockquote>User-defined Composite tags have many other features, including the
1177
+ ability to combine the values of multiple tags. See the
1178
+ <a href="config.html">config file documentation</a> for more details about
1179
+ user-defined tags, and lib/Image/ExifTool/README in the full distribution for a
1180
+ complete description of ValueConv features. Also, a
1181
+ <a href="http://u88.n24.queensu.ca/exiftool/forum/index.php?action=search2&amp;search=code+userdefined">quick
1182
+ search of the ExifTool forum</a> should reveal a number of user-defined tag
1183
+ examples, and there are other good (and often more complex) examples which can
1184
+ be found in the %Image::ExifTool::Exif::Composite hash of the
1185
+ lib/Image/ExifTool/Exif.pm source code.
1186
+ </blockquote>
1187
+
1188
+ <a name="Q20"></a>
1189
+ <p>20. <b>"ExifTool won't write an image due to errors"</b></p>
1190
+
1191
+ <blockquote>Minor errors may be ignored using the <code>-m</code> option
1192
+ (<a href="#Q15">FAQ 15</a> discusses this with respect to MakerNote errors), but
1193
+ sometimes there are more serious errors which can't be ignored. ExifTool may be
1194
+ used to fix metadata problems in JPEG images by deleting all metadata and
1195
+ rebuilding it from scratch. The command looks like this:
1196
+
1197
+ <pre>exiftool -all= -tagsfromfile @ -all:all -unsafe bad.jpg
1198
+ </pre>
1199
+
1200
+ where "<code>bad.jpg</code>" is the name of the image that requires fixing. This
1201
+ command deletes all metadata then copies all writable tags that can be extracted
1202
+ from the original image to the same locations in the updated image. The
1203
+ "<code>Unsafe</code>" tag is a <a href="TagNames/Shortcuts.html">shortcut</a>
1204
+ for unsafe EXIF tags in JPEG images which are not normally copied.</blockquote>
1205
+
1206
+ <blockquote>After repairing an image like this you should be able to write to it
1207
+ without errors, but note that <u>some metadata from the original image may have
1208
+ been lost in the process</u>.</blockquote>
1209
+
1210
+ <blockquote><b>Note</b>: ExifTool will not modify the JPEG image data, so if the
1211
+ image itself is corrupted (ie. if you get a message saying "Not a valid JPEG"),
1212
+ then ExifTool can not be used to repair the image.</blockquote>
1213
+
1214
+ <blockquote>If there are also MakerNote problems in the file, you may want to
1215
+ add the <code>-F</code> option to the command. See <a href='#Q15'>FAQ 15</a>
1216
+ for details. For example, to rebuild the EXIF only and fix the MakerNote
1217
+ offsets you could do this:
1218
+
1219
+ <pre>exiftool -exif:all= -tagsfromfile @ -exif:all -unsafe -thumbnailimage -F bad.jpg
1220
+ </pre>
1221
+
1222
+ <b>Advanced</b>: The byte order of the newly created EXIF is set by the value of
1223
+ the ExifByteOrder tag. Since this tag does not belong to the EXIF group, it is
1224
+ not copied with <code>-exif:all</code> above (but would be copied with
1225
+ <code>-all:all</code> as in the first example). If ExifByteOrder is not set
1226
+ then the byte order is determined by the ordering of the MakerNotes if they are
1227
+ copied, otherwise big-endian ("MM") byte order is used by default.
1228
+ ExifByteOrder may be set to a specific value to force a particular byte order
1229
+ when creating new EXIF (ie. "<code>-ExifByteOrder=II</code>" for little-endian).
1230
+ </blockquote>
1231
+
1232
+ <a name="Q21"></a>
1233
+ <p>21. <b>"How do I read/write values containing newline characters?"</b></p>
1234
+
1235
+ <blockquote>When reading, by default exiftool converts all control characters to
1236
+ "." to avoid messing up the output formatting, so newlines will appear as a "."
1237
+ in the output. The <code>-b</code> option may be used to bypass all output
1238
+ formatting (except that a line-feed character is inserted between items in a
1239
+ list), but this may not be appropriate when the values of many tags must be
1240
+ extracted. In this case, the formatted output (<code>-p</code>), JSON
1241
+ (<code>-j</code>), XML (<code>-X</code>) and PHP (<code>-php</code>) options
1242
+ provide alternative output formats which preserve newlines in values.</blockquote>
1243
+
1244
+ <blockquote>When writing, there are a number of options:
1245
+
1246
+ <ol type='a'>
1247
+ <li>In many shells, a newline may be inserted directly in the command
1248
+ line:
1249
+ <p>Bourne shells (press <i>RETURN</i> inside a quoted string)</p>
1250
+ <pre>exiftool -comment="line 1
1251
+ line 2" image.jpg
1252
+ </pre>
1253
+ <p>(Also, in Bourne shells the character sequence <code>$'\n'</code>
1254
+ may be used for a newline.)</p>
1255
+ <p>C shells (press "<code>\</code>" then <i>RETURN</i> inside a quoted string)</p>
1256
+ <pre>exiftool -comment="line 1\
1257
+ line 2" image.jpg
1258
+ </pre>
1259
+ <i class=lt>[Unfortunately the Windows cmd shell provides no method to get a
1260
+ newline (CR/LF in Windows) into the command line. A linefeed (LF) may be
1261
+ inserted with CTRL-T, but I have found no way to insert a carriage return
1262
+ (CR).]</i><br><br>
1263
+ </li>
1264
+ <li>Use the <code>-E</code> option to allow HTML character entities (Note:
1265
+ In Windows a newline is "<code>&amp;#xd;&amp;#xa;</code>" instead of just
1266
+ "<code>&amp;#xa;</code>"):
1267
+ <pre>exiftool -E "-comment=line 1&amp;#xa;line 2" image.jpg
1268
+ </pre></li>
1269
+ <li>Write the tag from the contents of a separate text file:
1270
+ <pre>exiftool "-comment&lt;=file.txt" image.jpg
1271
+ </pre></li>
1272
+ <li>Use <code>$/</code> in a redirection expression: (Note: Single quotes
1273
+ must be used in Mac/Linux shells around arguments containing a dollar sign,
1274
+ but double quotes are used instead in Windows. Also note that this technique
1275
+ is slower since the implied <code>-tagsFromFile</code> adds an extra unnecessary
1276
+ processing pass to read tags from the file.)
1277
+ <pre>exiftool '-comment&lt;line 1$/line 2' image.jpg
1278
+ </pre></li>
1279
+ </ol>
1280
+ </blockquote>
1281
+
1282
+ <a name="Q22"></a>
1283
+ <p>22. <b>"In what order are command-line assignments applied when writing?"</b></p>
1284
+
1285
+ <blockquote>When writing, tag assignments on the command line are queued and
1286
+ applied together as each target file is processed. In general, assignments
1287
+ later on the command line override earlier assignments, but there are
1288
+ exceptions:
1289
+ <ol><li>When writing list-type tags (ie. <code>-keywords=one</code>), new values
1290
+ are accumulated rather than overriding earlier assignments.<br>&nbsp;</li>
1291
+ <li>When copying values to list-type tags (ie.
1292
+ <code>"-keywords&lt;filename"</code>), new values are accumulated only if
1293
+ <code>-addTagsFromFile</code> is used, otherwise they override earlier
1294
+ assigments if <code>-tagsFromFile</code> is used or implied.<br>&nbsp;</li>
1295
+ <li>Tags copied with the <code>-tagsFromFile</code> option are assigned in
1296
+ order, and all together at the point in the command line where the
1297
+ <code>-tagsFromFile</code> option is located, regardless of whether these tags
1298
+ are specified immediately after the <code>-tagsFromFile</code> option or later
1299
+ on the command line. Remember that "<code>-tagsFromFile @</code>" is implied
1300
+ unless another file is specified when redirecting information with arguments
1301
+ like <code>"-DSTTAG&lt;SRCTAG"</code>.</li></ol> Note: When copying tag values,
1302
+ adding to lists, or shifting date/time values, the source value is always the
1303
+ original value found in the file, regardless of any previous assignments. For
1304
+ example, the following command sets Subject to the original value of Title in
1305
+ the file (NOT to "test"):
1306
+ <pre>exiftool -title=test "-subject&lt;title" a.jpg</pre></blockquote>
1307
+
1308
+ <a name="Q23"></a>
1309
+ <p>23a. <b>"Why do I get '<code>0 image files updated</code>' when writing?"</b>, or<br>
1310
+ 23b. <b>"ExifTool doesn't write some tags to a file"</b></p>
1311
+
1312
+ <blockquote>There are a few reasons why this may happen:
1313
+
1314
+ <ol><li>The value of the tag is not being set correctly.</li></ol>
1315
+
1316
+ This may be due to a tag value which can't be converted, in which case you
1317
+ should warning like this (note: you may need to use the <code>-v3</code> option
1318
+ to see the warning if other same-named tags are being set properly by the same
1319
+ assignment):
1320
+ <pre>Warning: Can't convert IFD0:Orientation (not in PrintConv)
1321
+ </pre>
1322
+ You get this warning if you write an invalid value to a tag which accepts only
1323
+ specific values. See the "Values" column in the appropriate table of the
1324
+ <a href="TagNames/index.html">tag name documentation</a> for a list of valid
1325
+ values for these types of tags. The value conversion may also be bypassed with
1326
+ the <code>-n</code> option, allowing numerical values to be written directly.
1327
+ See <a href="#Q6">FAQ number 6</a> for more details.
1328
+
1329
+ <ol start="2"><li>The information type isn't supported by the format of the
1330
+ target file.</li></ol>
1331
+
1332
+ Warnings are NOT generated when a tag isn't written because it is
1333
+ normal that many tags can't be written when copying between files of different
1334
+ formats.</blockquote>
1335
+
1336
+ <blockquote>Tags are not written if the format of the target file doesn't
1337
+ support the specific type of meta information. For example, CRW images do not
1338
+ support EXIF or IPTC metdata. Follow the links in the
1339
+ <a href="index.html#supported">Supported File Types</a> table for an indication
1340
+ of the tags supported by your file. If the tags aren't supported for your file
1341
+ type, then a <a href='metafiles.html'>metadata sidecar file</a> is an
1342
+ alternative.</blockquote>
1343
+
1344
+ <blockquote>Also note that MakerNotes tags can not be created or deleted
1345
+ individually, so they can only be written if they already exist in a
1346
+ file. The entire MakerNotes must be created or deleted as a block (see
1347
+ <a href="#Q8">FAQ number 8</a> for details).
1348
+
1349
+ <ol start="3"><li>A time value is being shifted but the specified tag doesn't
1350
+ exist.</li></ol>
1351
+
1352
+ For example, <code>-datetimeoriginal+=1</code> will have no effect unless
1353
+ the DateTimeOriginal tag exists in the image.</blockquote>
1354
+
1355
+ <a name="Q24"></a>
1356
+ <p>24. <b>"When I write a file the date/time gets reset to today's date"</b></p>
1357
+
1358
+ <blockquote>There is sometimes confusion between date/time values stored in the
1359
+ metadata of the file itself and date/time values stored in the filesystem (ie.
1360
+ in the disk directory information). A command like this may be used to extract
1361
+ all date/time information with an indication of where it is stored:
1362
+
1363
+ <pre>exiftool -time:all -a -G0:1 -s c:\images\test.jpg</pre>
1364
+
1365
+ and should give an output something like this:
1366
+
1367
+ <pre>[File:System] FileModifyDate : 2009:10:05 20:40:36-04:00
1368
+ [File:System] FileAccessDate : 2009:10:07 09:22:12-04:00
1369
+ [File:System] FileCreateDate : 2009:10:05 20:40:36-04:00
1370
+ [EXIF:IFD0] ModifyDate : 2003:10:31 15:44:19
1371
+ [EXIF:ExifIFD] DateTimeOriginal : 2003:10:31 15:44:19
1372
+ [EXIF:ExifIFD] CreateDate : 2003:10:31 15:44:19</pre>
1373
+
1374
+ The <code>-G0:1</code> option causes the family 0 and 1 group names to be
1375
+ reported in square brackets for each tag. Tags labelled "File:System" are
1376
+ stored in the filesystem, while other tags are stored in the location indicated
1377
+ inside the metadata of the file itself.</blockquote>
1378
+
1379
+ <blockquote>ExifTool's <b>default behaviour is to set all filesystem times to
1380
+ the current date/time when writing</b>, but the <code>-P</code> option may be
1381
+ used to preserve the original FileModifyDate. FileAccessDate represents the time
1382
+ the file was last accessed, and is set to the current date/time whenever any
1383
+ software (including ExifTool) accesses the file.</blockquote>
1384
+
1385
+ <blockquote>On systems where a filesystem creation date is maintained, ExifTool
1386
+ also sets this to the current date/time when the file is edited. On Windows the
1387
+ creation date is accessed through the FileCreateDate tag, and is also preserved
1388
+ with the <code>-P</code> option if Win32API::File::Time is available. On
1389
+ Mac/Linux FileInodeChangeDate is available instead of FileCreateDate, and the
1390
+ only way to preserve the file creation date is with the
1391
+ <code>-overwrite_original_in_place</code> option.</blockquote>
1392
+
1393
+ <blockquote>For example, commands like this act on common metadata tags, setting
1394
+ the filesystem modification date/time to the current date/time:
1395
+
1396
+ <pre><span class='blk'># common metadata date/time tags are incremented by 1 hour, while
1397
+ # FileModifyDate is set to the current date/time</span>
1398
+ exiftool -alldates+=1 c:\images</pre>
1399
+
1400
+ <i class=lt>[The AllDates tag is a shortcut which represents the 3 common
1401
+ metadata date/time tags: DateTimeOriginal, CreateDate and
1402
+ ModifyDate.]</i></blockquote>
1403
+
1404
+ <blockquote>However, FileModifyDate may be preserved with the <code>-P</code>
1405
+ option:
1406
+
1407
+ <pre><span class='blk'># FileModifyDate is not changed</span>
1408
+ exiftool -alldates+=1 -P c:\images</pre>
1409
+
1410
+ ExifTool also allows FileModifyDate to be written, which provides full control
1411
+ over the filesystem modification date/time when writing:
1412
+
1413
+ <pre><span class='blk'># FileModifyDate is incremented by 1 hour</span>
1414
+ exiftool -alldates+=1 -filemodifydate+=1 c:\images
1415
+
1416
+ <span class='blk'># FileModifyDate is set from the value of DateTimeOriginal
1417
+ # (before DateTimeOriginal is incremented by 1 hour)</span>
1418
+ exiftool -alldates+=1 "-filemodifydate&lt;datetimeoriginal" c:\images
1419
+ </pre></blockquote>
1420
+
1421
+ <a name="Q25"></a>
1422
+ <p>25. <b>"Can ExifTool be used as an image validator?"</b></p>
1423
+
1424
+ <blockquote>ExifTool is <u>not</u> designed as an image validator. It does issue
1425
+ warnings about some of the more important problems in the metadata when
1426
+ reading, and will often catch more problems when writing, but it does not
1427
+ attempt to do a full validation. If you are looking for a validator,
1428
+ try <a href="http://jhove.sourceforge.net">JHOVE</a>.</blockquote>
1429
+
1430
+ <hr>
1431
+ <i>Last revised June 25, 2013</i>
1432
+ <p class='lf'><a href="index.html">&lt;-- Back to ExifTool home page</a></p>
1433
+ </body>
1434
+ </html>