Legacy Abbey Games Forums

Don't think that would be possible without the use of the interwiki (rejected because each language would require diferent servers, it seems) or the use of a lot of javascript to interact with the sidebar and alter the links depending on the language the user chose.

I've edited the Navbox code because it seemed broken. I also created a new navbox, the Template:Reus/pt . This will make the life of readers easier, by linking the main game mechanics in most pages. This way they don't have to hunt for the information, they can easily finish to read an article and c...

Maarten wrote:I've set

Code: Select all

$wgRestrictDisplayTitle = false;

if you want to try it out..!

Cheers! It is working as intended (Example).

I take advantage of this opportunity to ask for a "Reur (Portuguese)" subforum, and also any other language in the MultiLangBar, please ! I would very much like if it was created, although I've only seen 3 Portuguese speakers on the forum. Thanks for the support, though. Hey Paulo, Na página dos Na...

Baseado na lista do usuário Touriste, criei esse tópico contendo todos os termos importantes de Reus, incluindo nome das fontes naturais, recursos, projetos, simbioses e habilidades dos gigantes. O objetivo principal desse tópico é simples, deifnir e discutir quais termos utilizar, já que essa será ...

I will be using this. Thank you very much :)

I have a problem with the Awe template, because in project page , it leads to the chapter on Awe on the Resources page . But the template leads to awe/fr that does not exist because "awe" alone is located in the resources page. Not sure if that is clear :/ Also, for the "see also" (thanks for the w...

I was wondering if we should allow the usage of {{DISPLAYTITLE}} for translated articles. This function allows the editors to choose which title to show on top of the page. So, for example, if we used {{DISPLAYTITLE:Biomas}} on the article Biomes/pt , it would instead should Biomas , on the top of t...

I will try adding support to that template as well, though that template is quite the mess. Edit: Because there are too many strings to translate (not only See also , but all the and s), the better solution would be to create subpages instead of adding the support as code. So, instead of {{See also|...

I can not make it work. I tried {{food/fr}} {{food=3}} {{food|3=fr}} {{food|3}} Did I do something wrong ? The language code is the second variable, while the value is the first. If I was to write in portuguese, I would have to use the following: {{food|3|pt}}, to show the number plus an image; or ...