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

End of paragraph character not parsed properly #43

Open
bdno86 opened this issue Jun 30, 2024 · 1 comment
Open

End of paragraph character not parsed properly #43

bdno86 opened this issue Jun 30, 2024 · 1 comment
Labels
proposal Uncommitted improvement ideas

Comments

@bdno86
Copy link

bdno86 commented Jun 30, 2024

Whenever I use \r instead of \n in strings contained in a JSON file, I expect that character to be parsed as a 'new paragraph' rather than a 'newline'.

It however seems that \r and \n are parsed the exact same way and both lead to a new line.

@rxcle
Copy link
Owner

rxcle commented Jun 30, 2024

Indeed there is at present [1.5.0] no mechanism to create new paragraphs from a single OUTPUT source. Any line break character from the source data will be turned into a soft linebreak within the existing paragraph.
One workaround for this limitation is to add a script that inserts appropriate paragraph breaks after the fact. Not ideal, but depending on the case it may work.

Thanks for pointing out this current shortcoming. It is added to the ambition list for a better out-of-the box solution in a future release.

@rxcle rxcle added proposal Uncommitted improvement ideas clarify Needs more details labels Jun 30, 2024
@rxcle rxcle added this to the backlog/minor-some milestone Jun 30, 2024
@rxcle rxcle removed the clarify Needs more details label Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Uncommitted improvement ideas
Projects
None yet
Development

No branches or pull requests

2 participants