From 696ee21e6314ee9b0d5776a45c7b37bacf71c969 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Wed, 14 Oct 2026 00:39:29 +0200 Subject: [PATCH] =?UTF-8?q?Answer=20architecture=20round=202:=200=20?= =?UTF-8?q?=F0=9F=94=B4,=200=20=F0=9F=9F=A1;=20the=20spec=20names=20a=20li?= =?UTF-8?q?ne=20opening=20another=20block=20as=20ending=20the=20table?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- spec/flavour.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/flavour.md b/spec/flavour.md index 42612f6..fe705cc 100644 --- a/spec/flavour.md +++ b/spec/flavour.md @@ -348,8 +348,8 @@ claimed and must parse as part of a pipe table, else it is a named error — esc holding an unescaped `|`, followed inside one paragraph by a line whose cells are all `-` runs, an alignment colon among them, and match it in count — GFM's table without the outer pipes — is a named error rather than the prose it reads as. `portableMarkdownToAdf` reads that shape as a -table, its body rows with or without the leading `|` until a line holding none, and drops an -alignment colon's alignment. A pipe table is a header row, a delimiter row whose cells are runs of +table, its body rows with or without the leading `|` until a line holding none or opening another +block, and drops an alignment colon's alignment. A pipe table is a header row, a delimiter row whose cells are runs of one or more `-` (canonical `---`), and body rows; rows follow code-fence indentation. Cells split on unescaped `|` before inline parsing — `\|` stays in the cell text, and the inline layer's ordinary CommonMark escaping yields the pipe; each cell is the inline content of