Lines Matching full:files
6 the other documentation files if you wish to use the JPEG library within
10 pages in files cjpeg.1, djpeg.1, jpegtran.1, rdjpgcom.1, wrjpgcom.1.
48 i.e., both the input and output files are named on the command line. This
63 of some Targa-format files. You have to tell djpeg which format to generate.
65 JPEG files are in the defacto standard JFIF file format. There are other,
99 -targa Input file is Targa format. Targa files that contain
101 recognized by cjpeg; for such files you must specify
103 For most Targa files, you won't need this switch.
122 In the other direction, quality values below 50 will produce very small files
166 space is needed, temporary files will be used.
289 file. This is useful for producing multiple files
308 space is needed, temporary files will be used.
316 Color GIF files are not the ideal input for JPEG; JPEG is really intended for
331 quality settings to make very small JPEG files; the percentage improvement
332 is often a lot more than it is on larger files. (At present, -optimize
333 mode is always selected when generating progressive JPEG files.)
335 GIF input files are no longer supported, to avoid the Unisys LZW patent.
337 of GIF files to JPEG is usually a bad idea anyway.)
364 To avoid the Unisys LZW patent, djpeg produces uncompressed GIF files. These
371 determined by -maxmemory), temporary files will be used. (MS-DOS versions
372 will try to get extended or expanded memory first.) The temporary files are
378 On MS-DOS, the temporary files are created in the directory named by the TMP
380 exist. Amiga implementations put the temp files in the directory named by
403 jpegtran performs various useful transformations of JPEG files.
421 where both the input and output files are JPEG files.
491 files these extra markers can be sizable.
508 annotations, titles, index terms, etc to your JPEG files, and later retrieve
