markdown support

[anonymous]

It'd be nice to see support for Markdown with SmartyPants support. Both are available as PHP libraries, so it shouldn't be difficult to include.

[eblot]

WikiRestructuredText is already available with Trac, which offers something similar to what Markdown seems to do.

Fancy formatting SmartyPants could be obtained with a customization of one of the already available plugins, such as EmoticonsPlugin or WikiGoodiesPlugin .

It is always possible to add such tools using the plugins architecture, but this cannot be part of the Trac core project. I really don't think it would be a good idea to add a PHP or PERL-written library to the Trac project which is itself written in Python ;-)

[anonymous]

It completely escaped me that Trac's written in Python, not PHP. My bad.

[anonymous]

Perhaps consider the python implementation of Markdown...

[anonymous]

Reopening this ticket, given the existence of a Python markdown module.

[anonymous]

Reopening this ticket, given the existence of a Python markdown module.

I love trac, but hate the wiki syntax - markdown support (well, and a proxy webdav view of the wiki) would make trac the ultimate über project and documentation tool from heaven.

See: http://www.trac-hacks.org/ticket/353#comment:4

Also, and note that markdown support is the #1 voted plugin request on trac-hacks.org - people (like me) badly want this: http://www.trac-hacks.org/wiki#VoteforaRequest-a-Hack

Smartypants would be pimp but not necessary.

[eblot]

Replying to anonymous:

Reopening this ticket, given the existence of a Python markdown module.

Also, and note that markdown support is the #1 voted plugin request on trac-hacks.org - people (like me) badly want this: http://www.trac-hacks.org/wiki#VoteforaRequest-a-Hack

Yes, this could be implemented as a plugin, so I would recommend to close this ticket as wontfix, as there are few chances that the wiki syntax changes at this point of the project, and Trac already supports two kinds of syntax.

[anonymous]

Well, but there's a difference between supporting markdown with a processing instruction, and supporting it properly _as_ wiki syntax.

I think the coolest plugin would simply have a look at the syntax and decide which wiki processor to use; the builtin trac processor or markdown, or something else better that someone thinks up in a year.

Wouldn't be hard, as there are definitive clues to use in each set of syntax. One could even provide an override in syntax or as a preference.

[cboos]

Replying to anonymous:

Reopening this ticket, given the existence of a Python markdown module.

... which means that a WikiProcessor plugin could be written in order to support that.

I think the coolest plugin would simply have a look at the syntax and decide which wiki processor to use; the builtin trac processor or markdown, or something else better that someone thinks up in a year.

That's #615.

[anonymous]

i can't afford to learn 20 different syntax languages for 20 different systems. i've got my cms setup with markdown. if i'm going to use trac, i'm going to want to configure it with markdown. i've already learned / memorized most of the markdown syntax. i don't want to have to break down and learn yet another syntax.

given that there's already a python implementation of markdown, for a python developer, it should be trivial to plug in support for markdown in addition to whatever existing syntaxes trac already supports.

i hope you now understand the reasons why markdown support is important, and why giving users a choice in markup syntax is important. i have an installation of trac setup but for all practical puproses i don't use it; because i'm handicapped by the syntax and refuse to learn yet another wiki syntax. multiply that by the size of the markdown community.

[cboos]

Please re-read comment:8. It is possible to write such a plugin, please do so or find someone to do it for you. We have already expressed that we're not interested in doing that as part of the core project.