Changes between Version 120 and Version 121 of WikiFormatting
- Timestamp:
- Dec 8, 2015, 11:31:41 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiFormatting
v120 v121 6 6 Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into a flexible and powerful whole. 7 7 8 Trac has a built in small and powerful wiki rendering engine. This wiki engine implements an evergrowing subset of the commands from other popular Wikis, especially [http://moinmo.in/ MoinMoin] and [trac:WikiCreole].8 Trac has a built-in small and powerful wiki rendering engine. This wiki engine implements a growing subset of the commands from other popular Wikis, especially [http://moinmo.in/ MoinMoin] and [trac:WikiCreole]. 9 9 10 10 This page will give you an in-depth explanation of the wiki markup available anywhere WikiFormatting is allowed. … … 13 13 14 14 A few other wiki pages present the advanced features of the Trac wiki markup in more depth: 15 - TracLinks covers all the possible ways to refer precisely to any Trac resource or parts thereof 16 - WikiPageNames covers the various names a wiki page can take, CamelCase or not17 - WikiMacros lists the macros available for generating dynamic content 18 - WikiProcessors and WikiHtml details how parts of the wiki text can be processed in special ways 19 - [trac:wiki:TracDev/Proposals/AdvancedWikiOperations AdvancedWikiOperations] provides some operations in uncommon or administrative scenarios 15 - TracLinks covers all the possible ways to refer precisely to any Trac resource or parts thereof. 16 - WikiPageNames covers the various names a wiki page can take, whether in CamelCase or not. 17 - WikiMacros lists the macros available for generating dynamic content. 18 - WikiProcessors and WikiHtml details how parts of the wiki text can be processed in special ways. 19 - [trac:wiki:TracDev/Proposals/AdvancedWikiOperations AdvancedWikiOperations] provides some operations in uncommon or administrative scenarios. 20 20 21 21 == Common wiki markup … … 36 36 {{{#!td 37 37 {{{ 38 == Level 2 ==38 == Level 2 39 39 === Level 3 ^([#hn note])^ 40 40 }}} 41 41 }}} 42 42 {{{#!td style="padding-left: 2em" 43 == Level 2 ==43 == Level 2 44 44 === Level 3 ^([#hn note])^ 45 45 }}} … … 64 64 {{{#!td 65 65 {{{ 66 * bullet slist66 * bullet list 67 67 on multiple lines 68 68 1. nested list … … 72 72 }}} 73 73 {{{#!td 74 * bullet slist74 * bullet list 75 75 on multiple lines 76 76 1. nested list … … 288 288 * {{{ ! }}} 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. 289 289 * all the font styles marks have to be used in opening/closing pairs, 290 and they must nest properly (in particular, an `''` italic can't be paired291 with a `//` one, and `'''` can't be paired with `**` )290 and they must nest properly; in particular, an `''` italic can't be paired 291 with a `//` one, and `'''` can't be paired with `**`. 292 292 293 293 == Headings … … 296 296 297 297 [=#hn] 298 The headline text can be followed by the same number of "=" characters, but this is no longer mandatory.298 The headline text can be followed by the same number of "=" characters, but this is not mandatory. That is, `=== Section3 ===` is identical to `=== Section3`. 299 299 300 300 Finally, the heading might optionally be followed by an explicit id. If not, an implicit but nevertheless readable id will be generated. … … 469 469 == Discussion Citations 470 470 471 To delineate a citation in an ongoing discussion thread, such as the ticket comment area, e -mail-like citation marks (">", ">>", etc.) may be used.471 To delineate a citation in an ongoing discussion thread, such as the ticket comment area, email-like citation marks (">", ">>", etc.) may be used. 472 472 473 473 ||= Wiki Markup =||= Display =|| … … 581 581 === Complex Tables 582 582 583 If the possibilities offered by the simple "pipe"-based markup for tables described above are not enough for your needs, you can create more elaboratedtables by using [#Processors-example-tables WikiProcessor based tables].583 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 [#Processors-example-tables WikiProcessor based tables]. 584 584 585 585 == Links 586 586 587 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as {{{!WikiPageLink}}}.587 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark ('!'), such as {{{!WikiPageLink}}}. 588 588 589 589 ||= Wiki Markup =||= Display =|| … … 683 683 }}} 684 684 685 It 's also very close to the syntax for the corresponding link to that anchor:685 It is also very close to the syntax for the corresponding link to that anchor: 686 686 {{{ 687 687 [#point1] … … 712 712 }}} 713 713 714 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)^)]]`.714 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)^)]]`. 715 715 716 716 == Escaping Links, WikiPageNames and other Markup == #Escaping 717 717 718 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark).718 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single exclamation mark ('!'). 719 719 720 720 ||= Wiki Markup =||= Display =|| … … 942 942 Your comment for editors here 943 943 }}} 944 see ;-)944 see. 945 945 }}} 946 946 }}} … … 951 951 Your comment for editors here 952 952 }}} 953 see ;-)953 see. 954 954 }}} 955 955 956 956 == Miscellaneous 957 957 958 An horizontal line can be used to separated different parts of your page: 959 960 ||= Wiki Markup =||= Display =|| 961 {{{#!td 958 ||= Wiki Markup =||= Display =|| 959 {{{#!td 960 Horizontal line: 962 961 {{{ 963 962 Four or more dashes will be replaced 964 by a nhorizontal line (<HR>)963 by a horizontal line (<HR>) 965 964 ---- 966 965 See? … … 969 968 {{{#!td 970 969 Four or more dashes will be replaced 971 by a nhorizontal line (<HR>)970 by a horizontal line (<HR>) 972 971 ---- 973 972 See? … … 975 974 |---------------------------------- 976 975 {{{#!td 977 {{{ 978 "macro" style [[br]] line break 979 }}} 980 }}} 981 {{{#!td 982 "macro" style [[br]] line break 976 Two examples of line breaks: 977 {{{ 978 "macro" style [[BR]] line break 979 }}} 980 or: 981 {{{ 982 !WikiCreole style \\ line\\break 983 }}} 984 }}} 985 {{{#!td 986 "macro" style [[BR]] line break 987 988 !WikiCreole style \\ line\\break 983 989 }}} 984 990 |---------------------------------- 985 {{{#!td986 {{{987 !WikiCreole style \\ line\\break988 }}}989 }}}990 {{{#!td991 !WikiCreole style \\ line\\break992 }}}