[
https://issues.apache.org/jira/browse/PDFBOX-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297806#comment-14297806
]
Maruan Sahyoun commented on PDFBOX-2619:
----------------------------------------
[~tilman] I think the line
{code}
DateConverter.toISO8601(xmpCreationDate).equals(DateConverter.toISO8601(creationDate)
{code}
in SynchronizedMetaDataValidation together with the current code in
DateConverter will not work correctly as both dates the XMP date and the PDF
date are converted into a Calendar and then formatted into an ISO8601 string
and compared. A better approach might be to convert the XMP ISO 8601 date
string into the corresponding PDF date string and do a string comparison. WDYT?
> XMP dates contain time zone, while document info dates do not, and this isn't
> detected by preflight
> ---------------------------------------------------------------------------------------------------
>
> Key: PDFBOX-2619
> URL: https://issues.apache.org/jira/browse/PDFBOX-2619
> Project: PDFBox
> Issue Type: Sub-task
> Components: Preflight
> Affects Versions: 1.8.8, 2.0.0
> Reporter: Tilman Hausherr
> Attachments: empty_word.pdf
>
>
> Another one from the Bavaria test suite:
> {code}
> /CreationDate(D:20090317081112)
> /ModDate(D:20090317081112)
> <xmp:CreateDate>2009-03-17T08:11:12Z</xmp:CreateDate>
> <xmp:ModifyDate>2009-03-17T08:11:12Z</xmp:ModifyDate>
> {code}
> The info dates do not have a timezone, but the xmp dates do (Z = "Zulu").
> This information (whether there was a timezone information in the string) is
> "lost" in our conversion methods :-(
> Amusingly, PDF Tools says the file is valid.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
