tika-dev mailing list archives

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

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

Hudson commented on TIKA-1325:

SUCCESS: Integrated in tika-trunk-jdk1.7 #28 (See [https://builds.apache.org/job/tika-trunk-jdk1.7/28/])
TIKA-1325 Have the TTF parser pull out a little bit more, and have it do so similar to the
AFM one does, plus add some TTF tests (nick: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1600917)
* /tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/font/AdobeFontMetricParser.java
* /tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/font/TrueTypeParser.java
* /tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/font/FontParsersTest.java

> 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

View raw message