refactor: separate CJK-friendly Emphasis as an extension - #86
Closed
tats-u wants to merge 1 commit into
Closed
Conversation
tats-u
marked this pull request as ready for review
March 1, 2026 15:03
tats-u
force-pushed
the
cjk-emphasis-ext
branch
from
March 18, 2026 14:51
a653bcb to
37321c7
Compare
This was referenced Jun 3, 2026
refactor: make CJK-friendly emphasis opt-in by new parser option
CMARK_OPT_CJK_FRIENDLY_EMPHASIS
#89
Closed
Author
|
Probably unneccessary: #78 (comment) |
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
1 participant
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.
This PR will make this extension opt-in. The fact that this extension is mandatory in the original PR #78 may be the blocker.
Warning: this is a tested slop by Copilot powered by Opus 4.6. I'm not so used to cmark-flavored C. (I understand C's syntax itself but have not got used to a lot of string/pointer operations)