[
https://issues.apache.org/jira/browse/TIKA-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355825#comment-16355825
]
Hudson commented on TIKA-2559:
--
FAILURE: Integrated in Jenkins build Tika-trunk #1433 (See
[
https://issues.apache.org/jira/browse/TIKA-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-2559.
---
Resolution: Fixed
Fix Version/s: 2.0.0
1.18
Thank you!
> Expose language
IMO, if the parser p1 has an exception and then we move to p2 before p1 is done
creating its SAX we can create a special tag indicating the exception e.g.,
Message here and have it output that before moving to p2 in the chain...
On 2/7/18, 7:00 AM, "Allison, Timothy B."
Mine too, but I know it is important for many use cases. Maybe adding to
XHtmlContentHandler some tracking of open tags and a new method to close
them?
2018-02-07 12:59 GMT-02:00 Allison, Timothy B. :
> Do we worry about properly closing tags on an exception?
>
>
>
Do we worry about properly closing tags on an exception?
kaboom
mailto:lfcnas...@gmail.com]
Sent: Monday, February 5, 2018 5:34 PM
To: dev@tika.apache.org
Subject: Re: Not-yet-broken breaking changes for Tika 2?
From a forensic use case it is better just
[
https://issues.apache.org/jira/browse/TIKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-2395.
---
Resolution: Won't Fix
I concur with [~tmortagne]...I don't think there's much we can do at the Tika
[
https://issues.apache.org/jira/browse/TIKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355543#comment-16355543
]
Thomas Mortagne commented on TIKA-2395:
---
I have a workaround on my side. I doubt it's really Tika's
[
https://issues.apache.org/jira/browse/TIKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355490#comment-16355490
]
Tim Allison commented on TIKA-2395:
---
+1 thank you! If only there were a
[
https://issues.apache.org/jira/browse/TIKA-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355477#comment-16355477
]
Hudson commented on TIKA-2567:
--
SUCCESS: Integrated in Jenkins build Tika-trunk #1432 (See
[
https://issues.apache.org/jira/browse/TIKA-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Burch resolved TIKA-2567.
--
Resolution: Fixed
Fix Version/s: 1.18
> Tika mistakenly determines mimetype of .min.js file as
[
https://issues.apache.org/jira/browse/TIKA-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355402#comment-16355402
]
Nick Burch commented on TIKA-2567:
--
The fun and joy of many programming languages looking very similar,
[
https://issues.apache.org/jira/browse/TIKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355202#comment-16355202
]
Thomas Mortagne edited comment on TIKA-2395 at 2/7/18 9:26 AM:
---
Might be seen
[
https://issues.apache.org/jira/browse/TIKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355202#comment-16355202
]
Thomas Mortagne commented on TIKA-2395:
---
Might be seen as a AutoCloseInputStream bug, I created
[
https://issues.apache.org/jira/browse/TIKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mortagne updated TIKA-2395:
--
Summary: The parser does not support AutoCloseInputStream anymore (was:
The parser does not
14 matches
Mail list logo