Hello,
As I am using markdown to write documentation, I am often tempted to make
links to terms in definition lists.
Since this is not possible for now (at least in php markdown extra), I was
wondering if this could be a common addition in major implementation
supporting definition lists.
the syntax would be
term {#id}
: definition
This syntax tries to follows current convention and use the similarity
between titles and terms.
Matthieu
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://six.pairlist.net/pipermail/markdown-discuss/attachments/20130701/4d92e28c/attachment.html>
This strikes me as a sound suggestion. It would allow us to use a definition list where currently we'd be forced to use headings and paragraphs. On 1 July 2013 08:33, Matthieu Codron <codronm+markdown at gmail.com> wrote:> Hello, > > As I am using markdown to write documentation, I am often tempted to make > links to terms in definition lists. > > Since this is not possible for now (at least in php markdown extra), I was > wondering if this could be a common addition in major implementation > supporting definition lists. > > the syntax would be > > term {#id} > : definition > > This syntax tries to follows current convention and use the similarity > between titles and terms. > > Matthieu > > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss at six.pairlist.net > http://six.pairlist.net/mailman/listinfo/markdown-discuss > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20130701/84dcdb9a/attachment.htm>
I don't know about the {#id} part, but MultiMarkdown recognizes that syntax
for definition lists.
Out of curiosity, do I understand correctly that
term
: definition
is already in common usage when people write plain text? I was not aware of
that, so if so, I may start adopting it in my own emails etc.
--Andy
On Jul 1, 2013, at 11:33 AM, Matthieu Codron <codronm+markdown at
gmail.com> wrote:
> Hello,
>
> As I am using markdown to write documentation, I am often tempted to make
links to terms in definition lists.
>
> Since this is not possible for now (at least in php markdown extra), I was
wondering if this could be a common addition in major implementation supporting
definition lists.
>
> the syntax would be
>
> term {#id}
> : definition
>
> This syntax tries to follows current convention and use the similarity
between titles and terms.
>
> Matthieu
Le 1-juil.-2013 ? 11:33, Matthieu Codron <codronm+markdown at gmail.com> a ?crit :> Hello, > > As I am using markdown to write documentation, I am often tempted to make > links to terms in definition lists. > > Since this is not possible for now (at least in php markdown extra), I was > wondering if this could be a common addition in major implementation > supporting definition lists. > > the syntax would be > > term {#id} > : definition > > This syntax tries to follows current convention and use the similarity > between titles and terms.I'm planning to add this to the next version of PHP Markdown Extra. -- Michel Fortin michel.fortin at michelf.ca http://michelf.ca
On Wed, Jul 3, 2013 at 6:00 PM, Michel Fortin wrote:> Le 1-juil.-2013 ? 11:33, Matthieu Codron <codronm+markdown at gmail.com> a > ?crit : > > > Hello, > > > > As I am using markdown to write documentation, I am often tempted to make > > links to terms in definition lists. > > > > Since this is not possible for now (at least in php markdown extra), I > was > > wondering if this could be a common addition in major implementation > > supporting definition lists. > > > > the syntax would be > > > > term {#id} > > : definition > > > > This syntax tries to follows current convention and use the similarity > > between titles and terms. > > I'm planning to add this to the next version of PHP Markdown Extra. >I'd love to see this in PHP Markdown Extra, but also in pandoc and MultiMarkdown... John, Fletcher, what do you think about it ? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20130706/d12695e8/attachment.html>
> > From: "Fletcher T. Penney" > > I'm not sure I want to head down that path yet for MultiMarkdown. I'm not > ruling it out for all time, but I worry about the "cruft" vs "reward" > balance. > > I understand your point of view. But I'd like to avoid futureimplementation divergences ; so I'd like to hear you about the propoosed syntax : if you were about to implement it in MultiMarkdown, would you adopt this syntax ? I know you cannot give a definitive answer, but at least can you confirm it seems good to you ? Thanks Matthieu -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20130711/47a1d722/attachment.html>
On Mon, Jul 1, 2013 at 11:33 AM, Matthieu Codron <codronm+markdown at gmail.com> wrote:> > the syntax would be > > term {#id} > : definition >Python-Markdown already has extensions for Attribute Lists [1] and Definition Lists [2] (both also available as part of Extra [3]). However, due to the restriction that definition list terms can only be on a single line (each line is a separate term), it was impossible to assign attrs to the term. I was already special casing headers (h1-6) for the same reason, so it wasn't too hard to adapt the code to work with dt's also. I just pushed a fix [4] which implements support for this syntax (you can set any kind of attribute supported by the attr_list extension) and it should be available in the next release of Python-Markdown (probably 2.3.2). As always, testing/feedback is welcome. [1]: http://pythonhosted.org/Markdown/extensions/attr_list.html [2]: http://pythonhosted.org/Markdown/extensions/definition_lists.html [3]:http://pythonhosted.org/Markdown/extensions/extra.html [4]:https://github.com/waylan/Python-Markdown/commit/a9ca97325e9039de90eae29fb3d8879bc9f367f6 ---- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg