aboutsummaryrefslogtreecommitdiff
path: root/doc/plugins/contrib
diff options
context:
space:
mode:
authorsmcv <smcv@web>2017-06-01 09:59:36 -0400
committeradmin <admin@branchable.com>2017-06-01 09:59:36 -0400
commitd20dd0c97eba396211fd546e241b0bdd557f9552 (patch)
tree6a23aff520e471c17f6a6fcb955743c07bf4ba93 /doc/plugins/contrib
parent2f765597defb81816ee1f6a6ed041d6c47dd8f7e (diff)
downloadikiwiki-d20dd0c97eba396211fd546e241b0bdd557f9552.tar
ikiwiki-d20dd0c97eba396211fd546e241b0bdd557f9552.tar.gz
Diffstat (limited to 'doc/plugins/contrib')
-rw-r--r--doc/plugins/contrib/i18nheadinganchors/discussion.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn b/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn
index 8e539b6af..ec6568010 100644
--- a/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn
+++ b/doc/plugins/contrib/i18nheadinganchors/discussion.mdwn
@@ -21,6 +21,13 @@ clearer where it goes)
> Can we assume Ikiwiki generates HTML5 all the time? I thought that was still a
> setting off by default... --[[anarcat]]
+>> ikiwiki always generates HTML5, since 3.20150107. The `html5` option has
+>> been repurposed to control whether we generate new-in-HTML5 semantic
+>> markup like `<section>` and `<nav>` (`html5` enabled), or HTML4 equivalents
+>> like `<div>` with a class (`html5` disabled). The default is still off,
+>> although I should probably either toggle it to on or remove the option
+>> altogether in the next release. --s
+
So perhaps we could try this Unicode-aware version of what Pandoc documents:
* Remove footnote links if any (this might have to be heuristic, or we could
@@ -55,6 +62,13 @@ supporting [IRIs](https://tools.ietf.org/html/rfc3987): `<a href="#visiting-北ä
> as an example, https://caniuse.com/ doesn't have that feature listed in their
> tables. :) -- [[anarcat]]
+>> That might well indicate that all major browsers have always supported it so
+>> there is no need to check. I don't see any particular reason why a browser vendor
+>> would not want to accept arbitrary non-whitespace as a valid anchor.
+>>
+>> In practice, minor or old browsers are probably insecure anyway, so I don't care
+>> too much about supporting them perfectly... --s
+
----
Documentation says: