You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by Oleg Tikhonov <ol...@gmail.com> on 2010/07/06 20:54:04 UTC
Re: [jira] Commented: (TIKA-451) Inconsistent date format for
Metadata.CREATION_DATE and Metadata.LAST_MODIFIED
+1, bull's eye.
On Tue, Jul 6, 2010 at 8:41 PM, Chris A. Mattmann (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/TIKA-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885614#action_12885614]
>
> Chris A. Mattmann commented on TIKA-451:
> ----------------------------------------
>
> +1 to Jukka's suggestion...
>
> > Inconsistent date format for Metadata.CREATION_DATE and
> Metadata.LAST_MODIFIED
> >
> ------------------------------------------------------------------------------
> >
> > Key: TIKA-451
> > URL: https://issues.apache.org/jira/browse/TIKA-451
> > Project: Tika
> > Issue Type: Improvement
> > Components: metadata, parser
> > Affects Versions: 0.7
> > Reporter: Nick Burch
> > Priority: Minor
> >
> > Currently, the PDF Parser does calendar.getTime().toString() which
> means dates end up in your local timezone, and are hard to parse
> > The Open Document parsers output in iso 8601 format, which avoids these
> two problems
> > The poi ole2 based parsers also output in date.toString() format, with
> the same timezone/parsing problems
> > We should probably select one format, and update the parsers to all
> output in it
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
--
Best regards, Oleg.