[
https://issues.apache.org/jira/browse/DOXIA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118512#comment-15118512
]
Hervé Boutemy commented on DOXIA-521:
-------------------------------------
in fact, the question is to define "better" :)
for Kristian, better is "consistent with Doxia's XHTML Sink output" as coded
for verbatim() Doxia event in
http://maven.apache.org/doxia/doxia/doxia-core/xref/org/apache/maven/doxia/sink/XhtmlBaseSink.html#L1091
I understand that it's not how Pegdown renders html natively
If we change the way Doxia renders Xhtml, we'll need to document this (which is
clearly not easy to find currently), since this will have an impact on how to
write a Doxia Sitetools skin that integrates a highlighting lib
> 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)