aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorsmcv <smcv@web>2017-06-01 10:03:51 -0400
committeradmin <admin@branchable.com>2017-06-01 10:03:51 -0400
commitaf501e9e14815297a2e9bc43dfb520eb24937b4a (patch)
tree6a856053a27b038126809985759230f7724dd1f6 /doc
parentd20dd0c97eba396211fd546e241b0bdd557f9552 (diff)
downloadikiwiki-af501e9e14815297a2e9bc43dfb520eb24937b4a.tar
ikiwiki-af501e9e14815297a2e9bc43dfb520eb24937b4a.tar.gz
current headinganchors does not damage headings' attributes, although it does not act on those headings
Diffstat (limited to 'doc')
-rw-r--r--doc/plugins/contrib/i18nheadinganchors/discussion.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn b/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn
index ec6568010..a172e5ac4 100644
--- a/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn
+++ b/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn
@@ -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
> 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
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