Menu
▾
▴
[Xena-devel] [ xena-Bugs-1962813 ] Unable to view jpe files
|
From: SourceForge.net <no...@so...> - 2008-09-24 23:04:02
|
Bugs item #1962813, was opened at 2008-05-13 05:59 Message generated for change (Comment added) made by mcarden You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=577089&aid=1962813&group_id=85722 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Wont Fix Priority: 3 Private: No Submitted By: John (vombatus) Assigned to: michael (mcarden) Summary: Unable to view jpe files Initial Comment: One of the AWB transfers has 3 jpe files. One of them was selected for Quality Assurance. I was unable to open the normalised version - a java error resulted (which was basically "unsupported JPEG process"). The original file could be viewed via the FastStone viewer. I attempted to view the source files directly from windows explorer - They cannot be viewed with the (default) Microsoft Picture viewer, but can be viewed with the FastStone viewer. Using xena directly gave the same results - the normalised version cannot be viewed with the viewer. You can export the file to a jpg - which again, will not view in Microsoft Picture Viewer, but can be seen using the FastStone viewer. I assume that our image normaliser cannot handle jpe files directly. I have placed the files on the 'Testing' share on the workbench - in a folder called "problem jpe files". The three files are of the same image - all the checksums are identical. However, I fail to see how they actually constitute real business records. In some circles, the image may be considered offensive. ---------------------------------------------------------------------- >Comment By: michael (mcarden) Date: 2008-09-24 23:03 Message: I will guess that a JPE file is a file with a JPEG extension that has been moved to a file system that only supports three character file extensions and handles the four character extension by truncating it. To my way of thinking, this would make the odd file extension completely unrelated to any oddness in the file's content. ---------------------------------------------------------------------- Comment By: John (vombatus) Date: 2008-09-23 01:28 Message: Because the data objects have already been run through DPR, the binary wrapped versions are in the repository. It would be difficult to extract the files, open and save them in an external program, run them through DPR and then somehow reassociate them with the originals. You would certainly not have any metadata which described what had happened. We have Microsoft Word 95 format documents in the repository - OpenOffice.org will not open them, but they can be opened with Word. Maybe we need a feature that allows for selecting a group of files for reprocessing, allows for an external program to open them (manually?) and save in a later format and then allow them to be reingested into the repository with all the necessary metadata. It is quite possible that we will receive 'slightly broken' files which could be fixed using this mechanism. ---------------------------------------------------------------------- Comment By: John (vombatus) Date: 2008-09-23 01:28 Message: Because the data objects have already been run through DPR, the binary wrapped versions are in the repository. It would be difficult to extract the files, open and save them in an external program, run them through DPR and then somehow reassociate them with the originals. You would certainly not have any metadata which described what had happened. We have Microsoft Word 95 format documents in the repository - OpenOffice.org will not open them, but they can be opened with Word. Maybe we need a feature that allows for selecting a group of files for reprocessing, allows for an external program to open them (manually?) and save in a later format and then allow them to be reingested into the repository with all the necessary metadata. It is quite possible that we will receive 'slightly broken' files which could be fixed using this mechanism. ---------------------------------------------------------------------- Comment By: Justin Waddell (jwaddell) Date: 2008-09-23 01:00 Message: I can't find any concrete references of JPE files (other than mis-named jpg files). It looks like these files are a little broken, with both Microsoft Picture Viewer and the Java Advanced Imaging library failing to handle them. Unless this becomes a widespread problem, I would suggest converting the images to another format with an external program, and then running through xena again. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=577089&aid=1962813&group_id=85722 |