Hard for me to tell since I don’t know what was originally entered, but it appears to be working for me (using Safari). You’re right though, this will suffer the same problem that non-URL-safe characters present in many browsers, since the name anchors are based on that. What it really needs to be compatible is transliteration, that occurs with URL titles in weblog entries.
Hard for me to tell since I don’t know what was originally entered…
If you look at the page source, you can see:
<h4 id='�лавна�_��ани�а'>Главная траница</h4>
[...]
<h5 id='First_one'>First one</h5>
[...]
<h5 id='Second_one'>Second one</h5>
[...]
<h5 id='�е�в�й_под�аздел'>Первый подраздел</h5>
[...]
<h5 id='��о�ой_под�аздел'>Второй подраздел</h5>
[...]
<h5 id='Third_one'>Third one</h5>
Normal code should be without any “?” in headers, like this:
<h4 id='Главная траница'>Главная траница</h4>
[...]
<h5 id='First_one'>First one</h5>
[...]
<h5 id='Second_one'>Second one</h5>
[...]
<h5 id='Первый подраздел'>Первый подраздел</h5>
[...]
<h5 id='Второй подраздел'>Второй подраздел</h5>
[...]
<h5 id='Third_one'>Third one</h5>
The most interesting part, that in Mediawiki the same native characters are perfectly shown in any browsers. So I presume that there is something wrong in script code.
I have not looked to see how Mediawiki parses their table of contents, but since I wrote this plugin from scratch, I doubt they are similar approaches. Unfortunately, it’s just not something I considered when writing it over a year ago. I do some a few other PCRE uses that would need the same modification that I suggested above, though. Email me (not PM please), referencing this thread, and I’ll send a new file over to you that might be a bit closer to what you’re after.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.