Perhaps I am working on too old of GNUStep base. I am still working
from 1.7.1, and have been too afraid of breaking my application to
move to the latest release. Now that I have shipped my app, perhaps I
can move forward to current gsbase. I have some nice jucy bugs that I
need to see if you have already fixed before I report them. (with
fixes of course) ;-)
I can tell you that in 1.7.1, GSbase most certainly did not use the
windows timezones before I changed it.
I'm sorry I brought it up, if it has already been delt with. In fact
you might be using my patch for all I know.
If you want to write this down in your scrapbook or something, on
9/22/2004 my company shipped our first commercial product using
GNUStep-base on Windows.
Our changes to gnustep stuff can be found at
http://www.deadbeef.com/gnustep/
----- Original Message ----- From: "Adam Fedor" <address@hidden>
To: "Jeremy Bettis" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, December 21, 2004 10:46 AM
Subject: Re: Re[2]: CEST TimeZone
On Dec 21, 2004, at 9:03 AM, Jeremy Bettis wrote:
<rant>
I think it is a shame that GNUstep has it's own set of timezone
files instead of just using the operating system's timezone info.
At least, how about not using them when the OS has zoneinfo or good
native time zone support. Such as Linux, Solaris, and MS-Windows.
Then you'd only need to install GSTimeZones on old crufty systems.
I have a patch ready for anyone who wants it that will make GNUStep
on Win32 ignore the GStimezones and use the Microsoft timezone
information, which is really quite complete.
GNUstep currently does use the system timezone information if it's
available (even on Windows). Did you know about this when you made
your patch, or does you patch fix something that is broken with the
current implementation?
I know the issue that will come up is DO, and NSCalendarDate
archiving. How about using GMT+offset in date coders.
</rant>
Also an issue I addressed previously:
http://lists.gnu.org/archive/html/bug-gnustep/2004-10/msg00018.html
although I have not implemented it.