== Level 2 ==
=== Level 3 ^([#hn note])^

First paragraph
on multiple lines.

Second paragraph.

* bullets list
  on multiple lines
  1. nested list
    a. different numbering 
       styles

 term:: definition on
        multiple lines

{{{
multiple lines, ''no wiki''
      white space respected
}}}

multiple lines, ''no wiki''
      white space respected

  if there's some leading
  space the text is quoted

>> ... (I said)
> (he replied)

||= Table Header =|| Cell ||
||||  (details below)  ||

{{{
#!div style="font-size: 80%"
Code highlighting:
  {{{#!python
  hello = lambda: "world"
  }}}
}}}

hello = lambda: "world"

{{{#!comment
Note to Editors: ...
}}}

Line [[br]] break 
Line \\ break
----

A new text paragraph is created whenever two blocks of text are separated by one or more empty lines.

A forced line break can also be inserted, using:

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | > Line 1\ | | Line 1[[BR]]Line 2 | > Line 2 | | | | | | > Paragraph one | | {.wiki} | | | Paragraph | > Paragraph two | | one | | | | | | Paragraph | | | two | | | | | +-----------------------------------+-----------------------------------+

The wiki supports both ordered/numbered and unordered lists.

Example:

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | - Item 1 | | * Item 1 | - Item 1.1 | | * Item 1.1 | - Item 1.1.1 | | * Item 1.1.1 | - Item 1.1.2 | | * Item 1.1.2 | - Item 1.1.3 | | * Item 1.1.3 | - Item 1.2 | | * Item 1.2 | - Item 2 | | * Item 2 | | | - items can start at the beginnin | <!-- --> | | g of a line | | | and they can span multiple line | - items can start at the | | s | beginning of a line and they | | - be careful though to continue | can span multiple lines | | the line | - be careful though to | | with the appropriate indentatio | continue the line with | | n, otherwise | the appropriate | | that will start a new paragraph.. | indentation, otherwise | | . | | | | that will start a new paragraph… | | 1. Item 1 | | | a. Item 1.a | 1. Item 1 | | a. Item 1.b | 1. Item 1.a | | i. Item 1.b.i | 2. Item 1.b | | i. Item 1.b.ii | 1. Item 1.b.i | | 1. Item 2 | 2. Item 1.b.ii | | And numbered lists can also be re | 2. Item 2 | | started | | | with an explicit number: | And numbered lists can also be | | 3. Item 3 | restarted with an explicit | | | number: | | | | | | 3. Item 3 | +-----------------------------------+-----------------------------------+

The wiki also supports definition lists.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | llama | | llama:: | : some kind of mammal, with | | some kind of mammal, with hair | hair | | ppython:: | | | some kind of reptile, without | ppython | | hair | : some kind of reptile, without | | (can you spot the typo?) | hair (can you spot the typo?) | | | | +-----------------------------------+-----------------------------------+

Note that you need a space in front of the defined term.

Block containing preformatted text are suitable for source code snippets, notes and examples. Use three curly braces wrapped around the text to define a block quote. The curly braces need to be on a separate line.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | {.wiki} | | {{{ | def HelloWorld(): | | def HelloWorld(): | print '''Hello World''' | | print '''Hello World''' | | | }}} | | | | | +-----------------------------------+-----------------------------------+

Note that this kind of block is also used for selecting lines that should be processed through WikiProcessors.

In order to mark a paragraph as blockquote, indent that paragraph with two spaces.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | Paragraph | | Paragraph | | | This text is a quote from someo | > This text is a quote from | | ne else. | > someone else. | | | | +-----------------------------------+-----------------------------------+

To delineate a citation in an ongoing discussion thread, such as the ticket comment area, e-mail-like citation marks (">", ">>", etc.) may be used.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | > > Someone's original text | | >> Someone's original text | > | | > Someone else's reply text | > Someone else's reply text | | > - which can be any kind of Wik | > | | i markup | > - which can be any kind of | | My reply text | > Wiki markup | | | | | | My reply text | +-----------------------------------+-----------------------------------+

Simple tables can be created like this:

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | -------- -------- -------- | | ||Cell 1||Cell 2||Cell 3|| | Cell 1 Cell 2 Cell 3 | | ||Cell 4||Cell 5||Cell 6|| | Cell 4 Cell 5 Cell 6 | | | -------- -------- -------- | +-----------------------------------+-----------------------------------+

Cell headings can be specified by wrapping the content in a pair of '=' characters. Note that the '=' characters have to stick to the cell separators, like this:

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | ------ -------- ----------- | | || ||= stable =||= latest | stable latest | | =|| | 0.10 0.10.5 0.10.6dev | | ||= 0.10 =|| 0.10.5 || 0.10.6de | 0.11 0.11.6 0.11.7dev | | v|| | ------ -------- ----------- | | ||= 0.11 =|| 0.11.6 || 0.11.7de | | | v|| | | | | | +-----------------------------------+-----------------------------------+

Finally, specifying an empty cell means that the next non empty cell will span the empty cells. For example:

Wiki Markup Display

|| 1 || 2 || 3 ||
|||| 1-2 || 3 ||
|| 1 |||| 2-3 ||
|||||| 1-2-3 ||

1 2 3 1-2 3 1 2-3 1-2-3 Note that if the content of a cell "sticks" to one side of the cell and only one, then the text will be aligned on that side. Example:

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | Text Numbers | | ||=Text =||= Numbers =|| | ------------------- --------- | | ||left align || 1.0|| | left align 1.0 | | || center || 4.5|| | center 4.5 | | || right align|| 4.5|| | right align 4.5 | | || default alignment || 2.5|| | default alignment 2.5 | | ||default|| 2.5|| | default 2.5 | | || default || 2.5|| | default 2.5 | | || default || 2.5|| | default 2.5 | | | | +-----------------------------------+-----------------------------------+

If contrary to the example above, the cells in your table contain more text, it might be convenient to spread a table row over multiple lines of markup. The \ character placed at the end of a line after a cell separator tells Trac to not start a new row for the cells on the next line.

+-----------------------------------------------------------------------+ | Wiki Markup | +=======================================================================+ | {.wiki} | | || this is column 1 [http://trac.edgewall.org/newticket new ticket] | | | | \ | | || this is column 2 [http://trac.edgewall.org/roadmap the road ahead] | | || \ | | || that's column 3 and last one || | | | +-----------------------------------------------------------------------+ | Display |

If the possibilities offered by the simple "pipe"-based markup for tables described above are not enough for your needs, you can create more elaborated tables by using WikiProcessor based tables.

Hyperlinks are automatically created for WikiPageNames and URLs. WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as !WikiPageLink.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | <a href="TitleIndex.html" class=" | | TitleIndex, http://www.edgewall.c | wiki">TitleIndex</a>, | | om/, !NotAlink | <a href="http://www.edgewall.com/ | | | " class="ext-link">​http://www.edgewall. | | | com/, | | | NotAlink | +-----------------------------------+-----------------------------------+

Links can be given a more descriptive title by writing the link followed by a space and a title and all this inside square brackets. If the descriptive title is omitted, then the explicit prefix is discarded, unless the link is an external link. This can be useful for wiki pages not adhering to the WikiPageNames convention.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | - <a href="http://www.edgewall. | | * [http://www.edgewall.com Edgew | com" class="ext-link"><span class | | all Software] | ="icon">​</span>Edgewall Software | | * [wiki:TitleIndex Title Index] | </a> | | * [wiki:TitleIndex] | - <a href="TitleIndex.html" cla | | * [wiki:ISO9000] | ss="wiki">Title Index</a> | | | - <a href="TitleIndex.html" cla | | | ss="wiki">TitleIndex | | | - [ISO9000?] | +-----------------------------------+-----------------------------------+

Following the ​WikiCreole trend, the descriptive title can also be specified by writing the link followed by a pipe ('|') and a title and all this inside double square brackets.

+-----------------------------------+-----------------------------------+ | {.wiki} | - <a href="http://www.edgewall. | | * [[http://www.edgewall.com|Edge | com" class="ext-link"><span class | | wall Software]] | ="icon">​</span>Edgewall Software | | * [[wiki:TitleIndex|Title Index] | </a> | | ] | - <a href="TitleIndex.html" cla | | or even [[TitleIndex|Title Ind | ss="wiki">Title Index</a> | | ex]] | or even | | * [[wiki:TitleIndex]] | <a href="TitleIndex.html" cla | | ''' but not ![[TitleIndex]]! ' | ss="wiki">Title Index</a> | | '' | - <a href="TitleIndex.html" cla | | * [[ISO9000]] | ss="wiki">TitleIndex</a> | | | but not | | | TitleIndex! | | | - [ISO9000?] | +-----------------------------------+-----------------------------------+

Note: the ​WikiCreole style for links is quick to type and certainly looks familiar as it's the one used on Wikipedia and in many other wikis. Unfortunately it conflicts with the syntax for macros. So in the rare case when you need to refer to a page which is named after a macro (typical examples being TitleIndex, InterTrac and InterWiki), by writing [[TitleIndex]] you will actually call the macro instead of linking to the page.

Wiki pages can link directly to other parts of the Trac system. Pages can refer to tickets, reports, changesets, milestones, source files and other Wiki pages using the following notations:

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | - Tickets: | | * Tickets: #1 or ticket:1 | <a href="/ticket/1" class="cl | | * Reports: {1} or report:1 | osed ticket" title="defect: WOL-I | | * Changesets: r1, [1] or changes | nterface (closed: fixed)">#1</a> | | et:1 | or | | * ... | <a href="/ticket/1" class="cl | | * targeting other Trac instances | osed ticket" title="defect: WOL-I | | , | nterface (closed: fixed)">ticket: | | so called InterTrac links: | 1</a> | | - Tickets: #Trac1 or Trac:tick | - Reports: | | et:1 | <a href="/report/1" class="re | | - Changesets: [Trac1] or Trac: | port">{1}</a> | | changeset:1 | or | | | report:1 | | | - Changesets: | | | <a href="/changeset/1" class= | | | "changeset" title="initial upload | | | ">r1, | | | <a href="/changeset/1" class= | | | "changeset" title="initial upload | | | ">[1] | | | or | | | <a href="/changeset/1" class= | | | "changeset" title="initial upload | | | ">changeset:1 | | | - … | | | - targeting other Trac | | | instances, so called | | | <a href="/wiki/InterTrac" cla | | | ss="wiki">InterTrac | | | links: | | | - Tickets: #Trac1 or | | | Trac:ticket:1 | | | - Changesets: [Trac1] or | | | Trac:changeset:1 | +-----------------------------------+-----------------------------------+

There are many more flavors of Trac links, see TracLinks for more in-depth information and a reference for all the default link resolvers.

An anchor, or more correctly speaking, an ​anchor name can be added explicitly at any place in the Wiki page, in order to uniquely identify a position in the document:

[=#point1]

This syntax was chosen to match the format for explicitly naming the header id documented above. For example:

== Long title == #title

It's also very close to the syntax for the corresponding link to that anchor:

[#point1]

Optionally, a label can be given to the anchor:

[[=#point1 '''Point 1''']]

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | > <a href="WikiFormatting#point2" | | [#point2 jump to the second point | class="wiki">jump to the second | | ] | point</a> | | | | | ... | > … | | | | | Point2: [=#point2] Jump here | > Point2: [] Jump here | | | | +-----------------------------------+-----------------------------------+

For more complex anchors (e.g. when a custom title is wanted), one can use the Span macro, e.g. [[span(id=point2, class=wikianchor, title=Point 2, ^(2)^)]].

You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark).

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | > NoHyperLink \#42 is not a link | | !NoHyperLink | | | !#42 is not a link | Various forms of escaping for | | | list markup: | | | | | {.wiki} | > `-` escaped minus sign\ | | Various forms of escaping for lis | > ``1. escaped number\ | | t markup: | > `*` escaped asterisk sign | | `-` escaped minus sign \\ | | | ``1. escaped number \\ | | | {{{*}}} escaped asterisk sign | | | | | +-----------------------------------+-----------------------------------+

Urls ending with .png, .gif or .jpg are no longer automatically interpreted as image links, and converted to <img> tags.

You now have to use the Image macro. The simplest way to include an image is to upload it as attachment to the current page, and put the filename in a macro call like [[Image(picture.gif)]].

In addition to the current page, it is possible to refer to other resources:

• [[Image(wiki:WikiFormatting:picture.gif)]] (referring to attachment on another page)
• [[Image(ticket:1:picture.gif)]] (file attached to a ticket)
• [[Image(htdocs:picture.gif)]] (referring to a file inside the environment htdocs directory)
• [[Image(source:/trunk/trac/htdocs/trac_logo_mini.png)]] (a file in repository)

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | [![trac\_logo\_mini.png](chrome/c | | [[Image(htdocs:common/trac_logo_m | ommon/trac_logo_mini.png "trac_lo | | ini.png)]] | go_mini.png")](chrome/common/trac | | | _logo_mini.png) | +-----------------------------------+-----------------------------------+

See WikiMacros for further documentation on the [[Image()]] macro, which has several useful options (title=, link=, etc.)

Macros are custom functions to insert dynamic content in a page.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | <div> | | [[RecentChanges(Trac,3)]] | | | | ### 03.11.2012 | | | | | | - TracIni | | | ([diff](/wiki/TracIni?action= | | | diff&version=6)) | | | - [TracSyntaxColoring](/wiki/Tr | | | acSyntaxColoring) | | | ([diff](/wiki/TracSyntaxColor | | | ing?action=diff&version=6)) | | | - TracAdmin | | | ([diff](/wiki/TracAdmin?actio | | | n=diff&version=6)) | | | | | | | +-----------------------------------+-----------------------------------+

See WikiMacros for more information, and a list of installed macros.

The detailed help for a specific macro can also be obtained more directly by appending a "?" to the macro name.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | <div class="trac-macrolist"> | | [[MacroList?]] | | | | ### [[MacroList]] | | | | | | Display a list of all installed | | | Wiki macros, including | | | documentation if available. | | | | | | Optionally, the name of a | | | specific macro can be provided as | | | an argument. In that case, only | | | the documentation for that macro | | | will be rendered. | | | | | | Note that this macro will not be | | | able to display the documentation | | | of macros if the PythonOptimize | | | option is enabled for | | | mod_python! | | | | | | | +-----------------------------------+-----------------------------------+

Trac supports alternative markup formats using WikiProcessors. For example, processors are used to write pages in reStructuredText or HTML.

Wiki Markup Display

[Example 1:] HTML

{{{
#!html
<h1 style="text-align: right; color: blue">
 HTML Test
</h1>
}}}

[Example 2:] Code Highlighting

{{{
#!python
class Test:

    def __init__(self):
        print "Hello World"
if __name__ == '__main__':
   Test()
}}}

class Test:
    def __init__(self):
        print "Hello World"
if __name__ == '__main__':
   Test()

[Example 3:] Complex Tables

{{{#!th rowspan=4 align=justify
With the `#td` and `#th` processors,
table cells can contain any content:
}}}
|----------------
{{{#!td
  - lists
  - embedded tables
  - simple multiline content
}}}
|----------------
{{{#!td
As processors can be easily nested, 
so can be tables:
  {{{#!th
  Example:
  }}}
  {{{#!td style="background: #eef"
  || must be at the third level now... ||
  }}}
}}}
|----------------
{{{#!td
Even when you don't have complex markup,
this form of table cells can be convenient
to write content on multiple lines.
}}}

With the #td and #th processors, table cells can contain any content:

• lists
• embedded tables
• simple multiline content

As processors can be easily nested, so can be tables:

+-----------------------------------+-----------------------------------+ | Example: | ------------------------------- | | | -- | | | must be at the third level now… | | | ------------------------------- | | | -- | +-----------------------------------+-----------------------------------+

Even when you don't have complex markup, this form of table cells can be convenient to write content on multiple lines.

See WikiProcessors for more information.

Comments can be added to the plain text. These will not be rendered and will not display in any other format than plain text.

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | {.wiki} | > Nothing to | | Nothing to | > | | {{{ | > see | | #!comment | > ![;-)](chrome/wikiextras-icons- | | Your comment for editors here | 16/smiley-wink.png) | | }}} | | | see ;-) | | | | | +-----------------------------------+-----------------------------------+

An horizontal line can be used to separated different parts of your page:

+-----------------------------------+-----------------------------------+ | Wiki Markup | Display | +===================================+===================================+ | ``` {.wiki} | Four or more dashes will be | | Four or more dashes will be repla | replaced by an horizontal line | | ced | (<HR>) |