[jira] [Comment Edited] (DOXIA-616) Markdown: Properly expose the language specified in fenced code blocks

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DOXIA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245923#comment-17245923 ] 

Michael Osipov edited comment on DOXIA-616 at 12/8/20, 2:39 PM:
----------------------------------------------------------------

It does. The first question is, does the code highligher we are using support this?


was (Author: michael-o):
It does. The first question is, does the code highligher we are using support ths?

> Markdown: Properly expose the language specified in fenced code blocks
> ----------------------------------------------------------------------
>
>                 Key: DOXIA-616
>                 URL: https://issues.apache.org/jira/browse/DOXIA-616
>             Project: Maven Doxia
>          Issue Type: Improvement
>          Components: Module - Markdown
>    Affects Versions: 1.8, 1.9, 1.9.1
>            Reporter: Bertrand Martin
>            Priority: Major
>
> h1. Use Case
> Writers can specify the language used in a fenced code block (typically for syntax highlighting), as in the example below:
> {code}
> ```java
> System.out.println("Beautiful\n");
> ```
> {code}
> Currently, the Doxia module for Markdown does not expose this information ("java") in the produced HTML, so a Maven skin (or frontend renderer) cannot leverage it.
> Produced HTML:
> {code:html}
> <div class="source"> <!-- No mention of Java :-( -->
> <pre>
> System.out.println("Beautiful\n");
> </pre>
> </div>
> {code}
> Wanted result:
> {code:html}
> <div class="source java"> <!-- :-) -->
> <pre>
> System.out.println("Beautiful\n");
> </pre>
> </div>
> {code}
> h1. Specification
> Un-comment this block:
> https://github.com/apache/maven-doxia/blob/c439714e8f4a9e86f9962ac6be9a0077ae9b4d30/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/FlexmarkDoxiaNodeRenderer.java#L103
> This should do the trick.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)