X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/6a60c225fea0524a4d722553d05d85641742b565..d5e65e582a34ae2494fee493ddcb2b959e4a4bce:/doc/bugs/No_link_for_blog_items_when_filename_contains_a_colon.mdwn diff --git a/doc/bugs/No_link_for_blog_items_when_filename_contains_a_colon.mdwn b/doc/bugs/No_link_for_blog_items_when_filename_contains_a_colon.mdwn index 5c32bc591..608d09b74 100644 --- a/doc/bugs/No_link_for_blog_items_when_filename_contains_a_colon.mdwn +++ b/doc/bugs/No_link_for_blog_items_when_filename_contains_a_colon.mdwn @@ -6,7 +6,7 @@ EDIT: I just found that in this wiki under the enabled, then `$safe_url_regexp` determines the URL unsafe because of the colon and hence removes the `src` attribute. -Digging into this, I find that [[rfc 3986]] pretty much discourages colons in +Digging into this, I find that [[!rfc 3986]] pretty much discourages colons in filenames: > A path segment that contains a colon character (e.g., "this:that") cannot be @@ -14,13 +14,12 @@ filenames: > mistaken for a scheme name. Such a segment must be preceded by > a dot-segment (e.g., "./this:that") to make a relative- path reference. -on the other hand, with `usedirs`, any link to another page will be prepended -by `../` anyway, so that makes them okay again. - -The solution still seems not to use colons. +The solution seems not to use colons. In any case, `htmlscrubber` should get a new regexp, courtesy of dato: `[^:]+($|\/)`. I have tested and verified this. [Commit/patch be0b4f60](http://git.madduck.net/v/code/ikiwiki.git?a=commit;h=be0b4f603f918444b906e42825908ddac78b7073) fixes this. + +[[done]]