fix: audit Korean Markdown emphasis across all posts - #121
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.
Problem and changes
A parser and final-HTML audit of all 12 content/posts files found 7 remaining emphasis failures across 3 posts: double quotes (2 occurrences), single quotes, a closing parenthesis, percent signs (2 occurrences), and inline-code backticks before Korean particles. Move punctuation outside strong delimiters, or include the particle when preserving inline code. Also escape currency dollar signs in 2 Astra paragraphs that remark-math otherwise consumes as math.
Post changes are exactly 9 lines across 3 files. Compared every post against main: all line counts and all text are preserved after removing only emphasis markers and currency escapes. PR #120 is already merged; its quoted Astra sentence remains covered.
Regression coverage
Validation