the Dune Buggy Archives

Notes1

  • Some of these rules aren't precisely accurate at the current revision of Kwiki, so you may want to check out the SandBox for a (slightly) more accurate picture of KwikiText as it stands now.
  • After modifying your character page hit the SAVE button without retyping the name of your page at the top or it will give you an error.

Level 1 Heading (H1)

= Level 1 Heading (H1)

Level 2 Heading (H2)

== Level 2 Heading (H2)

Level 3 Heading (H3)

=== Level 3

.


Level 4 Heading (H4)

==== Level 4 Heading (H4)

.


Level 5 Heading (H5)
===== Level 5 Heading (H5)

.


Level 6 Heading (H6)
====== Level 6 Heading (H6)

.


The horizontal lines in this page are made with 4 or more dashes:

----

Partial horizontal lines, depending upon the Wiki stylesheet in use, can be emulated with a string of * bolded &mdash;.

—————————————————————

*—————————————————————*

‏      —————————————————————

.


Paragraphs are separated by a blank line.

Like this. Another paragraph.

Paragraphs are separated by a blank line.

‏ Paragraphs can be first-line indented without invoking fixed pre text with the use of space glyphs, preceeded by a text-directional indicator, &lrm; usually:

‎ Use &emsp; widest, for distinctive first-line indent.

‎ Use &ensp; narrower, useful, but not as distinctive.

‎ Using ‏ should be for a non-breaking &ensp; but it probably doesn't work, as you probably can see.

‎ Multiple &nbsp; will indent the raw and view-source views, but not the paragraph or line.

‎ Use &thinsp; narrowest.

As compared to non-indented. The &emsp; and [=&]thinsp;can also be handy in more closely aligning preformatted text areas when odd width glyphs are also used, such as some extra-wide dingbat-ish symbols: Ⅷ (VIII connected), Ⅻ (XII connected), ⌨ (keyboard), ⁂ (asterisk triangle), ǋ (Nj ligature), etc.

.


Bold text, italic text, and underscore text.

*Bold text*, /italic text/, and _underscore text_.

Combination of bold and italics

/*Combination of bold and italics*/

. Inline code like /etc/passwd or CGI::Kwiki

Inline code like [=/etc/passwd] or [=CGI::Kwiki]

. Strikethrough

-Strikethrough-

. Underlined

_Underlined_

. All combined

/_*-All combined-*_/

Hint: If _[ Preview ]_shows unintentional strikethrough text, because of use of a simple ASCII dash within the paragraph, substitute the “–” ([=&]ndash;) or “−” ([=&]minus;) for the unintended strikethrough start, depending upon the contextual meaning of the dash.

.


WikiLinks are formed by two or more words in camel-case.

WikiLinks are formed by two or more words in /camel-case/.

External links begin with < spam://,>* like <spam://www.freepan.org*>*

External links begin with http://, like http://www.freepan.org

On some cases links can appear as < spam://.>* This means that you entered an address that is not whitelisted. Wait for an admin to whitelist it.

Forced wiki links are a alphanumeric string surrounded by square brackets.

Forced wiki [links] are a alphanumeric string surrounded by square brackets.

Named http links have text with an http: link inside, like FreePAN Site

Named http links have text with an http:// link inside, like [FreePAN http://www.freepan.org Site]

It is also possible to use named WikiLinks which can be helpful if a page is renamed (note that this technique is not supported by Wikiwyg 0.12):

[LinkText WikiLink]

Sometimes WordsShouldNotMakeAWikiLink so put a '!' beforehand.

Sometimes !WordsShouldNotMakeAWikiLink so put a '!' beforehand.

Same thing with http://foobar.com

Same thing with !http://foobar.com

Mailto links are just email addresses like mailto: mailto: mailto: mailto: mailto: mailto: mailto: mailto:foo@bar.com.

Mailto links are just email addresses like foo@bar.com.

.


Links to images display the image:

image

http://www.google.com/images/logo.gif

Hint: Outlinked images such as the above will NOT display in a properly secured browser. That setting destroys Map Quest (AOL), too, but not Google Maps. On the other hand, on-site ones like image should display just fine.

On the other hand, on-site ones like

Links to images with square-bracketed display text: image display the display text as a link.

Links to images with square-bracketed display text:

.


Unordered lists begin with a '* '. The number of asterisks determines the level, and the installed stylesheet determines the actual bullets used:

  • foo
  • bar
    • boom
    • bam
      • bop
        • boofraw
  • baz
* foo

Hint: “• Bulleted items” can be referred to in text by using the &bull; glyph.

.


Ordered lists begin with a '0 ' (zero):

  1. foo
  2. bar
    1. boom
    2. bam
  3. baz
0 foo

.


You can mix lists too:

  • Today:
    1. Eat icecream
    2. Buy a pony
  • Tomorrow:
    1. Eat more icecream
    2. Buy another pony
* Today:

.

This feature no longer works correctly in Kwiki >0.31. Notice that this produces two unordered lists at the top level, instead of one. – MattHoward


Any text that does not begin in the first column is rendered as preformatted text.

foo   bar

As seen above in the hint about paragraph indention, use of &lrm;&emsp; can be used to indent-first a paragraph, even if it's not specified in the stylesheet for the Kwiki.

.


You can comment out wiki-text with '# ' at the beginning of a line. This will make the text an html comment:

# These lines have been

⌗ The U+2317 hash can be used to indicate a # in the first position of a non-preformatted line. (⌗ == ⌗), or a normal #

‎# can be preceeded with an &lrm; to subvert the comment processing.

.


Simple Tables:

Dick Jane
height 72" 65"
weight 130lbs 150lbs
|        | Dick   | Jane |

NOTE - Do not leave any trailing whitespaces - they cause all kinds of strange formatting errors ( RajendraGokhale).

However, headings can be bolded, and even spaced-over, with [=&]emsp;, [=&]ensp;, and/or [=&]thinsp;

Column 1   Column 2
Row 1 Detail 1 Detail 2

But, as of v0.38, there is no way to right-justify nor center either for all text or table cells. Don't be tricked into using the [=&]rlm;:

‏This is Right-to-Left text rendering, using the above RLM meta-glyph. It doesn't truly work as expected, as you can see, and can make the text quite confusing, and very difficult to edit.

‎Also, combining ‏עברי or فارسى‎ in a table can make the table break on edit, whether Wikiwyg or action=edit.

.


Inline HTML is escaped.

<hr> <bold>No?</bold> <i>Yes?</i> <hr/>

Renders as: <hr> <bold>No?</bold> <i>Yes?< i> <hr >

Notice the ' `/` ' character in the tags is being rendered as italic markers.
http://www.dunebuggyarchives.com/KwikiFormattingRules
www.dunebuggyarchives.com
crawl=CC-MAIN-2019-09
17631
application/http; msgtype=response
sha1:NS2VBS24NRAIFIMXCEHHTOG765VADBFA
<urn:uuid:42d4e7fe-8461-48b8-8fe0-c8c4281b9ef9>
2019-02-23T04:21:58Z
65.182.176.155
application/xhtml+xml
sha1:OSPVJV4RG2ZFDL5TOKPVD7BK4GICGNGR
<urn:uuid:d7f8937d-0cfb-4e7a-a6bc-5a88bdfd29b2>
http://www.dunebuggyarchives.com/KwikiFormattingRules
response
<urn:uuid:34b7104d-133f-42f5-a021-980f3a1f7536>
isPartOf: CC-MAIN-2019-09
publisher: Common Crawl
description: Wide crawl of the web for February 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-137-198-92.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/