# Latest

**URL:** https://talk.commonmark.org/latest.md

[Latest](https://talk.commonmark.org/latest.md) · [Categories](https://talk.commonmark.org/categories.md) · [Tags](https://talk.commonmark.org/tags.md)

---

## [Welcome to CommonMark Discussion](https://talk.commonmark.org/t/welcome-to-commonmark-discussion/8)

<div class="topic-metadata">

**Author:** [@system](https://talk.commonmark.org/u/system)\
**Replies:** 0\
**Last updated:** [August 18, 2014, 7:54am UTC](https://talk.commonmark.org/t/welcome-to-commonmark-discussion/8 "2014-08-18T07:54:29Z")

</div>

Markdown is a plain text format for writing structured documents. CommonMark, is a strongly defined, highly compatible specification of Markdown, along with a suite of comprehensive tests to validate implementations. Th…

---

## [How to render HTML to Markdown?](https://talk.commonmark.org/t/how-to-render-html-to-markdown/4983)

<div class="topic-metadata">

**Author:** [@the\_arun](https://talk.commonmark.org/u/the_arun)\
**Replies:** 3\
**Last updated:** [September 28, 2026, 11:50am UTC](https://talk.commonmark.org/t/how-to-render-html-to-markdown/4983 "2026-09-28T11:50:18Z")

</div>

Using Commonmark java how to render html to markdown? I tried this example, but it is not rendering. @Slf4j class MarkdownTest { @Test void markdownTest() { String markdown = toMarkdown("\<b\> Hello World!\<…

---

## [Should fenced code blocks always remain visible as source?](https://talk.commonmark.org/t/should-fenced-code-blocks-always-remain-visible-as-source/9156)

<div class="topic-metadata">

**Author:** [@andrewvelez](https://talk.commonmark.org/u/andrewvelez)\
**Replies:** 0\
**Last updated:** [September 27, 2026, 6:03pm UTC](https://talk.commonmark.org/t/should-fenced-code-blocks-always-remain-visible-as-source/9156 "2026-09-27T18:03:19Z")

</div>

I started thinking about this after trying to save a Mermaid diagram from a GitHub README as an image. The diagram was written inside a fenced code block, but GitHub had replaced the source with the rendered diagram. Th…

---

## [Using link reference definitions as invisible structural markers — sound, or a bad idea?](https://talk.commonmark.org/t/using-link-reference-definitions-as-invisible-structural-markers-sound-or-a-bad-idea/9154)

<div class="topic-metadata">

**Author:** [@jones-kovai-co](https://talk.commonmark.org/u/jones-kovai-co)\
**Replies:** 0\
**Last updated:** [September 27, 2026, 6:02pm UTC](https://talk.commonmark.org/t/using-link-reference-definitions-as-invisible-structural-markers-sound-or-a-bad-idea/9154 "2026-09-27T18:02:53Z")

</div>

I’m designing the file format for a tool that round-trips rich documents to and from Markdown. Some blocks have no Markdown form (tabbed content, a few attribute-bearing containers), and I need to carry their structure i…

---

## [Transclusion or including sub-documents for reuse](https://talk.commonmark.org/t/transclusion-or-including-sub-documents-for-reuse/270)

<div class="topic-metadata">

**Author:** [@SvenDowideit](https://talk.commonmark.org/u/SvenDowideit)\
**Replies:** 20\
**Last updated:** [September 26, 2026, 9:27am UTC](https://talk.commonmark.org/t/transclusion-or-including-sub-documents-for-reuse/270 "2026-09-26T09:27:19Z")

</div>

Coming from Foswiki, and now working on Docker documentation in markdown, I stongly miss having built in transclusion. If there's any chance something basic can be included in Standrd Markdown - ala http://fletcher.git…

---

## [Code fences in list items](https://talk.commonmark.org/t/code-fences-in-list-items/9143)

<div class="topic-metadata">

**Author:** [@brainchild](https://talk.commonmark.org/u/brainchild)\
**Replies:** 2\
**Last updated:** [September 18, 2026, 11:55pm UTC](https://talk.commonmark.org/t/code-fences-in-list-items/9143 "2026-09-18T23:55:15Z")

</div>

I have been struggling with code blocks within list items. The combination may seem most natural to represent as in the following: - One \`\`\` foo \`\`\` ​ - Two ​ \`\`\` bar \`\`\` Indeed, it appears with most re…

---

## [Hongdown: A CommonMark formatter with highly opinionated styles](https://talk.commonmark.org/t/hongdown-a-commonmark-formatter-with-highly-opinionated-styles/8986)

<div class="topic-metadata">

**Author:** [@hongminhee](https://talk.commonmark.org/u/hongminhee)\
**Replies:** 3\
**Last updated:** [September 15, 2026, 9:17pm UTC](https://talk.commonmark.org/t/hongdown-a-commonmark-formatter-with-highly-opinionated-styles/8986 "2026-09-15T21:17:31Z")

</div>

I’m sharing Hongdown, a CommonMark formatter I built to solve a specific problem: existing formatters didn’t support the style conventions I needed. Background I initially tried using markdownlint with custom rules, bu…

---

## [Let table rows wrap over several lines](https://talk.commonmark.org/t/let-table-rows-wrap-over-several-lines/9133)

<div class="topic-metadata">

**Author:** [@alberti42](https://talk.commonmark.org/u/alberti42)\
**Replies:** 5\
**Last updated:** [September 14, 2026, 12:43pm UTC](https://talk.commonmark.org/t/let-table-rows-wrap-over-several-lines/9133 "2026-09-14T12:43:08Z")

</div>

Motivation This proposal is about making Markdown pipe tables legible without requiring special renderers – even when these tables provide rich information. For the motivation, I would like to start off with a premise, …

---

## [Making Markdown a first-class citizen of the Web](https://talk.commonmark.org/t/making-markdown-a-first-class-citizen-of-the-web/9132)

<div class="topic-metadata">

**Author:** [@Crissov](https://talk.commonmark.org/u/Crissov)\
**Replies:** 7\
**Last updated:** [September 14, 2026, 12:08pm UTC](https://talk.commonmark.org/t/making-markdown-a-first-class-citizen-of-the-web/9132 "2026-09-14T12:08:56Z")

</div>

Markdown (often as Commonmark) is very often used on the Web for user input of both short and long texts, e.g. articles and comments. However, in order to assist their users, site authors need to implement any further su…

---

## [Image tag should expand to figure when used with title](https://talk.commonmark.org/t/image-tag-should-expand-to-figure-when-used-with-title/265)

<div class="topic-metadata">

**Author:** [@halfdan](https://talk.commonmark.org/u/halfdan)\
**Replies:** 12\
**Last updated:** [September 10, 2026, 5:40pm UTC](https://talk.commonmark.org/t/image-tag-should-expand-to-figure-when-used-with-title/265 "2026-09-10T17:40:35Z")

</div>

With the syntax for images supporting titles in http://jgm.github.io/stmd/spec.html#images it would be great if the image tag would expand to a figure with caption like: !\[alt text\](/url "my caption") \<figure\> \<im…

---

## [MD Studio - a personal HTML-to-Markdown project](https://talk.commonmark.org/t/md-studio-a-personal-html-to-markdown-project/9130)

<div class="topic-metadata">

**Author:** [@marc](https://talk.commonmark.org/u/marc)\
**Replies:** 0\
**Last updated:** [September 5, 2026, 1:09pm UTC](https://talk.commonmark.org/t/md-studio-a-personal-html-to-markdown-project/9130 "2026-09-05T13:09:48Z")

</div>

Hi Everyone, First time poster here, so please point me in the right direction if this is not the appropriate category to post in. I’ve built a small browser-based HTML-to-Markdown converter and editor: It started a…

---

## [Interesting trend of executable markdown readme projects (Syntax comparison)](https://talk.commonmark.org/t/interesting-trend-of-executable-markdown-readme-projects-syntax-comparison/4577)

<div class="topic-metadata">

**Author:** [@mofosyne](https://talk.commonmark.org/u/mofosyne)\
**Replies:** 2\
**Last updated:** [August 28, 2026, 4:48pm UTC](https://talk.commonmark.org/t/interesting-trend-of-executable-markdown-readme-projects-syntax-comparison/4577 "2026-08-28T16:48:38Z")

</div>

Just noticed there is a whole bunch of projects focusing on executable readmes. Can you remind me what’s the common consensus on attributes for code blocks? I think Runme has the closest form to what was discussed rega…

---

## [Three things I decided not to parse, building a live-preview editor](https://talk.commonmark.org/t/three-things-i-decided-not-to-parse-building-a-live-preview-editor/9126)

<div class="topic-metadata">

**Author:** [@sth\_wicked](https://talk.commonmark.org/u/sth_wicked)\
**Replies:** 3\
**Last updated:** [August 27, 2026, 9:06am UTC](https://talk.commonmark.org/t/three-things-i-decided-not-to-parse-building-a-live-preview-editor/9126 "2026-08-27T09:06:29Z")

</div>

I’m building a Markdown notes app for the Mac (Margin) where the file on disk stays plain Markdown, so I’ll disclose that up front and you can discount accordingly. The editor is CodeMirror 6 on \`@lezer/markdown\` with a…

---

## [Semantic block for Poetry/Lyrics with optical alignment (the "longest line" rule)](https://talk.commonmark.org/t/semantic-block-for-poetry-lyrics-with-optical-alignment-the-longest-line-rule/9091)

<div class="topic-metadata">

**Author:** [@Beppe](https://talk.commonmark.org/u/Beppe)\
**Replies:** 8\
**Last updated:** [August 24, 2026, 4:34pm UTC](https://talk.commonmark.org/t/semantic-block-for-poetry-lyrics-with-optical-alignment-the-longest-line-rule/9091 "2026-08-24T16:34:36Z")

</div>

A block for poems and lyrics? Hey all, I’ve been writing a bit of poetry and some song lyrics in Markdown lately, and I keep running into the same annoyance, so I wanted to throw an idea out there and see what people th…

---

## [A list of common mistakes that people make while writing Markdown](https://talk.commonmark.org/t/a-list-of-common-mistakes-that-people-make-while-writing-markdown/9120)

<div class="topic-metadata">

**Author:** [@notriddle](https://talk.commonmark.org/u/notriddle)\
**Replies:** 0\
**Last updated:** [August 20, 2026, 11:45pm UTC](https://talk.commonmark.org/t/a-list-of-common-mistakes-that-people-make-while-writing-markdown/9120 "2026-08-20T23:45:15Z")

</div>

Continuing the discussion from Djot: A light markup language by @jgm, knowingly acting out xkcd 386 “Duty Calls”: I think the members of this forum spend too much time talking about power-user features like ease-of-impl…

---

## [Djot: A light markup language by @jgm](https://talk.commonmark.org/t/djot-a-light-markup-language-by-jgm/4229)

<div class="topic-metadata">

**Author:** [@vas](https://talk.commonmark.org/u/vas)\
**Replies:** 22\
**Last updated:** [August 19, 2026, 12:07pm UTC](https://talk.commonmark.org/t/djot-a-light-markup-language-by-jgm/4229 "2026-08-19T12:07:51Z")

</div>

Continuing the discussion from Beyond Markdown because I think @jgm’s jdot deserves its own forum topic. Link to a Playground created by @dtinth: https://djot-playground-poc.vercel.app

---

## [Beyond Markdown](https://talk.commonmark.org/t/beyond-markdown/2787)

<div class="topic-metadata">

**Author:** [@jgm](https://talk.commonmark.org/u/jgm)\
**Replies:** 63\
**Last updated:** [August 19, 2026, 11:22am UTC](https://talk.commonmark.org/t/beyond-markdown/2787 "2026-08-19T11:22:28Z")

</div>

Beyond Markdown In developing Commonmark, we have tried, as far as possible, to remain faithful to John Gruber’s original Markdown syntax description. We have diverged from it only occasionally, in the interest of removi…

---

## [Would a streaming guidance for CommonMark be useful?](https://talk.commonmark.org/t/would-a-streaming-guidance-for-commonmark-be-useful/9115)

<div class="topic-metadata">

**Author:** [@cjccjj](https://talk.commonmark.org/u/cjccjj)\
**Replies:** 0\
**Last updated:** [August 18, 2026, 7:20am UTC](https://talk.commonmark.org/t/would-a-streaming-guidance-for-commonmark-be-useful/9115 "2026-08-18T07:20:16Z")

</div>

As Markdown increasingly arrives live as a stream in chat apps, terminals, coding agents, and other interfaces, full-document Markdown parsing has become a performance bottleneck, causing CPU spikes and UI lag. Many UIs …

---

## [A (somewhat) formally verified implementation of Markdown](https://talk.commonmark.org/t/a-somewhat-formally-verified-implementation-of-markdown/9108)

<div class="topic-metadata">

**Author:** [@paulbutcher](https://talk.commonmark.org/u/paulbutcher)\
**Replies:** 0\
**Last updated:** [August 8, 2026, 7:47am UTC](https://talk.commonmark.org/t/a-somewhat-formally-verified-implementation-of-markdown/9108 "2026-08-08T07:47:17Z")

</div>

I’d like to announce lean-markdown a Lean implementation of both CommonMark and GitHub Flavored Markdown (GFM). A (somewhat) formally verified implementation of Markdown Guarantees Conformant: passes every test in the…

---

## [Illegal HTML from Autolinks in Link Text](https://talk.commonmark.org/t/illegal-html-from-autolinks-in-link-text/9092)

<div class="topic-metadata">

**Author:** [@pugmire](https://talk.commonmark.org/u/pugmire)\
**Replies:** 3\
**Last updated:** [July 28, 2026, 1:15pm UTC](https://talk.commonmark.org/t/illegal-html-from-autolinks-in-link-text/9092 "2026-07-28T13:15:40Z")

</div>

\[\<https://domain1.example.com\>\](https://domain2.example.com) The above renders to illegal HTML containing nested a elements: \<p\>\<a href="https://domain2.example.com"\>\<a href="https://domain1.example.com"\>https://domain…

---

## [Interoperable markers for automatic heading numbers](https://talk.commonmark.org/t/interoperable-markers-for-automatic-heading-numbers/9096)

<div class="topic-metadata">

**Author:** [@wintifrosch](https://talk.commonmark.org/u/wintifrosch)\
**Replies:** 1\
**Last updated:** [July 27, 2026, 2:07pm UTC](https://talk.commonmark.org/t/interoperable-markers-for-automatic-heading-numbers/9096 "2026-07-27T14:07:01Z")

</div>

Can Markdown editors agree on an interoperable convention for identifying persisted, automatically managed heading-number prefixes? Consider a document containing: # 1. Introduction ## 1.1 Background ## 1.2 Scope Some…

---

## [Bad Interaction Between Laziness Rule and Ordered Lists](https://talk.commonmark.org/t/bad-interaction-between-laziness-rule-and-ordered-lists/9085)

<div class="topic-metadata">

**Author:** [@pugmire](https://talk.commonmark.org/u/pugmire)\
**Replies:** 1\
**Last updated:** [July 10, 2026, 9:14am UTC](https://talk.commonmark.org/t/bad-interaction-between-laziness-rule-and-ordered-lists/9085 "2026-07-10T09:14:54Z")

</div>

I believe I have found an issue with the specification. In particular, the laziness rule for list items, combined with the details about when lists can interrupt paragraphs, together imply an undesirable treatment of ord…

---

## [Shall CommonMark inline inside HTML5 render as CommonMark? If not, why not?](https://talk.commonmark.org/t/shall-commonmark-inline-inside-html5-render-as-commonmark-if-not-why-not/8964)

<div class="topic-metadata">

**Author:** [@rokejulianlockhart](https://talk.commonmark.org/u/rokejulianlockhart)\
**Replies:** 1\
**Last updated:** [June 26, 2026, 12:54pm UTC](https://talk.commonmark.org/t/shall-commonmark-inline-inside-html5-render-as-commonmark-if-not-why-not/8964 "2026-06-26T12:54:12Z")

</div>

At github.com/MALSync/MALSync/issues/2092: …via the available “GitHub-Flavoured Markdown” markup syntax, I am able to utilise CommonMark inside a \<code\> tag, directly inline: 1. \<code\>\[por\](https://www.loc.gov/standa…

---

## [Lazy Continuation Lines in Multiline Setext Headings](https://talk.commonmark.org/t/lazy-continuation-lines-in-multiline-setext-headings/9087)

<div class="topic-metadata">

**Author:** [@pugmire](https://talk.commonmark.org/u/pugmire)\
**Replies:** 0\
**Last updated:** [June 24, 2026, 5:29am UTC](https://talk.commonmark.org/t/lazy-continuation-lines-in-multiline-setext-headings/9087 "2026-06-24T05:29:03Z")

</div>

I’ve found a small disagreement between the spec and commonmark.js. commonmark.js identifies the following as a setext heading within a list item: 1. Foo Bar ==== The spec defines lazy continuation lines such that …

---

## [Precedence of link title over code span](https://talk.commonmark.org/t/precedence-of-link-title-over-code-span/8982)

<div class="topic-metadata">

**Author:** [@taro137](https://talk.commonmark.org/u/taro137)\
**Replies:** 2\
**Last updated:** [June 22, 2026, 3:47pm UTC](https://talk.commonmark.org/t/precedence-of-link-title-over-code-span/8982 "2026-06-22T15:47:56Z")

</div>

In the definition of code spans in the latest 0.31.2 spec, it states: Code span backticks have higher precedence than any other inline constructs except HTML tags and autolinks. However, \[foo\](/ "bar\`baz")\` is tre…

---

## [Standardize listing of Markdown Flavors used in the MD document: GLFM, GFM, QMD, etc](https://talk.commonmark.org/t/standardize-listing-of-markdown-flavors-used-in-the-md-document-glfm-gfm-qmd-etc/9064)

<div class="topic-metadata">

**Author:** [@murz](https://talk.commonmark.org/u/murz)\
**Replies:** 4\
**Last updated:** [May 24, 2026, 4:55pm UTC](https://talk.commonmark.org/t/standardize-listing-of-markdown-flavors-used-in-the-md-document-glfm-gfm-qmd-etc/9064 "2026-05-24T16:55:33Z")

</div>

Standardizing a single common Markdown syntax seems like an impossible challenge! So, now we already have a lot of different popular “flavors” for Markdown syntax: CommonMark, GitLab Flavored Markdown (GLFM), GitHub Fla…

---

## [When the info string already starts with \`language-\`, do not add the \`language-\` prefix](https://talk.commonmark.org/t/when-the-info-string-already-starts-with-language-do-not-add-the-language-prefix/9054)

<div class="topic-metadata">

**Author:** [@znewt99](https://talk.commonmark.org/u/znewt99)\
**Replies:** 2\
**Last updated:** [May 23, 2026, 6:38pm UTC](https://talk.commonmark.org/t/when-the-info-string-already-starts-with-language-do-not-add-the-language-prefix/9054 "2026-05-23T18:38:26Z")

</div>

Should a change be made to the spec, so the behavior of cmark & commonmark.js matches the spec? For context, see commonmark.js issue #277 Here’s what the spec currently says: Although this spec doesn’t mandate any pa…

---

## [Support syntax highlighting for two languages in a small number of cases](https://talk.commonmark.org/t/support-syntax-highlighting-for-two-languages-in-a-small-number-of-cases/4903)

<div class="topic-metadata">

**Author:** [@sedyh](https://talk.commonmark.org/u/sedyh)\
**Replies:** 1\
**Last updated:** [May 22, 2026, 4:32pm UTC](https://talk.commonmark.org/t/support-syntax-highlighting-for-two-languages-in-a-small-number-of-cases/4903 "2026-05-22T16:32:26Z")

</div>

Hello. I’ve encountered that it can be very useful to enable simultaneous syntax highlighting for some exceptional cases. However, we are not talking about complex scenarios like nested language constructs, but about sho…

---

## [Fenced code blocks should add class to \`code\` rather than \`pre\`, matching the HTML best practice](https://talk.commonmark.org/t/fenced-code-blocks-should-add-class-to-code-rather-than-pre-matching-the-html-best-practice/136)

<div class="topic-metadata">

**Author:** [@mathias](https://talk.commonmark.org/u/mathias)\
**Replies:** 7\
**Last updated:** [May 22, 2026, 4:26pm UTC](https://talk.commonmark.org/t/fenced-code-blocks-should-add-class-to-code-rather-than-pre-matching-the-html-best-practice/136 "2026-05-22T16:26:54Z")

</div>

The spec currently says: An info string can be provided after the opening code fence. Opening and closing spaces will be stripped, and the first word is used here to populate the class attribute of the enclosing pre ta…

---

## [Adding internationalization (translation) support to the spec](https://talk.commonmark.org/t/adding-internationalization-translation-support-to-the-spec/9066)

<div class="topic-metadata">

**Author:** [@gemmaro](https://talk.commonmark.org/u/gemmaro)\
**Replies:** 0\
**Last updated:** [May 22, 2026, 2:58pm UTC](https://talk.commonmark.org/t/adding-internationalization-translation-support-to-the-spec/9066 "2026-05-22T14:58:07Z")

</div>

Hello, I have set up a workflow for translating the CommonMark specification into Japanese in my personal repository. The steps are described in the README. Before going further, I’d like to raise a few questions and …

[Next page](https://talk.commonmark.org/latest.md?page=1)
