----
-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
+Testing right-to-left text: (שרה) should be spelled shin (ש) resh (ר) heh (ה) from right to left.
+
+Testing it in a comment...
+
Here's a paragraph.
Here's another one with *emphasised* text.
OpenID test. It works!!
+Hupple hupple hupple hupple snork.
+
Test..
There are Polish diacritical characters: ą, ć, ę, ł, ń, ó, ś, ż, ź.
[[inline pages="sandbox/*" rootpage="sandbox" show="5"]]
-----
-[[newpage]]
----
-
-Ethan wants to make a [[sandbox/castle]] in the sand.
-
-hi
-
-just testing
-
-Testing a user page for [[users/kyle]]
-
-----
-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~
-
-----
-me too...
-
-[[if test="sandbox/C++" then="[[sandbox/C++]]" else="sad face!"]]
\ No newline at end of file
+---
\ No newline at end of file