Hi Derrell, I'm using Firefox Version 3.6.3
My idea for a workaround is that the RpcJava backend can take care of the problem while serialization and de-serialization the date objects. I'll have a look at it, maybe I'm able to provide such a workaround. Regards, Andreas Von: Derrell Lipman [mailto:[email protected]] Gesendet: Samstag, 12. Juni 2010 12:54 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] Java backend and Javascript date On Sat, Jun 12, 2010 at 05:01, Fink, Andreas <[email protected]> wrote: Hi, I've digged deeper in the problem and found out that the daylight saving offset is handled different in Java and Javascript. For example: The date 04/01/1980 is in javascript handled with a daylight saving offset and in Java without the offset. (In the year 1980 the daylight saving hour was added on the first Sunday in April. Javascript add the hour at the last Sunday in March...) Java does a quite good job compared to the official rules you can find here (in German): http://de.wikipedia.org/wiki/Sommerzeit#Deutschland Javascript only uses the last official daylight saving rule and not the really used rules. That's really hard to handle. That's almost certainly JavaScript-implementation specific. It is, actually, a very difficult job to keep up with daylight savings time rules. They change throughout the world on a much more frequent basis than one would think. There are regular updates to the Linux package that handles such things... and much less frequent updates to some browsers. What browser and browser version are you using? Derrell ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
