GiellaLT provides rule-based language technology aimed at minority and indigenous languages
The jspwiki format gives the possibility to use three levels of headers.
The first level is marked with: !!!
, the second !!
and the third is
!
. Paragraphs are made by placing an empty line before and after a
paragraph.
The jspwiki format gives the possibility to use ordered (numbered) and
unordered lists. Both list types can have up to three levels. The #
mark is used to make ordered lists, and the *
mark is used to make
unordered ones. #, ##, ###
and *, **, ***
gives the
first, second and third levels for respectively ordered and unordered
lists.
Emphasis is made by putting __
(two underscores) before and after the
word one wants to emphasise.
More than two underscores in a row crashes jspwiki output!
Here comes a short documentation, in tabular format.
---- = (hyphen) make a horizontal ruler. Extra '-' is ignored.
\\ = force a line break
[link] = create a hyperlink to an internal WikiPage called 'Link'.
[this is also a link] = create a hyperlink to an internal WikiPage called
'ThisIsAlsoALink' but show the link as typed with spaces.
[a sample|link] = create a hyperlink to an internal WikiPage called
'Link', but display the text 'a sample' to the
user instead of 'Link'.
~NoLink = disable link creation for the word in CamelCase.
[1] = make a reference to a footnote numbered 1.
[#1] = mark the footnote number 1.
[[link] = create text '[link]'.
!heading = small heading with text 'heading'
!!heading = medium heading with text 'heading'
!!!heading = large heading with text 'heading'
''text'' = print 'text' in italic.
__text__ = print 'text' in bold.
= print 'text' in monospaced font.
* text = make a bulleted list item with 'text'
# text = make a numbered list item with 'text'
;term:ex = make a definition for 'term' with the explanation 'ex'
||table ||header
| second | row
There is an example document for testing that documents the features that do work.
Breaking any of the following rules will cause parsing errors and an error message:
The following mark-up won’t cause syntax errors, but it doesn’t parse as intended, and thus produces unwanted XML/HTML: