tjt263 / fits

Automatically exported from code.google.com/p/fits
GNU Lesser General Public License v3.0
0 stars 0 forks source link

FITS crashes on OpenDocument Text files #24

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Running FITS on any ODT file results in the following error:

java.text.ParseException: Unparseable date: "PT6H4M0S"

(Despite this FITS does write an apparently normal output file).

Problem encountered with:

- FITS 0.5
- OS: Win XP

See attached ODT file (but this seems to happen with any ODT file)

Cheers,

Johan

Original issue reported on code.google.com by johan.va...@kb.nl on 29 Jun 2011 at 3:12

Attachments:

GoogleCodeExporter commented 8 years ago
I have seen this error before with certain files.  Unfortunately it's thrown 
from within the National Library of New Zealand Metadata Extractor and is 
written to either System.out System.err.  I don't think much can be done about 
it without changing the NLNZ source and recompiling the tool.

It should be ok to ignore. It will not be written to the output file if you are 
using the -o option.

Original comment by spencer_...@harvard.edu on 29 Jun 2011 at 3:48

GoogleCodeExporter commented 8 years ago
Another workaround would be to add the odt extension to the exclude-exts 
attribute of Metadata Extractor in the configuration file, i.e.:

<tool class="edu.harvard.hul.ois.fits.tools.nlnz.MetadataExtractor" 
exclude-exts="dng,zip,odb,ott,odg,otg,odp,otp,ods,ots,odc,otc,odi,oti,odf,otf,od
m,oth,odt"/>

(Although in that case you won't get any metadata for ODT documents)  

Original comment by johan.va...@kb.nl on 30 Jun 2011 at 12:29