• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

READMEH A D16-Oct-202019.8 KiB396321

jcapimin.cH A D16-Oct-20208.9 KiB281133

jcapistd.cH A D16-Oct-20205.7 KiB16268

jccoefct.cH A D16-Oct-202016 KiB451280

jccolor.cH A D16-Oct-202014.5 KiB461284

jcdctmgr.cH A D16-Oct-202012.2 KiB388260

jchuff.cH A D16-Oct-202027.7 KiB913524

jchuff.hH A D16-Oct-20201.7 KiB5322

jcinit.cH A D16-Oct-20202.3 KiB7332

jcmainct.cH A D16-Oct-20209 KiB294175

jcmarker.cH A D16-Oct-202016.9 KiB666403

jcmaster.cH A D16-Oct-202019.4 KiB591393

jcomapi.cH A D16-Oct-20203 KiB10745

jconfig.hH A D16-Oct-20201.2 KiB4630

jcparam.cH A D16-Oct-202024.9 KiB689447

jcphuff.cH A D16-Oct-202024.5 KiB834495

jcprepct.cH A D16-Oct-202011.8 KiB355214

jcsample.cH A D16-Oct-202018.4 KiB521299

jctrans.cH A D16-Oct-202013.7 KiB390219

jdapimin.cH A D16-Oct-202012.3 KiB396223

jdapistd.cH A D16-Oct-20209.1 KiB276155

jdatadst.cH A D16-Oct-20205 KiB15259

jdatasrc.cH A D16-Oct-20207.5 KiB21477

jdcoefct.cH A D16-Oct-202024.6 KiB739510

jdcolor.cH A D16-Oct-202012.7 KiB398245

jdct.hH A D16-Oct-20207.3 KiB18980

jddctmgr.cH A D16-Oct-20208.1 KiB270170

jdhuff.cH A D16-Oct-202020.6 KiB658349

jdhuff.hH A D16-Oct-20208.2 KiB20887

jdinput.cH A D16-Oct-202013.2 KiB382209

jdmainct.cH A D16-Oct-202020 KiB513260

jdmarker.cH A D16-Oct-202040.3 KiB1,367858

jdmaster.cH A D16-Oct-202019.2 KiB558331

jdmerge.cH A D16-Oct-202013.6 KiB403248

jdphuff.cH A D16-Oct-202020.1 KiB669388

jdpostct.cH A D16-Oct-20209.6 KiB292182

jdsample.cH A D16-Oct-202016.1 KiB480278

jdtrans.cH A D16-Oct-20205 KiB14471

jerror.cH A D16-Oct-20207.7 KiB257114

jerror.hH A D16-Oct-202013.6 KiB292244

jfdctflt.cH A D16-Oct-20205.4 KiB16986

jfdctfst.cH A D16-Oct-20207.4 KiB225104

jfdctint.cH A D16-Oct-202010.8 KiB284146

jidctflt.cH A D16-Oct-20208.3 KiB243130

jidctfst.cH A D16-Oct-202012.9 KiB369197

jidctint.cH A D16-Oct-202014.5 KiB390216

jidctred.cH A D16-Oct-202013.2 KiB399237

jinclude.hH A D16-Oct-20203.2 KiB9226

jmemansi.cH A D16-Oct-20204.7 KiB17087

jmemmgr.cH A D16-Oct-202040 KiB1,119658

jmemsys.hH A D16-Oct-20208.5 KiB21078

jmorecfg.hH A D16-Oct-202012.3 KiB372133

jpegint.hH A D16-Oct-202017.1 KiB429306

jpeglib.hH A D16-Oct-202047.8 KiB1,151572

jquant1.cH A D16-Oct-202030.6 KiB859487

jquant2.cH A D16-Oct-202047.3 KiB1,313764

jutils.cH A D16-Oct-20205.1 KiB180101

jversion.hH A D16-Oct-2020360 152

makefile.vcH A D16-Oct-2020910 2619

README

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