From 1f33007ae2b497f707002f45927adcd67163ddd5 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Fri, 30 Oct 2026 21:00:05 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20product-owner=20round=201:=200=20?= =?UTF-8?q?=F0=9F=94=B4,=201=20=F0=9F=9F=A1=20(0=20misread);=20state=20the?= =?UTF-8?q?=2032-try=20rule=20in=20the=20README=20and=20the=20flavour=20sp?= =?UTF-8?q?ec?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 3 ++- spec/flavour.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 94a1abf..2158364 100644 --- a/README.md +++ b/README.md @@ -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 `_(synced block not included)_` for a `syncBlock`. - `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`. - 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 diff --git a/spec/flavour.md b/spec/flavour.md index ff4e57a..b3e1fb5 100644 --- a/spec/flavour.md +++ b/spec/flavour.md @@ -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 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 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 (`docs/decisions.md` §Unknown nodes ride the carry).