ToDo settle with some formatting and explain it here
Space with more than one line creates a new paragraph.
There are two ways to specify a markup command:
TeX or RTF like escaping:
\\ outputs \
\< outputs <
\~ outputs non-breakable space like the HTML entity
\== outputs a horizontal line like the HTML tag <hr>
\{http://logand.com Logand} outputs an external link Logand
\{Sandbox} outputs an internal link Sandbox
XML like escaping:
<b>text</b> outputs the text in bold
<u>text</u> outputs the text underlined
<h2>heading 2</h2> or <h3>heading 3</h3> outputs a heading
<ul><li>1st</li><li>2nd</li></ul> outputs a bulleted list
<ol><li>1st</li><li>2nd</li></ol> outputs a numbered list
<table>
<tr><td>a1</td><td>a2</td></tr>
<tr><td>b1</td><td>b2</td></tr>
</table>
outputs a table
| a1 | a2 |
| b1 | b2 |
<pre>...</pre> preserves whitespace until the enclosing < character is encountered
if [ "$USER" != "root" ]; then
PATH=$HOME/bin:$PATH
else
PATH=/etc:/usr/etc:$PATH
fi
<lisp>some code</lisp> is like <pre> but expects the content to be picolisp code and creates cross reference links for built in functions
(println *OS) (de _markupXml (End) (char) (let? C (till ">" T) (char) (unless (= C End) (cons C (_markup (pack "/" C))))))
ToDo not sure whether to keep both TeX like and XML like formatting?
ToDo what other markup would be useful?
This page is linked from: picoWiki
Revisions: View source XHTMLV | RSSV
picoWiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively