You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ICS data, property values can span multiple lines, with all but the first starting with whitespace.
This seems to only work with standard blank (\x20) and tab (\t), but not with non-breaking space (\xa0).
The text was updated successfully, but these errors were encountered:
Per §3.1 of RFC 5545, those are the only two characters allowed:
That is, a long line can be split between any two characters by inserting a CRLF immediately followed by a single linear white-space character (i.e., SPACE or HTAB).
That said, that doesn't stop implementers from using other characters. Is this a situation you've encountered in the wild? If so, do you happen to know what program created the ICS file in question?
No idea which program was used to create the ICS file, it was a public holiday calendar I used for testing.
Will check if the data maybe got corrupted somewhere on the way...
While being more permissive with the whitespace char might be nice, seems your implementation is spec compliant.
Guess I'll deal with it with an extra "decode" step.
In ICS data, property values can span multiple lines, with all but the first starting with whitespace.
This seems to only work with standard blank (
\x20
) and tab (\t
), but not with non-breaking space (\xa0
).The text was updated successfully, but these errors were encountered: