aboutsummaryrefslogtreecommitdiffstats
path: root/tests/safe_mode/html_then_blockquote.txt
diff options
context:
space:
mode:
authorWaylan Limberg <waylan@gmail.com>2014-01-09 23:43:52 -0500
committerWaylan Limberg <waylan@gmail.com>2014-01-09 23:43:52 -0500
commitd0e088d535a478b9435ff49fd27583f5cb9c2641 (patch)
treeef151e966b286c1798e893d68b528763ad747de9 /tests/safe_mode/html_then_blockquote.txt
parentf1cb6743891ffd3f38ca0bf6a0c94210e7730361 (diff)
downloadmarkdown-d0e088d535a478b9435ff49fd27583f5cb9c2641.tar.gz
markdown-d0e088d535a478b9435ff49fd27583f5cb9c2641.tar.bz2
markdown-d0e088d535a478b9435ff49fd27583f5cb9c2641.zip
No longer percent encode spaces in urls.
The current implementation was wrong as it also percent encoded query strings (which should be plus encoded) and calling urllib.quote on the path (and urllib.quote_plus on the query string) assumes the url is not already encoded. What if the document author pasted a url that was already encoded? She probably did not intend for `%20` to become `%2520`. Or did she? It is now clear to me why many implementation do nothing to urls. Just pass them though as-is. To bad if they are not valid HTML. HTML authors have to encodee their own urls, so I guess markdown authors have to as well.
Diffstat (limited to 'tests/safe_mode/html_then_blockquote.txt')
0 files changed, 0 insertions, 0 deletions