[
https://issues.apache.org/jira/browse/TIKA-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025196#comment-14025196
]
Tim Allison commented on TIKA-1325:
-----------------------------------
Agreed and agreed. Thank you. It looks like FontBox-2122 will set TimeZone to
UTC soon. Both the Apple [apple |
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=2&cad=rja&uact=8&ved=0CCwQFjAB&url=https%3A%2F%2Fdeveloper.apple.com%2Ffonts%2FTTRefMan%2FRM06%2FChap6.html&ei=JbuVU56IDKrgsAT0roDQBQ&usg=AFQjCNF8E9E2b8EkUItZYKvXZHPZ7A_FXw]
and Microsoft [ microsoft |
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&cad=rja&uact=8&ved=0CCAQFjAA&url=http%3A%2F%2Fwww.microsoft.com%2Ftypography%2Ftt%2Fttf_spec%2Fttch02.doc&ei=FbqVU4_rE5S-sQTytYCYBw&usg=AFQjCNEQzC7L5oC8uFzWKFwHM5r0hJNHnw]
specs don't specify UTC, but I'd imagine that is what is meant...but my
imagination is not something to code from. :)
> 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
> Attachments: TIKA-1325_TimeZone.patch
>
>
> 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)
