Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom timezones handling #8

Open
GoogleCodeExporter opened this issue Mar 1, 2016 · 0 comments
Open

Custom timezones handling #8

GoogleCodeExporter opened this issue Mar 1, 2016 · 0 comments

Comments

@GoogleCodeExporter
Copy link

iCalendars often contain custom Timezone definitions (VTIMEZONE) which are not 
matching standard timezone names. In such a case the library will, wrongly, 
throw a 'bad parameter' exception.

The attached file is a test case.
In that file, parsing
EXDATE;TZID="Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna":20101216T10000
... will cause an exception

The library should handle custom timezones, but will presumably need a more 
richer  implementation than java.util.TimeZone: for example JodaTime's 
DateTimeZone which can be build dynamically by DateTimeZoneBuilder.


Original issue reported on code.google.com by [email protected] on 12 Jan 2011 at 8:53

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant