Can someone unsubscribe  or tell me how to do this from this
Tika emai list?




> Date: Tue, 4 Feb 2014 23:18:18 +0000
> From: j...@apache.org
> To: dev@tika.apache.org
> Subject: [jira] [Updated] (TIKA-1205) Allow PDFParser to fallback to other 
> parser if there is an exception
> 
> 
>      [ 
> https://issues.apache.org/jira/browse/TIKA-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
> Dave Meikle updated TIKA-1205:
> ------------------------------
> 
>     Fix Version/s:     (was: 1.5)
>                    1.6
> 
> Pushed out to 1.6, preparing for 1.5 RC
> 
> > Allow PDFParser to fallback to other parser if there is an exception
> > --------------------------------------------------------------------
> >
> >                 Key: TIKA-1205
> >                 URL: https://issues.apache.org/jira/browse/TIKA-1205
> >             Project: Tika
> >          Issue Type: Improvement
> >          Components: parser
> >            Reporter: Tim Allison
> >            Assignee: Tim Allison
> >            Priority: Trivial
> >             Fix For: 1.6
> >
> >
> > With TIKA-1201, there is now an option to use PDFBox's 
> > NonSequentialPDFParser instead of the traditional parser for parsing PDF 
> > files.  Following the description in PDFBOX-1199, it would be useful to 
> > allow fallback to the classic parser if NonSequentialPDFParser throws an 
> > IOException.  For the sake of symmetry, I propose a boolean 
> > useParserFallbackOnException parameter.  If this parameter is true, and if 
> > Tika's PDFParser is using the classic parser, Tika will fallback to the 
> > NonSequentialPDFParser if there is an IOException; if this parameter is 
> > true and if Tika's PDFParser is using the NonSequentialPDFParser it will 
> > fallback to the classic parser if there is an IOException.
> > Many thanks to Hong-Thai for championing the addition of the added 
> > NonSequentialPDFParser capability in TIKA-1201, and many thanks to Timo for 
> > PDFBox's NonSequentialPDFParser (PDFBOX-1199)!
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.1.5#6160)
                                          

Reply via email to