Quoting Graham Leggett <[EMAIL PROTECTED]>:
> Try the string "2008-04-11 00:02:00 +0200". Same timestamp. Different date.
* sigh *
Are you intentionally ignoring my repeated statement that we need
to CHANGE GNUCASH TO USE 1200Z? Let's try this example again with
that, and maybe we'll stop talking past each other:
2008-07-15 12:00:00 +0000 ==
2008-07-15 08:00:00 -0400 (US/EDT) ==
2008-07-15 05:00:00 -0700 (US/PDT) ==
2008-07-15 19:00:00 +0700 (???)
Notice how they ALL HAVE 7-15!
> The idea of an implicit timezone is nice in theory, but it comes with
> the responsibility of ensuring that the timezone is respected
> correctly everywhere a date is used. Practically, this just isn't
> going to happen, which means the bug will keep coming back.
Nah, it's pretty easy to be consistent. Indeed, GnuCash *IS*
already very consistent on this already.
> Regards,
> Graham
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
