[
https://issues.apache.org/jira/browse/TIKA-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019970#comment-14019970
]
Tim Allison commented on TIKA-1325:
-----------------------------------
Nick,
Thank you for fixing this. I just tried to build with both:
java version "1.6.0_30" and
java version "1.7.0_40"
on Red Hat Enterprise Linux Server release 6.5 (Santiago)
I got this:
Failed tests: testTTFParsing(org.apache.tika.parser.font.FontParsersTest):
expected:<1904-01-01T0[0]:00:00Z> but was:<1904-01-01T0[5]:00:00Z>
Looks about the same amount as our time zone differences with BST? :)
> 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)
