X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/dd6fd0f7b41d580eea3fdadc1932583b74fae792..16143c0e50806a497ada73b27a88fe5cd8c69287:/doc/sandbox.mdwn

diff --git a/doc/sandbox.mdwn b/doc/sandbox.mdwn
index be262321b..d7553cc19 100644
--- a/doc/sandbox.mdwn
+++ b/doc/sandbox.mdwn
@@ -2,6 +2,15 @@ This is the SandBox, a page anyone can edit to try out ikiwiki.
 
 ----
 
+So, I'm wondering why ikiwiki requires links to have no spaces in their names, and uses .html suffixes. I really don't like having to use [[CamelCase]] for multi-word links, and it's generally not good practice to encode stuff like filetype or specific technologies in the URL; that's what we have a MIME type for. Anyhow, this is really just a test for playing around in the sanbox, but those are the two things that bother me the most off the bat about ikiwiki.
+
+> For the former: because links with spaces get parsed as [[preprocessor_directives|preprocessordirective]].  You can get away with it if the first word doesn't correspond to a preprocessor directive.  If you have another syntax you'd prefer, feel free to propose it.  For instance, I can imagine extending the syntax with something like [["link with spaces"]].
+> For the latter: see the new `usedirs` option if you want to avoid .html suffixes.
+
+----
+
+testing openid ... ignore.
+
 Test. Проверка. テスト ığüşöçİ ทดสอบ éphémère
 
 Here's a paragraph.
@@ -12,7 +21,9 @@ do ë characters work? Sure.
 
 OpenID test. It works!!
 
-Test.
+Test..
+
+There are Polish diacritical characters: ą, ć, ę, ł, ń, ó, ś, ż, ź.
 
 # Header
 
@@ -93,4 +104,5 @@ what happens if i edit something with an openid set?
 So what's the point? [[How is this different to any other WiKi|features]]
 
 ----
-Test.. I was looking for a wiki supporting OpenID~ 
\ No newline at end of file
+Test.. I was looking for a wiki supporting OpenID~ 
+