Everything is the problem. None of it works the way the 'Example usage' at the top says it should....
It's used in <span class="searchmatch">Module</span>:<span class="searchmatch">User</span>:<span class="searchmatch">CodeCat</span> and it seems to work fine. It returns "French". So what problems are you seeing that I'm not?...
But there are no errors anywhere? It's just not doing what it should?...
O.K., I see that you've fixed it now. Thanks....
but the <span class="searchmatch">module</span> is already prepared to recognize the different contents before and after the colon. But findBestScript requires a <span class="searchmatch">language</span> <span class="searchmatch">code</span> and the...
<span class="searchmatch">Module</span>:wikimedia <span class="searchmatch">languages</span>/data defines the mapping from Wikimedia <span class="searchmatch">languages</span> to Wiktionary ones. So it's what you'd use if you have a Wikimedia <span class="searchmatch">code</span> and...
should always be possible to override the automatic transliteration as a matter of principle. It's not a good thing if the template is overriding the <span class="searchmatch">user</span>....
parameters, as long as the <span class="searchmatch">module</span> that supports it is able to predict in advance which names they have. For example, <span class="searchmatch">Module</span>:headword/templates does some...
In the <span class="searchmatch">code</span> above, {{rfscript}} handles the different <span class="searchmatch">languages</span> and scripts, but it's probably easier to do this directly in the <span class="searchmatch">module</span>. There is currently...
two-syllable e-stems like Lua error in <span class="searchmatch">Module</span>:parameters at line 647: Parameter 1 must be a valid <span class="searchmatch">language</span> or etymology <span class="searchmatch">language</span> <span class="searchmatch">code</span>; the value "fiu-fin-pro" is...