A better idea would be to start GnuCash with `TZ=EST5EDT gnucash`.
I think the simplest way to address the different timezone problem is to change
the XML backend to always store the time in UTC like the SQL backend does. A
time with a TZ mark is really UTC anyway, and internally all timestamps
A developer would have to chime in on those questions.
Regards,
Adrien
> On Oct 20, 2018, at 1:40 PM, Clayton Dewey wrote:
>
> Thanks, that's a good idea. I'll take that approach in the meantime.
> Long term, is this issue scheduled to be fixed in a future release?
> Would some level of financi
Thanks, that's a good idea. I'll take that approach in the meantime.
Long term, is this issue scheduled to be fixed in a future release?
Would some level of financial support help make that happen? I imagine
this is an issue for other geographically distributed companies.
Thanks,
Clayton
On 10/20
Possibly create a separate user account on the computer just for using GnuCash
and set it to EST — not convenient, but certainly avoiding confusion. Consider
setting a different screen background so you know at a glance which user you
are working with.
Regards,
Adrien
> On Oct 20, 2018, at 12:
Hi All,
I recently joined a company that uses GnuCash and have been enjoying
learning the application.
We are a distributed company and do all business in EST, while I reside
in MST. I know there is a bug in GnuCash where if I save a file in my
timezone it overrides the transaction date and time
