You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tyler Palsulich (JIRA)" <ji...@apache.org> on 2015/03/20 21:52:39 UTC

[jira] [Commented] (TIKA-1325) Move the font metadata definitions to properties

    [ https://issues.apache.org/jira/browse/TIKA-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372076#comment-14372076 ] 

Tyler Palsulich commented on TIKA-1325:
---------------------------------------

Does anyone know of an external standard for these metadata keys? Or, can we close this off?

> 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.3.4#6332)