-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mixed content]: Consolidate issues #985
Comments
Todo list for html content (WIP)toward next patch:
toward 0.4.0 (no defects):
|
(I've just noticed this more-or-less a duplicate of #488)Can I add a new issue on to HTML parsing? I noticed that InlineLexer handles Markdown inside of HTML and supports a limited set of Markdown (links work, lists don't). When I am writing Markdown for internationalization projects, I sometimes use a <div dir="rtl">
* list item 1
* list item 2
</div> With careful use of whitespace, this markdown list appears correctly right-aligned on GitHub:
Ideally MarkedJS would either support Markdown lists inside of a |
@mapmeld: Recommend creating a new issue entirely. Would also say that I'm not sure how CommonMark an GFM specifications actually handle this situation. I believe the "careful use of whitespace" hack works because their parser looks at empty line separations as the indicator for parsing. So, the empty line tells the GitHub parser to go ahead and create the |
@mapmeld: Having said that, I'm curious and would like to confirm...the letters aren't reversed because English is not an RTL language?? If so, do you change the language of the Markdown as well for the internationalization?? |
@joshbruce browsers are usually good at figuring out how to show a mix of LTR and RTL content. It's not a problem of showing English or Arabic letters or words in the wrong order, only issues with text layout. I'm using English in this issue as an Arabic example might make it confusing what I am trying to do. If there were an option to parse markdown inside of HTML (#488) then my examples would be OK The
|
@mapmeld: Thanks for the clarification. Think I'm trying to make sure we're not maybe trying to get Markdown and marked to do something they shouldn't...we got a lot of that already. :) Why not use CSS (one for LTR languages, then override with a second for RTL languages), for example? https://css-tricks.com/almanac/properties/d/direction/ - cleans up the Markdown to make it less HTML specific. Telling us how the specifications define and deal is usually the easiest way to make requests right now - we're really trying to not make up our own requirements when it comes to functionality right now. CommonMark does specify HTML ( Probably worth creating a new issue, which @Feder1co5oave or myself or one of the other contributors will then associate with this or something else. |
@joshbruce agreed, I don't want to overcomplicate the library. I added a test and tried out dividing the html rule into htmlstart, htmlend, and htmlcomment rules - currently only one test is having issues with the change. I'd need help fixing the RegEx for paragraphs so it doesn't extend into the HTML tag on the same line mapmeld@a8df1aa |
Issues related to processing HTML with Markdown inside. See #956
The text was updated successfully, but these errors were encountered: