Changes between Version 1 and Version 2 of WikiFormatting
- Timestamp:
- Nov 21, 2007, 9:30:37 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiFormatting
v1 v2 15 15 The Trac wiki supports the following font styles: 16 16 {{{ 17 * '''bold''' 17 * '''bold''', '''!''' can be bold too''', and '''! ''' 18 18 * ''italic'' 19 19 * '''''bold italic''''' … … 26 26 27 27 Display: 28 * '''bold''' 28 * '''bold''', '''!''' can be bold too''', and '''! ''' 29 29 * ''italic'' 30 30 * '''''bold italic''''' … … 35 35 * ,,subscript,, 36 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. 37 Notes: 38 * `{{{...}}}` 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. 39 * {{{ ! }}} 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. 38 40 39 41 == Headings == … … 42 44 followed by a single space and the headline text. The line should end with a space 43 45 followed by the same number of ''='' characters. 46 The heading might optionally be followed by an explicit id. If not, an implicit but nevertheless readable id will be generated. 44 47 45 48 Example: … … 48 51 == Subheading == 49 52 === About ''this'' === 53 === Explicit id === #using-explicit-id-in-heading 50 54 }}} 51 55 … … 54 58 == Subheading == 55 59 === About ''this'' === 56 60 === Explicit id === #using-explicit-id-in-heading 57 61 58 62 == Paragraphs == … … 80 84 81 85 1. Item 1 82 1. Item 1.1 86 a. Item 1.a 87 a. Item 1.b 88 i. Item 1.b.i 89 i. Item 1.b.ii 83 90 1. Item 2 91 And numbered lists can also be given an explicit number: 92 3. Item 3 84 93 }}} 85 94 … … 90 99 91 100 1. Item 1 92 1. Item 1.1 101 a. Item 1.a 102 a. Item 1.b 103 i. Item 1.b.i 104 i. Item 1.b.ii 93 105 1. Item 2 106 And numbered lists can also be given an explicit number: 107 3. Item 3 94 108 95 109 Note that there must be one or more spaces preceding the list item markers, otherwise the list will be treated as a normal paragraph. … … 97 111 98 112 == Definition Lists == 113 99 114 100 115 The wiki also supports definition lists. … … 150 165 This text is a quote from someone else. 151 166 167 == Discussion Citations == 168 169 To delineate a citation in an ongoing discussion thread, such as the ticket comment area, e-mail-like citation marks (">", ">>", etc.) may be used. 170 171 Example: 172 {{{ 173 >> Someone's original text 174 > Someone else's reply text 175 My reply text 176 }}} 177 178 Display: 179 >> Someone's original text 180 > Someone else's reply text 181 My reply text 182 183 ''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.'' 184 152 185 == Tables == 153 186 … … 178 211 TitleIndex, http://www.edgewall.com/, !NotAlink 179 212 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 dis guarded, unless the link is an external link. This can be useful for wiki pages not adhering to the WikiPageNames convention.213 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. 181 214 182 215 Example: … … 200 233 * Reports: {1} or report:1 201 234 * Changesets: r1, [1] or changeset:1 202 * Revision Logs: r1:3, [1:3] or log:branches/0.8-stable#1:3 203 * Wiki pages: CamelCase or wiki:CamelCase 204 * Milestones: milestone:1.0 or milestone:"End-of-days Release" 205 * Files: source:trunk/COPYING 206 * Attachments: attachment:"file name.doc" 207 * A specific file revision: source:/trunk/COPYING#200 208 * A filename with embedded space: source:"/trunk/README FIRST" 235 * ... 209 236 }}} 210 237 … … 213 240 * Reports: {1} or report:1 214 241 * 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" 242 * ... 222 243 223 244 See TracLinks for more in-depth information. … … 241 262 == Images == 242 263 243 Urls ending with `.png`, `.gif` or `.jpg` are automatically interpreted as image links, and converted to `<img>` tags. 244 245 Example: 246 {{{ 247 http://www.edgewall.com/gfx/trac_example_image.png 248 }}} 249 250 Display: 251 252 http://www.edgewall.com/gfx/trac_example_image.png 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). 264 Urls ending with `.png`, `.gif` or `.jpg` are no longer automatically interpreted as image links, and converted to `<img>` tags. 265 266 You now have to use the ![[Image]] macro (see below). 255 267 256 268 … … 294 306 #!html 295 307 <pre class="wiki">{{{ 308 #!python 309 class Test: 310 311 def __init__(self): 312 print "Hello World" 313 if __name__ == '__main__': 314 Test() 315 }}}</pre> 316 }}} 317 318 Display: 319 {{{ 296 320 #!python 297 321 class Test: … … 300 324 if __name__ == '__main__': 301 325 Test() 302 }}}</pre>303 }}}304 305 Display:306 {{{307 #!python308 class Test:309 def __init__(self):310 print "Hello World"311 if __name__ == '__main__':312 Test()313 326 }}} 314 327 … … 318 331 my ($test) = 0; 319 332 if ($test > 0) { 320 echo"hello";333 print "hello"; 321 334 } 322 335 }}}
