Open ducky64 opened 10 months ago
any update on that? i ran into the same pproblen, espacially the heavy use of throw.
If you just need it to run and parse calendars, the above diff / patch is sufficient. It will truncate multiline entries. Tested on a ESP32-S3, not sure it will run on something much weaker.
Ultimately, I think this library's structure is too brittle (non-recoverable validation) for my application, I instead chose to offload processing to a external server running Python that has a more robust parser.
yeah, im building an e paper calendar, i also thought about that, but i dont think im giving up yet. i also saw there are some forks, but my cpp knowledge is not good enough to check if they acutally work / improve stuff, but certainly seems so.
Thank you @ducky64, I'm not currently working in uICAL, but feel free to submit a pull request with new and passing tests.
should be interpreted as
per https://icalendar.org/iCalendar-RFC-5545/3-1-content-lines.html, where newline plus whitespace should effectively be discarded.
Currently, the parser tries to interpret these as VLINEs and errors out.
This gets generated by Google Calendar exports.
For anyone trying to just get something to work, a hack solution to discard the extra lines is:
In general, the parsing is very strict, which would seem undesirable for embedded applications and deployments which should probably prioritize uptime and availability.