Discovered something similar when using MultiMarkdown to create ePubs --- the colon in the footnotes isn't valid (though seems to work in most readers). Hyphens appear to be valid characters, in that context at least.
Any reason not to switch to hyphens instead of colons? Or could even remove altogether I suppose. I would be interested in choosing something more compatible with other implementations rather than everyone going their own route. F- On Jan 23, 2013, at 2:29 PM, Waylan Limberg <[email protected]> wrote: > I just received a [bug report] for Python-Markdown complaining that > colons are used in the ids of footnotes. For reference, we [output] > the same format at PHP Markdown Extra. The general complaint is that > the colon in the id attribute (`id="fnref:1"`) causes jquery to choke > when referencing that id from javascript because jquery uses colons to > indicate pseudo elements (as does CSS). As expected, jquery supports > escaping the colon - which eliminates the problem - except that > apparently the escaping causes a performance hit. > > My initial reaction is to say that this is jquery's problem, but what > do you think? Should the various implementations that support > footnotes all change to not use colons? I couldn't help but note that > Gruber's unreleased implementation (what he uses on > daringfireball.com) appears to use dashes instead. > > Any thoughts? > > [bug report]: https://github.com/waylan/Python-Markdown/issues/180 > [output]: http://michelf.ca/projects/php-markdown/extra/#fn-output > > -- > ---- > \X/ /-\ `/ |_ /-\ |\| > Waylan Limberg > _______________________________________________ > Markdown-Discuss mailing list > [email protected] > http://six.pairlist.net/mailman/listinfo/markdown-discuss -- Fletcher T. Penney [email protected]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Markdown-Discuss mailing list [email protected] http://six.pairlist.net/mailman/listinfo/markdown-discuss
