Consistency.

[ikiwiki.git] / doc / sandbox.mdwn

diff --git a/doc/sandbox.mdwn b/doc/sandbox.mdwn
index 3c612d0a171d22b17c9d61fa3d2a1c477d1c9c07..d7553cc19d30c99b11f965e843e75ac5a1d92a19 100644 (file)
--- a/doc/sandbox.mdwn
+++ b/doc/sandbox.mdwn
@@ -2,10 +2,29 @@ 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.
 
 Here's another one with *emphasised* text.
 
+do ë characters work? Sure.
+
+OpenID test. It works!!
+
+Test..
+
+There are Polish diacritical characters: ą, ć, ę, ł, ń, ó, ś, ż, ź.
+
 # Header
 
 ## Subheader
@@ -17,6 +36,7 @@ Here's another one with *emphasised* text.
 > > This is nested blockquote.
 >
 >> And without a space works too.
+>>> to three levels
 >
 > Back to the first level.
 
@@ -34,10 +54,13 @@ Numbered list
 
 Bulleted list
 
-* *item*
 * item
+* *item*
 * item
-* just to try this stuff - looks kool!
+* one
+  * two
+     * three
+       * four
 
 ----
 
@@ -53,27 +76,33 @@ Bulleted list
 * <http://www.gnu.org/>
 * [GNU](http://www.gnu.org/)
 * [Email](mailto:noone@invalid)
+* WikiLink without any markup.
 
-----
-&#1506;&#1489;&#1512;&#1497;&#1514;
-&#1506;&#1489;&#1512;&#1497;&#1514; &#1506;&#1460;&#1501; &#1504;&#1456;&#1511;&#1493;&#1468;&#1491;&#1493;&#1465;&#1514;
-----
+-----
 
-So did that work? --[[Joey]]
+This sandbox is also a [[blog]]!
+
+[[inline pages="sandbox/*" rootpage="sandbox" show="5"]]
 
 ----
+[[newpage]]
+---
 
-Turkish spesific characters (latin5) expected to be here --> ığüşöçİĞÜŞÖÇ
-(character encoding set as UTF-8 on the client side)
+Ethan wants to make a [[sandbox/castle]] in the sand.
 
-Hmm...  Rendered properly but now in this second entry, they all seem to be corrupted in the CGI form.  How about `sandbox.mdwn`?  --[[Roktas]]
+hi
 
-Displayed correctly after the previous (second) test, corrupted in the CGI form  though. --[[Roktas]]
+just testing
 
-Multibyte characters are rendered and stored correctly (looking at the `sandbox.mdwn` diff), but we have a problem in CGI forms.  --[[Roktas]]
+Testing a user page for [[users/kyle]]
 
 ----
+what happens if i edit something with an openid set?
 
-This sandbox is also a [[blog]]!
+-----------
+
+So what's the point? [[How is this different to any other WiKi|features]]
+
+----
+Test.. I was looking for a wiki supporting OpenID~ 
 
-[[inline pages="sandbox/*" rootpage="sandbox" show="5"]]