Quote:
Originally Posted by JimmXinu
FFF calls Calibre's set_custom() using the date string as formatted by your dateX_format setting from personal.ini.
I think what's happening is that Calibre looks at your formatted date and makes assumptions about it, trying multiple possible formats and keeping the first one in its list that works. And mon-day-year is before day-mon-year in that list.
This sounds kinda familar; I think we've seen something like it before. But good luck finding it...
Calibre's Published and Date columns are built-in and FFF populates them with the 'raw' date values, removing any confusion. The tweaks only apply to them.
|
That makes sense. For now I have edited my .ini date formats to be in ISO-format which at least takes care of the issue of calibre importing a blatantly wrong date (also lets file this one under yet-another-time-the-saved-metadata-column saved my ass).
Me thinks a better solution might be to always use ISO dates for import and date formats just for titlepage. If I were to go have a look at the code to make that change would it be wanted? (or are there a thousand other intricacies that I am blatantly unaware of when thinking up this approach?)