Thanks for this quick fix
Time zone guessing improved, fixes 'Assuming time zone Etc/GMT for Etc/G...
Hi, while playing with the source I saw a strange message in the log: ‘Assuming time zone Etc/GMT for Etc/GMT-2’. That couldn’t be right, so I found validateTimeZone in Event.java to be the cause of this. The current version just checks if one of the available timezones name matches the start of the event’s timezone name, making Etc/GMT match Etc/GMT-2, which is incorrect. My change first looks for an exact match if that fails it executes the old procedure.
Let me know what you think, I’m happy to tune the code if neccesary.