DokuWiki (на которой построен сайт ArtUser) поддерживает простой язык разметки, который по возможности сохраняет файлы данных как можно более читабельными. Здесь перечислены все возможные синтаксические конструкции, которые можно использовать при редактировании страниц. Просто посмотрите на исходный код этой страницы, нажав кнопку Отредактировать страницу вверху или внизу страницы. Если хотите поупражняться, используйте страницу Тестовая площадка.

DokuWiki поддерживает выделение текста жирным шрифтом, курсивом, подчеркнутый текст и вывод текста моноширинным шрифтом. Все эти конструкции можно объединить.

DokuWiki поддерживает выделение текста **жирным шрифтом**, //курсивом//, 
__подчеркнутый текст__ и вывод текста ''моноширинным шрифтом''. 
Все эти конструкции можно **__//''объединить''//__**.

Также можно использовать _{подстрочный} и ^{надстрочный} индексы.

Также можно использовать <sub>подстрочный</sub> и <sup>надстрочный</sup> индексы.

Ещё можно зачеркнуть текст.

Ещё можно <del>зачеркнуть текст</del>.

Абзацы отбиваются пустой строкой. Если нужно принудительно вставить перенос строки, не создавая абзац, вставьте два обратных слэша и за ним пробел или переход к новой строке.

Просто текст с разрывом строк
Обратите внимание, что два обратных слэша действую только в конце строки
или если за ними стоит
пробел. Если его не поставить, \\получится вот так.

Просто текст с разрывом строк\\ Обратите внимание,
что два обратных слэша действую только в конце строки\\
или если за ними стоит\\ пробел. Если его не поставить, \\получится вот так.

Принудительные переносы следует использовать только в случае крайней необходимости.

DokuWiki supports multiple ways of creating links.

External links are recognized automagically: http://www.google.com or simply www.google.com - You can set Linknames, too: This Link points to google. Email addresses like this one: andi@splitbrain.org are recognized, too.

DokuWiki supports multiple ways of creating links. External links are recognized

automagically: http://www.google.com or simply www.google.com - You can set

