Preserve ambiguous margin numbers in Markdown conversion - #196
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Preserve competing bare-number labels in the same page margin band instead of treating them as pagination. Both default furniture removal and optional compact normalization use the same ambiguity protection. Ordinary isolated and labelled page numbers remain removable.
A fresh public-form diagnostic found four project-key labels removed near the bottom of an otherwise readable form. This fixes that content loss, not blank-grid reconstruction. Synthetic regressions cover headers, footers, repeated pages, compact/furniture combinations and a protected oversized label.
Renderer identity moves to 1.20.1 with matching source/share schemas and current-version gates. The generated layout oracle changes only the two module bindings and source-set digest; no occurrence answers changed. No package release version or binary artifact changes.
Verification
Not a full release qualification, packaged bakeoff, desktop reinstallation, comparative benchmark or performance-superiority claim.