change.log 9.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217
  1. CHANGE LOG for Independent JPEG Group's JPEG software
  2. Version 6b 27-Mar-1998
  3. -----------------------
  4. jpegtran has new features for lossless image transformations (rotation
  5. and flipping) as well as "lossless" reduction to grayscale.
  6. jpegtran now copies comments by default; it has a -copy switch to enable
  7. copying all APPn blocks as well, or to suppress comments. (Formerly it
  8. always suppressed comments and APPn blocks.) jpegtran now also preserves
  9. JFIF version and resolution information.
  10. New decompressor library feature: COM and APPn markers found in the input
  11. file can be saved in memory for later use by the application. (Before,
  12. you had to code this up yourself with a custom marker processor.)
  13. There is an unused field "void * client_data" now in compress and decompress
  14. parameter structs; this may be useful in some applications.
  15. JFIF version number information is now saved by the decoder and accepted by
  16. the encoder. jpegtran uses this to copy the source file's version number,
  17. to ensure "jpegtran -copy all" won't create bogus files that contain JFXX
  18. extensions but claim to be version 1.01. Applications that generate their
  19. own JFXX extension markers also (finally) have a supported way to cause the
  20. encoder to emit JFIF version number 1.02.
  21. djpeg's trace mode reports JFIF 1.02 thumbnail images as such, rather
  22. than as unknown APP0 markers.
  23. In -verbose mode, djpeg and rdjpgcom will try to print the contents of
  24. APP12 markers as text. Some digital cameras store useful text information
  25. in APP12 markers.
  26. Handling of truncated data streams is more robust: blocks beyond the one in
  27. which the error occurs will be output as uniform gray, or left unchanged
  28. if decoding a progressive JPEG. The appearance no longer depends on the
  29. Huffman tables being used.
  30. Huffman tables are checked for validity much more carefully than before.
  31. To avoid the Unisys LZW patent, djpeg's GIF output capability has been
  32. changed to produce "uncompressed GIFs", and cjpeg's GIF input capability
  33. has been removed altogether. We're not happy about it either, but there
  34. seems to be no good alternative.
  35. The configure script now supports building libjpeg as a shared library
  36. on many flavors of Unix (all the ones that GNU libtool knows how to
  37. build shared libraries for). Use "./configure --enable-shared" to
  38. try this out.
  39. New jconfig file and makefiles for Microsoft Visual C++ and Developer Studio.
  40. Also, a jconfig file and a build script for Metrowerks CodeWarrior
  41. on Apple Macintosh. makefile.dj has been updated for DJGPP v2, and there
  42. are miscellaneous other minor improvements in the makefiles.
  43. jmemmac.c now knows how to create temporary files following Mac System 7
  44. conventions.
  45. djpeg's -map switch is now able to read raw-format PPM files reliably.
  46. cjpeg -progressive -restart no longer generates any unnecessary DRI markers.
  47. Multiple calls to jpeg_simple_progression for a single JPEG object
  48. no longer leak memory.
  49. Version 6a 7-Feb-96
  50. --------------------
  51. Library initialization sequence modified to detect version mismatches
  52. and struct field packing mismatches between library and calling application.
  53. This change requires applications to be recompiled, but does not require
  54. any application source code change.
  55. All routine declarations changed to the style "GLOBAL(type) name ...",
  56. that is, GLOBAL, LOCAL, METHODDEF, EXTERN are now macros taking the
  57. routine's return type as an argument. This makes it possible to add
  58. Microsoft-style linkage keywords to all the routines by changing just
  59. these macros. Note that any application code that was using these macros
  60. will have to be changed.
  61. DCT coefficient quantization tables are now stored in normal array order
  62. rather than zigzag order. Application code that calls jpeg_add_quant_table,
  63. or otherwise manipulates quantization tables directly, will need to be
  64. changed. If you need to make such code work with either older or newer
  65. versions of the library, a test like "#if JPEG_LIB_VERSION >= 61" is
  66. recommended.
  67. djpeg's trace capability now dumps DQT tables in natural order, not zigzag
  68. order. This allows the trace output to be made into a "-qtables" file
  69. more easily.
  70. New system-dependent memory manager module for use on Apple Macintosh.
  71. Fix bug in cjpeg's -smooth option: last one or two scanlines would be
  72. duplicates of the prior line unless the image height mod 16 was 1 or 2.
  73. Repair minor problems in VMS, BCC, MC6 makefiles.
  74. New configure script based on latest GNU Autoconf.
  75. Correct the list of include files needed by MetroWerks C for ccommand().
  76. Numerous small documentation updates.
  77. Version 6 2-Aug-95
  78. -------------------
  79. Progressive JPEG support: library can read and write full progressive JPEG
  80. files. A "buffered image" mode supports incremental decoding for on-the-fly
  81. display of progressive images. Simply recompiling an existing IJG-v5-based
  82. decoder with v6 should allow it to read progressive files, though of course
  83. without any special progressive display.
  84. New "jpegtran" application performs lossless transcoding between different
  85. JPEG formats; primarily, it can be used to convert baseline to progressive
  86. JPEG and vice versa. In support of jpegtran, the library now allows lossless
  87. reading and writing of JPEG files as DCT coefficient arrays. This ability
  88. may be of use in other applications.
  89. Notes for programmers:
  90. * We changed jpeg_start_decompress() to be able to suspend; this makes all
  91. decoding modes available to suspending-input applications. However,
  92. existing applications that use suspending input will need to be changed
  93. to check the return value from jpeg_start_decompress(). You don't need to
  94. do anything if you don't use a suspending data source.
  95. * We changed the interface to the virtual array routines: access_virt_array
  96. routines now take a count of the number of rows to access this time. The
  97. last parameter to request_virt_array routines is now interpreted as the
  98. maximum number of rows that may be accessed at once, but not necessarily
  99. the height of every access.
  100. Version 5b 15-Mar-95
  101. ---------------------
  102. Correct bugs with grayscale images having v_samp_factor > 1.
  103. jpeg_write_raw_data() now supports output suspension.
  104. Correct bugs in "configure" script for case of compiling in
  105. a directory other than the one containing the source files.
  106. Repair bug in jquant1.c: sometimes didn't use as many colors as it could.
  107. Borland C makefile and jconfig file work under either MS-DOS or OS/2.
  108. Miscellaneous improvements to documentation.
  109. Version 5a 7-Dec-94
  110. --------------------
  111. Changed color conversion roundoff behavior so that grayscale values are
  112. represented exactly. (This causes test image files to change.)
  113. Make ordered dither use 16x16 instead of 4x4 pattern for a small quality
  114. improvement.
  115. New configure script based on latest GNU Autoconf.
  116. Fix configure script to handle CFLAGS correctly.
  117. Rename *.auto files to *.cfg, so that configure script still works if
  118. file names have been truncated for DOS.
  119. Fix bug in rdbmp.c: didn't allow for extra data between header and image.
  120. Modify rdppm.c/wrppm.c to handle 2-byte raw PPM/PGM formats for 12-bit data.
  121. Fix several bugs in rdrle.c.
  122. NEED_SHORT_EXTERNAL_NAMES option was broken.
  123. Revise jerror.h/jerror.c for more flexibility in message table.
  124. Repair oversight in jmemname.c NO_MKTEMP case: file could be there
  125. but unreadable.
  126. Version 5 24-Sep-94
  127. --------------------
  128. Version 5 represents a nearly complete redesign and rewrite of the IJG
  129. software. Major user-visible changes include:
  130. * Automatic configuration simplifies installation for most Unix systems.
  131. * A range of speed vs. image quality tradeoffs are supported.
  132. This includes resizing of an image during decompression: scaling down
  133. by a factor of 1/2, 1/4, or 1/8 is handled very efficiently.
  134. * New programs rdjpgcom and wrjpgcom allow insertion and extraction
  135. of text comments in a JPEG file.
  136. The application programmer's interface to the library has changed completely.
  137. Notable improvements include:
  138. * We have eliminated the use of callback routines for handling the
  139. uncompressed image data. The application now sees the library as a
  140. set of routines that it calls to read or write image data on a
  141. scanline-by-scanline basis.
  142. * The application image data is represented in a conventional interleaved-
  143. pixel format, rather than as a separate array for each color channel.
  144. This can save a copying step in many programs.
  145. * The handling of compressed data has been cleaned up: the application can
  146. supply routines to source or sink the compressed data. It is possible to
  147. suspend processing on source/sink buffer overrun, although this is not
  148. supported in all operating modes.
  149. * All static state has been eliminated from the library, so that multiple
  150. instances of compression or decompression can be active concurrently.
  151. * JPEG abbreviated datastream formats are supported, ie, quantization and
  152. Huffman tables can be stored separately from the image data.
  153. * And not only that, but the documentation of the library has improved
  154. considerably!
  155. The last widely used release before the version 5 rewrite was version 4A of
  156. 18-Feb-93. Change logs before that point have been discarded, since they
  157. are not of much interest after the rewrite.