# A proposal to support the \<mark\> tag with Markdown

**URL:** <https://talk.commonmark.org/t/a-proposal-to-support-the-mark-tag-with-markdown/1981>\
**Category:** Extensions\
**Created:** [January 11, 2016, 10:11pm UTC](https://talk.commonmark.org/t/a-proposal-to-support-the-mark-tag-with-markdown/1981 "2016-01-11T22:11:59Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jgm](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/jgm/32/1360_2.png) [@jgm](https://talk.commonmark.org/u/jgm)\
**Post date:** [January 12, 2016, 6:45pm UTC](https://talk.commonmark.org/t/a-proposal-to-support-the-mark-tag-with-markdown/1981/3 "2016-01-12T18:45:29Z")

</div>

> [@tin-pot](#):
>
> the specification would specify that distinctions like this one (was “\_\_” used or “\*\*”?, was “\_” used or “\*”?, and so on) have to be represented in the parser’s output, and  
> the CommonMark DTD would provide appropriate attributes to host this information,

There’s an item in the thread [Issues we MUST resolve before 1.0 release [6 remaining] - #25 by jgm](http://talk.commonmark.org/t/issues-to-resolve-before-1-0-release/1287/25) about this (how many of these aspects of the concrete input should be recorded in the AST, so renderers have access to them).

---

_[View the full topic](https://talk.commonmark.org/t/a-proposal-to-support-the-mark-tag-with-markdown/1981)._