Thank you!
it helps, but still I need to compute the timeoffset. Ok I think I can 
live with it ;-)

Wolfgang

Am 11.05.2014 01:14, schrieb B Bruen:
> On Sat, 10 May 2014 17:32:13 +0200
> "Wolfgang, dl7nb" <dl...@gmx.de> wrote:
>
>> Hi,
>> System.TimeZone is defined as follows:
>>
>>      Return the system timezone.
>>      The returned value is the number of seconds you must add to the
>> locale time to get the UTC time.
>>
>> *That is not always done correctly. *
> Actually, it is correct, it just doesn't recognize "daylight savings". The 
> reason lies deep inside the way tzutils works and somewhere in the extensive 
> documentation.  (I have forgotten where.)
>
>> During winter I used it and it has a result of 3600. This is correct as
>> the difference between UTC and the time her in Germany is 1 hour (or
>> 3600 seconds)
>> -
>> But now (summertime) we have daylight saving time, which means we have a
>> difference of 2 hours. System.TimeZone still shows 3600. It should show
>> 7200 to have the correct number of seconds.
>> -
>> So how can I find out what UTC.time really is??
>> How can I solve this problem?
> Probably the simplest way is :
>    Shell ("date --utc") To sUTCDate
> You can use the date options to return the string as you require it.
>
> hth
>


------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Gambas-user mailing list
Gambas-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gambas-user

Reply via email to