mirror of
https://github.com/xoofx/markdig.git
synced 2026-02-03 21:36:36 +00:00
Markdig not converting in between words formatting for Markdown properly #440
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HarshKhaneja on GitHub (Feb 23, 2021).
Markdig is not converting in-words formatting properly.
@MihaZupan commented on GitHub (Feb 23, 2021):
While it may be unexpected, Markdig is CommonMark-compliant here:
Example 378 of the specification:
@MihaZupan commented on GitHub (Feb 28, 2021):
Going to assume this answered the question. Feel free to reopen the issue if you have other examples of unexpected behavior.
@HarshKhaneja commented on GitHub (Mar 15, 2021):
Hey Miha,
Scenario is like this:- i have a selector, the user can also select whitespaces while doing the formatting, example :- This is a Test, in this sentence the user can select individual words for formatting and there comes a use-case in which he can select trailing and leading spaces too using the selector just like a text box, according to you if i go ahead and trim on leading and trailing spaces, then for me the spaces between words will be lost, this will create problem in readability, and if i don't trim on the spaces then Markdig parser leaves special characters in the result.. So trimming on leading and trailing spaces is not a solution instead the parser should parse according to the starting and closing tags which have been applied in selected text, Note:- Selected text can contain leading and trailing spaces.
Regards,
Harsh
@xoofx commented on GitHub (Mar 15, 2021):
No, the parser is parsing according to the CommonMark specs, not to what you would expect. We really can't change that behavior, so you need to change the way you are approaching your problem.