Changes between Version 1 and Version 2 of WikiFormatting
- Timestamp:
- Apr 30, 2019 4:37:54 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiFormatting
v1 v2 1 = WikiFormatting = 1 = WikiFormatting 2 2 3 [[TracGuideToc]] 3 4 4 5 Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into a flexible and powerful whole. 5 6 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://moinmo.in/ MoinMoin] and [trac:WikiCreole]. 8 7 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 8 10 9 This page will give you an in-depth explanation of the wiki markup available anywhere WikiFormatting is allowed. 11 10 12 The ''Cheat sheet'' below gives you a quickoverview for the most common syntax, each link in the ''Category'' column will lead you to the more detailed explanation later in this page.11 The sections below provide an overview for the most common syntax, each link in the ''Category'' column will lead you to the more detailed explanation later in this page. 13 12 14 13 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 talks about 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 20 21 == C heat sheet ==14 - TracLinks covers all the possible ways to refer precisely to any Trac resource or parts thereof. 15 - WikiPageNames covers the various names a wiki page can take, whether in CamelCase or not. 16 - WikiMacros lists the macros available for generating dynamic content. 17 - WikiProcessors and WikiHtml details how parts of the wiki text can be processed in special ways. 18 - [trac:wiki:TracDev/Proposals/AdvancedWikiOperations AdvancedWikiOperations] provides some operations in uncommon or administrative scenarios. 19 20 == Common wiki markup 22 21 23 22 ||= '''Category''' =||= '''Wiki Markup''' =||= '''Display''' =|| … … 28 27 || `'''bold'''`, `''italic''`, `'''''Wikipedia style'''''` || \ 29 28 || '''bold''', ''italic'', '''''Wikipedia style''''' || 30 || {{{`monospaced and ''nowiki''`}}} || \31 || `monospaced and ''nowiki''` ||29 || {{{`monospaced (''other markup ignored'')`}}} || \ 30 || `monospaced (''other markup ignored'')` || 32 31 || `**bold**`, `//italic//`, `**//!WikiCreole style//**` || \ 33 32 || **bold**, //italic//, **//!WikiCreole style//** || … … 36 35 {{{#!td 37 36 {{{ 38 == Level 2 ==37 == Level 2 39 38 === Level 3 ^([#hn note])^ 40 39 }}} … … 64 63 {{{#!td 65 64 {{{ 66 * bullet slist67 on multiple paragraphs65 * bullet list 66 on multiple lines 68 67 1. nested list 69 68 a. different numbering … … 72 71 }}} 73 72 {{{#!td 74 * bullet slist75 on multiple paragraphs73 * bullet list 74 on multiple lines 76 75 1. nested list 77 76 a. different numbering … … 85 84 {{{ 86 85 term:: definition on 87 multiple paragraphs86 multiple lines 88 87 }}} 89 88 }}} 90 89 {{{#!td 91 90 term:: definition on 92 multiple paragraphs91 multiple lines 93 92 }}} 94 93 |----------------------------------------------------------- … … 175 174 || see [#point1 (1)] || 176 175 |----------------------------------------------------------- 177 {{{#!th rowspan= 2178 [#Escaping LinksandWikiPageNamesEscaping Markup]176 {{{#!th rowspan=3 177 [#Escaping Escaping Markup] 179 178 }}} 180 179 || `!'' doubled quotes` ||\ … … 182 181 || `!wiki:WikiFormatting`, `!WikiFormatting` ||\ 183 182 || !wiki:WikiFormatting, !WikiFormatting || 183 || [[html(<code>`{{{-}}}` triple curly brackets</code>)]] ||\ 184 || `{{{-}}}` triple curly brackets || 184 185 |----------------------------------------------------------- 185 186 ||= [#Images Images] =|| `[[Image(`''link''`)]]` || [[Image(htdocs:../common/trac_logo_mini.png)]] || … … 241 242 }}} 242 243 243 244 == Font Styles == 244 == Font Styles 245 245 246 246 The Trac wiki supports the following font styles: … … 262 262 * **also bold**, //italic as well//, 263 263 and **'' bold italic **'' //(since 0.12)// 264 * [[span(style=color: #FF0000, a red text )]] 264 265 }}} 265 266 }}} … … 279 280 * **also bold**, //italic as well//, 280 281 and **'' bold italic **'' //(since 0.12)// 282 * [[span(style=color: #FF0000, a red text )]] 281 283 }}} 282 284 … … 285 287 * {{{ ! }}} 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. 286 288 * all the font styles marks have to be used in opening/closing pairs, 287 and they must nest properly (in particular, an `''` italic can't be paired 288 with a `//` one, and `'''` can't be paired with `**`) 289 290 291 == Headings == 292 293 You can create heading by starting a line with one up to six ''equal'' characters ("=") 294 followed by a single space and the headline text. 289 and they must nest properly; in particular, an `''` italic can't be paired 290 with a `//` one, and `'''` can't be paired with `**`. 291 292 == Headings 293 294 You can create heading by starting a line with one up to six ''equal'' characters ("=") followed by a single space and the headline text. 295 295 296 296 [=#hn] 297 The headline text can be followed by the same number of "=" characters, but this is no longer mandatory.297 The headline text can be followed by the same number of "=" characters, but this is not mandatory. That is, `=== Section3 ===` is identical to `=== Section3`. 298 298 299 299 Finally, the heading might optionally be followed by an explicit id. If not, an implicit but nevertheless readable id will be generated. … … 312 312 {{{ 313 313 #!div 314 = Heading = 314 315 == Subheading 315 316 === About ''this'' === … … 319 320 }}} 320 321 321 == Paragraphs ==322 == Paragraphs 322 323 323 324 A new text paragraph is created whenever two blocks of text are separated by one or more empty lines. … … 347 348 }}} 348 349 349 == Lists ==350 == Lists 350 351 351 352 The wiki supports both ordered/numbered and unordered lists. … … 403 404 }}} 404 405 405 406 == Definition Lists == 406 == Definition Lists 407 407 408 408 The wiki also supports definition lists. … … 428 428 Note that you need a space in front of the defined term. 429 429 430 431 == Preformatted Text == 430 == Preformatted Text 432 431 433 432 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. … … 451 450 Note that this kind of block is also used for selecting lines that should be processed through WikiProcessors. 452 451 453 == Blockquotes ==452 == Blockquotes 454 453 455 454 In order to mark a paragraph as blockquote, indent that paragraph with two spaces. … … 467 466 }}} 468 467 469 == Discussion Citations ==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.468 == Discussion Citations 469 470 To delineate a citation in an ongoing discussion thread, such as the ticket comment area, email-like citation marks (">", ">>", etc.) may be used. 472 471 473 472 ||= Wiki Markup =||= Display =|| … … 487 486 }}} 488 487 489 490 == Tables ==491 === Simple Tables === 488 == Tables 489 === Simple Tables 490 492 491 Simple tables can be created like this: 493 492 ||= Wiki Markup =||= Display =|| … … 579 578 }}} 580 579 581 === Complex Tables === 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 elaborated tables by using [#Processors-example-tables WikiProcessor based tables]. 584 585 586 == Links == 587 588 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as {{{!WikiPageLink}}}. 580 === Complex Tables 581 582 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]. 583 584 == Links 585 586 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark ('!'), such as {{{!WikiPageLink}}}. 589 587 590 588 ||= Wiki Markup =||= Display =|| … … 638 636 }}} 639 637 640 '''Note''': the [trac:WikiCreole] style for links is quick to type and 641 certainly looks familiar as it's the one used on Wikipedia and in many 642 other wikis. Unfortunately it conflicts with the syntax for [#Macros macros]. 643 So in the rare case when you need to refer to a page which is named after 644 a macro (typical examples being TitleIndex, InterTrac and InterWiki), 645 by writing `[[TitleIndex]]` you will actually call the macro instead of linking 646 to the page. 647 648 == Trac Links == 638 '''Note''': the [trac:WikiCreole] style for links is quick to type and certainly looks familiar as it is the one used on Wikipedia and in many other wikis. Unfortunately it conflicts with the syntax for [#Macros macros]. 639 So in the rare case when you need to refer to a page which is named after a macro (typical examples being TitleIndex, InterTrac and InterWiki), by writing `[[TitleIndex]]` you will actually call the macro instead of linking to the page. 640 641 == Trac Links 649 642 650 643 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: … … 676 669 There are many more flavors of Trac links, see TracLinks for more in-depth information and a reference for all the default link resolvers. 677 670 678 679 == Setting Anchors == 671 == Setting Anchors 680 672 681 673 An anchor, or more correctly speaking, an [http://www.w3.org/TR/REC-html40/struct/links.html#h-12.2.1 anchor name] can be added explicitly at any place in the Wiki page, in order to uniquely identify a position in the document: … … 690 682 }}} 691 683 692 It 's also very close to the syntax for the corresponding link to that anchor:684 It is also very close to the syntax for the corresponding link to that anchor: 693 685 {{{ 694 686 [#point1] … … 719 711 }}} 720 712 721 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)^)]]`. 722 723 724 == Escaping Links and WikiPageNames == 725 726 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark). 713 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)^)]]`. 714 715 == Escaping Links, WikiPageNames and other Markup == #Escaping 716 717 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single exclamation mark ('!'). 727 718 728 719 ||= Wiki Markup =||= Display =|| … … 732 723 !#42 is not a link 733 724 }}} 725 {{{ 726 Various forms of escaping for list markup: 727 ^^- escaped minus sign \\ 728 ^^1. escaped number \\ 729 ^^* escaped asterisk sign 730 }}} 734 731 }}} 735 732 {{{#!td 736 733 !NoHyperLink 737 734 !#42 is not a link 738 }}} 739 740 == Images == 735 736 Various forms of escaping for list markup: 737 ^^- escaped minus sign \\ 738 ^^1. escaped number \\ 739 ^^* escaped asterisk sign 740 }}} 741 742 == Images 741 743 742 744 Urls ending with `.png`, `.gif` or `.jpg` are no longer automatically interpreted as image links, and converted to `<img>` tags. … … 762 764 See WikiMacros for further documentation on the `[[Image()]]` macro, which has several useful options (`title=`, `link=`, etc.) 763 765 764 765 == Macros == 766 == Macros 766 767 767 768 Macros are ''custom functions'' to insert dynamic content in a page. … … 791 792 }}} 792 793 793 794 == Processors == 794 == Processors 795 795 796 796 Trac supports alternative markup formats using WikiProcessors. For example, processors are used to write pages in … … 929 929 See WikiProcessors for more information. 930 930 931 932 == Comments == 931 == Comments 933 932 934 933 Comments can be added to the plain text. These will not be rendered and will not display in any other format than plain text. … … 942 941 Your comment for editors here 943 942 }}} 944 see ;-)943 see. 945 944 }}} 946 945 }}} … … 951 950 Your comment for editors here 952 951 }}} 953 see ;-) 954 }}} 955 956 == Miscellaneous == 957 958 An horizontal line can be used to separated different parts of your page: 959 960 ||= Wiki Markup =||= Display =|| 961 {{{#!td 952 see. 953 }}} 954 955 == Miscellaneous 956 957 ||= Wiki Markup =||= Display =|| 958 {{{#!td 959 Horizontal line: 962 960 {{{ 963 961 Four or more dashes will be replaced 964 by a nhorizontal line (<HR>)962 by a horizontal line (<HR>) 965 963 ---- 966 964 See? … … 969 967 {{{#!td 970 968 Four or more dashes will be replaced 971 by a nhorizontal line (<HR>)969 by a horizontal line (<HR>) 972 970 ---- 973 971 See? … … 975 973 |---------------------------------- 976 974 {{{#!td 977 {{{ 978 "macro" style [[br]] line break 979 }}} 980 }}} 981 {{{#!td 982 "macro" style [[br]] line break 975 Two examples of line breaks: 976 {{{ 977 "macro" style [[BR]] line break 978 }}} 979 or: 980 {{{ 981 !WikiCreole style \\ line\\break 982 }}} 983 }}} 984 {{{#!td 985 "macro" style [[BR]] line break 986 987 !WikiCreole style \\ line\\break 983 988 }}} 984 989 |---------------------------------- 985 {{{#!td986 {{{987 !WikiCreole style \\ line\\break988 }}}989 }}}990 {{{#!td991 !WikiCreole style \\ line\\break992 }}}993
