1The Independent JPEG Group's JPEG software 2========================================== 3 4README for release 9c of 14-Jan-2018 5==================================== 6 7This distribution contains the ninth public release of the Independent JPEG 8Group's free JPEG software. You are welcome to redistribute this software and 9to use it for any purpose, subject to the conditions under LEGAL ISSUES, below. 10 11This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone, 12Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson, 13Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers, 14and other members of the Independent JPEG Group. 15 16IJG is not affiliated with the ISO/IEC JTC1/SC29/WG1 standards committee 17(previously known as JPEG, together with ITU-T SG16). 18 19 20DOCUMENTATION ROADMAP 21===================== 22 23This file contains the following sections: 24 25OVERVIEW General description of JPEG and the IJG software. 26LEGAL ISSUES Copyright, lack of warranty, terms of distribution. 27REFERENCES Where to learn more about JPEG. 28ARCHIVE LOCATIONS Where to find newer versions of this software. 29ACKNOWLEDGMENTS Special thanks. 30FILE FORMAT WARS Software *not* to get. 31TO DO Plans for future IJG releases. 32 33Other documentation files in the distribution are: 34 35User documentation: 36 install.txt How to configure and install the IJG software. 37 usage.txt Usage instructions for cjpeg, djpeg, jpegtran, 38 rdjpgcom, and wrjpgcom. 39 *.1 Unix-style man pages for programs (same info as usage.txt). 40 wizard.txt Advanced usage instructions for JPEG wizards only. 41 change.log Version-to-version change highlights. 42Programmer and internal documentation: 43 libjpeg.txt How to use the JPEG library in your own programs. 44 example.c Sample code for calling the JPEG library. 45 structure.txt Overview of the JPEG library's internal structure. 46 filelist.txt Road map of IJG files. 47 coderules.txt Coding style rules --- please read if you contribute code. 48 49Please read at least the files install.txt and usage.txt. Some information 50can also be found in the JPEG FAQ (Frequently Asked Questions) article. See 51ARCHIVE LOCATIONS below to find out where to obtain the FAQ article. 52 53If you want to understand how the JPEG code works, we suggest reading one or 54more of the REFERENCES, then looking at the documentation files (in roughly 55the order listed) before diving into the code. 56 57 58OVERVIEW 59======== 60 61This package contains C software to implement JPEG image encoding, decoding, 62and transcoding. JPEG (pronounced "jay-peg") is a standardized compression 63method for full-color and grayscale images. 64 65This software implements JPEG baseline, extended-sequential, and progressive 66compression processes. Provision is made for supporting all variants of these 67processes, although some uncommon parameter settings aren't implemented yet. 68We have made no provision for supporting the hierarchical or lossless 69processes defined in the standard. 70 71We provide a set of library routines for reading and writing JPEG image files, 72plus two sample applications "cjpeg" and "djpeg", which use the library to 73perform conversion between JPEG and some other popular image file formats. 74The library is intended to be reused in other applications. 75 76In order to support file conversion and viewing software, we have included 77considerable functionality beyond the bare JPEG coding/decoding capability; 78for example, the color quantization modules are not strictly part of JPEG 79decoding, but they are essential for output to colormapped file formats or 80colormapped displays. These extra functions can be compiled out of the 81library if not required for a particular application. 82 83We have also included "jpegtran", a utility for lossless transcoding between 84different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple 85applications for inserting and extracting textual comments in JFIF files. 86 87The emphasis in designing this software has been on achieving portability and 88flexibility, while also making it fast enough to be useful. In particular, 89the software is not intended to be read as a tutorial on JPEG. (See the 90REFERENCES section for introductory material.) Rather, it is intended to 91be reliable, portable, industrial-strength code. We do not claim to have 92achieved that goal in every aspect of the software, but we strive for it. 93 94We welcome the use of this software as a component of commercial products. 95No royalty is required, but we do ask for an acknowledgement in product 96documentation, as described under LEGAL ISSUES. 97 98 99LEGAL ISSUES 100============ 101 102In plain English: 103 1041. We don't promise that this software works. (But if you find any bugs, 105 please let us know!) 1062. You can use this software for whatever you want. You don't have to pay us. 1073. You may not pretend that you wrote this software. If you use it in a 108 program, you must acknowledge somewhere in your documentation that 109 you've used the IJG code. 110 111In legalese: 112 113The authors make NO WARRANTY or representation, either express or implied, 114with respect to this software, its quality, accuracy, merchantability, or 115fitness for a particular purpose. This software is provided "AS IS", and you, 116its user, assume the entire risk as to its quality and accuracy. 117 118This software is copyright (C) 1991-2018, Thomas G. Lane, Guido Vollbeding. 119All Rights Reserved except as specified below. 120 121Permission is hereby granted to use, copy, modify, and distribute this 122software (or portions thereof) for any purpose, without fee, subject to these 123conditions: 124(1) If any part of the source code for this software is distributed, then this 125README file must be included, with this copyright and no-warranty notice 126unaltered; and any additions, deletions, or changes to the original files 127must be clearly indicated in accompanying documentation. 128(2) If only executable code is distributed, then the accompanying 129documentation must state that "this software is based in part on the work of 130the Independent JPEG Group". 131(3) Permission for use of this software is granted only if the user accepts 132full responsibility for any undesirable consequences; the authors accept 133NO LIABILITY for damages of any kind. 134 135These conditions apply to any software derived from or based on the IJG code, 136not just to the unmodified library. If you use our work, you ought to 137acknowledge us. 138 139Permission is NOT granted for the use of any IJG author's name or company name 140in advertising or publicity relating to this software or products derived from 141it. This software may be referred to only as "the Independent JPEG Group's 142software". 143 144We specifically permit and encourage the use of this software as the basis of 145commercial products, provided that all warranty or liability claims are 146assumed by the product vendor. 147 148 149The Unix configuration script "configure" was produced with GNU Autoconf. 150It is copyright by the Free Software Foundation but is freely distributable. 151The same holds for its supporting scripts (config.guess, config.sub, 152ltmain.sh). Another support script, install-sh, is copyright by X Consortium 153but is also freely distributable. 154 155The IJG distribution formerly included code to read and write GIF files. 156To avoid entanglement with the Unisys LZW patent (now expired), GIF reading 157support has been removed altogether, and the GIF writer has been simplified 158to produce "uncompressed GIFs". This technique does not use the LZW 159algorithm; the resulting GIF files are larger than usual, but are readable 160by all standard GIF decoders. 161 162 163REFERENCES 164========== 165 166We recommend reading one or more of these references before trying to 167understand the innards of the JPEG software. 168 169The best short technical introduction to the JPEG compression algorithm is 170 Wallace, Gregory K. "The JPEG Still Picture Compression Standard", 171 Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44. 172(Adjacent articles in that issue discuss MPEG motion picture compression, 173applications of JPEG, and related topics.) If you don't have the CACM issue 174handy, a PDF file containing a revised version of Wallace's article is 175available at http://www.ijg.org/files/Wallace.JPEG.pdf. The file (actually 176a preprint for an article that appeared in IEEE Trans. Consumer Electronics) 177omits the sample images that appeared in CACM, but it includes corrections 178and some added material. Note: the Wallace article is copyright ACM and IEEE, 179and it may not be used for commercial purposes. 180 181A somewhat less technical, more leisurely introduction to JPEG can be found in 182"The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by 183M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides 184good explanations and example C code for a multitude of compression methods 185including JPEG. It is an excellent source if you are comfortable reading C 186code but don't know much about data compression in general. The book's JPEG 187sample code is far from industrial-strength, but when you are ready to look 188at a full implementation, you've got one here... 189 190The best currently available description of JPEG is the textbook "JPEG Still 191Image Data Compression Standard" by William B. Pennebaker and Joan L. 192Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1. 193Price US$59.95, 638 pp. The book includes the complete text of the ISO JPEG 194standards (DIS 10918-1 and draft DIS 10918-2). 195Although this is by far the most detailed and comprehensive exposition of 196JPEG publicly available, we point out that it is still missing an explanation 197of the most essential properties and algorithms of the underlying DCT 198technology. 199If you think that you know about DCT-based JPEG after reading this book, 200then you are in delusion. The real fundamentals and corresponding potential 201of DCT-based JPEG are not publicly known so far, and that is the reason for 202all the mistaken developments taking place in the image coding domain. 203 204The original JPEG standard is divided into two parts, Part 1 being the actual 205specification, while Part 2 covers compliance testing methods. Part 1 is 206titled "Digital Compression and Coding of Continuous-tone Still Images, 207Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS 20810918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of 209Continuous-tone Still Images, Part 2: Compliance testing" and has document 210numbers ISO/IEC IS 10918-2, ITU-T T.83. 211IJG JPEG 8 introduced an implementation of the JPEG SmartScale extension 212which is specified in two documents: A contributed document at ITU and ISO 213with title "ITU-T JPEG-Plus Proposal for Extending ITU-T T.81 for Advanced 214Image Coding", April 2006, Geneva, Switzerland. The latest version of this 215document is Revision 3. And a contributed document ISO/IEC JTC1/SC29/WG1 N 2165799 with title "Evolution of JPEG", June/July 2011, Berlin, Germany. 217IJG JPEG 9 introduces a reversible color transform for improved lossless 218compression which is described in a contributed document ISO/IEC JTC1/SC29/ 219WG1 N 6080 with title "JPEG 9 Lossless Coding", June/July 2012, Paris, 220France. 221 222The JPEG standard does not specify all details of an interchangeable file 223format. For the omitted details we follow the "JFIF" conventions, version 2. 224JFIF version 1 has been adopted as Recommendation ITU-T T.871 (05/2011) : 225Information technology - Digital compression and coding of continuous-tone 226still images: JPEG File Interchange Format (JFIF). It is available as a 227free download in PDF file format from http://www.itu.int/rec/T-REC-T.871. 228A PDF file of the older JFIF document is available at 229http://www.w3.org/Graphics/JPEG/jfif3.pdf. 230 231The TIFF 6.0 file format specification can be obtained by FTP from 232ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation scheme 233found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems. 234IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6). 235Instead, we recommend the JPEG design proposed by TIFF Technical Note #2 236(Compression tag 7). Copies of this Note can be obtained from 237http://www.ijg.org/files/. It is expected that the next revision 238of the TIFF spec will replace the 6.0 JPEG design with the Note's design. 239Although IJG's own code does not support TIFF/JPEG, the free libtiff library 240uses our library to implement TIFF/JPEG per the Note. 241 242 243ARCHIVE LOCATIONS 244================= 245 246The "official" archive site for this software is www.ijg.org. 247The most recent released version can always be found there in 248directory "files". This particular version will be archived as 249http://www.ijg.org/files/jpegsrc.v9c.tar.gz, and in Windows-compatible 250"zip" archive format as http://www.ijg.org/files/jpegsr9c.zip. 251 252The JPEG FAQ (Frequently Asked Questions) article is a source of some 253general information about JPEG. 254It is available on the World Wide Web at http://www.faqs.org/faqs/jpeg-faq/ 255and other news.answers archive sites, including the official news.answers 256archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/. 257If you don't have Web or FTP access, send e-mail to mail-server@rtfm.mit.edu 258with body 259 send usenet/news.answers/jpeg-faq/part1 260 send usenet/news.answers/jpeg-faq/part2 261 262 263ACKNOWLEDGMENTS 264=============== 265 266Thank to Juergen Bruder for providing me with a copy of the common DCT 267algorithm article, only to find out that I had come to the same result 268in a more direct and comprehensible way with a more generative approach. 269 270Thank to Istvan Sebestyen and Joan L. Mitchell for inviting me to the 271ITU JPEG (Study Group 16) meeting in Geneva, Switzerland. 272 273Thank to Thomas Wiegand and Gary Sullivan for inviting me to the 274Joint Video Team (MPEG & ITU) meeting in Geneva, Switzerland. 275 276Thank to Thomas Richter and Daniel Lee for inviting me to the 277ISO/IEC JTC1/SC29/WG1 (previously known as JPEG, together with ITU-T SG16) 278meeting in Berlin, Germany. 279 280Thank to John Korejwa and Massimo Ballerini for inviting me to 281fruitful consultations in Boston, MA and Milan, Italy. 282 283Thank to Hendrik Elstner, Roland Fassauer, Simone Zuck, Guenther 284Maier-Gerber, Walter Stoeber, Fred Schmitz, and Norbert Braunagel 285for corresponding business development. 286 287Thank to Nico Zschach and Dirk Stelling of the technical support team 288at the Digital Images company in Halle for providing me with extra 289equipment for configuration tests. 290 291Thank to Richard F. Lyon (then of Foveon Inc.) for fruitful 292communication about JPEG configuration in Sigma Photo Pro software. 293 294Thank to Andrew Finkenstadt for hosting the ijg.org site. 295 296Thank to Thomas G. Lane for the original design and development of 297this singular software package. 298 299Thank to Lars Goehler, Andreas Heinecke, Sebastian Fuss, Yvonne Roebert, 300Andrej Werner, and Ulf-Dietrich Braumann for support and public relations. 301 302 303FILE FORMAT WARS 304================ 305 306The ISO/IEC JTC1/SC29/WG1 standards committee (previously known as JPEG, 307together with ITU-T SG16) currently promotes different formats containing 308the name "JPEG" which is misleading because these formats are incompatible 309with original DCT-based JPEG and are based on faulty technologies. 310IJG therefore does not and will not support such momentary mistakes 311(see REFERENCES). 312There exist also distributions under the name "OpenJPEG" promoting such 313kind of formats which is misleading because they don't support original 314JPEG images. 315We have no sympathy for the promotion of inferior formats. Indeed, one of 316the original reasons for developing this free software was to help force 317convergence on common, interoperable format standards for JPEG files. 318Don't use an incompatible file format! 319(In any case, our decoder will remain capable of reading existing JPEG 320image files indefinitely.) 321 322The ISO committee pretends to be "responsible for the popular JPEG" in their 323public reports which is not true because they don't respond to actual 324requirements for the maintenance of the original JPEG specification. 325Furthermore, the ISO committee pretends to "ensure interoperability" with 326their standards which is not true because their "standards" support only 327application-specific and proprietary use cases and contain mathematically 328incorrect code. 329 330There are currently different distributions in circulation containing the 331name "libjpeg" which is misleading because they don't have the features and 332are incompatible with formats supported by actual IJG libjpeg distributions. 333One of those fakes is released by members of the ISO committee and just uses 334the name of libjpeg for misdirection of people, similar to the abuse of the 335name JPEG as described above, while having nothing in common with actual IJG 336libjpeg distributions and containing mathematically incorrect code. 337The other one claims to be a "derivative" or "fork" of the original libjpeg, 338but violates the license conditions as described under LEGAL ISSUES above 339and violates basic C programming properties. 340We have no sympathy for the release of misleading, incorrect and illegal 341distributions derived from obsolete code bases. 342Don't use an obsolete code base! 343 344According to the UCC (Uniform Commercial Code) law, IJG has the lawful and 345legal right to foreclose on certain standardization bodies and other 346institutions or corporations that knowingly perform substantial and 347systematic deceptive acts and practices, fraud, theft, and damaging of the 348value of the people of this planet without their knowing, willing and 349intentional consent. 350The titles, ownership, and rights of these institutions and all their assets 351are now duly secured and held in trust for the free people of this planet. 352People of the planet, on every country, may have a financial interest in 353the assets of these former principals, agents, and beneficiaries of the 354foreclosed institutions and corporations. 355IJG asserts what is: that each man, woman, and child has unalienable value 356and rights granted and deposited in them by the Creator and not any one of 357the people is subordinate to any artificial principality, corporate fiction 358or the special interest of another without their appropriate knowing, 359willing and intentional consent made by contract or accommodation agreement. 360IJG expresses that which already was. 361The people have already determined and demanded that public administration 362entities, national governments, and their supporting judicial systems must 363be fully transparent, accountable, and liable. 364IJG has secured the value for all concerned free people of the planet. 365 366A partial list of foreclosed institutions and corporations ("Hall of Shame") 367is currently prepared and will be published later. 368 369 370TO DO 371===== 372 373Version 9 is the second release of a new generation JPEG standard 374to overcome the limitations of the original JPEG specification, 375and is the first true source reference JPEG codec. 376More features are being prepared for coming releases... 377 378Please send bug reports, offers of help, etc. to jpeg-info@jpegclub.org. 379
