Escapes a pipe where the format would end the cell at it
All 4 scenarios hold
The reporter publishes the value a row ran with, and not the text of the cell. It therefore writes every value back out, and each format writes that value back the way that format can.
Where the formats differ, the rules below show all three side by side. Markdown and AsciiDoc come first. Both are plain text, and both answer most questions alike. HTML comes last, because its answer is markup and always the longest.
A collection does not fit that shape. Markdown alone puts a whole collection inside a table cell. AsciiDoc opens a bulleted block or a description list below the cell. HTML nests list markup inside the cell. A table can hold neither of those, so the notation rule belongs to markdown alone.
Markdown and AsciiDoc both end a cell at a pipe. A value that holds a pipe would split the row, and the table would lose a column from that point on. Both formats therefore escape every pipe in the value, wherever that pipe sits: in a plain value, in a sentence, or inside a collection.
HTML has no cell delimiter to protect, so it leaves the character alone. It still counts a pipe as significant whitespace, which is the ws class in its column.
| Scenario | Cell | In markdown? | In AsciiDoc? | In HTML? |
|---|---|---|---|---|
| A value that is one pipe | "|" | \| | \| | <span class="literal ws">|</span> |
| A pipe inside a sentence | "Text with | a pipe" | Text with \| a pipe | ++Text with ++\|++ a pipe++ | <span class="literal ws">Text with | a pipe</span> |
| A pipe inside a set | {"||"} | {\|\|} | * \|\| | <ul class="coll set"><li><span class="literal ws">||</span></li></ul> |
| A pipe inside a map value | [b: "||"] | [b: \|\|] | ++b++:: \|\| | <dl class="coll map"><dt>b</dt><dd><span class="literal ws">||</span></dd></dl> |