Tried to find something about [edit] in Language Extension Bundle documentation but found nothing. It seems it’s not dependent on translation markup and it’s completely different subject.
It turns out 1 level headings should never be used
Interesting. Is this a known issue or could you report that one please?
I asking because it sounds like an okay workaround for now, but we don’t know into which unrelated issues (with skins etc.) we could run if not using level headings in the whole wiki.
Cause must me more mysterious than this.
Could derivate from an earlier or later syntax error. I got an idea on how to nail down this issue. By making a copy of that page for easier testing (not touching the live version) and then selectively deleting other sections or just using the section in question.
adrelanos: [ [ [ that's wrong
Every tvar needs to have a different name. Also, we don't usually put | inside the tvar and I have no idea what effects that has.
My conclusion… This works better.
* [[<tvar|1>Main Page|</>Very brief introduction and summary on Whonix Homepage]]
* [[<tvar|2>Anonymity|</>Why do you need anonymity?]]
* [[<tvar|3>The World Wide Web And Your Privacy|</>The World Wide Web and your privacy]]
[hr]
What about the following syntax? Does it look correct?
* [[<tvar|about>About|</> More About Whonix]]
<Nemo_bis> adrelanos: usually we do
[code]
[[<tvar|about>Special:MyLanguage/About</>|More About Whonix]]
[/code]
[hr]
And according to extension documentation, these are global variables across all translateable pages.
Quick fixed the documentation page for now using a small script:
But we must search the whole wiki for tvar|A and use better variables names. Because those links are very likely broken as well.
[hr]
Didn’t apply the
Special:MyLanguage/
thing yet. If you think it’s a good idea, I think I can come up with a small script to auto mass search and replace those on the documentation page as well. What do you think?
[hr]
If it’s the same link / phrase / translation, then using the same variable name would mean less work for translators because those are auto replaced.
That number should not be global for all pages. That would be a burden for no advantage, I think.
Instead of documentation_1 or could be about_1 and so forth. Anyhow. There is no reason to force us to use numbers for other pages.
For example, if we had a link such as
[[<tvar|about>About|</> More About Whonix]]
on multiple pages (don’t know a good example right now), then “about” would be a good global variable, I think. (Because then somehow, translation on one page = translation on all pages using some special markup.)
This won’t work unfortunately. Since it’s global variables, we cannot use the same variable name twice. So we cannot use the variable name “1” on more than one page.
(Unless in the rare cases, where we want to save work for translators.)
That’s why my original idea included various_prefix_number, i.e. about_1 etc.
Okay. Thanks. Looks like quite a lot work has been done.
What do we do in case these pages are partially rewritten? I’d say in that case we just add a small prefix? a1, a2, a3, … as variable names? (Otherwise going through renumbering all those again would be too much work.)
By the way, if you feel one day we could use a separate forum for translation stuff and translators support, just say so. We’re flexible here, can be done easily and quickly.
What about changing the subject of this thread to “Translations Technical Developer Discussion”?
On Advanced Security Guide - Whonix when I press edit, it opens a different section. Got no idea how to fix it. Can you fix it please? I’ll try to understand the fix next time.