Roundup Tracker - Issues

Issue 2551105

classification
Title: Markdown2 emphasis intra-word
Type: behavior Severity: normal
Components: Web interface Versions: 2.0.0
process
Status: new Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: ced, rouilj
Priority: Keywords: patch

Created on 2020-11-22 15:15 by ced, last changed 2020-11-22 20:29 by rouilj.

Files
File name Uploaded Description Edit Remove
intra-word-emphasis.patch ced, 2020-11-22 15:15
Messages
msg7035 Author: [hidden] (ced) Date: 2020-11-22 15:15
When writing markdow like: 'self.this_long_attr'

markdown2 replaces the '_' by <em>
markdown does not replace
mistune does not replace
simplemde does not replace

So I think we should activate code-friendly[1] extra on markdown2 to ensure the same result in each implementation.

[1] https://github.com/trentm/python-markdown2/wiki/code-friendly
msg7036 Author: [hidden] (rouilj) Date: 2020-11-22 20:29
Unfortunately code-friendly looks like it may clobber _emphesis_
as well.

"The code-friendly extra disables the use of leading, trailing and --
most importantly-- intra-word emphasis (<em>) and strong (<strong>) 
using single or double underscores, respectively."

https://github.com/trentm/python-markdown2/issues/38

I wonder if we wouldn't be better served by exposing the python 
configuration arrays for markdown and have people perform 
overrides/settings using interface.py.

This would allow people to tune markdown as they want it without
core code changes. I am not quite sure how to structure this.

Analogs are: setting values in Cache_Control in class Client in
cgi/client.py, ability to override functions in the rest rate
limiting code (getRateLimit) etc.

Thoughts?
History
Date User Action Args
2020-11-22 20:29:36rouiljsetnosy: + rouilj
messages: + msg7036
2020-11-22 15:15:31cedcreate