This fixture proves the mandatory quotation-mark, reverse-solidus and newline escapes without changing a readable accented character or the ordinary solidus.

Input and expected output

Enter the two lines `Ada said "C:\notes"` and `next line — café` as raw text, select Escape, Quoted JSON string and Readable Unicode. The exact result is `"Ada said \"C:\\notes\"\nnext line — café"`. The outer quotes belong to the complete JSON value; the inner quotes and path reverse solidus are data; the physical line break becomes the two-character escape \n.

Round-trip check

Copy the result, choose Unescape once with Quoted JSON string, and transform it. The original two lines return exactly. The em dash and é remain readable because neither character must be escaped by RFC 8259. Choose ASCII-only before escaping to represent those non-ASCII scalars with \u sequences instead; both forms decode to the same Unicode text when the destination follows the standard.

Verify the destination and layer count

Compare the result with the producer and destination contracts. JSON escaping protects only one JSON string grammar; it does not sanitize HTML, SQL, JavaScript, shell input or another parser. Decode one reviewed layer at a time, reject malformed Unicode, and keep a known fixture for important integrations.