You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/11/25 11:24:00 UTC

[jira] [Resolved] (DOXIA-763) MarkdownSink: Distinguish between verbatim with source attribute and without

     [ https://issues.apache.org/jira/browse/DOXIA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved DOXIA-763.
-----------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/maven-doxia/commit/ac99291a53152e5f8863c29417c914170de2caa9.

> MarkdownSink: Distinguish between verbatim with source attribute and without
> ----------------------------------------------------------------------------
>
>                 Key: DOXIA-763
>                 URL: https://issues.apache.org/jira/browse/DOXIA-763
>             Project: Maven Doxia
>          Issue Type: Bug
>          Components: Module - Markdown
>    Affects Versions: 2.0.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 2.1.0
>
>
> Currently both lead to [fenced code blocks without info string|https://spec.commonmark.org/0.31.2/#fenced-code-blocks] however the MarkdownParser emits fenced code blocks without info string with the special classes {{nocode nohighlight}} (https://github.com/apache/maven-doxia/blob/c36b51695bdf4fe6f515d7e3fcdcec264867d990/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownParser.java#L152) which basically makes it just a verbatim block. In order to emit without those classes one has to provide an info string (usually the programming language of the following block). As the language is not provided in Sink API one should instead rely on a hardcoded info string {{unknown}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)