35a - review: an image refusal beside a marker names the line it shares, README wording, 41 filed
CI / gate (push) Successful in 43s
CI / publish (push) Has been skipped

This commit is contained in:
2026-09-28 22:17:22 +02:00
parent daaa2134b3
commit 75c5917712
3 changed files with 20 additions and 13 deletions
+3 -3
View File
@@ -118,9 +118,9 @@ Plain markdown is a second flavour of the same grammar. `adfToPlainMarkdown` wri
tools render — GitHub, GitLab, Obsidian and the like — keeping the content and dropping the rest:
attributes, colours, layout, identity. It refuses only
`not-an-adf-document`, `unsupported-document-version` and `unsupported-nesting-depth`, and writes
no directive. `plainMarkdownToAdf` reads what `markdownToAdf` reads, refusing what it refuses, and
the conventions below as nodes, taking other tools' spellings too; a backslash keeps a marker text:
`\==x==`, `> \[!NOTE]`, `- \[x]`. Markdown
no directive. `plainMarkdownToAdf` reads what `markdownToAdf` reads and refuses what it refuses,
and reads the conventions below as nodes, taking other tools' spellings too; a backslash keeps a
marker as text: `\==x==`, `> \[!NOTE]`, `- \[x]`. Markdown
`adfToPlainMarkdown` wrote reads back and writes again byte for byte; the document it came from
does not come back. To edit a document and save it back, use `adfToMarkdown` and `markdownToAdf`:
saving what this pair read replaces mentions, attachments and macros with text.