[ https://issues.apache.org/jira/browse/DOXIA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy closed DOXIA-501. ------------------------------- Resolution: Duplicate Assignee: Hervé Boutemy Fix Version/s: MSITE-756 MSITE-728 I recently explained it in MSITE-728, with a workaround similar to the way Michael proposes it Yes, Markdown and Velocity don't play well together because they give a meaning to the same markup syntax: we can't do anything against it (changing Markdown or Velocity syntax is not an option) notice that I implemented MSITE-756 to help users investigate in case Velocity is used and was previously completely hidden: it makes Velocity result visible before Doxia parsing > Impossible to use ### header when also using Velocity > ----------------------------------------------------- > > Key: DOXIA-501 > URL: https://issues.apache.org/jira/browse/DOXIA-501 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Markdown > Affects Versions: 1.4 > Reporter: Hendrik Schreiber > Assignee: Hervé Boutemy > Labels: close-pending > Fix For: MSITE-728, MSITE-756 > > > Markdown and Velocity don't play nicely with each other. > A regular Markdown H3 is usually written like this: > ### My Header > This does not work with Velocity, because ## starts a comment. So, it needs > to be escaped like this: > \#\#\# My Header // DOES NOT WORK > Unfortunately, this does not work, but simply generates "###" in the output, > not a level 3 header. For some reason, Markdown does not interpret the "###". > There is a workaround posted on > http://mail-archives.apache.org/mod_mbox/maven-users/201303.mbox/%3c514afc2f.9070...@apache.org%3e > --- however, that is certainly not satisfying and very awkward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)