Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 1 | The Independent JPEG Group's JPEG software |
| 2 | ========================================== |
| 3 | |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 4 | README for release 6a of 7-Feb-96 |
| 5 | ================================= |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 6 | |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 7 | This distribution contains the sixth public release of the Independent JPEG |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 8 | Group's free JPEG software. You are welcome to redistribute this software and |
| 9 | to use it for any purpose, subject to the conditions under LEGAL ISSUES, below. |
| 10 | |
Thomas G. Lane | 88aeed4 | 1992-12-10 00:00:00 +0000 | [diff] [blame] | 11 | Serious users of this software (particularly those incorporating it into |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 12 | larger programs) should contact IJG at jpeg-info@uunet.uu.net to be added to |
| 13 | our electronic mailing list. Mailing list members are notified of updates |
| 14 | and have a chance to participate in technical discussions, etc. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 15 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 16 | This software is the work of Tom Lane, Philip Gladstone, Luis Ortiz, Jim |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 17 | Boucher, Lee Crocker, Julian Minguillon, George Phillips, Davide Rossi, |
| 18 | Ge' Weijers, and other members of the Independent JPEG Group. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 19 | |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 20 | IJG is not affiliated with the official ISO JPEG standards committee. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 21 | |
| 22 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 23 | DOCUMENTATION ROADMAP |
| 24 | ===================== |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 25 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 26 | This file contains the following sections: |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 27 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 28 | OVERVIEW General description of JPEG and the IJG software. |
| 29 | LEGAL ISSUES Copyright, lack of warranty, terms of distribution. |
| 30 | REFERENCES Where to learn more about JPEG. |
| 31 | ARCHIVE LOCATIONS Where to find newer versions of this software. |
| 32 | RELATED SOFTWARE Other stuff you should get. |
| 33 | FILE FORMAT WARS Software *not* to get. |
| 34 | TO DO Plans for future IJG releases. |
| 35 | |
| 36 | Other documentation files in the distribution are: |
| 37 | |
| 38 | User documentation: |
| 39 | install.doc How to configure and install the IJG software. |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 40 | usage.doc Usage instructions for cjpeg, djpeg, jpegtran, |
| 41 | rdjpgcom, and wrjpgcom. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 42 | *.1 Unix-style man pages for programs (same info as usage.doc). |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 43 | wizard.doc Advanced usage instructions for JPEG wizards only. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 44 | change.log Version-to-version change highlights. |
| 45 | Programmer and internal documentation: |
| 46 | libjpeg.doc How to use the JPEG library in your own programs. |
| 47 | example.c Sample code for calling the JPEG library. |
| 48 | structure.doc Overview of the JPEG library's internal structure. |
| 49 | filelist.doc Road map of IJG files. |
| 50 | coderules.doc Coding style rules --- please read if you contribute code. |
| 51 | |
| 52 | Please read at least the files install.doc and usage.doc. Useful information |
| 53 | can also be found in the JPEG FAQ (Frequently Asked Questions) article. See |
| 54 | ARCHIVE LOCATIONS below to find out where to obtain the FAQ article. |
| 55 | |
| 56 | If you want to understand how the JPEG code works, we suggest reading one or |
| 57 | more of the REFERENCES, then looking at the documentation files (in roughly |
| 58 | the order listed) before diving into the code. |
Thomas G. Lane | bd543f0 | 1991-12-13 00:00:00 +0000 | [diff] [blame] | 59 | |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 60 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 61 | OVERVIEW |
| 62 | ======== |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 63 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 64 | This package contains C software to implement JPEG image compression and |
Thomas G. Lane | bd543f0 | 1991-12-13 00:00:00 +0000 | [diff] [blame] | 65 | decompression. JPEG (pronounced "jay-peg") is a standardized compression |
Thomas G. Lane | 88aeed4 | 1992-12-10 00:00:00 +0000 | [diff] [blame] | 66 | method for full-color and gray-scale images. JPEG is intended for compressing |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 67 | "real-world" scenes; line drawings, cartoons and other non-realistic images |
| 68 | are not its strong suit. JPEG is lossy, meaning that the output image is not |
| 69 | exactly identical to the input image. Hence you must not use JPEG if you |
| 70 | have to have identical output bits. However, on typical photographic images, |
| 71 | very good compression levels can be obtained with no visible change, and |
| 72 | remarkably high compression levels are possible if you can tolerate a |
| 73 | low-quality image. For more details, see the references, or just experiment |
| 74 | with various compression settings. |
| 75 | |
| 76 | This software implements JPEG baseline, extended-sequential, and progressive |
| 77 | compression processes. Provision is made for supporting all variants of these |
| 78 | processes, although some uncommon parameter settings aren't implemented yet. |
| 79 | For legal reasons, we are not distributing code for the arithmetic-coding |
| 80 | variants of JPEG; see LEGAL ISSUES. We have made no provision for supporting |
| 81 | the hierarchical or lossless processes defined in the standard. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 82 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 83 | We provide a set of library routines for reading and writing JPEG image files, |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 84 | plus two sample applications "cjpeg" and "djpeg", which use the library to |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 85 | perform conversion between JPEG and some other popular image file formats. |
| 86 | The library is intended to be reused in other applications. |
| 87 | |
Thomas G. Lane | 88aeed4 | 1992-12-10 00:00:00 +0000 | [diff] [blame] | 88 | In order to support file conversion and viewing software, we have included |
| 89 | considerable functionality beyond the bare JPEG coding/decoding capability; |
| 90 | for example, the color quantization modules are not strictly part of JPEG |
| 91 | decoding, but they are essential for output to colormapped file formats or |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 92 | colormapped displays. These extra functions can be compiled out of the |
| 93 | library if not required for a particular application. We have also included |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 94 | "jpegtran", a utility for lossless transcoding between different JPEG |
| 95 | processes, and "rdjpgcom" and "wrjpgcom", two simple applications for |
| 96 | inserting and extracting textual comments in JFIF files. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 97 | |
| 98 | The emphasis in designing this software has been on achieving portability and |
Thomas G. Lane | 88aeed4 | 1992-12-10 00:00:00 +0000 | [diff] [blame] | 99 | flexibility, while also making it fast enough to be useful. In particular, |
| 100 | the software is not intended to be read as a tutorial on JPEG. (See the |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 101 | REFERENCES section for introductory material.) Rather, it is intended to |
| 102 | be reliable, portable, industrial-strength code. We do not claim to have |
| 103 | achieved that goal in every aspect of the software, but we strive for it. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 104 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 105 | We welcome the use of this software as a component of commercial products. |
| 106 | No royalty is required, but we do ask for an acknowledgement in product |
| 107 | documentation, as described under LEGAL ISSUES. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 108 | |
| 109 | |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 110 | LEGAL ISSUES |
| 111 | ============ |
| 112 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 113 | In plain English: |
| 114 | |
| 115 | 1. We don't promise that this software works. (But if you find any bugs, |
| 116 | please let us know!) |
| 117 | 2. You can use this software for whatever you want. You don't have to pay us. |
| 118 | 3. You may not pretend that you wrote this software. If you use it in a |
| 119 | program, you must acknowledge somewhere in your documentation that |
| 120 | you've used the IJG code. |
| 121 | |
| 122 | In legalese: |
| 123 | |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 124 | The authors make NO WARRANTY or representation, either express or implied, |
| 125 | with respect to this software, its quality, accuracy, merchantability, or |
| 126 | fitness for a particular purpose. This software is provided "AS IS", and you, |
| 127 | its user, assume the entire risk as to its quality and accuracy. |
| 128 | |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 129 | This software is copyright (C) 1991-1996, Thomas G. Lane. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 130 | All Rights Reserved except as specified below. |
| 131 | |
| 132 | Permission is hereby granted to use, copy, modify, and distribute this |
| 133 | software (or portions thereof) for any purpose, without fee, subject to these |
| 134 | conditions: |
| 135 | (1) If any part of the source code for this software is distributed, then this |
| 136 | README file must be included, with this copyright and no-warranty notice |
| 137 | unaltered; and any additions, deletions, or changes to the original files |
| 138 | must be clearly indicated in accompanying documentation. |
| 139 | (2) If only executable code is distributed, then the accompanying |
| 140 | documentation must state that "this software is based in part on the work of |
| 141 | the Independent JPEG Group". |
| 142 | (3) Permission for use of this software is granted only if the user accepts |
| 143 | full responsibility for any undesirable consequences; the authors accept |
| 144 | NO LIABILITY for damages of any kind. |
| 145 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 146 | These conditions apply to any software derived from or based on the IJG code, |
| 147 | not just to the unmodified library. If you use our work, you ought to |
| 148 | acknowledge us. |
| 149 | |
Thomas G. Lane | 88aeed4 | 1992-12-10 00:00:00 +0000 | [diff] [blame] | 150 | Permission is NOT granted for the use of any IJG author's name or company name |
| 151 | in advertising or publicity relating to this software or products derived from |
| 152 | it. This software may be referred to only as "the Independent JPEG Group's |
| 153 | software". |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 154 | |
| 155 | We specifically permit and encourage the use of this software as the basis of |
| 156 | commercial products, provided that all warranty or liability claims are |
| 157 | assumed by the product vendor. |
| 158 | |
| 159 | |
| 160 | ansi2knr.c is included in this distribution by permission of L. Peter Deutsch, |
| 161 | sole proprietor of its copyright holder, Aladdin Enterprises of Menlo Park, CA. |
| 162 | ansi2knr.c is NOT covered by the above copyright and conditions, but instead |
| 163 | by the usual distribution terms of the Free Software Foundation; principally, |
| 164 | that you must include source code if you redistribute it. (See the file |
| 165 | ansi2knr.c for full details.) However, since ansi2knr.c is not needed as part |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 166 | of any program generated from the IJG code, this does not limit you more than |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 167 | the foregoing paragraphs do. |
| 168 | |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 169 | The configuration script "configure" was produced with GNU Autoconf. It |
| 170 | is copyright by the Free Software Foundation but is freely distributable. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 171 | |
| 172 | It appears that the arithmetic coding option of the JPEG spec is covered by |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 173 | patents owned by IBM, AT&T, and Mitsubishi. Hence arithmetic coding cannot |
| 174 | legally be used without obtaining one or more licenses. For this reason, |
| 175 | support for arithmetic coding has been removed from the free JPEG software. |
| 176 | (Since arithmetic coding provides only a marginal gain over the unpatented |
| 177 | Huffman mode, it is unlikely that very many implementations will support it.) |
Thomas G. Lane | bd543f0 | 1991-12-13 00:00:00 +0000 | [diff] [blame] | 178 | So far as we are aware, there are no patent restrictions on the remaining |
| 179 | code. |
| 180 | |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame] | 181 | WARNING: Unisys has begun to enforce their patent on LZW compression against |
| 182 | GIF encoders and decoders. You will need a license from Unisys to use the |
| 183 | included rdgif.c or wrgif.c files in a commercial or shareware application. |
| 184 | At this time, Unisys is not enforcing their patent against freeware, so |
| 185 | distribution of this package remains legal. However, we intend to remove |
| 186 | GIF support from the IJG package as soon as a suitable replacement format |
| 187 | becomes reasonably popular. |
| 188 | |
Thomas G. Lane | bd543f0 | 1991-12-13 00:00:00 +0000 | [diff] [blame] | 189 | We are required to state that |
| 190 | "The Graphics Interchange Format(c) is the Copyright property of |
| 191 | CompuServe Incorporated. GIF(sm) is a Service Mark property of |
| 192 | CompuServe Incorporated." |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 193 | |
| 194 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 195 | REFERENCES |
| 196 | ========== |
| 197 | |
| 198 | We highly recommend reading one or more of these references before trying to |
| 199 | understand the innards of the JPEG software. |
| 200 | |
| 201 | The best short technical introduction to the JPEG compression algorithm is |
| 202 | Wallace, Gregory K. "The JPEG Still Picture Compression Standard", |
| 203 | Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44. |
| 204 | (Adjacent articles in that issue discuss MPEG motion picture compression, |
| 205 | applications of JPEG, and related topics.) If you don't have the CACM issue |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 206 | handy, a PostScript file containing a revised version of Wallace's article |
| 207 | is available at ftp.uu.net, graphics/jpeg/wallace.ps.gz. The file (actually |
| 208 | a preprint for an article that appeared in IEEE Trans. Consumer Electronics) |
| 209 | omits the sample images that appeared in CACM, but it includes corrections |
| 210 | and some added material. Note: the Wallace article is copyright ACM and |
| 211 | IEEE, and it may not be used for commercial purposes. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 212 | |
| 213 | A somewhat less technical, more leisurely introduction to JPEG can be found in |
| 214 | "The Data Compression Book" by Mark Nelson, published by M&T Books (Redwood |
| 215 | City, CA), 1991, ISBN 1-55851-216-0. This book provides good explanations and |
| 216 | example C code for a multitude of compression methods including JPEG. It is |
| 217 | an excellent source if you are comfortable reading C code but don't know much |
| 218 | about data compression in general. The book's JPEG sample code is far from |
| 219 | industrial-strength, but when you are ready to look at a full implementation, |
| 220 | you've got one here... |
| 221 | |
| 222 | The best full description of JPEG is the textbook "JPEG Still Image Data |
| 223 | Compression Standard" by William B. Pennebaker and Joan L. Mitchell, published |
| 224 | by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1. Price US$59.95, 638 pp. |
| 225 | The book includes the complete text of the ISO JPEG standards (DIS 10918-1 |
| 226 | and draft DIS 10918-2). This is by far the most complete exposition of JPEG |
| 227 | in existence, and we highly recommend it. |
| 228 | |
| 229 | The JPEG standard itself is not available electronically; you must order a |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 230 | paper copy through ISO or ITU. (Unless you feel a need to own a certified |
| 231 | official copy, we recommend buying the Pennebaker and Mitchell book instead; |
| 232 | it's much cheaper and includes a great deal of useful explanatory material.) |
| 233 | In the USA, copies of the standard may be ordered from ANSI Sales at (212) |
| 234 | 642-4900, or from Global Engineering Documents at (800) 854-7179. (ANSI |
| 235 | doesn't take credit card orders, but Global does.) It's not cheap: as of |
| 236 | 1992, ANSI was charging $95 for Part 1 and $47 for Part 2, plus 7% |
| 237 | shipping/handling. The standard is divided into two parts, Part 1 being the |
| 238 | actual specification, while Part 2 covers compliance testing methods. Part 1 |
| 239 | is titled "Digital Compression and Coding of Continuous-tone Still Images, |
| 240 | Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS |
| 241 | 10918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of |
| 242 | Continuous-tone Still Images, Part 2: Compliance testing" and has document |
| 243 | numbers ISO/IEC IS 10918-2, ITU-T T.83. |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 244 | |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 245 | Extensions to the original JPEG standard are defined in JPEG Part 3, a new ISO |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 246 | document. Part 3 is undergoing ISO balloting and is expected to be approved |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 247 | by the end of 1995; it will have document numbers ISO/IEC IS 10918-3, ITU-T |
| 248 | T.84. IJG currently does not support any Part 3 extensions. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 249 | |
| 250 | The JPEG standard does not specify all details of an interchangeable file |
| 251 | format. For the omitted details we follow the "JFIF" conventions, revision |
| 252 | 1.02. A copy of the JFIF spec is available from: |
| 253 | Literature Department |
| 254 | C-Cube Microsystems, Inc. |
| 255 | 1778 McCarthy Blvd. |
| 256 | Milpitas, CA 95035 |
| 257 | phone (408) 944-6300, fax (408) 944-6314 |
| 258 | A PostScript version of this document is available at ftp.uu.net, file |
| 259 | graphics/jpeg/jfif.ps.gz. It can also be obtained by e-mail from the C-Cube |
| 260 | mail server, netlib@c3.pla.ca.us. Send the message "send jfif_ps from jpeg" |
| 261 | to the server to obtain the JFIF document; send the message "help" if you have |
| 262 | trouble. |
| 263 | |
| 264 | The TIFF 6.0 file format specification can be obtained by FTP from sgi.com |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 265 | (192.48.153.1), file graphics/tiff/TIFF6.ps.Z; or you can order a printed |
| 266 | copy from Aldus Corp. at (206) 628-6593. The JPEG incorporation scheme |
| 267 | found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems. |
| 268 | IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6). |
| 269 | Instead, we recommend the JPEG design proposed by TIFF Technical Note #2 |
| 270 | (Compression tag 7). Copies of this Note can be obtained from sgi.com or |
| 271 | from ftp.uu.net:/graphics/jpeg/. It is expected that the next revision of |
| 272 | the TIFF spec will replace the 6.0 JPEG design with the Note's design. |
| 273 | Although IJG's own code does not support TIFF/JPEG, the free libtiff library |
| 274 | uses our library to implement TIFF/JPEG per the Note. libtiff is available |
| 275 | from sgi.com:/graphics/tiff/. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 276 | |
| 277 | |
| 278 | ARCHIVE LOCATIONS |
| 279 | ================= |
| 280 | |
| 281 | The "official" archive site for this software is ftp.uu.net (Internet |
| 282 | address 192.48.96.9). The most recent released version can always be found |
| 283 | there in directory graphics/jpeg. This particular version will be archived |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 284 | as graphics/jpeg/jpegsrc.v6a.tar.gz. If you are on the Internet, you |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 285 | can retrieve files from ftp.uu.net by standard anonymous FTP. If you don't |
| 286 | have FTP access, UUNET's archives are also available via UUCP; contact |
| 287 | help@uunet.uu.net for information on retrieving files that way. |
| 288 | |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 289 | Numerous Internet sites maintain copies of the UUNET files. However, only |
| 290 | ftp.uu.net is guaranteed to have the latest official version. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 291 | |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 292 | You can also obtain this software in DOS-compatible "zip" archive format from |
| 293 | the SimTel archives (ftp.coast.net:/SimTel/msdos/graphics/), or on CompuServe |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 294 | in the Graphics Support forum (GO CIS:GRAPHSUP), library 12 "JPEG Tools". |
| 295 | Again, these versions may sometimes lag behind the ftp.uu.net release. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 296 | |
| 297 | The JPEG FAQ (Frequently Asked Questions) article is a useful source of |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 298 | general information about JPEG. It is updated constantly and therefore is |
| 299 | not included in this distribution. The FAQ is posted every two weeks to |
Thomas G. Lane | 489583f | 1996-02-07 00:00:00 +0000 | [diff] [blame^] | 300 | Usenet newsgroups comp.graphics.misc, news.answers, and other groups. |
| 301 | You can always obtain the latest version from the news.answers archive at |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 302 | rtfm.mit.edu. By FTP, fetch /pub/usenet/news.answers/jpeg-faq/part1 and |
| 303 | .../part2. If you don't have FTP, send e-mail to mail-server@rtfm.mit.edu |
| 304 | with body |
| 305 | send usenet/news.answers/jpeg-faq/part1 |
| 306 | send usenet/news.answers/jpeg-faq/part2 |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 307 | |
| 308 | |
| 309 | RELATED SOFTWARE |
| 310 | ================ |
| 311 | |
| 312 | Numerous viewing and image manipulation programs now support JPEG. (Quite a |
| 313 | few of them use this library to do so.) The JPEG FAQ described above lists |
| 314 | some of the more popular free and shareware viewers, and tells where to |
| 315 | obtain them on Internet. |
| 316 | |
| 317 | If you are on a Unix machine, we highly recommend Jef Poskanzer's free |
| 318 | PBMPLUS image software, which provides many useful operations on PPM-format |
| 319 | image files. In particular, it can convert PPM images to and from a wide |
| 320 | range of other formats. You can obtain this package by FTP from ftp.x.org |
| 321 | (contrib/pbmplus*.tar.Z) or ftp.ee.lbl.gov (pbmplus*.tar.Z). There is also |
| 322 | a newer update of this package called NETPBM, available from |
| 323 | wuarchive.wustl.edu under directory /graphics/graphics/packages/NetPBM/. |
| 324 | Unfortunately PBMPLUS/NETPBM is not nearly as portable as the IJG software |
| 325 | is; you are likely to have difficulty making it work on any non-Unix machine. |
| 326 | |
| 327 | A different free JPEG implementation, written by the PVRG group at Stanford, |
| 328 | is available from havefun.stanford.edu in directory pub/jpeg. This program |
| 329 | is designed for research and experimentation rather than production use; |
| 330 | it is slower, harder to use, and less portable than the IJG code, but it |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 331 | is easier to read and modify. Also, the PVRG code supports lossless JPEG, |
| 332 | which we do not. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 333 | |
| 334 | |
| 335 | FILE FORMAT WARS |
| 336 | ================ |
| 337 | |
| 338 | Some JPEG programs produce files that are not compatible with our library. |
| 339 | The root of the problem is that the ISO JPEG committee failed to specify a |
| 340 | concrete file format. Some vendors "filled in the blanks" on their own, |
| 341 | creating proprietary formats that no one else could read. (For example, none |
| 342 | of the early commercial JPEG implementations for the Macintosh were able to |
| 343 | exchange compressed files.) |
| 344 | |
| 345 | The file format we have adopted is called JFIF (see REFERENCES). This format |
| 346 | has been agreed to by a number of major commercial JPEG vendors, and it has |
| 347 | become the de facto standard. JFIF is a minimal or "low end" representation. |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 348 | We recommend the use of TIFF/JPEG (TIFF revision 6.0 as modified by TIFF |
| 349 | Technical Note #2) for "high end" applications that need to record a lot of |
| 350 | additional data about an image. TIFF/JPEG is fairly new and not yet widely |
| 351 | supported, unfortunately. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 352 | |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 353 | The upcoming JPEG Part 3 standard defines a file format called SPIFF. |
| 354 | SPIFF is interoperable with JFIF, in the sense that most JFIF decoders should |
| 355 | be able to read the most common variant of SPIFF. SPIFF has some technical |
| 356 | advantages over JFIF, but its major claim to fame is simply that it is an |
| 357 | official standard rather than an informal one. At this point it is unclear |
| 358 | whether SPIFF will supersede JFIF or whether JFIF will remain the de-facto |
| 359 | standard. IJG intends to support SPIFF once the standard is frozen, but we |
| 360 | have not decided whether it should become our default output format or not. |
| 361 | (In any case, our decoder will remain capable of reading JFIF indefinitely.) |
| 362 | |
| 363 | Various proprietary file formats incorporating JPEG compression also exist. |
| 364 | We have little or no sympathy for the existence of these formats. Indeed, |
| 365 | one of the original reasons for developing this free software was to help |
| 366 | force convergence on common, open format standards for JPEG files. Don't |
| 367 | use a proprietary file format! |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 368 | |
| 369 | |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 370 | TO DO |
| 371 | ===== |
| 372 | |
Thomas G. Lane | bc79e06 | 1995-08-02 00:00:00 +0000 | [diff] [blame] | 373 | In future versions, we are considering supporting some of the upcoming JPEG |
| 374 | Part 3 extensions --- principally, variable quantization and the SPIFF file |
| 375 | format. |
| 376 | |
| 377 | Tuning the software for better behavior at low quality/high compression |
| 378 | settings is also of interest. The current method for scaling the |
| 379 | quantization tables is known not to be very good at low Q values. |
Thomas G. Lane | 88aeed4 | 1992-12-10 00:00:00 +0000 | [diff] [blame] | 380 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 381 | As always, speeding things up is high on our priority list. |
Thomas G. Lane | 2cbeb8a | 1991-10-07 00:00:00 +0000 | [diff] [blame] | 382 | |
| 383 | Please send bug reports, offers of help, etc. to jpeg-info@uunet.uu.net. |