Read the three directive forms, their attributes and the fences that nest them

2026-09-01 08:12:03 +02:00
parent 4ad80e79c5
commit f328ed4cab
24 changed files with 581 additions and 89 deletions
@@ -87,11 +87,15 @@ least the opening's length, and a container's fence is longer than every directi
 anywhere in its body, however deeply a list item or blockquote nests it; a colon run inside a code
 fence or opaque carry is content. Canonical form uses minimal lengths.
 Directive fence lines follow code-fence indentation (up to three spaces relative to their
-container); trailing whitespace on a fence line is tolerated in input, never emitted.
+container).

 **Leaf block**: `::name arg {attrs}` — a block-position node with no body, `arg` reading as
 above.

+Canonical spacing is the only spacing input reads: one space parts the name, `arg` and `{attrs}`,
+and one parts each attribute pair, with no padding inside the braces. Trailing whitespace on a
+directive block line is tolerated in input, never emitted.
+
 **Claiming at block level**, symmetric with inline: a line whose leading run of two or more
 colons is followed immediately by a name character is claimed and must parse fully as a container
 opening or a leaf, else it is a named error. A bare colon-run line is a closing fence while a