xref: /dokuwiki/data/pages/wiki/syntax.txt (revision a445efaff5f3ce00ba6abb9b6a49fe395547090d)
1====== Formatting Syntax ======
2
3[[doku>DokuWiki]] supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing the //Edit this page// button at the top or bottom of the page. If you want to try something, just use the [[playground:playground|playground]] page. The simpler markup is easily accessible via [[doku>toolbar|quickbuttons]], too.
4
5===== Basic Text Formatting =====
6
7DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts. Of course you can **__//''combine''//__** all these.
8
9  DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts.
10  Of course you can **__//''combine''//__** all these.
11
12You can use <sub>subscript</sub> and <sup>superscript</sup>, too.
13
14  You can use <sub>subscript</sub> and <sup>superscript</sup>, too.
15
16You can mark something as <del>deleted</del> as well.
17
18  You can mark something as <del>deleted</del> as well.
19
20**Paragraphs** are created from blank lines. If you want to **force a newline** without a paragraph, you can use two backslashes followed by a whitespace or the end of line.
21
22This is some text with some linebreaks\\ Note that the
23two backslashes are only recognized at the end of a line\\
24or followed by\\ a whitespace \\this happens without it.
25
26  This is some text with some linebreaks\\ Note that the
27  two backslashes are only recognized at the end of a line\\
28  or followed by\\ a whitespace \\this happens without it.
29
30You should use forced newlines only if really needed.
31
32===== Links =====
33
34DokuWiki supports multiple ways of creating links.
35
36==== External ====
37
38External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: [[http://www.google.com|This Link points to google]]. Email addresses like this one: <andi@splitbrain.org> are recognized, too.
39
40  DokuWiki supports multiple ways of creating links. External links are recognized
41  automagically: http://www.google.com or simply www.google.com - You can set
42  link text as well: [[http://www.google.com|This Link points to google]]. Email
43  addresses like this one: <andi@splitbrain.org> are recognized, too.
44
45==== Internal ====
46
47Internal links are created by using square brackets. You can either just give a [[pagename]] or use an additional [[pagename|link text]].
48
49  Internal links are created by using square brackets. You can either just give
50  a [[pagename]] or use an additional [[pagename|link text]].
51
52[[doku>pagename|Wiki pagenames]] are converted to lowercase automatically, special characters are not allowed.
53
54You can use [[some:namespaces]] by using a colon in the pagename.
55
56  You can use [[some:namespaces]] by using a colon in the pagename.
57
58For details about namespaces see [[doku>namespaces]].
59
60Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to [[syntax#internal|this Section]].
61
62  This links to [[syntax#internal|this Section]].
63
64Notes:
65
66  * Links to [[syntax|existing pages]] are shown in a different style from [[nonexisting]] ones.
67  * DokuWiki does not use [[wp>CamelCase]] to automatically create links by default, but this behavior can be enabled in the [[doku>config]] file. Hint: If DokuWiki is a link, then it's enabled.
68  * When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much.
69
70==== Interwiki ====
71
72DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].
73
74  DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
75  For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].
76
77
78==== Windows Shares ====
79
80Windows shares like [[\\server\share|this]] are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate [[wp>Intranet]].
81
82  Windows Shares like [[\\server\share|this]] are recognized, too.
83
84Notes:
85
86  * For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the "local zone").
87  * For Mozilla and Firefox it can be enabled through different workaround mentioned in the [[http://kb.mozillazine.org/Links_to_local_pages_don't_work|Mozilla Knowledge Base]].
88
89
90==== Image Links ====
91
92You can also use an image to link to another internal or external page by combining the syntax for links and [[#images_and_other_files|images]] (see below) like this:
93
94  [[http://www.php.net|{{wiki:dokuwiki-128.png}}]]
95
96[[http://www.php.net|{{wiki:dokuwiki-128.png}}]]
97
98Please note: The image formatting is the only formatting syntax accepted in link names.
99
100The whole [[#images_and_other_files|image]] and [[#links|link]] syntax is supported (including image resizing, internal and external images and URLs and interwiki links).
101
102===== Footnotes =====
103
104You can add footnotes ((This is a footnote)) by using double parentheses.
105
106  You can add footnotes ((This is a footnote)) by using double parentheses.
107
108===== Sectioning =====
109
110You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically -- this can be disabled by including the string ''<nowiki>~~NOTOC~~</nowiki>'' in the document.
111
112==== Headline Level 3 ====
113=== Headline Level 4 ===
114== Headline Level 5 ==
115
116  ==== Headline Level 3 ====
117  === Headline Level 4 ===
118  == Headline Level 5 ==
119
120By using four or more dashes, you can make a horizontal line:
121
122----
123
124===== Images and Other Files =====
125
126You can include external and internal [[doku>images]] with curly brackets. Optionally you can specify the size of them.
127
128Real size:                        {{wiki:dokuwiki-128.png}}
129
130Resize to given width:            {{wiki:dokuwiki-128.png?50}}
131
132Resize to given width and height((when the aspect ratio of the given width and height doesn't match that of the image, it will be cropped to the new ratio before resizing)): {{wiki:dokuwiki-128.png?200x50}}
133
134Resized external image:           {{http://de3.php.net/images/php.gif?200x50}}
135
136  Real size:                        {{wiki:dokuwiki-128.png}}
137  Resize to given width:            {{wiki:dokuwiki-128.png?50}}
138  Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
139  Resized external image:           {{http://de3.php.net/images/php.gif?200x50}}
140
141
142By using left or right whitespaces you can choose the alignment.
143
144{{ wiki:dokuwiki-128.png}}
145
146{{wiki:dokuwiki-128.png }}
147
148{{ wiki:dokuwiki-128.png }}
149
150  {{ wiki:dokuwiki-128.png}}
151  {{wiki:dokuwiki-128.png }}
152  {{ wiki:dokuwiki-128.png }}
153
154Of course, you can add a title (displayed as a tooltip by most browsers), too.
155
156{{ wiki:dokuwiki-128.png |This is the caption}}
157
158  {{ wiki:dokuwiki-128.png |This is the caption}}
159
160If you specify a filename (external or internal) that is not an image (''gif, jpeg, png''), then it will be displayed as a link instead.
161
162For linking an image to another page see [[#Image Links]] above.
163
164===== Lists =====
165
166Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a ''*'' for unordered lists or a ''-'' for ordered ones.
167
168  * This is a list
169  * The second item
170    * You may have different levels
171  * Another item
172
173  - The same list but ordered
174  - Another item
175    - Just use indention for deeper levels
176  - That's it
177
178<code>
179  * This is a list
180  * The second item
181    * You may have different levels
182  * Another item
183
184  - The same list but ordered
185  - Another item
186    - Just use indention for deeper levels
187  - That's it
188</code>
189
190Also take a look at the [[faq:lists|FAQ on list items]].
191
192===== Smileys =====
193
194DokuWiki converts commonly used [[wp>emoticon]]s to their graphical equivalents. More smileys can be placed in the ''smiley'' directory and configured in the ''conf/smileys.conf'' file. Here is an overview of Smileys included in DokuWiki.
195
196  * 8-) %%  8-)  %%
197  * 8-O %%  8-O  %%
198  * :-( %%  :-(  %%
199  * :-) %%  :-)  %%
200
201  * =)  %%  =)   %%
202  * :-/ %%  :-/  %%
203  * :-\ %%  :-\  %%
204  * :-? %%  :-?  %%
205  * :-D %%  :-D  %%
206  * :-P %%  :-P  %%
207  * :-O %%  :-O  %%
208  * :-X %%  :-X  %%
209  * :-| %%  :-|  %%
210  * ;-) %%  ;-)  %%
211  * ^_^ %%  ^_^  %%
212  * :?: %%  :?:  %%
213  * :!: %%  :!:  %%
214  * LOL %%  LOL  %%
215  * FIXME %%  FIXME %%
216  * DELETEME %% DELETEME %%
217
218===== Typography =====
219
220[[DokuWiki]] can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.
221
222-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
223"He thought 'It's a man's world'..."
224
225<code>
226-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
227"He thought 'It's a man's world'..."
228</code>
229
230Please note: These conversions can be turned off through a [[doku>config:typography|config option]] and a [[doku>entities|pattern file]].
231
232===== Quoting =====
233
234Some times you want to mark some text to show it's a reply or comment. You can use the following syntax:
235
236  I think we should do it
237
238  > No we shouldn't
239
240  >> Well, I say we should
241
242  > Really?
243
244  >> Yes!
245
246  >>> Then lets do it!
247
248I think we should do it
249
250> No we shouldn't
251
252>> Well, I say we should
253
254> Really?
255
256>> Yes!
257
258>>> Then lets do it!
259
260===== Tables =====
261
262DokuWiki supports a simple syntax to create tables.
263
264^ Heading 1      ^ Heading 2       ^ Heading 3          ^
265| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
266| Row 2 Col 1    | some colspan (note the double pipe) ||
267| Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |
268
269Table rows have to start and end with a ''|'' for normal rows or a ''^'' for headers.
270
271  ^ Heading 1      ^ Heading 2       ^ Heading 3          ^
272  | Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
273  | Row 2 Col 1    | some colspan (note the double pipe) ||
274  | Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |
275
276To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!
277
278Vertical tableheaders are possible, too.
279
280|              ^ Heading 1            ^ Heading 2          ^
281^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
282^ Heading 4    | no colspan this time |                    |
283^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |
284
285As you can see, it's the cell separator before a cell which decides about the formatting:
286
287  |              ^ Heading 1            ^ Heading 2          ^
288  ^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
289  ^ Heading 4    | no colspan this time |                    |
290  ^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |
291
292You can have rowspans (vertically connected cells) by adding '':::'' into the cells below the one to which they should connect.
293
294^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
295| Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
296| Row 2 Col 1    | :::                        | Row 2 Col 3        |
297| Row 3 Col 1    | :::                        | Row 2 Col 3        |
298
299Apart from the rowspan syntax those cells should not contain anything else.
300
301  ^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
302  | Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
303  | Row 2 Col 1    | :::                        | Row 2 Col 3        |
304  | Row 3 Col 1    | :::                        | Row 2 Col 3        |
305
306You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.
307
308^           Table with alignment           ^^^
309|         right|    center    |left          |
310|left          |         right|    center    |
311| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |
312
313This is how it looks in the source:
314
315  ^           Table with alignment           ^^^
316  |         right|    center    |left          |
317  |left          |         right|    center    |
318  | xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |
319
320Note: Vertical alignment is not supported.
321
322===== No Formatting =====
323
324If you need to display text exactly like it is typed (without any formatting), enclose the area either with ''%%<nowiki>%%'' tags or even simpler, with double percent signs ''<nowiki>%%</nowiki>''.
325
326<nowiki>
327This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
328</nowiki>
329The same is true for %%//__this__ text// with a smiley ;-)%%.
330
331  <nowiki>
332  This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
333  </nowiki>
334  The same is true for %%//__this__ text// with a smiley ;-)%%.
335
336===== Code Blocks =====
337
338You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags ''%%<code>%%'' or ''%%<file>%%''.
339
340  This is text is indented by two spaces.
341
342<code>
343This is preformatted code all spaces are preserved: like              <-this
344</code>
345
346<file>
347This is pretty much the same, but you could use it to show that you quoted a file.
348</file>
349
350Those blocks were created by this source:
351
352    This is text is indented by two spaces.
353
354  <code>
355  This is preformatted code all spaces are preserved: like              <-this
356  </code>
357
358  <file>
359  This is pretty much the same, but you could use it to show that you quoted a file.
360  </file>
361
362==== Syntax Highlighting ====
363
364[[wiki:DokuWiki]] can highlight sourcecode, which makes it easier to read. It uses the [[http://qbnz.com/highlighter/|GeSHi]] Generic Syntax Highlighter -- so any language supported by GeSHi is supported. The syntax is the same like in the code and file blocks in the previous section, but this time the name of the used language is inserted inside the tag. Eg. ''<nowiki><code java></nowiki>'' or ''<nowiki><file java></nowiki>''.
365
366<code java>
367/**
368 * The HelloWorldApp class implements an application that
369 * simply displays "Hello World!" to the standard output.
370 */
371class HelloWorldApp {
372    public static void main(String[] args) {
373        System.out.println("Hello World!"); //Display the string.
374    }
375}
376</code>
377
378The following language strings are currently recognized: //abap, actionscript-french, actionscript, actionscript3, ada, apache, applescript, asm, asp, autoit, avisynth, bash, basic4gl, bf, bibtex, blitzbasic, bnf, boo, c, c_mac, caddcl, cadlisp, cfdg, cfm, cil, cmake, cobol, cpp, cpp-qt, csharp, css, d, dcs, delphi, diff, div, dos, dot, eiffel, email, erlang, fo, fortran, freebasic, genero, glsl, gml, gnuplot, groovy, gettext, haskell, hq9plus, html, idl, ini, inno, intercal, io, java5, java, javascript, kixtart, klonec, klonecpp, latex, lisp, locobasic, lolcode, lotusformulas, lotusscript, lscript, lsl2, lua, m68k, make, matlab, mirc, modula3, mpasm, mxml, mysql, nsis, oberon2, objc, ocaml-brief, ocaml, oobas, oracle8, oracle11, pascal, perl, per, php-brief, php, pic16, pixelbender, plsql, povray, powershell, progress, prolog, properties, providex, python, qbasic, rails, rebol, reg, robots, ruby, sas, scala, scheme, scilab, sdlbasic, smalltalk, smarty, sql, tcl, teraterm, text, thinbasic, tsql, typoscript, vbnet, vb, verilog, vhdl, vim, visualfoxpro, visualprolog, whitespace, winbatch, whois, xml, xorg_conf, xpp, z80//
379
380==== Downloadable Code Blocks ====
381
382When you use the ''%%<code>%%'' or ''%%<file>%%'' syntax as above, you might want to make the shown code available for download as well. You can to this by specifying a file name after language code like this:
383
384<code>
385<file php myexample.php>
386<?php echo "hello world!"; ?>
387</file>
388</code>
389
390<file php myexample.php>
391<?php echo "hello world!"; ?>
392</file>
393
394If you don't want any highlighting but want a downloadable file, specify a dash (''-'') as the language code: ''%%<code - myfile.foo>%%''.
395
396
397===== Embedding HTML and PHP =====
398
399You can embed raw HTML or PHP code into your documents by using the ''%%<html>%%'' or ''%%<php>%%'' tags. (Use uppercase tags if you need to enclose block level elements.)
400
401HTML example:
402
403<code>
404<html>
405This is some <span style="color:red;font-size:150%;">inline HTML</span>
406</html>
407<HTML>
408<p style="border:2px dashed red;">And this is some block HTML</p>
409</HTML>
410</code>
411
412<html>
413This is some <span style="color:red;font-size:150%;">inline HTML</span>
414</html>
415<HTML>
416<p style="border:2px dashed red;">And this is some block HTML</p>
417</HTML>
418
419PHP example:
420
421<code>
422<php>
423echo 'A logo generated by PHP:';
424echo '<img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" />';
425echo '(generated inline HTML)';
426</php>
427<PHP>
428echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
429echo '<td><img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" /></td>';
430echo '</tr></table>';
431</PHP>
432</code>
433
434<php>
435echo 'A logo generated by PHP:';
436echo '<img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" />';
437echo '(inline HTML)';
438</php>
439<PHP>
440echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
441echo '<td><img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" /></td>';
442echo '</tr></table>';
443</PHP>
444
445**Please Note**: HTML and PHP embedding is disabled by default in the configuration. If disabled, the code is displayed instead of executed.
446
447===== RSS/ATOM Feed Aggregation =====
448[[DokuWiki]] can integrate data from external XML feeds. For parsing the XML feeds, [[http://simplepie.org/|SimplePie]] is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:
449
450^ Parameter  ^ Description ^
451| any number | will be used as maximum number items to show, defaults to 8 |
452| reverse    | display the last items in the feed first |
453| author     | show item authors names |
454| date       | show item dates |
455| description| show the item description. If [[doku>config:htmlok|HTML]] is disabled all tags will be stripped |
456| //n//[dhm] | refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours). |
457
458The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. [[wiki:DokuWiki]] will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells [[wiki:DokuWiki]] to re-render the page if it is more than //refresh period// since the page was last rendered.
459
460**Example:**
461
462  {{rss>http://slashdot.org/index.rss 5 author date 1h }}
463
464{{rss>http://slashdot.org/index.rss 5 author date 1h }}
465
466
467===== Control Macros =====
468
469Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:
470
471^ Macro           ^ Description |
472| %%~~NOTOC~~%%   | If this macro is found on the page, no table of contents will be created |
473| %%~~NOCACHE~~%% | DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the %%<php>%% syntax above is used), adding this macro will force DokuWiki to rerender a page on every call |
474
475===== Syntax Plugins =====
476
477DokuWiki's syntax can be extended by [[doku>plugins|Plugins]]. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:
478
479~~INFO:syntaxplugins~~
480