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
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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: