[
https://issues.apache.org/jira/browse/TIKA-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019980#comment-14019980
]
Nick Burch commented on TIKA-1325:
----------------------------------
I didn't change the date parts, I just added a test which touched them...
We currently fetch a Date object from FontBox, then pass that into the Tika
Metadata for an internalDate property
Any chance you could step into the code in your "non standard" timezone, and
see if you can work out if it's a problem with FontBox, or a problem with how
we're using the date that fontbox gives us?
> Move the font metadata definitions to properties
> ------------------------------------------------
>
> Key: TIKA-1325
> URL: https://issues.apache.org/jira/browse/TIKA-1325
> Project: Tika
> Issue Type: Improvement
> Components: metadata, parser
> Affects Versions: 1.5, 1.6
> Reporter: Nick Burch
>
> As noticed while working on TIKA-1182, the AFM font parser has a bunch of
> hard coded strings it uses as metadata keys, while the TTF font parser
> doesn't have many
> We should switch these to being proper Properties, with definitions from a
> well known standard (+ compatibility fallbacks), and have both use largely
> the same set
--
This message was sent by Atlassian JIRA
(v6.2#6252)
