#246 Image filetype .pam incorrectly detected as Microsoft Word,

[Christopher Smart]

Issue:
Image filetype .pam incorrectly detected as Microsoft Word, fails normalisation.

File:
"image-pam.pam"

Exception:
org.xml.sax.SAXException: Cannot connect to OpenOffice.org - possibly something wrong with the input file
Trace:
au.gov.naa.digipres.xena.kernel.normalise.NormaliserManager.parse(NormaliserManager.java:826)
au.gov.naa.digipres.xena.kernel.normalise.NormaliserManager.normalise(NormaliserManager.java:1005)
au.gov.naa.digipres.xena.core.Xena.normalise(Xena.java:599)
au.gov.naa.digipres.xena.core.Xena.normalise(Xena.java:543)
au.gov.naa.digipres.xena.litegui.NormalisationThread.normaliseFile(NormalisationThread.java:328)
au.gov.naa.digipres.xena.litegui.NormalisationThread.normaliseStandard(NormalisationThread.java:250)
au.gov.naa.digipres.xena.litegui.NormalisationThread.run(NormalisationThread.java:191)

[Daniel Black]

Should it just be that these incorrect detection bugs have a nicer UI ? The efforts of poor detection can only be improved with better magic descriptions.

au.gov.naa.digipres.xena.core.Xena.normalise(Xena.java:599) -> catch generic exception and throw a XenaNormalisationFailedException -

NormalisationThread.java:328 - catch XenaNormalisationFailedException and maybe IOException.

Thoughts?

If so this bug goes to Feature Tracker pri 6 with dup bugs: 2906433, 2906440, 2906441, 2906442

[Christopher Smart]

Sounds good to me..

[Allan Cunliffe]

I agree. As discussed, we should catch any unsupported file formats and binary normalise them, rather than throwing a Java error in the GUI and failing normalisation.