Linknames, too: [[http://www.google.com|This Link points to google]]. Email

addresses like this one: <andi@splitbrain.org> are recognized, too.

Internal links are created by using square brackets. You can either just give a wiki:pagename or use an additional Title Text. Wiki pagenames are converted to lowercase automatically, special characters are not allowed.

Internal links are created by using square brackets. You can either just give

a [[pagename]] or use an additional [[pagename|Title Text]]. Wiki pagenames

are converted to lowercase automatically, special chars are not allowed.

You can use namespaces by using a colon in the pagename.

You can use [[wiki:namespaces]] by using a colon in the pagename.

For details about namespaces see wiki:namespaces.

Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section.

This links to [[syntax#internal|this Section]].

Notes:

• Links to existing pages are shown in a different style from nonexisting ones.

• DokuWiki does not use CamelCase to automatically create links by default, but this behaviour can be enabled in the wiki:config file. Hint: If DokuWiki is a link, then it’s enabled.

• When a section’s heading is changed, its bookmark changes, too. So don’t rely on section linking too much.

DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia’s page about Wikis: Wiki.

DokuWiki supports [[doku>wiki:interwiki|Interwiki]] links. These are quick links to other Wikis.

For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].

You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this:

[[http://www.php.net|{{wiki:dokuwiki-128.png}}]]

Please note: The image formatting is the only formatting syntax accepted in link names.

The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links).

You can add footnotes ¹⁾ by using double parentheses.

You can add footnotes ((This is a footnote)) by using double parentheses.

You 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 ~~NOTOC~~ in the document.

==== Headline Level 3 ====

=== Headline Level 4 ===

== Headline Level 5 ==

By using four or more dashes, you can make a horizontal line:

You can include external and internal wiki:images with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height:

Resized external image:

Real size:                        {{wiki:dokuwiki-128.png}}

Resize to given width:            {{wiki:dokuwiki-128.png?50}}

Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}

Resized external image:           {{http://de3.php.net/images/php.gif?200x50}}

By using left or right whitespaces you can choose the alignment.

{{ wiki:dokuwiki-128.png}}

{{wiki:dokuwiki-128.png }}

{{ wiki:dokuwiki-128.png }}

Of course, you can add a title (displayed as a tooltip by most browsers), too.

{{ wiki:dokuwiki-128.png |This is the caption}}

If you specify a filename (external or internal) that is not an image (gif, jpeg, png), then it will be displayed as a link instead.

For linking an image to another page see Image Links above.

Dokuwiki 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.

• This is a list

• The second item

• You may have different levels

• Another item

1. The same list but ordered

1. Another item

1. Just use indention for deeper levels

1. That’s it

  * This is a list

  * The second item

    * You may have different levels

  * Another item



  - The same list but ordered

  - Another item

    - Just use indention for deeper levels

  - That's it

DokuWiki converts commonly used emoticons 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.

• 8-)

• 8-O

• :-(

• :-)

• =)

• :-/

• :-\

• :-?

• :-D

• :-P

• :-O

• :-X

• :-|

• ;-)

• ^_^

• :?:

• :!:

• LOL

• FIXME

• DELETEME

DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.

→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ®

«He thought „It’s a man’s world“…»

-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)

"He thought 'It's a man's world'..."

Please note: These conversions can be turned off through a config option and a pattern file.

Some times you want to mark some text to show it’s a reply or comment. You can use the following syntax:

I think we should do it

> No we shouldn't

>> Well, I say we should

> Really?

>> Yes!

>>> Then lets do it!

I think we should do it

No we shouldn’t

Well, I say we should

Really?

Yes!

Then lets do it!

DokuWiki supports a simple syntax to create tables.

Table rows have to start and end with a | for normal rows or a ^ for headers.

^ Heading 1      ^ Heading 2       ^ Heading 3          ^

| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |

| Row 2 Col 1    | some colspan (note the double pipe) ||

| Row 3 Col 1    | Row 2 Col 2     | Row 2 Col 3        |

To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!

Vertical tableheaders are possible, too.

As you can see, it’s the cell separator before a cell which decides about the formatting:

|              ^ Heading 1            ^ Heading 2          ^

^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |

^ Heading 4    | no colspan this time |                    |

^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |

Note: Vertical spans (rowspan) are not possible.

You 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.

This is how it looks in the source:

^           Table with alignment           ^^^

|         right|    center    |left          |

|left          |         right|    center    |

| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |

You can include non-parsed 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.

This is preformatted code all spaces are preserved: like              <-this

This is pretty much the same, but you could use it to show that you quoted a file.  

To let the parser ignore an area completely (ie. do no formatting on it), enclose the area either with nowiki tags or even simpler, with double percent signs %%.

This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.

See the source of this page to see how to use these blocks.

DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax is the same like in the code block in the previous section, but this time the name of the used language is inserted inside the tag. Eg. <code java>.

 
/** 
 
 * The HelloWorldApp class implements an application that
 
 * simply displays "Hello World!" to the standard output.
 
 */
 
class HelloWorldApp {
 
    public static void main(String[] args) {
 
        System.out.println("Hello World!"); //Display the string.
 
    }
 
}

The following language strings are currently recognized: abap actionscript-french, actionscript, ada, apache, applescript, asm, asp, autoit, bash, basic4gl, blitzbasic, bnf, caddcl, cadlisp, cfdg, cfm, c_mac, c, cpp, cpp-qt, csharp, css, delphi, diff, div, dos, dot, d, eiffel, fortran, freebasic, genero, gml, groovy, haskell, html, idl, ini, inno, io, java5, java, javascript, latex, lisp, lua, m68k, matlab, mirc, mpasm, mysql, nsis, objc, ocaml-brief, ocaml, oobas, oracle8, pascal, perl, per, php-brief, php, plsql, python, qbasic, rails, reg, robots, ruby, sas, scheme, sdlbasic, smalltalk, smarty, sql, tcl, text, thinbasic, tsql, vbnet, vb, vhdl, visualfoxpro, winbatch, xml, xpp, z80

DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, 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:

The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. 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 DokuWiki to re-render the page if it is more than refresh period since the page was last rendered.

Example:

{{rss>http://www.artuser.ru/feed.php 5 author date 1h }}

• Ксения Токарева От tema_dub (04.03.2024 10:01)
• Кравчук Дмитрий От Кравчук Д.Е. (23.05.2022 20:50)
• Рудник Михаил От Рудник Михаил Маркович (25.07.2021 09:44)
• Дедык Яков От Яков Дедык (29.05.2021 22:03)
• Белова Виктория Викторовна От Виктория (28.03.2021 22:37)

/*

Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble: