Changes between Version 3 and Version 4 of WikiFormatting
- Timestamp:
- 11/09/05 18:26:14 (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiFormatting
v3 v4 1 1 = WikiFormatting = 2 3 Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into flexible and powerful whole. 4 5 Trac 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 especially [http://moin.sf.net/ MoinWiki]. 2 [[TracGuideToc]] 3 4 Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into a flexible and powerful whole. 5 6 Trac 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, 7 especially [http://moinmoin.wikiwikiweb.de/ MoinMoin]. 8 6 9 7 10 This page demonstrates the formatting syntax available anywhere WikiFormatting is allowed. 8 11 9 == Font styles == 10 11 The Trac wiki support the following font styles: '''bold''', ''italic'', 12 __underline__ and ~~strike-through~~. 13 14 {{{ 15 The Trac wiki support the following font styles: '''bold''', ''italic'', 16 __underline__ and ~~strike-through~~. 17 }}} 18 19 20 == Heading == 21 22 You can create heading by starting a line with one up to five ''equal\\ '=' characters 12 13 == Font Styles == 14 15 The Trac wiki supports the following font styles: 16 {{{ 17 * '''bold''' 18 * ''italic'' 19 * '''''bold italic''''' 20 * __underline__ 21 * {{{monospace}}} or `monospace` 22 * ~~strike-through~~ 23 * ^superscript^ 24 * ,,subscript,, 25 }}} 26 27 Display: 28 * '''bold''' 29 * ''italic'' 30 * '''''bold italic''''' 31 * __underline__ 32 * {{{monospace}}} or `monospace` 33 * ~~strike-through~~ 34 * ^superscript^ 35 * ,,subscript,, 36 37 Note that the `{{{...}}}` 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 39 == Headings == 40 41 You can create heading by starting a line with one up to five ''equal'' characters ("=") 23 42 followed by a single space and the headline text. The line should end with a space 24 followed by the same number of ''equal'' characters. 25 26 ''Note: As of writing, headings cannot contain TracLinks.'' 27 28 === Example: === 43 followed by the same number of ''='' characters. 44 45 Example: 29 46 {{{ 30 47 = Heading = 31 48 == Subheading == 32 }}} 49 === About ''this'' === 50 }}} 51 52 Display: 53 = Heading = 54 == Subheading == 55 === About ''this'' === 33 56 34 57 35 58 == Paragraphs == 36 59 37 A new text paragraph is created whenever two blocks of text are separated 38 by one or more empty lines. 60 A new text paragraph is created whenever two blocks of text are separated by one or more empty lines. 39 61 40 62 A forced line break can also be inserted, using: … … 46 68 Line 1[[BR]]Line 2 47 69 48 Text paragraphs can be indented by starting the lines with two or more spaces.49 70 50 71 == Lists == 72 51 73 The wiki supports both ordered/numbered and unordered lists. 52 74 … … 61 83 1. Item 2 62 84 }}} 85 63 86 Display: 64 87 * Item 1 … … 70 93 1. Item 2 71 94 72 == Preformatted text == 73 Block quotes, preformatted text, are suitable for source code snippets, notes and examples. Use three ''curly braces'' wrapped around the text to define a block quote: 95 Note that there must be one or more spaces preceding the list item markers, otherwise the list will be treated as a normal paragraph. 96 97 98 == Definition Lists == 99 100 The wiki also supports definition lists. 101 102 Example: 103 {{{ 104 llama:: 105 some kind of mammal, with hair 106 ppython:: 107 some kind of reptile, without hair 108 (can you spot the typo?) 109 }}} 110 111 Display: 112 llama:: 113 some kind of mammal, with hair 114 ppython:: 115 some kind of reptile, without hair 116 (can you spot the typo?) 117 118 Note that you need a space in front of the defined term. 119 120 121 == Preformatted Text == 122 123 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. 74 124 75 125 Example: 76 126 {{{ 77 127 {{{ 78 def HelloWorld() 128 def HelloWorld(): 79 129 print "Hello World" 80 130 }}} … … 83 133 Display: 84 134 {{{ 85 def HelloWorld() 135 def HelloWorld(): 86 136 print "Hello World" 87 137 }}} 138 139 140 == Blockquotes == 141 142 In order to mark a paragraph as blockquote, indent that paragraph with two spaces. 143 144 Example: 145 {{{ 146 This text is a quote from someone else. 147 }}} 148 149 Display: 150 This text is a quote from someone else. 88 151 89 152 == Tables == … … 94 157 ||Cell 4||Cell 5||Cell 6|| 95 158 }}} 159 96 160 Display: 97 161 ||Cell 1||Cell 2||Cell 3|| 98 162 ||Cell 4||Cell 5||Cell 6|| 99 163 164 Note that more complex tables can be created using 165 [wiki:WikiRestructuredText#BiggerReSTExample reStructuredText]. 166 167 100 168 == Links == 101 169 102 !Hyperlinks are automatically created for WikiPageNames and urls. !WikiPageLinks can be disabled by 103 prepending an exclamation mark (!) character, such as {{{!WikiPageLink}}}. 104 105 Examples: 106 107 TitleIndex, http://www.edgewall.com/. 108 109 Links can be given a more descriptive title by writing the link followed by 110 a space and a title and all this inside two square brackets. Like this: 170 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as {{{!WikiPageLink}}}. 171 172 Example: 173 {{{ 174 TitleIndex, http://www.edgewall.com/, !NotAlink 175 }}} 176 177 Display: 178 TitleIndex, http://www.edgewall.com/, !NotAlink 179 180 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 disguarded, unless the link is an external link. This can be useful for wiki pages not adhering to the WikiPageNames convention. 181 182 Example: 111 183 {{{ 112 184 * [http://www.edgewall.com/ Edgewall Software] 113 185 * [wiki:TitleIndex Title Index] 114 }}} 115 Display: 116 186 * [wiki:ISO9000] 187 }}} 188 189 Display: 117 190 * [http://www.edgewall.com/ Edgewall Software] 118 191 * [wiki:TitleIndex Title Index] 192 * [wiki:ISO9000] 193 119 194 120 195 === Trac Links === 121 196 122 Wiki pages can link directly to other parts of the Trac system. 123 Pages can refer to tickets, reports, changesets, milestones, source files and 124 other Wiki pages using the following notation: 125 * Tickets: '''!#1''' or '''!ticket:1''' 126 * Reports: '''!{1}''' or '''!report:1''' 127 * Changesets: '''![1]''' or '''!changeset:1''' 128 * Wiki pages: '''CamelCase''' or '''!wiki:CamelCase''' 129 * Milestones: '''!milestone:1.0''' 130 * Files: '''!source:trunk/COPYING''' 131 * A specific file revision: '''!source:/trunk/COPYING#200''' 132 Display: 197 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: 198 {{{ 133 199 * Tickets: #1 or ticket:1 134 200 * Reports: {1} or report:1 135 * Changesets: [1] or changeset:1 201 * Changesets: r1, [1] or changeset:1 202 * Revision Logs: r1:3, [1:3] or log:branches/0.8-stable#1:3 136 203 * Wiki pages: CamelCase or wiki:CamelCase 137 * Milestones: milestone:1.0 204 * Milestones: milestone:1.0 or milestone:"End-of-days Release" 138 205 * Files: source:trunk/COPYING 206 * Attachments: attachment:"file name.doc" 139 207 * A specific file revision: source:/trunk/COPYING#200 208 * A filename with embedded space: source:"/trunk/README FIRST" 209 }}} 210 211 Display: 212 * Tickets: #1 or ticket:1 213 * Reports: {1} or report:1 214 * Changesets: r1, [1] or changeset:1 215 * Revision Logs: r1:3, [1:3] or log:branches/0.8-stable#1:3 216 * Wiki pages: CamelCase or wiki:CamelCase 217 * Milestones: milestone:1.0 or milestone:"End-of-days Release" 218 * Files: source:trunk/COPYING 219 * Attachments: attachment:"file name.doc" 220 * A specific file revision: source:/trunk/COPYING#200 221 * A filename with embedded space: source:"/trunk/README FIRST" 140 222 141 223 See TracLinks for more in-depth information. 142 224 143 == Escaping Links and WikiNames == 144 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single '!' (exclamation mark). 145 225 226 == Escaping Links and WikiPageNames == 227 228 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark). 229 230 Example: 146 231 {{{ 147 232 !NoHyperLink … … 153 238 !#42 is not a link 154 239 240 155 241 == Images == 156 242 157 Urls ending with .png, .gif or .jpg are automatically interpreted as image links, and converted to IMGtags.243 Urls ending with `.png`, `.gif` or `.jpg` are automatically interpreted as image links, and converted to `<img>` tags. 158 244 159 245 Example: … … 161 247 http://www.edgewall.com/gfx/trac_example_image.png 162 248 }}} 249 163 250 Display: 164 251 165 252 http://www.edgewall.com/gfx/trac_example_image.png 166 253 254 However, this doesn't give much control over the display mode. This way of inserting images is deprecated in favor of the more powerful `Image` macro (see WikiMacros). 255 256 167 257 == Macros == 168 Macros are ''custom functions'' to insert dynamic content in a page. See WikiMacros for usage. 258 259 Macros are ''custom functions'' to insert dynamic content in a page. 169 260 170 261 Example: … … 172 263 [[Timestamp]] 173 264 }}} 265 174 266 Display: 175 267 [[Timestamp]] 176 268 269 See WikiMacros for more information, and a list of installed macros. 270 271 177 272 == Processors == 178 Trac supports alternative markup formats using WikiProcessors. For example, processors are used to write pages in [wiki:WikiRestructuredText reStructuredText] or [wiki:WikiHtml HTML]. 179 180 See WikiProcessors for more information. 181 182 '''Example 1:''' 273 274 Trac supports alternative markup formats using WikiProcessors. For example, processors are used to write pages in 275 [wiki:WikiRestructuredText reStructuredText] or [wiki:WikiHtml HTML]. 276 277 Example 1: 183 278 {{{ 184 279 #!html … … 188 283 }}}</pre> 189 284 }}} 285 190 286 Display: 191 287 {{{ … … 194 290 }}} 195 291 196 '''Example 2:''' 292 Example: 197 293 {{{ 198 294 #!html … … 206 302 }}}</pre> 207 303 }}} 304 208 305 Display: 209 306 {{{ … … 216 313 }}} 217 314 315 Perl: 316 {{{ 317 #!perl 318 my ($test) = 0; 319 if ($test > 0) { 320 echo "hello"; 321 } 322 }}} 323 324 See WikiProcessors for more information. 325 326 218 327 == Miscellaneous == 219 328 220 329 Four or more dashes will be replaced by a horizontal line (<HR>) 221 330 331 Example: 222 332 {{{ 223 333 ---- … … 230 340 ---- 231 341 See also: TracLinks, TracGuide, WikiHtml, WikiMacros, WikiProcessors, TracSyntaxColoring. 232