Re: [Python-markdown-discuss] Future of the HeaderId extension??

Waylan Limberg a écrit le 2011-06-29 11:28 :
> I understand your point and I even considered that when I first
> implemented it. My thinking at the time was that adding ids to headers
> it not even noticeable in the browser by the enduser reading a
> document. It doesn't change the semantics of the html at all. It just
> provides a few extra hooks (for styling or linking) which may or may
> not be used.
> 
> I don't know how many times I've wanted to link to a specific section
> of a long document and hit view-source in my browser to find the id of
> the section so I could link to `somepage.html#somesection`. It has
> always been dissatisfying to find no ids to utilize. And yet, when
> they are there, I'm completely unaware of their existence until I need
> them.

Good point, and it happens to me too.

> I find it interesting that PHP Markdown Extra's documentation [1]
> specifically states that "Setting the id attribute will work only with
> headers for now." That indicates to me that other attributes could be
> forthcoming.

Other good point.

> Therefore, I'm going to have extra use the new attr_list
> extension for defining ids (and classes and other stuff on headers and
> anything else).
> 
> [1]: http://michelf.com/projects/php-markdown/extra/#header-id
> 
> The HeaderId ext will only be used to auto-generate ids. If you want
> to define Ids, you'll need to use the attr_list extension (or extra).

It would be interesting to have a dedicated mailing list about Markdown
Extra to discuss about the evolution of its specification.

Regards,

Jean-Philippe