Damiano created TIKA-1414:
-
Summary: How to extract embedded images from PDFs?
Key: TIKA-1414
URL: https://issues.apache.org/jira/browse/TIKA-1414
Project: Tika
Issue Type: Bug
Components:
> From: Hong-Thai Nguyen
> Sent: September 11, 2014 1:40:08pm PDT
> To: dev@tika.apache.org
> Subject: Re: NPE on all *.odt, odp, .ods documents
>
> I was wrong when saying that All OpenDocument are failed, some files
> passed, but alot of them failed with NPE in OpenDocumentParser line 161.
OK,
I was wrong when saying that All OpenDocument are failed, some files
passed, but alot of them failed with NPE in OpenDocumentParser line 161.
I'm looking to OpenDocumentParser.java on 1.6. The bug comes from block
lines 126-130 when input is TikaInputStream (our case):
if (container instanceof Zip
> From: Hong-Thai Nguyen
> Sent: September 11, 2014 5:21:41am PDT
> To: dev@tika.apache.org
> Subject: NPE on all *.odt, odp, .ods documents
>
> Hi all,
>
> I've tested the conversion Tika 1.6 with our corpus, all OpenOffice
> document types are failed with NPE. Fix has been done on
> https://is
Ahh... Good points! +1 1.7
Tyler
On Thu, Sep 11, 2014 at 2:34 PM, Nick Burch wrote:
> On Thu, 11 Sep 2014, Tyler Palsulich wrote:
>
>> BTW, we don't have any x.y.z releases yet - should we just
>>> call this 1.7? That's probably just as easy?
>>>
>>
>> Both sound good to me. We don't want to ru
On Thu, 11 Sep 2014, Tyler Palsulich wrote:
BTW, we don't have any x.y.z releases yet - should we just
call this 1.7? That's probably just as easy?
Both sound good to me. We don't want to run out of numbers < 2.0,
though. ;)
As long as we don't hit 1.FF, we're probably OK, it is 2 digit non
no worries, we can always do 1.10, 1.11..etc
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
> BTW, we don't have any x.y.z releases yet - should we just
> call this 1.7? That's probably just as easy?
Both sound good to me. We don't want to run out of numbers < 2.0, though. ;)
Tyler
I have no objection on version naming politic :)
The 1.7 with 13 fixed issues is not bad:
https://issues.apache.org/jira/browse/TIKA-1393?jql=project%20%3D%20TIKA%20AND%20fixVersion%20%3D%201.7%20AND%20resolution%20%3D%20Fixed%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
On Th
+1 let me know what you guys think I'll wait until tomorrow
based on what people say.
BTW, we don't have any x.y.z releases yet - should we just
call this 1.7? That's probably just as easy?
++
Chris Mattmann, Ph.D.
Chief Architect
I
Probably want to add TIKA-1411.
Nick and all, anything else?
-Original Message-
From: Hong-Thai Nguyen [mailto:thaicha...@gmail.com]
Sent: Thursday, September 11, 2014 10:10 AM
To: dev@tika.apache.org
Subject: Re: NPE on all *.odt, odp, .ods documents
Hi Chris,
Sound perfect too me.
H
Hi Chris,
Sound perfect too me.
Hong-Thai
> On 11 Sep 2014, at 15:56, "Mattmann, Chris A (3980)"
> wrote:
>
> Hi Hong-Thai,
>
> Sure, we can easily do a patch release that incorporates this.
>
> Here would be the process:
>
> 1. RM to create branch http://svn.apache.org/repos/asf/tika/bran
Hi Hong-Thai,
Sure, we can easily do a patch release that incorporates this.
Here would be the process:
1. RM to create branch http://svn.apache.org/repos/asf/tika/branches/1.6
from
http://svn.apache.org/repos/asf/tika/tags/1.6-rc2
2. RM to apply TIKA-1412 to
http://svn.apache.org/repos/asf/ti
Hi all,
I've tested the conversion Tika 1.6 with our corpus, all OpenOffice
document types are failed with NPE. Fix has been done on
https://issues.apache.org/jira/browse/TIKA-1412, but available from 1.7.
That's a fatal error for me.
Should we release a 1.6.1 with the fix of TIKA-1412 ?
Tack tr
14 matches
Mail list logo
