On 29/11/2018 11:08, Marcos Passos wrote:
In addition to the issues you already mentioned:
- Fetching data from different TZDB releases for auditing purposes That one is not just for auditing ... it is essential to unwind historic data that was normalized using an older version! We do need a full working tzdist service of some sort?
- Lack of an API that provides a fast way to find gaps and overlaps for disambiguation purposes
Em qui, 29 de nov de 2018 às 09:00, Lester Caine <lester@lsces.co.uk <mailto:lester@lsces.co.uk>> escreveu:
On 29/11/2018 10:22, Marcos Passos wrote: > We know that, but we have some specific requirement the current API does > not fulfill. Thank you for bringing it up anyway.
It would be useful to know just what? My own problem is the unreliability of the inclusion of the backzone data and the poor support for tracking the version of TZ data being used.
-- Lester Caine - G8HFL ----------------------------- Contact - https://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - https://lsces.co.uk EnquirySolve - https://enquirysolve.com/ Model Engineers Digital Workshop - https://medw.co.uk Rainbow Digital Media - https://rainbowdigitalmedia.co.uk