X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/bd881a8ee6dee2f06118596f78c5ac9296a35098..2fc21bff0adc27d9374aa6b5f5011ca422df47d8:/doc/bugs/footnotes-look-weird.mdwn diff --git a/doc/bugs/footnotes-look-weird.mdwn b/doc/bugs/footnotes-look-weird.mdwn index 7ea9f240c..a821ab43c 100644 --- a/doc/bugs/footnotes-look-weird.mdwn +++ b/doc/bugs/footnotes-look-weird.mdwn @@ -76,6 +76,27 @@ screen readers), as detailed in [this Stack Overflow discussion][]. >> are enabled in their configuration, but I understand that makes the >> configuration more complicated and error-prone. >> +>>> Discount enables enough features by default that adding footnotes doesn't +>>> seem bad to me. I'm also tempted by something like +>>> +>>> ``` +>>> mdwn_enable: [footnotes] +>>> mdwn_disable: [alphalist, superscript] +>>> ``` +>>> +>>> where the default for anything that was neither specifically enabled +>>> nor specifically disabled would be to enable everything that we don't +>>> think is a poor fit for the processing model (pandoc-style document +>>> headers) or likely to trigger by mistake (typographic quotes and +>>> [[maybe alpha lists|forum/"S."_gets_replace_by_"a."_in_my_ikiwiki]]). +>>> --[[smcv]] +>>> +>>>> Makes perfect sense to me. --[[anarcat]] +>>>> +>>>>> I have now enabled footnotes in Discount by default, with a new +>>>>> `mdwn_footnotes` option that can switch them off if they become +>>>>> problematic. --[[smcv]] +>>> >> For example, to enable footnotes, one needs to call Discount like this: >> >> Text::Markdown::Discount::markdown($text, Text::Markdown::Discount::MKD_EXTRA_FOOTNOTE()) @@ -90,6 +111,21 @@ screen readers), as detailed in [this Stack Overflow discussion][]. >> >> In the meantime, wouldn't it be better to have some styling here to >> workaround the problem in MMD? +>> +>>> Honestly, I'd rather have ikiwiki's level of support for the non-preferred +>>> Markdown implementation be: if you are stuck on a platform with no C compiler +>>> or Perl headers, you can use the pure-Perl Markdown flavours, and they +>>> will sort of mostly work (but might not look great). +>>> +>>> I'm a little concerned that styling these rather generically-named classes +>>> might interfere with the implementations of footnotes in other Markdown +>>> implementations, or indeed non-Markdown - I wouldn't want to style +>>> `a.footnote` if the HTML produced by some other htmlize hook was +>>> `[1]` for instance. +>>> But they're probably harmless. +>>> +>>>> Alright, your call. :) At least this bug will be available as a workaround +>>>> for others that stumble upon the same problem! :) --[[anarcat]] Note that I also make the bottom `
` small as well so that it has less weight than the rest of the text. -- [[anarcat]]