Edgewall Software
Home
Trac
Trac Hacks
Genshi
Babel
Bitten
Home
Download
Documentation
Mailing Lists
License
FAQ
Search:
Login
Preferences
Help/Guide
About Trac
Wiki
Timeline
Roadmap
Browse Source
View Tickets
New Ticket
Search
Context Navigation
-1
Start Page
Index
History
Editing TracDev/Proposals/AdvancedWikiFormatting
Adjust edit area height:
8
12
16
20
24
28
32
36
40
Edit side-by-side
[[PageOutline(2-3)]] = Trac Wiki Syntax enhancements = Note: all the syntax enhancements that went into [milestone:0.12] can be seen in [[.@25|version 25]] of this page. == Topics == === Tables === - add `|+` MediaWiki style caption or `#!caption` - support WikiCreole single pipe style (#6630) - also support MediaWiki style?? (#1424) === Definition lists === - nesting definition lists (#7721) - terms should automatically get an anchor, much like headings (but ''nice'' anchors, see [#Headings] below) === Lists === There are several enhancements that come to mind: - ''1)'' style numbered items and ''o'' style numbered items (see also #5498) ||= Wiki Markup =||= Display =|| {{{#!td {{{ o this is a list o that's another list 1) Point 1 2) Point 2 }}} }}} {{{#!td o this is a list o that's another list 1) Point 1 2) Point 2 }}} - support empty lines between items (#1936, #6482 and more specifically #8140) ||= Wiki Markup =||= Display =|| {{{#!td {{{ 1. start a list 1. continue in the same list }}} }}} {{{#!td 1. start a list 1. continue in the same list }}} - when continuing an item on the next line, one should stay within the item if we don't dedent past the item starter symbol (nearly works, but see #4848) - support for WikiCreole-style lists (gains compatibility with e.g. MediaWiki) ||= Wiki Markup =||= Display =|| {{{#!td {{{ * start a list ** subitem *** sub-subitem # ordered list ## numbered subitem }}} }}} {{{#!td * start a list ** subitem *** sub-subitem # ordered list ## numbered subitem }}} Notes: - issue #6482 is at work here, as the tables are not part of their corresponding item - slight difficulty for the VerticalHorizontalParsing, need to consider empty lines as potential "no-ops" in some situations. === Headings === The automatic ids generated for headings are not readable. We should replace spaces by hyphens, at the very least. Compatibility with the old compact style could be achieved by using the `name` attribute, whereas `id` would be used for the new, more readable style. This is especially important for languages when titles use sentence-style capitalization, not title-style capitalization (see e.g. [Wikipedia:Wikipedia:Manual_of_Style_(capital_letters)#Section_headings Section_headings] in Wikipedia). See #8645. === Enhanced processors === Allowing `{{{ div ...` would be easy, is it worth it? ''probably not, let's keep #! '' For div and tables, add some more "standard" classes (we already have "important" for divs and "listing" for tables): - see MoinMoin:HelpOnAdmonitions - another interesting possibility: [http://meta.wikimedia.org/wiki/Help:Collapsing#Collapsible_DIV collapsible and collapsed] (#9214) === TracLinks === ==== CamelCase ==== The MoinMoin style internal free link has been introduced to cope with wiki words with appended content, like when writing `["WikiProcessor"]s`. First, the implementation is restricted: it doesn't allow for a lhref equivalent, `["WikiProcessor" the wiki processors]` (#7695). What if we would instead re-use the lhref regexp, in the quoted case? It would be equivalent to making the ''wiki:'' prefix the default namespace. The advantage would be that ''any'' word could be wikified that way. - `["checking"]` -> ["checking"]: works already - `["checking" the check]` -> ["checking" the check]: doesn't work ==== Alternative forms of linking ==== #linking - shorthand for `[[Image(<img>)]]`: `{{<img>}}`, see MoinMoin:HelpOnLinking - `[=#anchor <label>]` creation, see #6413 **FIXME: document this in WikiFormatting** - shorthand for footnotes? see #9037 == Compatibility with other Wiki Markups == #Compatibility_with_other_Wiki_Markups While achieving universality is likely not possible, there are both many interesting ideas that could be grabbed from other Wiki markups and incompatibilities than could be eased out. Here are several other markups that are very interesting for us as they also target similar kinds of users that we do: - GoogleCode uses http://code.google.com/p/support/wiki/WikiSyntax [[br]] * Mostly compatible markup, with the notable exception of `*...*` and `_..._` used for bold and italics. This is ''not'' something we're going to support, considering all the complaints we already had with our underline style `__...__`. * Internal Wiki links are a bit easier to write: `[Wikipage]` instead of `["Wikipage"]` for us. * automatic heading anchors are more readable (`== Wiki-style markup ==` corresponds to `Wiki-style_markup` instead of `Wiki-stylemarkup`) (#8645) - BitBucket uses http://www.wikicreole.org/wiki/Creole1.0 [[br]] * See WikiCreole. - RedMine uses http://www.redmine.org/help/wiki_syntax_detailed.html based on http://hobix.com/textile [[br]] * also uses `*...*` and `_..._` used for bold and italics... * syntax for bulleted lists is similar to the WikiCreole one - MoinMoin, the original model for the Trac wiki syntax has since its version 1.6.0 increased its compatibility with WikiCreole: - `[[...]]` links and `{{...}}` for embedding, see MoinMoin:HelpOnLinking - `<<...>>` macro calls, see MoinMoin:HelpOnMacros - [http://daringfireball.net/projects/markdown/syntax Markdown] is used in a number of developer oriented sites (e.g. [http://stackoverflow.com/editing-help StackOverflow], [http://gitorious.org/gitorious/mainline/blobs/master/lib/markup_renderer.rb Gitorious wiki], [http://github.github.com/github-flavored-markdown/ GitHub Flavored Markdown]). Some of the interesting parts: - [http://daringfireball.net/projects/markdown/syntax#header headings by underlining] (similar to reStructuredText, but limited to `========` and `--------`) - the [http://daringfireball.net/projects/markdown/syntax#list rules for list items] are quite interesting as well (how to deal with empty lines and paragraphs within lists) - others?
Note:
See
WikiFormatting
and
TracWiki
for help on editing wiki content.
Change information
Your email or username:
E-mail address and name can be saved in the
Preferences
Comment about this change (optional):
Note:
See
TracWiki
for help on using the wiki.