Blame | Last modification | View Log | RSS feed
Hi, Folks.I am pleased to announce the availability of JasPer version 1.700.x.Numerous changes have been made to the software since the 1.600.0 release.A few of the highlights are listed below. This list is in no particularorder, and is not intended to be exhaustive.1) A preliminary attempt at a color management subsystem has been addedto JasPer. This will allow for more accurate color reproduction whentranscoding or rendering image data. Some of the underlying colormanagement functionality makes use of the ICC color profile fileformat. Consequently, support for handling this file format is nowpresent in JasPer. This support intelligently handles shared tags viareference counting. (Thanks to Scott Houchin <scott.houchin@kodak.com>for providing some ICC profiles for use in JasPer, and for answering anumber of questions about the ICC color profile file format.) Some sampleICC profiles have been included with the JasPer distribution.2) Previously, the configure process did not generate a configurationheader file. Instead, all of the configure-related preprocessor defineswere hardwired into the makefiles. Unfortunately, this approach hasthe strong potential to cause problems when non-JasPer applicationprograms are built against the JasPer library (since such applicationprograms will often fail to specify the correct configure-relatedpreprocessor defines for JasPer). In order to resolve this problem, theconfigure-related preprocessor defines are now saved in a configurationheader file (which is always included by application programs).3) Temporary files created with the jas_stream_tmpfile functionwere not correctly removed upon file close under Microsoft Windows.Apparently, the Microsoft Windows operating system will not allow a fileto be unlinked when it is open. The problem has been solved by deferringthe unlink operation until the time of file close. (Thank you to RickBryan <rlbryan@pobox.com> for pointing out this bug and providing asuggested fix.)4) An option has been added to the JPEG encoder to allow a quality factorto be specified. (Thanks to Jason Fritts <jefritts@cse.wustl.edu>for providing a suggested patch which I adopted with a few minormodifications.)5) A new make target has been added for RPM building. This functionalityis experimental, and not officially supported. Your mileage may vary.Void where prohibited by law. Batteries not included. :) (Thanksto Alexander Karaivanov <adk@medical-insight.com> for providing thenecessary changes.)6) The code now compiles with many fewer warnings on most platforms.Previously, some unresolved type issues and missing type casts causednumerous warnings to be generated by most compilers. Also, someprototypes were missing or broken. The majority of these problems havebeen fixed (either by using consistent types or adding type casts).The source files jpc_enc.c and jpc_t1enc.c still need to be fixed,however. Hopefully, this will happen in the next release.The new JasPer release is available from the JasPer Project Home Page(i.e., http://www.ece.uvic.ca/~mdadams/jasper) and the JPEG web site(i.e., http://www.jpeg.org/software).Regards,Michael---Michael Adams, Assistant ProfessorDept. of Elec. and Comp. Engineering, University of VictoriaP.O. Box 3055 STN CSC, Victoria, BC, V8W 3P6, CANADAE-mail: mdadams@ece.uvic.ca, Web: www.ece.uvic.ca/~mdadams