From 4707f556a72efaeba51b85adbfbbd8cc59ba8a51 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 29 Feb 2008 13:47:48 -0500 Subject: [PATCH] web commit by http://madduck.myopenid.com/: remove comment about relative links always using ../, which is not true --- ...o_link_for_blog_items_when_filename_contains_a_colon.mdwn | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) 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..0e8ead4ea 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 @@ -14,10 +14,7 @@ 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.