dbf-halloween2015

annotate libs/libjpeg/README @ 1:c3f5c32cb210

barfed all the libraries in the source tree to make porting easier
author John Tsiombikas <nuclear@member.fsf.org>
date Sun, 01 Nov 2015 00:36:56 +0200
parents
children
rev   line source
nuclear@1 1 The Independent JPEG Group's JPEG software
nuclear@1 2 ==========================================
nuclear@1 3
nuclear@1 4 README for release 8c of 16-Jan-2011
nuclear@1 5 ====================================
nuclear@1 6
nuclear@1 7 This distribution contains the eighth public release of the Independent JPEG
nuclear@1 8 Group's free JPEG software. You are welcome to redistribute this software and
nuclear@1 9 to use it for any purpose, subject to the conditions under LEGAL ISSUES, below.
nuclear@1 10
nuclear@1 11 This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
nuclear@1 12 Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
nuclear@1 13 Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
nuclear@1 14 and other members of the Independent JPEG Group.
nuclear@1 15
nuclear@1 16 IJG is not affiliated with the official ISO JPEG standards committee.
nuclear@1 17
nuclear@1 18
nuclear@1 19 DOCUMENTATION ROADMAP
nuclear@1 20 =====================
nuclear@1 21
nuclear@1 22 This file contains the following sections:
nuclear@1 23
nuclear@1 24 OVERVIEW General description of JPEG and the IJG software.
nuclear@1 25 LEGAL ISSUES Copyright, lack of warranty, terms of distribution.
nuclear@1 26 REFERENCES Where to learn more about JPEG.
nuclear@1 27 ARCHIVE LOCATIONS Where to find newer versions of this software.
nuclear@1 28 ACKNOWLEDGMENTS Special thanks.
nuclear@1 29 FILE FORMAT WARS Software *not* to get.
nuclear@1 30 TO DO Plans for future IJG releases.
nuclear@1 31
nuclear@1 32 Other documentation files in the distribution are:
nuclear@1 33
nuclear@1 34 User documentation:
nuclear@1 35 install.txt How to configure and install the IJG software.
nuclear@1 36 usage.txt Usage instructions for cjpeg, djpeg, jpegtran,
nuclear@1 37 rdjpgcom, and wrjpgcom.
nuclear@1 38 *.1 Unix-style man pages for programs (same info as usage.txt).
nuclear@1 39 wizard.txt Advanced usage instructions for JPEG wizards only.
nuclear@1 40 change.log Version-to-version change highlights.
nuclear@1 41 Programmer and internal documentation:
nuclear@1 42 libjpeg.txt How to use the JPEG library in your own programs.
nuclear@1 43 example.c Sample code for calling the JPEG library.
nuclear@1 44 structure.txt Overview of the JPEG library's internal structure.
nuclear@1 45 filelist.txt Road map of IJG files.
nuclear@1 46 coderules.txt Coding style rules --- please read if you contribute code.
nuclear@1 47
nuclear@1 48 Please read at least the files install.txt and usage.txt. Some information
nuclear@1 49 can also be found in the JPEG FAQ (Frequently Asked Questions) article. See
nuclear@1 50 ARCHIVE LOCATIONS below to find out where to obtain the FAQ article.
nuclear@1 51
nuclear@1 52 If you want to understand how the JPEG code works, we suggest reading one or
nuclear@1 53 more of the REFERENCES, then looking at the documentation files (in roughly
nuclear@1 54 the order listed) before diving into the code.
nuclear@1 55
nuclear@1 56
nuclear@1 57 OVERVIEW
nuclear@1 58 ========
nuclear@1 59
nuclear@1 60 This package contains C software to implement JPEG image encoding, decoding,
nuclear@1 61 and transcoding. JPEG (pronounced "jay-peg") is a standardized compression
nuclear@1 62 method for full-color and gray-scale images.
nuclear@1 63
nuclear@1 64 This software implements JPEG baseline, extended-sequential, and progressive
nuclear@1 65 compression processes. Provision is made for supporting all variants of these
nuclear@1 66 processes, although some uncommon parameter settings aren't implemented yet.
nuclear@1 67 We have made no provision for supporting the hierarchical or lossless
nuclear@1 68 processes defined in the standard.
nuclear@1 69
nuclear@1 70 We provide a set of library routines for reading and writing JPEG image files,
nuclear@1 71 plus two sample applications "cjpeg" and "djpeg", which use the library to
nuclear@1 72 perform conversion between JPEG and some other popular image file formats.
nuclear@1 73 The library is intended to be reused in other applications.
nuclear@1 74
nuclear@1 75 In order to support file conversion and viewing software, we have included
nuclear@1 76 considerable functionality beyond the bare JPEG coding/decoding capability;
nuclear@1 77 for example, the color quantization modules are not strictly part of JPEG
nuclear@1 78 decoding, but they are essential for output to colormapped file formats or
nuclear@1 79 colormapped displays. These extra functions can be compiled out of the
nuclear@1 80 library if not required for a particular application.
nuclear@1 81
nuclear@1 82 We have also included "jpegtran", a utility for lossless transcoding between
nuclear@1 83 different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple
nuclear@1 84 applications for inserting and extracting textual comments in JFIF files.
nuclear@1 85
nuclear@1 86 The emphasis in designing this software has been on achieving portability and
nuclear@1 87 flexibility, while also making it fast enough to be useful. In particular,
nuclear@1 88 the software is not intended to be read as a tutorial on JPEG. (See the
nuclear@1 89 REFERENCES section for introductory material.) Rather, it is intended to
nuclear@1 90 be reliable, portable, industrial-strength code. We do not claim to have
nuclear@1 91 achieved that goal in every aspect of the software, but we strive for it.
nuclear@1 92
nuclear@1 93 We welcome the use of this software as a component of commercial products.
nuclear@1 94 No royalty is required, but we do ask for an acknowledgement in product
nuclear@1 95 documentation, as described under LEGAL ISSUES.
nuclear@1 96
nuclear@1 97
nuclear@1 98 LEGAL ISSUES
nuclear@1 99 ============
nuclear@1 100
nuclear@1 101 In plain English:
nuclear@1 102
nuclear@1 103 1. We don't promise that this software works. (But if you find any bugs,
nuclear@1 104 please let us know!)
nuclear@1 105 2. You can use this software for whatever you want. You don't have to pay us.
nuclear@1 106 3. You may not pretend that you wrote this software. If you use it in a
nuclear@1 107 program, you must acknowledge somewhere in your documentation that
nuclear@1 108 you've used the IJG code.
nuclear@1 109
nuclear@1 110 In legalese:
nuclear@1 111
nuclear@1 112 The authors make NO WARRANTY or representation, either express or implied,
nuclear@1 113 with respect to this software, its quality, accuracy, merchantability, or
nuclear@1 114 fitness for a particular purpose. This software is provided "AS IS", and you,
nuclear@1 115 its user, assume the entire risk as to its quality and accuracy.
nuclear@1 116
nuclear@1 117 This software is copyright (C) 1991-2011, Thomas G. Lane, Guido Vollbeding.
nuclear@1 118 All Rights Reserved except as specified below.
nuclear@1 119
nuclear@1 120 Permission is hereby granted to use, copy, modify, and distribute this
nuclear@1 121 software (or portions thereof) for any purpose, without fee, subject to these
nuclear@1 122 conditions:
nuclear@1 123 (1) If any part of the source code for this software is distributed, then this
nuclear@1 124 README file must be included, with this copyright and no-warranty notice
nuclear@1 125 unaltered; and any additions, deletions, or changes to the original files
nuclear@1 126 must be clearly indicated in accompanying documentation.
nuclear@1 127 (2) If only executable code is distributed, then the accompanying
nuclear@1 128 documentation must state that "this software is based in part on the work of
nuclear@1 129 the Independent JPEG Group".
nuclear@1 130 (3) Permission for use of this software is granted only if the user accepts
nuclear@1 131 full responsibility for any undesirable consequences; the authors accept
nuclear@1 132 NO LIABILITY for damages of any kind.
nuclear@1 133
nuclear@1 134 These conditions apply to any software derived from or based on the IJG code,
nuclear@1 135 not just to the unmodified library. If you use our work, you ought to
nuclear@1 136 acknowledge us.
nuclear@1 137
nuclear@1 138 Permission is NOT granted for the use of any IJG author's name or company name
nuclear@1 139 in advertising or publicity relating to this software or products derived from
nuclear@1 140 it. This software may be referred to only as "the Independent JPEG Group's
nuclear@1 141 software".
nuclear@1 142
nuclear@1 143 We specifically permit and encourage the use of this software as the basis of
nuclear@1 144 commercial products, provided that all warranty or liability claims are
nuclear@1 145 assumed by the product vendor.
nuclear@1 146
nuclear@1 147
nuclear@1 148 ansi2knr.c is included in this distribution by permission of L. Peter Deutsch,
nuclear@1 149 sole proprietor of its copyright holder, Aladdin Enterprises of Menlo Park, CA.
nuclear@1 150 ansi2knr.c is NOT covered by the above copyright and conditions, but instead
nuclear@1 151 by the usual distribution terms of the Free Software Foundation; principally,
nuclear@1 152 that you must include source code if you redistribute it. (See the file
nuclear@1 153 ansi2knr.c for full details.) However, since ansi2knr.c is not needed as part
nuclear@1 154 of any program generated from the IJG code, this does not limit you more than
nuclear@1 155 the foregoing paragraphs do.
nuclear@1 156
nuclear@1 157 The Unix configuration script "configure" was produced with GNU Autoconf.
nuclear@1 158 It is copyright by the Free Software Foundation but is freely distributable.
nuclear@1 159 The same holds for its supporting scripts (config.guess, config.sub,
nuclear@1 160 ltmain.sh). Another support script, install-sh, is copyright by X Consortium
nuclear@1 161 but is also freely distributable.
nuclear@1 162
nuclear@1 163 The IJG distribution formerly included code to read and write GIF files.
nuclear@1 164 To avoid entanglement with the Unisys LZW patent, GIF reading support has
nuclear@1 165 been removed altogether, and the GIF writer has been simplified to produce
nuclear@1 166 "uncompressed GIFs". This technique does not use the LZW algorithm; the
nuclear@1 167 resulting GIF files are larger than usual, but are readable by all standard
nuclear@1 168 GIF decoders.
nuclear@1 169
nuclear@1 170 We are required to state that
nuclear@1 171 "The Graphics Interchange Format(c) is the Copyright property of
nuclear@1 172 CompuServe Incorporated. GIF(sm) is a Service Mark property of
nuclear@1 173 CompuServe Incorporated."
nuclear@1 174
nuclear@1 175
nuclear@1 176 REFERENCES
nuclear@1 177 ==========
nuclear@1 178
nuclear@1 179 We recommend reading one or more of these references before trying to
nuclear@1 180 understand the innards of the JPEG software.
nuclear@1 181
nuclear@1 182 The best short technical introduction to the JPEG compression algorithm is
nuclear@1 183 Wallace, Gregory K. "The JPEG Still Picture Compression Standard",
nuclear@1 184 Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.
nuclear@1 185 (Adjacent articles in that issue discuss MPEG motion picture compression,
nuclear@1 186 applications of JPEG, and related topics.) If you don't have the CACM issue
nuclear@1 187 handy, a PostScript file containing a revised version of Wallace's article is
nuclear@1 188 available at http://www.ijg.org/files/wallace.ps.gz. The file (actually
nuclear@1 189 a preprint for an article that appeared in IEEE Trans. Consumer Electronics)
nuclear@1 190 omits the sample images that appeared in CACM, but it includes corrections
nuclear@1 191 and some added material. Note: the Wallace article is copyright ACM and IEEE,
nuclear@1 192 and it may not be used for commercial purposes.
nuclear@1 193
nuclear@1 194 A somewhat less technical, more leisurely introduction to JPEG can be found in
nuclear@1 195 "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
nuclear@1 196 M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides
nuclear@1 197 good explanations and example C code for a multitude of compression methods
nuclear@1 198 including JPEG. It is an excellent source if you are comfortable reading C
nuclear@1 199 code but don't know much about data compression in general. The book's JPEG
nuclear@1 200 sample code is far from industrial-strength, but when you are ready to look
nuclear@1 201 at a full implementation, you've got one here...
nuclear@1 202
nuclear@1 203 The best currently available description of JPEG is the textbook "JPEG Still
nuclear@1 204 Image Data Compression Standard" by William B. Pennebaker and Joan L.
nuclear@1 205 Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.
nuclear@1 206 Price US$59.95, 638 pp. The book includes the complete text of the ISO JPEG
nuclear@1 207 standards (DIS 10918-1 and draft DIS 10918-2).
nuclear@1 208 Although this is by far the most detailed and comprehensive exposition of
nuclear@1 209 JPEG publicly available, we point out that it is still missing an explanation
nuclear@1 210 of the most essential properties and algorithms of the underlying DCT
nuclear@1 211 technology.
nuclear@1 212 If you think that you know about DCT-based JPEG after reading this book,
nuclear@1 213 then you are in delusion. The real fundamentals and corresponding potential
nuclear@1 214 of DCT-based JPEG are not publicly known so far, and that is the reason for
nuclear@1 215 all the mistaken developments taking place in the image coding domain.
nuclear@1 216
nuclear@1 217 The original JPEG standard is divided into two parts, Part 1 being the actual
nuclear@1 218 specification, while Part 2 covers compliance testing methods. Part 1 is
nuclear@1 219 titled "Digital Compression and Coding of Continuous-tone Still Images,
nuclear@1 220 Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
nuclear@1 221 10918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of
nuclear@1 222 Continuous-tone Still Images, Part 2: Compliance testing" and has document
nuclear@1 223 numbers ISO/IEC IS 10918-2, ITU-T T.83.
nuclear@1 224 IJG JPEG 8 introduces an implementation of the JPEG SmartScale extension
nuclear@1 225 which is specified in a contributed document at ITU and ISO with title "ITU-T
nuclear@1 226 JPEG-Plus Proposal for Extending ITU-T T.81 for Advanced Image Coding", April
nuclear@1 227 2006, Geneva, Switzerland. The latest version of the document is Revision 3.
nuclear@1 228
nuclear@1 229 The JPEG standard does not specify all details of an interchangeable file
nuclear@1 230 format. For the omitted details we follow the "JFIF" conventions, revision
nuclear@1 231 1.02. JFIF 1.02 has been adopted as an Ecma International Technical Report
nuclear@1 232 and thus received a formal publication status. It is available as a free
nuclear@1 233 download in PDF format from
nuclear@1 234 http://www.ecma-international.org/publications/techreports/E-TR-098.htm.
nuclear@1 235 A PostScript version of the JFIF document is available at
nuclear@1 236 http://www.ijg.org/files/jfif.ps.gz. There is also a plain text version at
nuclear@1 237 http://www.ijg.org/files/jfif.txt.gz, but it is missing the figures.
nuclear@1 238
nuclear@1 239 The TIFF 6.0 file format specification can be obtained by FTP from
nuclear@1 240 ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation scheme
nuclear@1 241 found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems.
nuclear@1 242 IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).
nuclear@1 243 Instead, we recommend the JPEG design proposed by TIFF Technical Note #2
nuclear@1 244 (Compression tag 7). Copies of this Note can be obtained from
nuclear@1 245 http://www.ijg.org/files/. It is expected that the next revision
nuclear@1 246 of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
nuclear@1 247 Although IJG's own code does not support TIFF/JPEG, the free libtiff library
nuclear@1 248 uses our library to implement TIFF/JPEG per the Note.
nuclear@1 249
nuclear@1 250
nuclear@1 251 ARCHIVE LOCATIONS
nuclear@1 252 =================
nuclear@1 253
nuclear@1 254 The "official" archive site for this software is www.ijg.org.
nuclear@1 255 The most recent released version can always be found there in
nuclear@1 256 directory "files". This particular version will be archived as
nuclear@1 257 http://www.ijg.org/files/jpegsrc.v8c.tar.gz, and in Windows-compatible
nuclear@1 258 "zip" archive format as http://www.ijg.org/files/jpegsr8c.zip.
nuclear@1 259
nuclear@1 260 The JPEG FAQ (Frequently Asked Questions) article is a source of some
nuclear@1 261 general information about JPEG.
nuclear@1 262 It is available on the World Wide Web at http://www.faqs.org/faqs/jpeg-faq/
nuclear@1 263 and other news.answers archive sites, including the official news.answers
nuclear@1 264 archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/.
nuclear@1 265 If you don't have Web or FTP access, send e-mail to mail-server@rtfm.mit.edu
nuclear@1 266 with body
nuclear@1 267 send usenet/news.answers/jpeg-faq/part1
nuclear@1 268 send usenet/news.answers/jpeg-faq/part2
nuclear@1 269
nuclear@1 270
nuclear@1 271 ACKNOWLEDGMENTS
nuclear@1 272 ===============
nuclear@1 273
nuclear@1 274 Thank to Juergen Bruder for providing me with a copy of the common DCT
nuclear@1 275 algorithm article, only to find out that I had come to the same result
nuclear@1 276 in a more direct and comprehensible way with a more generative approach.
nuclear@1 277
nuclear@1 278 Thank to Istvan Sebestyen and Joan L. Mitchell for inviting me to the
nuclear@1 279 ITU JPEG (Study Group 16) meeting in Geneva, Switzerland.
nuclear@1 280
nuclear@1 281 Thank to Thomas Wiegand and Gary Sullivan for inviting me to the
nuclear@1 282 Joint Video Team (MPEG & ITU) meeting in Geneva, Switzerland.
nuclear@1 283
nuclear@1 284 Thank to John Korejwa and Massimo Ballerini for inviting me to
nuclear@1 285 fruitful consultations in Boston, MA and Milan, Italy.
nuclear@1 286
nuclear@1 287 Thank to Hendrik Elstner, Roland Fassauer, Simone Zuck, Guenther
nuclear@1 288 Maier-Gerber, Walter Stoeber, Fred Schmitz, and Norbert Braunagel
nuclear@1 289 for corresponding business development.
nuclear@1 290
nuclear@1 291 Thank to Nico Zschach and Dirk Stelling of the technical support team
nuclear@1 292 at the Digital Images company in Halle for providing me with extra
nuclear@1 293 equipment for configuration tests.
nuclear@1 294
nuclear@1 295 Thank to Richard F. Lyon (then of Foveon Inc.) for fruitful
nuclear@1 296 communication about JPEG configuration in Sigma Photo Pro software.
nuclear@1 297
nuclear@1 298 Thank to Andrew Finkenstadt for hosting the ijg.org site.
nuclear@1 299
nuclear@1 300 Last but not least special thank to Thomas G. Lane for the original
nuclear@1 301 design and development of this singular software package.
nuclear@1 302
nuclear@1 303
nuclear@1 304 FILE FORMAT WARS
nuclear@1 305 ================
nuclear@1 306
nuclear@1 307 The ISO JPEG standards committee actually promotes different formats like
nuclear@1 308 "JPEG 2000" or "JPEG XR" which are incompatible with original DCT-based
nuclear@1 309 JPEG and which are based on faulty technologies. IJG therefore does not
nuclear@1 310 and will not support such momentary mistakes (see REFERENCES).
nuclear@1 311 We have little or no sympathy for the promotion of these formats. Indeed,
nuclear@1 312 one of the original reasons for developing this free software was to help
nuclear@1 313 force convergence on common, interoperable format standards for JPEG files.
nuclear@1 314 Don't use an incompatible file format!
nuclear@1 315 (In any case, our decoder will remain capable of reading existing JPEG
nuclear@1 316 image files indefinitely.)
nuclear@1 317
nuclear@1 318
nuclear@1 319 TO DO
nuclear@1 320 =====
nuclear@1 321
nuclear@1 322 Version 8 is the first release of a new generation JPEG standard
nuclear@1 323 to overcome the limitations of the original JPEG specification.
nuclear@1 324 More features are being prepared for coming releases...
nuclear@1 325
nuclear@1 326 Please send bug reports, offers of help, etc. to jpeg-info@uc.ag.