Quote:
Originally Posted by Gary_M_Mugford
I took a couple of cropped screen shots to show what I see [1] in the columns editor and then in the book editor's custom screen. I hope they have been uploaded correctly here. NOTE: I switched to yyyy-MM-dd in my most recent attempt to fix things.
[...]
At this point, I don't find it hard to believe that it is machine specific rather than a problem with calibre. But I'm at a loss as to HOW it is still functional, yet producing these anomalies.
|
There are clear problems with the Qt (the graphics toolkit) date editing widget. Not much I can do about Qt, unfortunately.
Using the metadata editor with the format set to dd-MMM-yyyy (because I have fixed the format bug and want to use the format that you see):
1) I confirm that clicking on an "undefined" date, it changes to 01 Jan 101.
2) Double-click on the day and change it to 10. Press tab to move to the month. The day change 'sticks'.
3) Type 'Jun' and press tab. The month reverts back to 'Jan' (thanks, Qt).
4) Press tab. The date 10-Jan-101 is stored, so the day stayed changed and the month stayed reverted.
Playing some, I find:
1) if I type a leading 0 into the year field, I am allowed only one more digit between 0 and 7 (why those)? If the first character is something other than a zero, then I can type more digits.
2) If I do not provide a 4-digit year, then the year reverts to its previous value when I leave the date editor. This means that I must change the year to something with 4 digits to make anything stick.
3) If the year has 4 digits, then month changes stick.
To summarize: if the year is changed first to have 4 digits, then from then on editing is reasonably well behaved.
I am looking at the impact of changing the default date to 01-Jan-1000. I think that might work around the editing problem. Of course, it will also prevent entering dates before 1000, which could be a problem where someone has images of ancient manuscripts.