Bug#842239: Arbitrary document metadata date chosen

On 3 November 2016 at 07:28, martin f krafft wrote: > Weird. Does the concept of NOW() or TODAY() fade near the dateline? Nah. It was probably brain fade on my part resolving the timezone issues and failing to write regression tests to check them. Plus not wanting to add a

Bug#842239: Arbitrary document metadata date chosen

also sprach Jeffrey Ratcliffe [2016-11-02 21:59 +0100]: > As of v1.5.0, the document date metadata field defaults to the > previous date used. I made this change to fix time zone problems > people near the international date line were having. Weird. Does the concept

Bug#842239: Arbitrary document metadata date chosen

As of v1.5.0, the document date metadata field defaults to the previous date used. I made this change to fix time zone problems people near the international date line were having. For the next version, I have gone back to storing an date offset, using a new dependency to calculate them. I hope

Bug#842239: Arbitrary document metadata date chosen

Package: gscan2pdf Version: 1.5.5-1 Severity: normal I just went ahead to save a scanned document, when I noticed that the document metadata was auto-filled with 2016-10-12 as date. That was 13 days ago. I have no idea where it got this information from, but clearly it should either default to