Hi, I know you're aware of the problem, but I'm adding this so it's not lost. A Debian user asked if it was possible for orage to support system timezone data instead of shipping its. This is valid for a lot of good reasons, so I'm adding this bug. Thanks for the work, keep going! Cheers, -- Yves-Alexis
Yes, I 100% agree. Several good reasons to do this; one of which is to be able to fix Bug 3876. It just is not easy.
(In reply to comment #1) > Yes, I 100% agree. Several good reasons to do this; > one of which is to be able to fix Bug 3876. > It just is not easy. > Maybe tzfile(5) manpage could help you? (the debian reporter pointed this manpage) Cheers,
*** Bug 4848 has been marked as a duplicate of this bug. ***
*** Bug 3834 has been marked as a duplicate of this bug. ***
Any news on this?
I have coded conversion program, which reads os tz timezone data and outputs libical timezone data. It has been tested and is waiting that we can again start using trunk after the 4.6.... Currently the conversion process is manual. I am not sure if it is worth automating or if it is good enough that people can run it when needed (=when tz data changes). I am planning to create better timezone selection library function, which will then fix 3876. That will take some time.
Thanks! (I guess you can start breaking trunk, if 4.6 is the stable branch :) )
This is finally done in git Orage 4.7.4. There is now conversion utility (tz_convert) which can change data from system timezone files to ical format, which is used i Orage. So the support is not realtime, but Orage now supports zoneinfo data.
in 4.8.0