Hi!
I tried to find where I could fix a translation error myself on translatewiki, but I cannot find it, so maybe you can help me?
In the nl: version of VE "citation" is translated as "citeren". This however means "quoting" and very confusing to the Dutch. A better translation would be "referentie". (as in "reference")
@Ciell there is a little trick. you can add "&uselang=qqx" to the url of a webpage (or ?uselang=qqx depends a bit on the url) and this special languagecode will show you the names of all the messages used in the interface:
https://nl.wikipedia.org/wiki/Aomi?veaction=editsource&uselang=qqx
So in this case you are looking for the MediaWiki message: MediaWiki:Citoid-citoidtool-title
Very interesting @TheDJ!
But that doesn't show the VE-buttons to me? It does show all the different tabs on a page.
It looks like you found it: https://translatewiki.net/w/i.php?title=MediaWiki:Citoid-citoidtool-title/nl&diff=9107632&oldid=8787415
Yes, I did correct that one.
But my question is a general one: the "=qqx"-trick is interesting, in cases where you don't know the name of the right Mediawiki: page. But it doesn't show me the buttons?
@TheDJ There's another thing we have to solve before we can implement the VE. The citation list ('referentielijst' - Mediawiki:cite-ve-dialogbutton-referenceslist-tooltip) now gives the wrong parameters, we prefer a template instead of wikicode. Where can I have this changed?
@Ciell I don't think that is changeable. If you want to use a template, you should be using the template inserter, not the references list inserter. On en.wp we have made the layout of <references /> equal to the layout of {{reflist}}. And using it like that, will also make the params of the template unreachable, see usages of {{Reflist}} inside of english wikipedia. Because it sees the references element inside of the template, it knows that it will have to live update that content (based on refs beings added/removed etc), and other changes are for that reason not possible.
Of course, you can manipulate the Toolbar using Javascript to do whatever you want. But that is up to the communities that want to deviate from standards.
@TheDJ Thank you very much for your reply.
Could you maybe have a look at our template, to see if your solution would work for WPNL as well?
Please see https://nl.wikipedia.org/wiki/Sjabloon:References for the template I'm referring to.
Well the biggest problem for nlwp that I just noticed, is their multilevel wrapping.. Appendix -> References -> <references /> By default they already hardly use ANY of their {{references}} template options, so those would probably be easy to get rid of, but this multilevel wrapping makes it so that the 'fix' that was made for reflist to make it updatable even though it is not a true <references /> element, doesn't work as the <references /> cannot be found nested inside a template. I'll have to take a look later at the exact template options and if and how they are needed.
