diff options
| -rw-r--r-- | doc/bugs/No_link_for_blog_items_when_filename_contains_a_colon.mdwn | 13 |
1 files changed, 12 insertions, 1 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 313c1addd..b78515596 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 @@ -57,4 +57,15 @@ What do you think about that? Does the patch have any side-effects I didn't see? > I almost really fixed this in 2.53, but missed one case. All fixed now > AFAICS. --[[Joey]] -[[tag done]] +>> Hmm, did you fix it now in 2.54? If so, I suspect there is still one little case left (might well be the last one, +>> at least I hope so ;-) ): I just created a test post in the sandbox here: [[sandbox/test: with a colon in its name]] +>> (btw, why doesn't this get a hyperlink here?). +>> +>> As it is put in the list of blog posts as a relative link, it starts +>> with `<word><colon>` -- this makes the browser think that "test" is a protocol specification which is to replace `http`, +>> so it complains (at least Opera and Firefox/Iceweasel on my Debian Etch do). What I described above for subpages +>> with this name pattern also still happens on my local install (ikiwiki 2.54 on Debian Etch), but this is basically +>> the same problem. +>> +>> I think the cleanest solution would be to quote colons in page names (like it is currently done for slashes)? +>> Starting the links with "`./`", as I proposed above, now seems a bit ugly to me... --Mathias |