On Friday, January 27, 2012 22:37:53 you wrote: > On 28/01/2012, at 1:03 AM, ext Stephen Kelly wrote: > > On Friday, January 27, 2012 13:30:35 Thiago Macieira wrote: > > > Correct. What do we need extending them with? The only virtuals you > > > left in the API were stream (which I didn't get) and utcOffset, > > > which doesn't seem to need to be a virtual. > > > > Different timezones (and countries) have daylight savings time at > > different times of the year (or different days from year to year). > > Different implementations of utcOffset would take account of that. So > > there's a dependence on both the timezone and the datetime object. > > > > What do you propose? > > > > > > And therefore the olson db and > > > > windows registry timezone information code would need to be in > > > > QtCore?> > > > > See Lorn's email. I don't know why we'd need to keep them in QtCore. > > > > Lorn's email said he used the windows and olsondb info. If not in > > QtCore, where would they go? > On *nix, since the timezone database is part of the system/distribution, the > db doesn't need to be in Qt, although it _could_ be. The conversion was > only best name/place match, but you could get valid windows timezone data > in windows using "Australia/Brisbane" without cygwin, and vice versa, "E. > Australia Standard Time" on linux/mac would get Australia/Brisbane.
I'm not convinced a 'best match' timezone mapping is good enough. That's why I proposed an interface where both Olson and windows can be first class citizens. > > Anyway, I think Lorn needs to give more input and maybe his patch. > > I have attached a patch to the QTBUG-71 > https://bugreports.qt-project.org/secure/attachment/27114/tz2.diff Thanks. Do you intend to polish up and port it to Qt5? -- Stephen Kelly <[email protected]> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
