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
When multiple sequential new line characters appear inside a quoted CSV field, Pandoc coalesces these into a single SoftBreak in the resulting AST. According to RFC 4180, this would seem to be incorrect behavior. The RFC's grammar treats CR and LF like any other character inside a quoted field.
Shouldn't individual LineBreaks be returned for \r\n\r\n\r\n rather than a single SoftBreak by the CSV reader?
At minimum, I would think there should be no information loss during the read, which means encoding the original number of line breaks in some way. Currently, it's not possible to reconstruct the input data accurately from the AST.
Tested with Pandoc 3.1.13
The text was updated successfully, but these errors were encountered:
you'll see that the table cell content in current.odt does not preserve line breaks accurately, whereas expected.odt is correctly formatted like the input CSV above.
When multiple sequential new line characters appear inside a quoted CSV field, Pandoc coalesces these into a single
SoftBreak
in the resulting AST. According to RFC 4180, this would seem to be incorrect behavior. The RFC's grammar treats CR and LF like any other character inside a quoted field.Shouldn't individual
LineBreak
s be returned for\r\n\r\n\r\n
rather than a singleSoftBreak
by the CSV reader?At minimum, I would think there should be no information loss during the read, which means encoding the original number of line breaks in some way. Currently, it's not possible to reconstruct the input data accurately from the AST.
Tested with Pandoc 3.1.13
The text was updated successfully, but these errors were encountered: