Hector VillarrealandClaude Opus 5.5 533c0dadaf #2225: a field that only looks quoted keeps the tabs and line breaks in it ...

Addresses CodeRabbit review on #3231, "Reparse consumed separators when a
field is not quoted": parse_tsv read "a<TAB>b"x as one quoted field,
then fell back to its raw text without the separator it had consumed,
so the cells "a, b"x and c pasted back as two. The new copy (which no
longer quotes a cell holding only a quote) makes that text. A field
whose closing quote doesn't end it, or that never closes, is now read
again as unquoted text, so its tabs and line breaks separate cells.
The text read again is bounded by the input's length, so hostile input
stays linear.

Test: a_field_that_is_not_really_quoted_keeps_its_separators.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-03 04:19:49 -06:00

..

examples

fix: satisfy stricter clippy lints CI's newer stable toolchain catches

2026-10-12 02:52:07 +02:00

src

#2225: a field that only looks quoted keeps the tabs and line breaks in it

2026-11-03 04:19:49 -06:00

tests/it

Merge the updated Python cells branch (57d7ea9b, main 25881a8e) into the Python mode layer

2026-11-02 02:52:48 -05:00

Cargo.toml

Equations: Insert › Equation with a LaTeX editor, Office Math in xlsx and equations in PDF (#471)

2026-11-02 15:45:36 +01:00