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.

Sign up for GitHub

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

Jump to bottom

Timezone #1

Open
melitele opened this issue May 15, 2015 · 1 comment
Open

Timezone #1

melitele opened this issue May 15, 2015 · 1 comment

Comments

@melitele
Copy link
Member

Since Furot trip timing is displayed in the timezone of current stop, generated iCalendar data should contain timezone components (VTIMEZONE - see http://tools.ietf.org/html/rfc5545) at stops after each timezone change.
@pirxpilot
Copy link
Member

That looks like a calendar software ignoring iCal spec. What Furkot exports is known as floating time - which corresponds to a local time regardless of timezone. Google Calendar does not have problems with it.

We can of course switch to exporting fixed time - UTC time + TZ info - especially if it turns out that many calendard apps cannot properly handle floating time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pirxpilot @melitele