urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

current headinganchors does not damage headings' attributes, although it does not act on those headings

master
smcv 2017-06-01 10:03:51 -04:00 committed by admin
parent d20dd0c97e
commit af501e9e14
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/plugins/contrib/i18nheadinganchors/discussion.mdwn
View File

@ -84,6 +84,10 @@ or similar.
> It's not a bug, it's a limitation. :) But sure, it's a thing. It's an issue in > It's not a bug, it's a limitation. :) But sure, it's a thing. It's an issue in
> headinganchors as well of course. -- [[anarcat]] > headinganchors as well of course. -- [[anarcat]]
>> No, current/historical headinganchors has a different bug: it ignores headings
>> that have any attributes, and does not generate anchors for them. That gives it
>> degraded functionality, but no information loss. I think that's less bad. --s
I think we should try to use an existing ID before generating our own, with the I think we should try to use an existing ID before generating our own, with the
generation step as a fallback, just like Pandoc does. If a htmlize layer like generation step as a fallback, just like Pandoc does. If a htmlize layer like
Text::MultiMarkdown or Pandoc is generating worse IDs than this plugin, the Text::MultiMarkdown or Pandoc is generating worse IDs than this plugin, the