[BUG] incorrect timestamps applied to metadata in content.opf

[Hasimir]

[BUG] incorrect timestamps applied to metadata in content.opf

[Hasimir]

The test project created for #69 includes a demonstration of this error as it includes a generated EPUB 3 file with a detached GPG signature file. The GPG signature can show that the file could not possibly have been created at the timestamp it uses ... well, not without breaking a 4096-bit RSA and 512-bit SHA2.

To verify the signature on the file, my key is: 0x321E4E2373590E5D

It can also be found in many of my github projects, on the MIT keyserver and the SKS keyserver pool.

[drmacro]

I see the problem. Will investigate.

[drmacro]

Hasimir says:

As mentioned on dita-users the previous fix to convert localtime to UTC is an odd half-fix. Specifically the time conversion does correctly calculate the difference between the system time which the OT runs on and UTC, including adjusting the date where necessary. However the time is only ever recorded as a 12 hour clock and not a 24 hour clock. So any UTC time between 13:00Z and 23:59Z loses 12 hours.

I am not certain what happens with 00:00Z since I haven't run a transformation at exactly that time. I'm also not certain if this is an issue with XSLT or Java itself. It is, however, less of a worry than the situation prior to the half-fix since it does at least prevent the generation of a timestamp in the future from the point of the transformation which was previously the case for those of us ahead of UTC (i.e. from Europe to Asia and Oceania). It is also not picked up by epubcheck.

[Hasimir]

Fix tested with OT 1.8.5 and works as expected.