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

Fix \n being escaped to \\n, leading to no newlines in actual text #617

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

tobias-93
Copy link
Contributor

If a newline is included in a text field, such as the description, the backslash in \n is first doubled by the parser (so converted to \\n), then the \n is parsed. This results in \\n being included in the final ICS export, which is shown in calendar tools as \n instead of a newline. This PR fixes that, to make sure an intentional \n in the input is also exported as a newline.

@markuspoerschke
Copy link
Owner

Looks good to me, thanks!

@markuspoerschke markuspoerschke merged commit ecbff43 into markuspoerschke:2.x Jul 11, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants