README.ijg 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280
  1. libjpeg-turbo note: This file has been modified by The libjpeg-turbo Project
  2. to include only information relevant to libjpeg-turbo, to wordsmith certain
  3. sections, and to remove impolitic language that existed in the libjpeg v8
  4. README. It is included only for reference. Please see README.md for
  5. information specific to libjpeg-turbo.
  6. The Independent JPEG Group's JPEG software
  7. ==========================================
  8. This distribution contains a release of the Independent JPEG Group's free JPEG
  9. software. You are welcome to redistribute this software and to use it for any
  10. purpose, subject to the conditions under LEGAL ISSUES, below.
  11. This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
  12. Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
  13. Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
  14. and other members of the Independent JPEG Group.
  15. IJG is not affiliated with the ISO/IEC JTC1/SC29/WG1 standards committee
  16. (also known as JPEG, together with ITU-T SG16).
  17. DOCUMENTATION ROADMAP
  18. =====================
  19. This file contains the following sections:
  20. OVERVIEW General description of JPEG and the IJG software.
  21. LEGAL ISSUES Copyright, lack of warranty, terms of distribution.
  22. REFERENCES Where to learn more about JPEG.
  23. ARCHIVE LOCATIONS Where to find newer versions of this software.
  24. FILE FORMAT WARS Software *not* to get.
  25. TO DO Plans for future IJG releases.
  26. Other documentation files in the distribution are:
  27. User documentation:
  28. usage.txt Usage instructions for cjpeg, djpeg, jpegtran,
  29. rdjpgcom, and wrjpgcom.
  30. *.1 Unix-style man pages for programs (same info as usage.txt).
  31. wizard.txt Advanced usage instructions for JPEG wizards only.
  32. change.log Version-to-version change highlights.
  33. Programmer and internal documentation:
  34. libjpeg.txt How to use the JPEG library in your own programs.
  35. example.c Sample code for calling the JPEG library.
  36. structure.txt Overview of the JPEG library's internal structure.
  37. coderules.txt Coding style rules --- please read if you contribute code.
  38. Please read at least usage.txt. Some information can also be found in the JPEG
  39. FAQ (Frequently Asked Questions) article. See ARCHIVE LOCATIONS below to find
  40. out where to obtain the FAQ article.
  41. If you want to understand how the JPEG code works, we suggest reading one or
  42. more of the REFERENCES, then looking at the documentation files (in roughly
  43. the order listed) before diving into the code.
  44. OVERVIEW
  45. ========
  46. This package contains C software to implement JPEG image encoding, decoding,
  47. and transcoding. JPEG (pronounced "jay-peg") is a standardized compression
  48. method for full-color and grayscale images. JPEG's strong suit is compressing
  49. photographic images or other types of images that have smooth color and
  50. brightness transitions between neighboring pixels. Images with sharp lines or
  51. other abrupt features may not compress well with JPEG, and a higher JPEG
  52. quality may have to be used to avoid visible compression artifacts with such
  53. images.
  54. JPEG is lossy, meaning that the output pixels are not necessarily identical to
  55. the input pixels. However, on photographic content and other "smooth" images,
  56. very good compression ratios can be obtained with no visible compression
  57. artifacts, and extremely high compression ratios are possible if you are
  58. willing to sacrifice image quality (by reducing the "quality" setting in the
  59. compressor.)
  60. This software implements JPEG baseline, extended-sequential, and progressive
  61. compression processes. Provision is made for supporting all variants of these
  62. processes, although some uncommon parameter settings aren't implemented yet.
  63. We have made no provision for supporting the hierarchical or lossless
  64. processes defined in the standard.
  65. We provide a set of library routines for reading and writing JPEG image files,
  66. plus two sample applications "cjpeg" and "djpeg", which use the library to
  67. perform conversion between JPEG and some other popular image file formats.
  68. The library is intended to be reused in other applications.
  69. In order to support file conversion and viewing software, we have included
  70. considerable functionality beyond the bare JPEG coding/decoding capability;
  71. for example, the color quantization modules are not strictly part of JPEG
  72. decoding, but they are essential for output to colormapped file formats or
  73. colormapped displays. These extra functions can be compiled out of the
  74. library if not required for a particular application.
  75. We have also included "jpegtran", a utility for lossless transcoding between
  76. different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple
  77. applications for inserting and extracting textual comments in JFIF files.
  78. The emphasis in designing this software has been on achieving portability and
  79. flexibility, while also making it fast enough to be useful. In particular,
  80. the software is not intended to be read as a tutorial on JPEG. (See the
  81. REFERENCES section for introductory material.) Rather, it is intended to
  82. be reliable, portable, industrial-strength code. We do not claim to have
  83. achieved that goal in every aspect of the software, but we strive for it.
  84. We welcome the use of this software as a component of commercial products.
  85. No royalty is required, but we do ask for an acknowledgement in product
  86. documentation, as described under LEGAL ISSUES.
  87. LEGAL ISSUES
  88. ============
  89. In plain English:
  90. 1. We don't promise that this software works. (But if you find any bugs,
  91. please let us know!)
  92. 2. You can use this software for whatever you want. You don't have to pay us.
  93. 3. You may not pretend that you wrote this software. If you use it in a
  94. program, you must acknowledge somewhere in your documentation that
  95. you've used the IJG code.
  96. In legalese:
  97. The authors make NO WARRANTY or representation, either express or implied,
  98. with respect to this software, its quality, accuracy, merchantability, or
  99. fitness for a particular purpose. This software is provided "AS IS", and you,
  100. its user, assume the entire risk as to its quality and accuracy.
  101. This software is copyright (C) 1991-2016, Thomas G. Lane, Guido Vollbeding.
  102. All Rights Reserved except as specified below.
  103. Permission is hereby granted to use, copy, modify, and distribute this
  104. software (or portions thereof) for any purpose, without fee, subject to these
  105. conditions:
  106. (1) If any part of the source code for this software is distributed, then this
  107. README file must be included, with this copyright and no-warranty notice
  108. unaltered; and any additions, deletions, or changes to the original files
  109. must be clearly indicated in accompanying documentation.
  110. (2) If only executable code is distributed, then the accompanying
  111. documentation must state that "this software is based in part on the work of
  112. the Independent JPEG Group".
  113. (3) Permission for use of this software is granted only if the user accepts
  114. full responsibility for any undesirable consequences; the authors accept
  115. NO LIABILITY for damages of any kind.
  116. These conditions apply to any software derived from or based on the IJG code,
  117. not just to the unmodified library. If you use our work, you ought to
  118. acknowledge us.
  119. Permission is NOT granted for the use of any IJG author's name or company name
  120. in advertising or publicity relating to this software or products derived from
  121. it. This software may be referred to only as "the Independent JPEG Group's
  122. software".
  123. We specifically permit and encourage the use of this software as the basis of
  124. commercial products, provided that all warranty or liability claims are
  125. assumed by the product vendor.
  126. The Unix configuration script "configure" was produced with GNU Autoconf.
  127. It is copyright by the Free Software Foundation but is freely distributable.
  128. The same holds for its supporting scripts (config.guess, config.sub,
  129. ltmain.sh). Another support script, install-sh, is copyright by X Consortium
  130. but is also freely distributable.
  131. The IJG distribution formerly included code to read and write GIF files.
  132. To avoid entanglement with the Unisys LZW patent (now expired), GIF reading
  133. support has been removed altogether, and the GIF writer has been simplified
  134. to produce "uncompressed GIFs". This technique does not use the LZW
  135. algorithm; the resulting GIF files are larger than usual, but are readable
  136. by all standard GIF decoders.
  137. We are required to state that
  138. "The Graphics Interchange Format(c) is the Copyright property of
  139. CompuServe Incorporated. GIF(sm) is a Service Mark property of
  140. CompuServe Incorporated."
  141. REFERENCES
  142. ==========
  143. We recommend reading one or more of these references before trying to
  144. understand the innards of the JPEG software.
  145. The best short technical introduction to the JPEG compression algorithm is
  146. Wallace, Gregory K. "The JPEG Still Picture Compression Standard",
  147. Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.
  148. (Adjacent articles in that issue discuss MPEG motion picture compression,
  149. applications of JPEG, and related topics.) If you don't have the CACM issue
  150. handy, a PDF file containing a revised version of Wallace's article is
  151. available at http://www.ijg.org/files/Wallace.JPEG.pdf. The file (actually
  152. a preprint for an article that appeared in IEEE Trans. Consumer Electronics)
  153. omits the sample images that appeared in CACM, but it includes corrections
  154. and some added material. Note: the Wallace article is copyright ACM and IEEE,
  155. and it may not be used for commercial purposes.
  156. A somewhat less technical, more leisurely introduction to JPEG can be found in
  157. "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
  158. M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides
  159. good explanations and example C code for a multitude of compression methods
  160. including JPEG. It is an excellent source if you are comfortable reading C
  161. code but don't know much about data compression in general. The book's JPEG
  162. sample code is far from industrial-strength, but when you are ready to look
  163. at a full implementation, you've got one here...
  164. The best currently available description of JPEG is the textbook "JPEG Still
  165. Image Data Compression Standard" by William B. Pennebaker and Joan L.
  166. Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.
  167. Price US$59.95, 638 pp. The book includes the complete text of the ISO JPEG
  168. standards (DIS 10918-1 and draft DIS 10918-2).
  169. The original JPEG standard is divided into two parts, Part 1 being the actual
  170. specification, while Part 2 covers compliance testing methods. Part 1 is
  171. titled "Digital Compression and Coding of Continuous-tone Still Images,
  172. Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
  173. 10918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of
  174. Continuous-tone Still Images, Part 2: Compliance testing" and has document
  175. numbers ISO/IEC IS 10918-2, ITU-T T.83.
  176. The JPEG standard does not specify all details of an interchangeable file
  177. format. For the omitted details we follow the "JFIF" conventions, revision
  178. 1.02. JFIF 1.02 has been adopted as an Ecma International Technical Report
  179. and thus received a formal publication status. It is available as a free
  180. download in PDF format from
  181. http://www.ecma-international.org/publications/techreports/E-TR-098.htm.
  182. A PostScript version of the JFIF document is available at
  183. http://www.ijg.org/files/jfif.ps.gz. There is also a plain text version at
  184. http://www.ijg.org/files/jfif.txt.gz, but it is missing the figures.
  185. The TIFF 6.0 file format specification can be obtained by FTP from
  186. ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation scheme
  187. found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems.
  188. IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).
  189. Instead, we recommend the JPEG design proposed by TIFF Technical Note #2
  190. (Compression tag 7). Copies of this Note can be obtained from
  191. http://www.ijg.org/files/. It is expected that the next revision
  192. of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
  193. Although IJG's own code does not support TIFF/JPEG, the free libtiff library
  194. uses our library to implement TIFF/JPEG per the Note.
  195. ARCHIVE LOCATIONS
  196. =================
  197. The "official" archive site for this software is www.ijg.org.
  198. The most recent released version can always be found there in
  199. directory "files".
  200. The JPEG FAQ (Frequently Asked Questions) article is a source of some
  201. general information about JPEG.
  202. It is available on the World Wide Web at http://www.faqs.org/faqs/jpeg-faq/
  203. and other news.answers archive sites, including the official news.answers
  204. archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/.
  205. If you don't have Web or FTP access, send e-mail to mail-server@rtfm.mit.edu
  206. with body
  207. send usenet/news.answers/jpeg-faq/part1
  208. send usenet/news.answers/jpeg-faq/part2
  209. FILE FORMAT WARS
  210. ================
  211. The ISO/IEC JTC1/SC29/WG1 standards committee (also known as JPEG, together
  212. with ITU-T SG16) currently promotes different formats containing the name
  213. "JPEG" which are incompatible with original DCT-based JPEG. IJG therefore does
  214. not support these formats (see REFERENCES). Indeed, one of the original
  215. reasons for developing this free software was to help force convergence on
  216. common, interoperable format standards for JPEG files.
  217. Don't use an incompatible file format!
  218. (In any case, our decoder will remain capable of reading existing JPEG
  219. image files indefinitely.)
  220. TO DO
  221. =====
  222. Please send bug reports, offers of help, etc. to jpeg-info@jpegclub.org.