John, your point about "GnuCash isn't for you" is well understood, but it is unfortunately also a very sad state of affairs. The transaction date bug is a major design flaw that has been in GnuCash from the very beginning, and that has been recognized as a major flaw since more than 16 years ago.
It is not in principle difficult to fix. I even started doing so myself in 2014. The reason I never finished fixing it is that the datatype used for transaction dates propagates to hundreds of places where it is hardcoded, crossing several programming languages and data representations (e.g., Scheme for the report system, XML for saved accounts, etc.). This makes it difficult to fix in an incremental way. I was simply not familiar enough with the sprawling code base to have any confidence that the bugfix wouldn't cause problems elsewhere - there are many subsystems of GnuCash that I never use at all. If there is any more experienced GnuCash developer who is actually familiar with how all these subsystems hang together, I'd be happy to have another go at fixing this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/365065 Title: gnucash is confused by timezone changes To manage notifications about this bug go to: https://bugs.launchpad.net/gnucash/+bug/365065/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
