"Fossies" - the Fresh Open Source Software Archive
Member "mumble-1.3.2/3rdPartyLicenses/libjpeg_turbo_license.txt" (9 Jul 2020, 17356 Bytes) of package /linux/misc/mumble-1.3.2.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
For more information about "libjpeg_turbo_license.txt" see the Fossies "Dox" file reference
1 libjpeg-turbo is covered by three compatible BSD-style open source licenses:
3 1. The IJG (Independent JPEG Group) License.
4 This license applies to the libjpeg API library and associated programs
5 (any code inherited from libjpeg, and any modifications to that code.)
7 2. The Modified (3-clause) BSD License
8 This license covers the TurboJPEG API library and associated programs.
10 3. The zlib License
11 This license is a subset of the other two, and it covers the libjpeg-turbo
12 SIMD extensions.
14 -----BEGIN IJG LICENSE-----
15 libjpeg-turbo note: This file has been modified by The libjpeg-turbo Project
16 to include only information relevant to libjpeg-turbo, to wordsmith certain
17 sections, and to remove impolitic language that existed in the libjpeg v8
18 README. It is included only for reference. Please see README.md for
19 information specific to libjpeg-turbo.
22 The Independent JPEG Group's JPEG software
25 This distribution contains a release of the Independent JPEG Group's free JPEG
26 software. You are welcome to redistribute this software and to use it for any
27 purpose, subject to the conditions under LEGAL ISSUES, below.
29 This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
30 Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
31 Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
32 and other members of the Independent JPEG Group.
34 IJG is not affiliated with the ISO/IEC JTC1/SC29/WG1 standards committee
35 (also known as JPEG, together with ITU-T SG16).
38 DOCUMENTATION ROADMAP
41 This file contains the following sections:
43 OVERVIEW General description of JPEG and the IJG software.
44 LEGAL ISSUES Copyright, lack of warranty, terms of distribution.
45 REFERENCES Where to learn more about JPEG.
46 ARCHIVE LOCATIONS Where to find newer versions of this software.
47 FILE FORMAT WARS Software *not* to get.
48 TO DO Plans for future IJG releases.
50 Other documentation files in the distribution are:
52 User documentation:
53 usage.txt Usage instructions for cjpeg, djpeg, jpegtran,
54 rdjpgcom, and wrjpgcom.
55 *.1 Unix-style man pages for programs (same info as usage.txt).
56 wizard.txt Advanced usage instructions for JPEG wizards only.
57 change.log Version-to-version change highlights.
58 Programmer and internal documentation:
59 libjpeg.txt How to use the JPEG library in your own programs.
60 example.c Sample code for calling the JPEG library.
61 structure.txt Overview of the JPEG library's internal structure.
62 coderules.txt Coding style rules --- please read if you contribute code.
64 Please read at least usage.txt. Some information can also be found in the JPEG
65 FAQ (Frequently Asked Questions) article. See ARCHIVE LOCATIONS below to find
66 out where to obtain the FAQ article.
68 If you want to understand how the JPEG code works, we suggest reading one or
69 more of the REFERENCES, then looking at the documentation files (in roughly
70 the order listed) before diving into the code.
76 This package contains C software to implement JPEG image encoding, decoding,
77 and transcoding. JPEG (pronounced "jay-peg") is a standardized compression
78 method for full-color and grayscale images. JPEG's strong suit is compressing
79 photographic images or other types of images that have smooth color and
80 brightness transitions between neighboring pixels. Images with sharp lines or
81 other abrupt features may not compress well with JPEG, and a higher JPEG
82 quality may have to be used to avoid visible compression artifacts with such
85 JPEG is lossy, meaning that the output pixels are not necessarily identical to
86 the input pixels. However, on photographic content and other "smooth" images,
87 very good compression ratios can be obtained with no visible compression
88 artifacts, and extremely high compression ratios are possible if you are
89 willing to sacrifice image quality (by reducing the "quality" setting in the
92 This software implements JPEG baseline, extended-sequential, and progressive
93 compression processes. Provision is made for supporting all variants of these
94 processes, although some uncommon parameter settings aren't implemented yet.
95 We have made no provision for supporting the hierarchical or lossless
96 processes defined in the standard.
98 We provide a set of library routines for reading and writing JPEG image files,
99 plus two sample applications "cjpeg" and "djpeg", which use the library to
100 perform conversion between JPEG and some other popular image file formats.
101 The library is intended to be reused in other applications.
103 In order to support file conversion and viewing software, we have included
104 considerable functionality beyond the bare JPEG coding/decoding capability;
105 for example, the color quantization modules are not strictly part of JPEG
106 decoding, but they are essential for output to colormapped file formats or
107 colormapped displays. These extra functions can be compiled out of the
108 library if not required for a particular application.
110 We have also included "jpegtran", a utility for lossless transcoding between
111 different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple
112 applications for inserting and extracting textual comments in JFIF files.
114 The emphasis in designing this software has been on achieving portability and
115 flexibility, while also making it fast enough to be useful. In particular,
116 the software is not intended to be read as a tutorial on JPEG. (See the
117 REFERENCES section for introductory material.) Rather, it is intended to
118 be reliable, portable, industrial-strength code. We do not claim to have
119 achieved that goal in every aspect of the software, but we strive for it.
121 We welcome the use of this software as a component of commercial products.
122 No royalty is required, but we do ask for an acknowledgement in product
123 documentation, as described under LEGAL ISSUES.
126 LEGAL ISSUES
129 In plain English:
131 1. We don't promise that this software works. (But if you find any bugs,
132 please let us know!)
133 2. You can use this software for whatever you want. You don't have to pay us.
134 3. You may not pretend that you wrote this software. If you use it in a
135 program, you must acknowledge somewhere in your documentation that
136 you've used the IJG code.
138 In legalese:
140 The authors make NO WARRANTY or representation, either express or implied,
141 with respect to this software, its quality, accuracy, merchantability, or
142 fitness for a particular purpose. This software is provided "AS IS", and you,
143 its user, assume the entire risk as to its quality and accuracy.
145 This software is copyright (C) 1991-2016, Thomas G. Lane, Guido Vollbeding.
146 All Rights Reserved except as specified below.
148 Permission is hereby granted to use, copy, modify, and distribute this
149 software (or portions thereof) for any purpose, without fee, subject to these
151 (1) If any part of the source code for this software is distributed, then this
152 README file must be included, with this copyright and no-warranty notice
153 unaltered; and any additions, deletions, or changes to the original files
154 must be clearly indicated in accompanying documentation.
155 (2) If only executable code is distributed, then the accompanying
156 documentation must state that "this software is based in part on the work of
157 the Independent JPEG Group".
158 (3) Permission for use of this software is granted only if the user accepts
159 full responsibility for any undesirable consequences; the authors accept
160 NO LIABILITY for damages of any kind.
162 These conditions apply to any software derived from or based on the IJG code,
163 not just to the unmodified library. If you use our work, you ought to
164 acknowledge us.
166 Permission is NOT granted for the use of any IJG author's name or company name
167 in advertising or publicity relating to this software or products derived from
168 it. This software may be referred to only as "the Independent JPEG Group's
171 We specifically permit and encourage the use of this software as the basis of
172 commercial products, provided that all warranty or liability claims are
173 assumed by the product vendor.
176 The Unix configuration script "configure" was produced with GNU Autoconf.
177 It is copyright by the Free Software Foundation but is freely distributable.
178 The same holds for its supporting scripts (config.guess, config.sub,
179 ltmain.sh). Another support script, install-sh, is copyright by X Consortium
180 but is also freely distributable.
182 The IJG distribution formerly included code to read and write GIF files.
183 To avoid entanglement with the Unisys LZW patent (now expired), GIF reading
184 support has been removed altogether, and the GIF writer has been simplified
185 to produce "uncompressed GIFs". This technique does not use the LZW
186 algorithm; the resulting GIF files are larger than usual, but are readable
187 by all standard GIF decoders.
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."
198 We recommend reading one or more of these references before trying to
199 understand the innards of the JPEG software.
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
206 handy, a PDF file containing a revised version of Wallace's article is
207 available at http://www.ijg.org/files/Wallace.JPEG.pdf. 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 IEEE,
211 and it may not be used for commercial purposes.
213 A somewhat less technical, more leisurely introduction to JPEG can be found in
214 "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
215 M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides
216 good explanations and example C code for a multitude of compression methods
217 including JPEG. It is an excellent source if you are comfortable reading C
218 code but don't know much about data compression in general. The book's JPEG
219 sample code is far from industrial-strength, but when you are ready to look
220 at a full implementation, you've got one here...
222 The best currently available description of JPEG is the textbook "JPEG Still
223 Image Data Compression Standard" by William B. Pennebaker and Joan L.
224 Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.
225 Price US$59.95, 638 pp. The book includes the complete text of the ISO JPEG
226 standards (DIS 10918-1 and draft DIS 10918-2).
228 The original JPEG standard is divided into two parts, Part 1 being the actual
229 specification, while Part 2 covers compliance testing methods. Part 1 is
230 titled "Digital Compression and Coding of Continuous-tone Still Images,
231 Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
232 10918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of
233 Continuous-tone Still Images, Part 2: Compliance testing" and has document
234 numbers ISO/IEC IS 10918-2, ITU-T T.83.
236 The JPEG standard does not specify all details of an interchangeable file
237 format. For the omitted details we follow the "JFIF" conventions, revision
238 1.02. JFIF 1.02 has been adopted as an Ecma International Technical Report
239 and thus received a formal publication status. It is available as a free
240 download in PDF format from
242 A PostScript version of the JFIF document is available at
243 http://www.ijg.org/files/jfif.ps.gz. There is also a plain text version at
244 http://www.ijg.org/files/jfif.txt.gz, but it is missing the figures.
246 The TIFF 6.0 file format specification can be obtained by FTP from
247 ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation scheme
248 found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems.
249 IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).
250 Instead, we recommend the JPEG design proposed by TIFF Technical Note #2
251 (Compression tag 7). Copies of this Note can be obtained from
252 http://www.ijg.org/files/. It is expected that the next revision
253 of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
254 Although IJG's own code does not support TIFF/JPEG, the free libtiff library
255 uses our library to implement TIFF/JPEG per the Note.
258 ARCHIVE LOCATIONS
261 The "official" archive site for this software is www.ijg.org.
262 The most recent released version can always be found there in
263 directory "files".
265 The JPEG FAQ (Frequently Asked Questions) article is a source of some
266 general information about JPEG.
267 It is available on the World Wide Web at http://www.faqs.org/faqs/jpeg-faq/
268 and other news.answers archive sites, including the official news.answers
269 archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/.
270 If you don't have Web or FTP access, send e-mail to email@example.com
271 with body
272 send usenet/news.answers/jpeg-faq/part1
273 send usenet/news.answers/jpeg-faq/part2
276 FILE FORMAT WARS
279 The ISO/IEC JTC1/SC29/WG1 standards committee (also known as JPEG, together
280 with ITU-T SG16) currently promotes different formats containing the name
281 "JPEG" which are incompatible with original DCT-based JPEG. IJG therefore does
282 not support these formats (see REFERENCES). Indeed, one of the original
283 reasons for developing this free software was to help force convergence on
284 common, interoperable format standards for JPEG files.
285 Don't use an incompatible file format!
286 (In any case, our decoder will remain capable of reading existing JPEG
287 image files indefinitely.)
290 TO DO
293 Please send bug reports, offers of help, etc. to firstname.lastname@example.org.
294 -----END IJG LICENSE-----
296 -----BEGIN TURBOJPEG LICENSE-----
298 * Copyright (C)2009-2016 D. R. Commander. All Rights Reserved.
300 * Redistribution and use in source and binary forms, with or without
301 * modification, are permitted provided that the following conditions are met:
303 * - Redistributions of source code must retain the above copyright notice,
304 * this list of conditions and the following disclaimer.
305 * - Redistributions in binary form must reproduce the above copyright notice,
306 * this list of conditions and the following disclaimer in the documentation
307 * and/or other materials provided with the distribution.
308 * - Neither the name of the libjpeg-turbo Project nor the names of its
309 * contributors may be used to endorse or promote products derived from this
310 * software without specific prior written permission.
312 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS",
313 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
314 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
315 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE
316 * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
317 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
318 * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
319 * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
320 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
321 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
322 * POSSIBILITY OF SUCH DAMAGE.
324 -----END TURBOJPEG LICENSE-----
327 -----BEGIN ZLIB LICENSE-----
328 ; Copyright 2009 Pierre Ossman <email@example.com> for Cendio AB
329 ; Copyright (C) 2010, D. R. Commander.
331 ; Based on the x86 SIMD extension for IJG JPEG library - version 1.02
333 ; Copyright (C) 1999-2006, MIYASAKA Masaru.
335 ; This software is provided 'as-is', without any express or implied
336 ; warranty. In no event will the authors be held liable for any damages
337 ; arising from the use of this software.
339 ; Permission is granted to anyone to use this software for any purpose,
340 ; including commercial applications, and to alter it and redistribute it
341 ; freely, subject to the following restrictions:
343 ; 1. The origin of this software must not be misrepresented; you must not
344 ; claim that you wrote the original software. If you use this software
345 ; in a product, an acknowledgment in the product documentation would be
346 ; appreciated but is not required.
347 ; 2. Altered source versions must be plainly marked as such, and must not be
348 ; misrepresented as being the original software.
349 ; 3. This notice may not be removed or altered from any source distribution.
350 -----END ZLIB LICENSE-----