On Tue, Apr 4, 2023 at 7:03 AM john <jra...@ceridwen.us> wrote: > Nope. Whoever implemented that 20 years ago didn't hook it up to anything > and nobody has since. Maybe because the implementation itself isn't very > useful. It's saved as a string, and only "Asia/Tokyo", "Australia/Sydney", > "America/New_York", "America/Chicago", "Europe/London", or "Europe/Paris" > are available. To apply it to a time would require conversion to a > gmtoffset. > > But once you had that what would you do with it? Quotes almost never have > a time on them. I guess you could apply a rule that says that if right now > is between 0900 and 1600 on the indicated date (quotes do usually have > dates) in the security's time zone then that's the time of the quote, > otherwise it's 1600 in that timezone on the indicated date. The quote > display would have to be tz-sensitive too. I'm not at all convinced that > doing all of that would materially improve anything, and implementing it > would be a lot of work. >
Would it be correct and helpful if Currently, the timezone setting is ignored were added to the Investment section on creating a new security in the Gnucash Guide? _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
