search for: fnref

I just realised I hadn't updated the version of PHP Markdown and Extra on the dingus as I pretended I did in my two announcements. It is now fixed: PHP Markdown 1.0.2b7 and PHP Markdown Extra 1.1b1 can now be tested on the dingus. <http://www.michelf.com/projects/php-markdown/dingus/> Sorry for any inconvenience. Michel Fortin michel.fortin@michelf.com http://www.michelf.com/

...have one feature suggestion for the PHP Markdown Extra syntax. If you're posting to a CMS system where multiple articles may appear on the same HTML page, you need to assign each article a GUID so that the footnote links make sense (i.e., you can't have two articles that both use "fnref" as the anchor name for the footnotes, since you would end up with two anchors with the same name if two articles are published on the same page). It's of course possible to do this with a search and replace of "fnref" to something like "2007-01-23-1" prior to publ...

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...

...ich will work for everyone. I decided I'd follow what I've seen on Daring Fireball, as I think it's a pretty good default, but with some minor differences. Here is the default output from the first sample: <p>That's some text with a footnote. <sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup></p> <div class="footnotes"> <hr /> <ol> <li id="fn:1"> <p>And that's the footnote. <a href="#fnref:1&quo...

...n for the PHP > Markdown Extra syntax. If you're posting to a CMS system > where multiple articles may appear on the same HTML page, > you need to assign each article a GUID so that the footnote > links make sense (i.e., you can't have two articles that > both use "fnref" as the anchor name for the footnotes, since > you would end up with two anchors with the same name if two > articles are published on the same page). It's of course > possible to do this with a search and replace of "fnref" to > something like "2007-01-23-1...

...&gt;</code> tags. Most browsers will display it properly, but it is not a complete XHTML document. Without a <code>&lt;head&gt;</code> section there is nowhere to put metadata (e.g. there is no <code>&lt;title&gt;</code>). <a href="#fnref:snippets" rev="footnote">&#8617;</a></p> </li> </ol> </div> The current MultiMarkdown output is: <div class="footnotes"> <hr /> <p>Footnotes:</p> <div id="snippets"><p><a href=&...