[ptx] .jpe suffix patch fix

[Hal V Engel]

On Sunday 12 June 2005 02:11 pm, Stanislav Brabec wrote:
> Hallo.
>
> There is an updated JPE patch. It fixes typo in array indexes in
> jpeg.cxx and is updated for actual CVS version.
>
> I would be very glad to get this patch included. As Hal V Engel wrote,
> renaming JPE files to JPG is not a good solution - on some systems are
> JPE files associated with color management aware applications and JPG
> files with plain image viewer.

I think you didn't understand me.  The implication of what you wrote is that 
image files with embedded profiles are a special case.  This is in my view 
backwards.  Image files that do not have embedded profiles are in fact the 
special case since the files are missing critical image data.  In addition I 
don't know of any color management aware program that uses the file extension 
to in anyway change it's behavior with regard to color management and non-CM 
aware software simply ignores any CM data embedded in the image file 
regardless of the file extension.  All CM aware programs look at the files 
embedded tags to see if the file is color managed.  The JPE extension is 
non-standard and is there so that users will know which files are color 
managed not for the use of the imaging software.   The correct way to handle 
this is to ALWAYS color manage your files and use standard file extensions 
(JPG in the case of jpeg files).    At best the JPE extension is a kluge.

>
> Missing embedded profile in nona result can be easily worked around by
> third party applications.
>

This is true but as I wrote a future release of Nona will have the ability to 
pass CM information through by embedding the profile from the input files 
into the output files.  Enblend already has this in it's CVS version.

Hal