dates already entered still depend on local time zone settings?

[paolo palmerini]

geert,
thanks for the reply.
i had a look at the bugreport. the situation is what you mentioned: the
bug was first reported in 2004, since then there has been only one patch
proposed but has never been committed. now the activity on this bug
seems to be quite reduced, if any. apart from adding my personal request
for a bugfix, i wonder how could i contribute to make gnucash improve on
this. i have some coding skills but probably it would take me too long
before i be able to contribute to gnucash code development.

the patch proposed solution would work for me, but until it is
committed, i cannot use it.

so, there are two workarounds for me:

1. impose setting the same time zone on all computers from which my
gnucash file is being modified;

2. implement the patch algorithm as a separate external parser (might be
a few lines perl script) that "corrects" the XML gnucash file. 

for many reasons (having little to do with gnucash and more with my
organisation internal structure), the second solution could be the best.

but of course none of them would be as good as having gnucash correctly
dealing with time zones. so, if there is anything that i could do to
make it happpen, i'll be glad to try.

thanks
p.


On 02/10/2011 05:57 PM, Geert Janssens wrote:
> On Thursday 10 February 2011, Peter Boosten wrote:
>> On 10 feb 2011, at 15:40, Geert Janssens <janssens-geert at telenet.be>
>>
>> wrote:
>>> I don't see a good work around for this situation, sorry. Perhaps
>>> someone else
>>> can help you with that.
>> Not having investigated this, but trying to look with a fresh view:
>>
>> Where does that time in the xml come from (midnight in this case)? If
>> this is just a fictuous time, then setting it to noon gives you twelve
>> hours of time zone slack without ever resetting the date.
>>
>> On the other hand, if the times really matter, then why not store the
>> timestamp in UTC, and display in local time? A transaction in this
>> time zone is probably on a different date than when entered in China.
>> Might come in handy whenever GC goes multi user.
>>
>> One for the programmers :-)
> Thanks for your suggestions. But can you please add your comments in the 
> bugreport I mentioned ? That will keep all information regarding this topic in 
> on central place.
>
> Thanks
>
> Geert
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> 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.
>
>

-- 
me, myself... [http://www.palmerini.org]
...and my podcast
[http://www.palmerini.org/podkasbaht]