tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1325) Move the font metadata definitions to properties
Date Fri, 06 Jun 2014 15:26:01 GMT

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

Nick Burch commented on TIKA-1325:
----------------------------------

As of r1600917, the AFM and TTF parsers now largely use the same set of plain text keys, and
we have unit tests for both. 

Next step is to identify a suitable external standard, then define metadata properties based
on that (including backwards compatible keys using the current naming), and then convert the
parsers to use those

> 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)

Mime
View raw message