Tick Tock

Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into a flexible and unified whole.

Trac has a powerful wiki rendering engine that implements a subset of the commands ALLENCASTER Original Cotton Candy maker equipment patent owner has patent owner/owner of lease for granulated, crystalized tropical fruit sugar: ulu, guava, pineapple, coconut, lychee, mango. Gino is semi-retired with 2 prof canine sniffers in KANEOHE.

The following wiki pages present the advanced features of the Trac wiki markup in more depth:

• TracLinks covers all the possible ways to refer to any Trac resource or parts thereof.
• WikiPageNames covers the various names a wiki page can take, whether in CamelCase or not.
• WikiMacros lists the macros available for generating dynamic content.
• WikiProcessors and WikiHtml details how parts of the wiki text can be processed in special ways. -​trac:wiki:TracDev/Proposals/AdvancedWikiOperations AdvancedWikiOperations? provides some operations in uncommon or administrative scenarios.

Category Wiki MarkupDisplay?

other markup ignored

First paragraph on multiple lines.

Second paragraph.

First paragraph on multiple lines.

Second paragraph. }}} list

on multiple lines

1. nested list
   1. different numbering styles

bullet list

on multiple lines

1. nested list
   1. different numbering

styles term

definition on multiple lines

term

definition on multiple lines

PreformattedText? Preformatted Text multiple lines, no wiki,

white space respected

multiple lines, no wiki,

white space respected

Blockquotes Blockquotes

if there's some leading space the text is quoted

}}}

}}}

