[
https://issues.apache.org/jira/browse/TIKA-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515140#comment-16515140
]
Andreas Beeker commented on TIKA-2666:
--------------------------------------
I've fixed the unsigned handling in POI, but as noted in
[#62451|[https://bz.apache.org/bugzilla/show_bug.cgi?id=62451]] I don't think
that's POI business to default to 00:00. If you look at the screenshot closely,
you see that the formatting (leading space) is off anyway and I interpret it as
Windows having a problem with those properties. So I leave it up to you, if you
want to surpress e.g. date properties in the future or greater than year 2099
...
> Document last printed in the year 27321
> ---------------------------------------
>
> Key: TIKA-2666
> URL: https://issues.apache.org/jira/browse/TIKA-2666
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.17
> Reporter: Isabelle Giguere
> Priority: Minor
> Attachments: Genetic_Factors_and_the_Directionality_of.ppt,
> PPT_lastPrinted_00.png, tika-app-1.17.metadata.txt
>
>
> Tika extracts a strange last print date for the attached PowerPoint (97-2003)
> In the attached screen shot PPT_lastPrinted_00.png, the date for last print
> was set to 00:00
> But when Tika extracts metadata from this document, the last print date is in
> the year 27321 !
> Last-Printed: 27321-01-23T08:20:12Z
> meta:print-date: 27321-01-23T08:20:12Z
> Attached metadata obtained using Tika 1.17
> This weird date is causing issues further down in processing. We can
> probably filter it out for now, but I do wonder how 00:00 turns into
> 27321-01-23T08:20:12Z
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
