Frank Schönheit - Sun Microsystems Germany wrote:
Hi Alex,
Hi Frank,
This doesn't really have to do with number formatting. The problem is that in the underlying core in all applications, dates are not transferred as "day, month, year", but as "days since <whenever>", where <whenever> is application-, context-, and settings-dependent. And all those places taking a date from whereever, processing it, and using it in a new context, are prone to "forget" that there might be different bases for date calculation. While this is a wonderful (ehm) technical explanation,
:-) Well it helped me anyway to understand the problem better. it doesn't help
the user anything. But it might explain that there is no single point where this problem can be fixed, since in real it's a plurality of problems ... Sorry to say that.
Oh dear, and it also means that you guys have to spend your time continually trying to get something to work again and again when you've already fixed it. :-(
It seems to be a very fragile point in the underlying core. Is there no hope of unifying the API or putting it into a single interface to try and avoid to deal with such problems ?
I agree that every occurance is a potentially severe issue, since it trashs the user's data.
Yes, our professional liability relies on accurate date calculation - we can't afford to have incorrect dates calculated in the documents we send out to our clients :-(
Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
