[
https://issues.apache.org/jira/browse/DOXIA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118557#comment-15118557
]
Hudson commented on DOXIA-521:
------------------------------
SUCCESS: Integrated in doxia-all #233 (See
[https://builds.apache.org/job/doxia-all/233/])
[DOXIA-521] fixed typo (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1726935])
*
./doxia/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownToDoxiaHtmlSerializer.java
[DOXIA-521] improved comment to define why Pegdown html output has to be
tweaked to match Doxia Xhtml Sink convention (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1726934])
*
./doxia/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownToDoxiaHtmlSerializer.java
> Markdown: Allow using the standard "<pre><code>" for code blocks
> ----------------------------------------------------------------
>
> Key: DOXIA-521
> URL: https://issues.apache.org/jira/browse/DOXIA-521
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Markdown
> Affects Versions: 1.6
> Reporter: Santiago M. Mola
>
> Pegdown, as well as other Markdown parsers, translates code blocks to
> <pre><code>. This is the standard as per the Markdown specifications and both
> themes and tools (e.g. http://highlightjs.org/) rely on this syntax.
> However, the doxia markdown module overrides this behaviour and uses "<div
> class="source"><pre>. It would be nice to revert the default behaviour to the
> standard. If there are use cases for such an alternative syntax, it could be
> provided as an option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)