Closed rjhorniii closed 6 years ago
I've captured an example. It's related to \n vs \r\n at the end of lines, and it's reproducible. So debugging can proceed.
Yes, the RFC says all lines end with \r\n. Google doesn't always do that. ics parser will need more changes.
It might not be Google, but the problem is with the line endings. It's fixed in an update to ics-golang.
There is an occasional problem with line break logic and google. When this happens, the individual lines are ended with a \r rather than being combined into a long line. This does not occur with google events that are created within google calendar by hand. So far, this only occurs with events that are attached to emails, then processed by gmail and added to the google calendar.
The gmail processing also truncates the description. This appears to be a bug/feature of the gmail processing. It's truncated on the Google calendar.
The original emails need to be saved and examined in detail to figure out what was done. The preliminary examination indicates that the attachment is OK and that ical2org converts it properly. The preliminary asessment is that the problem with continuations is related the gmail/gcalendar and not the original ICS. But, this line break mess ought to be fixable. The description shortening appears to be inherent in gmail/gcalendar.