Template talk:Foreignname

This looks like a good idea to me, but does everyone else agree that we should keep it? Vol (Talk)

I guess so. It seems a bit silly to list all the European names when they're the same, though. GP

Yeah, the enemy names are pretty much all different between languages, though. Vol (Talk)

Well, let's see what awaits us with Pikmin 3. Being a Wii game, some official manuals in Portuguese (for instance) might be created, so we might use this template more. Let's just wait and see. {Espyo^T} 09:47, 6 February 2011 (EST)

Language order

I've moved the languages in the following order; Dut, Fre, Ger, Ita, Spa: languages the games have been translated into; Chi, Kor, Por, Rus: the languages the games have not been translated into but have an official translation of the Smash Bros. series; every other language. All sorted internally alphabetically. --Raltseye prata med mej 12:30, 4 July 2018 (EDT)

Portuguese language flag

Hey, so I noticed this issue where, due to Pikmin 4's Portuguese translation being into Brazilian Portuguese, there were only two options for adding the name to the foreign names section, neither of which was ideal:

• Por: In my opinion, this makes the most sense in cases where there is only one name, as specifying the region would be unnecessary. However, this uses the Portuguese flag, which can confuse users.
• PorB: This uses the Brazilian flag, but is often unnecessarily specific.

As such I have changed the former to use the Brazilian flag. 2 B (talk) 09:41, August 20, 2023 (EDT)

About the Scientific/Japanese/whatever name in other languages

Continuing from here, how would the other-language versions of the technical names be listed in creature articles? 2 B (talk) 17:55, March 28, 2024 (EDT)

Retitle to "Foreign names"

I think Porplemontage or someone could retitle this template to "Foreign names" not necessarily because of Super Mario Wiki but just so that the template title is grammatically correct and has spacing. Results May Vary (talk) 04:58, June 2, 2025 (EDT)

Chinese romanisations

When editing some pages that wanted Chinese translation, I noticed that Traditional and Simplified Chinese are functionally considered separate languages and thus require romanisation and meaning to be listed twice for a complete table. This isn't quite right and a bit inefficient, as Traditional and Simplified Chinese are *essentially* different fonts. There is no difference between the two beyond the exchange in glyphs. Unless the intent is for Traditional to list another Chinese language (e.g. Cantonese), or perhaps use the Bopomofo script for Taiwanese Mandarin, there should be no scenario where a different romanisation is used every single time. Therefore, I believe that this template should merge the meaning field (as ChiM) and automatically place the romanisation in the opposite field (Trad -> Simp, Simp -> Trad) if both aren't filled in. This would make editing much easier. - 95.147.100.70 02:54, March 5, 2026 (UTC)