Labels: Type-Defect Priority-High Milestone-Release2.0.x Component-Reviews
New issue 3602 by chip...@gmail.com: Master bug: Plain text is rendered
incorrectly when escaping for Markdown.
What version are you running?
This is the master bug for cases where the Markdown escaping is broken.
The intention is for our Markdown escaping to perfectly represent provided
text (from pre-2.0 review requests, or from non-Markdown commit messages)
without any artifacts (such as stray "\" symbols).
This doesn't always work perfectly due to the manner in which we're
escaping. This is because, currently, we need to be compatible with Python
exclusively to Python Markdown rendering, which will allow us to better
handle intelligent escaping, fixing most problems.
If you have a case where your text is not escaped and rendered properly,
please post it here as a comment.
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.