
Paragraph break that many parsers and editors mishandle.
line-separatorinvisibleUnicode's own line and paragraph breaks, separate from the line feed and carriage return inherited from ASCII. They mean the same thing and are handled correctly by far fewer programs.
From word processors and page-layout software, and from anything that converted rich text to plain text without normalising the breaks.
Rarely enough that TraceFree PRO replaces them with an ordinary line feed rather than deleting them: the break was meant, only the encoding of it was unusual.
| Preset | Action |
|---|---|
conservative | replaced |
default | replaced |
report-only | asked about |
strict | replaced |
Context guards can only ever make a cleanup gentler, never sharper. A rule saying “always remove” does not override them.
In TraceFree PRO, turn on the clipboard watcher and copy the text. On the command line:
tracefree clean --backup document.txt
pbpaste | tracefree clean | pbcopyReport without changing anything — exit code 1 on findings, so it works in CI:
tracefree check -r ./docsThis page never prints the character itself, only ways of writing it. A page about invisible characters that contained invisible characters would be unreviewable — and that is the problem the program exists to solve.
| Notation | Value |
|---|---|
| Unicode | U+2029 |
| Rust | \u{2029} |
| JavaScript, Python | \u2029 |
| HTML | 
 
 |
| Regex (PCRE, Rust) | \x{2029} |
Paste anything into the browser demo and see what is in it. Same engine as the app, running entirely on your device — nothing is uploaded.

