On Sunday 19 June 2016 11:31:39 John Ralls wrote: > Devs, > > Bug 767824[1] has me thinking about this again. As I think everyone > knows I want to change it from midnight local to 11:00AM UTC for the > next version, but since fixing this bug also requires a scrub > function at file read time to correct the (probably few) files with > borked timestamps I'm thinking of doing it now. > > To review, a timestamp of 11:00AM UTC won't change date with the > timezone except in -12, the zone immediately to the east of the > International Date Line, and +13 and +14. Places affected according > to [2] include Adak, Midway, and Baker Islands (-12), Samoa and > Tokelau (+13), and Kiribati (+14). > > Comments? > > Regards, > John Ralls > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=767824 > <https://bugzilla.gnome.org/show_bug.cgi?id=767824> [2] > http://www.timeanddate.com/time/map/ > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Hi John, In addition to the time stamp use cases Christian already mentioned, I believe the time stamp is also relevant for sorting entries on an invoice/bill ledger. This was implemented as a hack by Christian IIRC such that to move an entry up or down the list on the same day, internally the post dates of the two entries would be swapped. As the post times currently all differ, this would effectively alter the sorting order. If all post times will be normalized this hack will no longer work. That's one other case to keep in mind when dropping post times. Other than that I'm fine with making the time change for the next release. Regards, Geert _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
