3
0
mirror of https://github.com/larvit/adf-codec.git synced 2026-11-21 15:42:58 +01:00

Answer product-owner round 1: 0 🔴, 1 🟡 (0 misread); state the 32-try rule in the README and the flavour spec

This commit is contained in:
2026-10-30 21:00:05 +01:00
committed by Lillem4n
parent b0a94fb896
commit 1f33007ae2
2 changed files with 4 additions and 2 deletions
+2 -1
View File
@@ -479,7 +479,8 @@ saving what this pair read replaces mentions, attachments and macros with text.
its key, `_(jira-issues-table not included)_`, or `_(extension not included)_` without one, and its key, `_(jira-issues-table not included)_`, or `_(extension not included)_` without one, and
`_(synced block not included)_` for a `syncBlock`. `_(synced block not included)_` for a `syncBlock`.
- `backgroundColor`, `code`, `em`, `link`, `strike` and `strong` stay; every other mark drops, - `backgroundColor`, `code`, `em`, `link`, `strike` and `strong` stay; every other mark drops,
keeping its text, and so does a mark the flavour cannot spell where it stands. Code text keeps keeping its text, and so does a mark the flavour cannot spell where it stands. A line still
read back wrong after 32 tries drops every `em`, `strike` and `strong` at once. Code text keeps
no mark but `code` and `link`. no mark but `code` and `link`.
- A newline in text is a hard break and in an expand's title a space, edge whitespace outside a - A newline in text is a hard break and in an expand's title a space, edge whitespace outside a
link or code span is trimmed, carriage returns and null characters are removed, and an empty link or code span is trimmed, carriage returns and null characters are removed, and an empty
+2 -1
View File
@@ -573,7 +573,8 @@ putting a code span outside another mark, `code` over anything but a text node h
text holding a line ending or a null character, or a spelling CommonMark's flanking rules cannot text holding a line ending or a null character, or a spelling CommonMark's flanking rules cannot
open or close where the run sits (`un**-real**istic`), or one CommonMark's matching pairs elsewhere open or close where the run sits (`un**-real**istic`), or one CommonMark's matching pairs elsewhere
— the intra-word `*` runs together with a neighbouring `**`, and the multiple-of-3 rule can leave — the intra-word `*` runs together with a neighbouring `**`, and the multiple-of-3 rule can leave
the merged run's pairing to another delimiter — rides the inline carry whole. An opaque carry inside the merged run's pairing to another delimiter — rides the inline carry whole. So does every node
holding `em`, `strike` or `strong` in a line still read back wrong after 32 tries. An opaque carry inside
a mark spelling is a named error in input: the carry restores its node exactly, marks included a mark spelling is a named error in input: the carry restores its node exactly, marks included
(`docs/decisions.md` §Unknown nodes ride the carry). (`docs/decisions.md` §Unknown nodes ride the carry).