View Single Post
Old 08-10-2020, 02:00 PM   #495
capink
Wizard
capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.
 
Posts: 1,207
Karma: 1995558
Join Date: Aug 2015
Device: Kindle
Quote:
Originally Posted by davidfor View Post
This was asked a long time ago. At the time, I suggested time zone issues. I don't remember if I looked at it then, or some other time for another plugin. If I remember rightly, it is calibre trying to compensate for a timestamp that in one place has a timezone and in another place doesn't, or doesn't need the timezone.
Quote:
Originally Posted by thiago.eec View Post
When I was working on Skoob Books plugin (Jun. 2019), I've noticed this.

Skoob website only give us the year of publication, so I chose to set the pubdate to YYYY-01-01, but this made dates to be set as (YYYY-1)-12-31. As a workaround I chose to set it as YYYY-01-02. Since the real date was only the Year, this would make no difference.

Now, I've just checked and setting pubdate as YYYY-01-01 works normally. It must have been fixed in this interval.

I asked Kovid about this issue and he said that it is done so that the month is one in all time zones, and that it is safe to bypass it using parse_date.

Thanks for your input.
capink is offline   Reply With Quote