Please describe the problem:
libical's conversion of system time zone information into the internal format is intentionally limited to rules for one year. The rationale is that when this information is put into a VTIMEZONE and sent to other programs, these programs get what they are known to handle.

This behavior is problematic in several situations:
* displaying old events or events that are far in the future
* exporting such events

Steps to reproduce:
See bug #548268 comment #21.

Actual results:


Expected results:
libical should convert all information found in the system timezone database. Then later it should be decided per event and usage which part of the timezone information is used:
* internally Evolution should always use all information (events might span changes in the DST rules)
* externally Evolution should pick the definition which matches the closest future recurrences or, if there are none, the first occurence


Does this happen every time?


Other information: