3 Wiki markup is a core feature, tightly integrating all the other parts of mtrack into a flexible and powerful whole.
5 mtrack has a built in small and powerful wiki rendering engine. This wiki engine implements an ever growing subset of the commands from other popular Wikis,
6 especially [http://moinmoin.wikiwikiweb.de/ MoinMoin].
9 This page demonstrates the formatting syntax available anywhere !WikiFormatting is allowed.
14 The Trac wiki supports the following font styles:
16 * '''bold''', '''!''' can be bold too''', and '''! '''
18 * '''''bold italic'''''
20 * {{{monospace}}} or `monospace`
27 * '''bold''', '''!''' can be bold too''', and '''! '''
29 * '''''bold italic'''''
31 * {{{monospace}}} or `monospace`
37 * `{{{...}}}` and {{{`...`}}} 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.
38 * {{{ ! }}} tells wiki parser to not take the following characters as wiki format, so pay attention to put a space after !, e.g. when ending bold.
42 You can create heading by starting a line with one up to five ''equal'' characters ("=")
43 followed by a single space and the headline text. The line should end with a space
44 followed by the same number of ''='' characters.
45 The heading might optionally be followed by an explicit id. If not, an implicit but nevertheless readable id will be generated.
51 === About ''this'' ===
52 === Explicit id === #using-explicit-id-in-heading
58 === About ''this'' ===
59 === Explicit id === #using-explicit-id-in-heading
63 A new text paragraph is created whenever two blocks of text are separated by one or more empty lines.
65 A forced line break can also be inserted, using:
76 The wiki supports both ordered/numbered and unordered lists.
94 And numbered lists can also be given an explicit number:
113 And numbered lists can also be given an explicit number:
116 Note that there must be one or more spaces preceding the list item markers, otherwise the list will be treated as a normal paragraph.
119 == Definition Lists ==
122 The wiki also supports definition lists.
127 some kind of mammal, with hair
129 some kind of reptile, without hair
130 (can you spot the typo?)
135 some kind of mammal, with hair
137 some kind of reptile, without hair
138 (can you spot the typo?)
140 Note that you need a space in front of the defined term.
143 == Preformatted Text ==
145 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.
164 In order to mark a paragraph as blockquote, indent that paragraph with two spaces.
168 This text is a quote from someone else.
172 This text is a quote from someone else.
174 == Discussion Citations ==
176 To delineate a citation in an ongoing discussion thread, such as the ticket comment area, e-mail-like citation marks (">", ">>", etc.) may be used.
180 >> Someone's original text
181 > Someone else's reply text
186 >> Someone's original text
187 > Someone else's reply text
190 ''Note: Some !WikiFormatting elements, such as lists and preformatted text, are lost in the citation area. Some reformatting may be necessary to create a clear citation.''
194 Simple tables can be created like this:
196 ||Cell 1||Cell 2||Cell 3||
197 ||Cell 4||Cell 5||Cell 6||
201 ||Cell 1||Cell 2||Cell 3||
202 ||Cell 4||Cell 5||Cell 6||
206 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as {{{!WikiPageLink}}}.
210 TitleIndex, http://www.edgewall.com/, !NotAlink
214 TitleIndex, http://www.edgewall.com/, !NotAlink
216 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.
220 * [http://www.edgewall.com/ Edgewall Software]
221 * [wiki:TitleIndex Title Index]
226 * [http://www.edgewall.com/ Edgewall Software]
227 * [wiki:TitleIndex Title Index]
232 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:
234 * Tickets: #1 or ticket:1
235 * Reports: {1} or report:1
236 * Changesets: r1, [1] or changeset:1
241 * Tickets: #1 or ticket:1
242 * Reports: {1} or report:1
243 * Changesets: r1, [1] or changeset:1
246 There are many more flavors of Trac links, see TracLinks for more in-depth information.
249 == Escaping Links and WikiPageNames ==
251 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark).
268 Urls ending with `.png`, `.gif` or `.jpg` are no longer automatically interpreted as image links, and converted to `<img>` tags.
270 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)]]`.
272 In addition to the current page, it is possible to refer to other resources:
273 * `[[Image(wiki:WikiFormatting:picture.gif)]]` (referring to attachment on another page)
274 * `[[Image(ticket:1:picture.gif)]]` (file attached to a ticket)
275 * `[[Image(htdocs:picture.gif)]]` (referring to a file inside project htdocs)
276 * `[[Image(source:/trunk/trac/htdocs/trac_logo_mini.png)]]` (a file in repository)
278 Example display: [[Image(htdocs:../common/trac_logo_mini.png)]]
281 See WikiMacros for further documentation on the `[[Image()]]` macro.
287 Macros are ''custom functions'' to insert dynamic content in a page.
291 [[RecentChanges(Trac,3)]]
295 [[RecentChanges(Trac,3)]]
297 See WikiMacros for more information, and a list of installed macros.
302 Trac supports alternative markup formats using WikiProcessors. For example, processors are used to write pages in HTML.
307 <pre class="wiki">{{{
309 <h1 style="text-align: right; color: blue">HTML Test</h1>
316 <h1 style="text-align: right; color: blue">HTML Test</h1>
322 <pre class="wiki">{{{
328 if __name__ == '__main__':
339 if __name__ == '__main__':
352 See WikiProcessors for more information.
357 Comments can be added to the plain text. These will not be rendered and will not display in any other format than plain text.
365 == Data output from SQL command line utilities ==
367 If you have text that you want to copy and paste from a command line utility,
368 such as psql, then you can enclose it in the ''dataset'' processor:
373 current_query | procpid | usename | client_addr | elapsed
374 --------------------------------------+---------+---------+--------------+-----------------
375 SELECT * FROM build_mailing(59508) | 6595 | user | 10.16.40.80 | 00:04:24.377262
376 FETCH NEXT FROM "<unnamed portal 5>" | 27597 | user | 10.16.40.80 | 00:00:44.208982
377 commit | 19188 | user | 10.16.40.67 | 00:00:00.013402
378 COMMIT | 26390 | user | 10.16.1.56 | 00:00:00.007778
384 current_query | procpid | usename | client_addr | elapsed
385 --------------------------------------+---------+---------+--------------+-----------------
386 SELECT * FROM build_mailing(59508) | 6595 | user | 10.16.40.80 | 00:04:24.377262
387 FETCH NEXT FROM "<unnamed portal 5>" | 27597 | user | 10.16.40.80 | 00:00:44.208982
388 commit | 19188 | user | 10.16.40.67 | 00:00:00.013402
389 COMMIT | 26390 | user | 10.16.1.56 | 00:00:00.007778
394 Four or more dashes will be replaced by a horizontal line (<HR>)