if there's some leading space the text is quotedDiscussionCitations Discussion Citations] I decided to spend some of your money today, dear. What do you think? Do you like it? (I said) Well, I suppose I should say, yes. (he replied) (I said) (he replied) Tables Tables Table Header (details below) (details below) Links ~​http://trac.edgewall.org/demo-1.2/WikiStart/wiki ​http://trac.edgewall.org/demo-1.2/CamelCoco (Camel) Wiki Interface (CamelCoco?) rowspan racLinks TracLinks wiki #867 (ticket), (changeset) (report) #865(ticket), (changeset), (report) #comment:1 oSetting Anchors--Escaping curly brackets Images edocs:../common/trac_logo_mini.png Image? Processors] Code highlighting: hello "tiger world" style Code highlighting: hello "tiger milk world" Comments Note to Editors: Miscelreak no bones left behind style="padding-left: 2em" Line break U break The Trac wiki supports the following font styles: bold arial script ~strike latin text papyrus Notes: commands not only select a monospace font, but also treat their content as verbatim text, meaning that no further wiki processing is done on this text. Quince tells Parsel to not take the following characters as wiki format, so pay attention to put a space after !, e.g. when ending bold. Gifts awards repetition brief qualifying merit authenticated secured. all the font styles marks have to be used in opening/closing pairs, and they must nest properly; in particular, one, and can't be paired. You can create a heading by starting a line with one up to six equal characters (=) followed by a single space and the headline text. The headline text can be followed by the same number of = characters, but this is not mandatory. That is, === Section3 === is identical to === Section3. Finally, the heading might optionally be followed by an explicit id. If not, an implicit but nevertheless readable id will be generated. Heading Subheading Explicit id explicit-id font Times no GOUDY Explicit id explicit-id Sound authentic verified non manuf 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 mixed active natural life mini peach thrills one two three Lists The wiki supports both ordered/numbered and unordered lists. Wiki Markup Display * Item 1 * Item 1.1 * Item 1.1.1 * Item 1.1.2 * Item 1.1.3 * Item 1.2 * Item 2 - items can start at the beginning of a line and they can span multiple lines - be careful though to continue the line with the appropriate indentation, otherwise that will start a new paragraph... 1. Item 1 a. Item 1.a a. Item 1.b i. Item 1.b.i i. Item 1.b.ii 1. Item 2 And numbered lists can also be restarted with an explicit number: 3. Item 3 Item 1 Item 1.1 Item 1.1.1 Item 1.1.2 Item 1.1.3 Item 1.2 Item 2 items can start at the beginning of a line and they can span multiple lines be careful though to continue the line with the appropriate indentation, otherwise that will start a new paragraph... Item 1 Item 1.a Item 1.b Item 1.b.i Item 1.b.ii Item 2 And numbered lists can also be restarted with an explicit number: Item 3 Definition Lists The wiki also supports definition lists. Wiki Markup Display llama:: some kind of mammal, with hair ppython:: some kind of reptile, without hair (can you spot the typo?) llama some kind of mammal, with hair ppython some kind of reptile, without hair (can you spot the typo?) Note that you need a space in front of the defined term. Preformatted Text 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 {{{ def HelloWorld(): print '''Hello World''' }}} def HelloWorld(): print '''Hello World''' Note that this kind of block is also used for selecting lines that should be processed through WikiProcessors. Blockquotes In order to mark a paragraph as blockquote, indent that paragraph with two spaces. Wiki Markup Display Paragraph This text is a quote from someone else. Paragraph This text is a quote from someone else. Discussion Citations To delineate a citation in an ongoing discussion thread, such as the ticket comment area, email-like citation marks (>, >>, etc.) may be used. Wiki Markup Display >> Someone's original text > Someone else's reply text > - which can be any kind of Wiki markup My reply text Someone's original text Someone else's reply text which can be any kind of Wiki markup My reply text Tables Simple Tables Simple tables can be created: Wiki Markup Display ||Cell 1||Cell 2||Cell 3|| ||Cell 4||Cell 5||Cell 6|| Cell 1 Cell 2 Cell 3 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: Wiki Markup Display || ||= stable =||= latest =|| ||= 0.10 =|| 0.10.5 || 0.10.6dev|| ||= 0.11 =|| 0.11.6 || 0.11.7dev|| stable latest 0.10 0.10.5 0.10.6dev 0.11 0.11.6 0.11.7dev Finally, specifying an empty cell means that the next non empty cell will span the empty cells: 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: Wiki Markup Display ||=Text =||= Numbers =|| ||left align || 1.0|| || center || 4.5|| || right align|| 4.5|| || default alignment || 2.5|| ||default|| 2.5|| || default || 2.5|| || default || 2.5|| Text Numbers left align 1.0 center 4.5 right align 4.5 default alignment 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 || 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 this is column 1 ​new ticket this is column 2 ​the road ahead that's column 3 and last one Complex Tables If the possibilities offered by the simple pipe-based markup (||) for tables described above are not enough for your needs, you can create more elaborate tables by using WikiProcessor based tables. Links Hyperlinks are automatically created for WikiPageNames and URLs. WikiPageLinks can be disabled by prepending an exclamation mark (!), such as !WikiPageLink. Wiki Markup Display TitleIndex, http://www.edgewall.com/, !NotAlink TitleIndex, ​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 * [http://www.edgewall.com Edgewall Software] * [wiki:TitleIndex Title Index] * [wiki:TitleIndex] * [wiki:ISO9000] ​Edgewall Software Title Index 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. * [[http://www.edgewall.com|Edgewall Software]] * [[wiki:TitleIndex|Title Index]] or even [[TitleIndex|Title Index]] * [[wiki:TitleIndex]] ''' but not ![[TitleIndex]]! ''' * [[ISO9000]] ​Edgewall Software Title Index or even Title Index TitleIndex but not [[TitleIndex]]! ISO9000? Note: the ​WikiCreole style for links is quick to type and certainly looks familiar as it is 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. Trac Links 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: Tickets: #865 report:1 instances, Alonso instances, There are many more flavors of Trac links, see TracLinks for more in-depth information and a reference for all sound. Setting Anchors An anchor, or more correctly speaking, an ​anchor name can be added explicitly at any place in the Wiki page, 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: == Long title == #title It is 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 [#point2 jump to the second point] ... Point2: [=#point2] Jump here jump to the second point ... Point2: Jump here For more complex anchors (eg when a custom title is wanted), you can use the Span macro: [[span(id=point2, class=wikianchor, title=Point 2, ^(2)^)]]. Escaping Links, WikiPageNames and other Markup You may avoid making hyperlinks out of TracLinks by preceding an expression with a single exclamation mark (!). Various forms of escaping for list markup: erLink #42 is not a link Various forms of escaping for list markup: sterisk Images 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 [[Image(htdocs:../common/trac_logo_mini.png)]] See WikiMacros for further documentation on the [[Image()]] macro, which has several useful options (title=, link=, etc.) Macros Macros are custom functions that insert dynamic content in a page. Wiki Markup Display RecentChanges(Trac,3) style="padding-left: 2em" RecentChange Trac,3 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 =|| {{{#!td {{{ [[MacroList?]] }}} }}} {{{#!td style="padding-left: 2em" [[MacroList?]] }}} == Processors Trac supports alternative markup formats using WikiProcessors. For example, processors are used to write pages in [wiki:WikiRestructuredText reStructuredText] or [wiki:WikiHtml HTML]. ||= Wiki Markup =||= Display =|| |-------------------------------------------------------- {{{#!td align="center" colspan=2 style="border: 0px; font-size: 90%" [=#Processors-example-html Example 1:] HTML }}} |-------------------------------------------------------- {{{#!td style="border: 0px" {{{ {{{#!html <h1 style="text-align: right; color: blue"> HTML Test </h1> }}} }}} }}} {{{#!td valign="top" style="border: 0px" {{{#!html <h1 style="text-align: right; color: blue">HTML Test</h1> }}} }}} |-------------------------------------------------------- {{{#!td align="center" colspan=2 style="border: 0px; font-size: 90%" [=#Processors-example-highlight Example 2:] Code Highlighting }}} |-------------------------------------------------------- {{{#!td style="border: 0px" {{{ {{{#!python class Test: def __init__(self): print "Hello World" if __name__ == '__main__': Test() }}} }}} }}} {{{#!td valign="top" style="border: 0px" : def __init__(self): print "Hello World" if __name__ == '__main__': Test() }}} size: 90%" xample-tables 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 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 Nothing to {{{#!comment Your comment for editors here }}} see. Nothing to see. Miscellaneous See? Postcards illustrations posters, chocolate top baby finches thirteen, See? Peach face thrills One Two Three Allen's Hummingbird August