Edgewall Software

Changes between Version 120 and Version 121 of WikiFormatting


Ignore:
Timestamp:
Dec 8, 2015, 11:31:41 AM (8 years ago)
Author:
figaro
Comment:

Further cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • WikiFormatting

    v120 v121  
    66Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into a flexible and powerful whole.
    77
    8 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://moinmo.in/ MoinMoin] and [trac:WikiCreole].
     8Trac 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].
    99
    1010This page will give you an in-depth explanation of the wiki markup available anywhere WikiFormatting is allowed.
    … …  
    1313
    1414A 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 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
     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.
    2020
    2121== Common wiki markup
    … …  
    3636{{{#!td
    3737 {{{
    38  == Level 2 ==
     38 == Level 2
    3939 === Level 3 ^([#hn note])^
    4040 }}}
    4141}}}
    4242{{{#!td style="padding-left: 2em"
    43 == Level 2 ==
     43== Level 2
    4444=== Level 3 ^([#hn note])^
    4545}}}
    … …  
    6464{{{#!td
    6565 {{{
    66  * bullets list
     66 * bullet list
    6767   on multiple lines
    6868   1. nested list
    … …  
    7272}}}
    7373{{{#!td
    74 * bullets list
     74* bullet list
    7575  on multiple lines
    7676  1. nested list
    … …  
    288288 * {{{ ! }}} 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.
    289289 * 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 paired
    291    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 `**`.
    292292
    293293== Headings
    … …  
    296296
    297297[=#hn]
    298 The headline text can be followed by the same number of "=" characters, but this is no longer mandatory.
     298The headline text can be followed by the same number of "=" characters, but this is not mandatory. That is, `=== Section3 ===` is identical to `=== Section3`.
    299299
    300300Finally, the heading might optionally be followed by an explicit id. If not, an implicit but nevertheless readable id will be generated.
    … …  
    469469== Discussion Citations
    470470
    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. 
     471To delineate a citation in an ongoing discussion thread, such as the ticket comment area, email-like citation marks (">", ">>", etc.) may be used. 
    472472
    473473||= Wiki Markup =||= Display =||
    … …  
    581581=== Complex Tables
    582582
    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 elaborated tables by using [#Processors-example-tables WikiProcessor based tables].
     583If 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].
    584584
    585585== Links
    586586
    587 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as {{{!WikiPageLink}}}.
     587Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark ('!'), such as {{{!WikiPageLink}}}.
    588588
    589589||= Wiki Markup =||= Display =||
    … …  
    683683}}}
    684684
    685 It's also very close to the syntax for the corresponding link to that anchor:
     685It is also very close to the syntax for the corresponding link to that anchor:
    686686{{{
    687687[#point1]
    … …  
    712712}}}
    713713
    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)^)]]`.
     714For 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)^)]]`.
    715715
    716716== Escaping Links, WikiPageNames and other Markup == #Escaping
    717717
    718 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark).
     718You may avoid making hyperlinks out of TracLinks by preceding an expression with a single exclamation mark ('!').
    719719
    720720||= Wiki Markup =||= Display =||
    … …  
    942942  Your comment for editors here
    943943  }}}
    944   see ;-)
     944  see.
    945945  }}}
    946946}}}
    … …  
    951951  Your comment for editors here
    952952  }}}
    953   see ;-)
     953  see.
    954954}}}
    955955
    956956== Miscellaneous
    957957
    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:
    962961  {{{
    963962  Four or more dashes will be replaced
    964   by an horizontal line (<HR>)
     963  by a horizontal line (<HR>)
    965964  ----
    966965  See?
    … …  
    969968{{{#!td
    970969Four or more dashes will be replaced
    971 by an horizontal line (<HR>)
     970by a horizontal line (<HR>)
    972971----
    973972See?
    … …  
    975974|----------------------------------
    976975{{{#!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
    983989}}}
    984990|----------------------------------
    985 {{{#!td
    986   {{{
    987   !WikiCreole style \\ line\\break
    988   }}}
    989 }}}
    990 {{{#!td
    991 !WikiCreole style \\ line\\break
    992 }}}