Quote:
Originally Posted by capink
Regarding the date problem reported by Rellwood, from my own testing, it happens only in these situations: - If the day in the date string is the first day of month (=1) it is incremented one day.
- If the day in the date string is the last day of the month (28, 29, 30, 31 depending on month and year), it is decremented one day.
(The presence of absence of time or timezone in the date string does not change this behavior)
The plugin call a function in Calibre (field_from_string > parse_only_date > fix_only_date), which is responsible for the behavior described above. I don't know why Calibre does this, but I am sure there is good reason for it.
This can be bypassed by calling parse_date directly, but since I don't understand the problem of dates very well, I cannot be sure whether this will lead to any unforeseen problems. So, I will leave this problem to someone who understands it better to deal with it.
Edit: Rellwood reported dates where the day is neither the first nor the last day of the month, this does not happen for me.
|
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.