11.06.2019 15:30, Lester Caine wrote:
On 11/06/2019 12:32, Vlad Khorsun wrote:
One of "simple" solutions could be to ask sever once for whole conversion
table and to keep it at some temp file (or nearby fbclient\app) for future
usage.
It is also not ideal, as different servers could have different ICU versions,
but
it could be a starting point to think on the better solution.
So, actially, we need not an "id to name" conversion table. We need whole
time
zone database. It is a "bit" more complex task.
It is even more complex that that ...
The IDENTIFIERS used in the TZ database are purely that. Identifiers. And the guide lines for using TZ data points specifically to
using something other than those identifiers when supplying displays in client applications. On top of this, the current rule set
being used by the operating system may well not match the rules used previously to when processing the data, so we need access to
ALL the historic changes to the rules or at least a copy of the rules used to store data and the current rules with some mechanism
to update that data ...
Yes, and we want to avoid it at client side.
Windows have its own time zone database and it support historic changes in
rules
but it is not complete (comparing with ICU's one) and often is outdated (we
speak
about client machines, not servers).
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
