[
https://issues.apache.org/jira/browse/TIKA-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020025#comment-14020025
]
Tim Allison commented on TIKA-1325:
-----------------------------------
Looks like Fontbox/TTFDataStream isn't setting a timezone, so it defaults to
"default" timezone. My nonstandard default is different from your standard
default. :)
{code}
/**
* Read an eight byte international date.
*
* @return An signed short.
* @throws IOException If there is an error reading the data.
*/
public Calendar readInternationalDate() throws IOException
{
long secondsSince1904 = readLong();
GregorianCalendar cal = new GregorianCalendar(1904, 0, 1);
long millisFor1904 = cal.getTimeInMillis();
millisFor1904 += (secondsSince1904 * 1000);
cal.setTimeInMillis(millisFor1904);
return cal;
}
{code}
Should we comment out:
{code}
assertEquals("1904-01-01T00:00:00Z",
metadata.get(Metadata.CREATION_DATE));
{code}
> 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)
