Template talk:Languages

(First topic)

There is an error with this template. If en_us is not included, there will be a blank space on top of the other languages.--Platform (talk) 14:43, November 1, 2022 (EDT)

Issue has just been fixed.--Platform (talk) 00:35, April 2, 2023 (EDT)

Mario Movie requires new languages to be added.

Quote "template does not currently support listings for Armenian, Catalan, Georgian, Macedonian, or Vietnamese languages. Romanian listing uses wrong ISO code." The page has those languages already in the "names in other languages" section but they dont display yet.
— The preceding unsigned comment was added by Zachruff (talk).

I don't think the languages in the template are necessarily intended to be represented with ISO codes, but with whatever abbreviation of that language's name is most intuitive to use. Serbian and Lithuanian parameters aren't written in ISO format either; the exceptions seem to be Slovak and Slovenian's parameters, which I assume is the case because both start with "slo". -- KOOPA CON CARNE 22:25, April 6, 2023 (EDT)

Native Language Names

I see that this has been changed to have the native language name be the default. I would have no issue with this other than the fact that the "in other languages" box at the bottom lists the languages all with their English names. I think we should be consistent with that and also have the language names in English here too. Zachruff (talk) 18:00, November 20, 2023 (EST)

Reorganize the language order

This talk page proposal has already been settled. Please do not edit this section or its subsections. If you wish to discuss the article, please do so in a new section below the proposal.

Documentation language order 4-2
I've seen that the language order is different in the documentation compared to what you see in the game infobox or later in the page. Which I think makes it look inconsistent. This proposal aims to avoid this inconsistency, so the order used for the game infobox correctly matches the documentation.

Proposer: Yoshi18 (talk)
Deadline: May 13, 2025, 23:59 GMT

Documentation Language Order

1. Yoshi18 (talk) Per proposal.
2. EvieMaybe (talk) it's basically just English (the wiki's language), Japanese (the franchise's language of origin), then alphabetical from there. makes perfect sense, and matches the "names in other languages" template.
3. Jdtendo (talk) Per EvieMaybe.
4. CarlosYoshiBoi (talk) I suggest listing languages in alphabetical order in the game language box:
   • Chinese (Simplified)
   • Chinese (Traditional)
   • Dutch
   • English
   • English (United Kingdom)
   • English (United States)
   • French
   • French (Canada)
   • French (France)
   • German
   • Italian
   • Japanese
   • Korean
   • Portuguese
   • Portuguese (Brazil)
   • Portuguese (Portugal)
   • Russian
   • Spanish
   • Spanish (Latin America)
   • Spanish (Spain)

Current Language Order

1. YoYo (talk) Per my comment
2. RickTommy (talk) I personally think that this template and the Names in Other Languages template should be in age/importance order (Template talk:Foreign names#Order).

Language Ordered Comments

that literally is the exact same order the language template already uses, only with English included (which isn't used in articles since the article already is English) - YoYo (Talk) 12:37, May 7, 2025 (EDT)

You're probably confusing the {{Languages}} template (used in game infoboxes) with the {{Foreign names}} template (used for "Names in other languages" sections). Currently, the language order of the two templates don't match. Jdtendo^(T|C) 07:09, May 8, 2025 (EDT)

@YoYo This is not the order the template uses. Look at the documentation compared to the template on game pages like Super Mario Party Jamboree. Dutch is for example very noticeably lower in the list. Yoshi18 (talk/contribs) 18:09, May 8, 2025 (EDT)

@CarlosYoshiBoi, just like in our documentation, we have to do the wiki language (English) first, then the country of the origin (Japan) and then on alphabetic order. Yoshi18 (talk/contribs) 18:07, May 8, 2025 (EDT)

@Yoshi18 I kinda meant for the language box when it comes to what languages games can be played in. CarlosYoshiBoi (talk) 19:24, May 8, 2025 (PDT)

Something happened with Dutch and Spanish in the page for language order

Now that the proposal has been passed and the order for the languages has been changed, I noticed something in front of Dutch and Spanish for some reason. CarlosYoshiBoi (talk) 16:32, May 17, 2025 (PDT)

Japanese and Korean parameter names

All parameter names in this template are based on two-letter ISO 639 language codes, except for Japanese (parameter: "jp", ISO code: "ja") and Korean (parameter: "kr", ISO code: "ko"). Moreover, "kr" is the ISO code of an unrelated language. For consistency, the Japanese and Korean parameters should be renamed to "ja" and "ko" respectively. Jdtendo^(T|C) 04:54, September 13, 2025 (EDT)

Rename Japanese and Korean parameters

This talk page proposal has already been settled. Please do not edit this section or its subsections. If you wish to discuss the article, please do so in a new section below the proposal.

canceled by proposer
In this template, all parameter names are based on two-letter ISO 639 language codes, except for two: Japanese (parameter: "jp", ISO code: "ja") and Korean (parameter: "kr", ISO code: "ko"). Moreover, "kr" is the ISO code of Kanuri, an unrelated language. I think this inconsistency is due to confusion with the ISO 3166 region codes of Japan ("JP") and South Korea ("KR"), even though regions are not languages.

For consistency with other codes, the Japanese and Korean parameters should be renamed to "ja" and "ko" respectively.

Proposer: Jdtendo (talk)
Deadline: October 16, 2025, 23:59 GMT

Support: ja & ko

1. Jdtendo (talk) Per proposal
2. PaperSplash (talk) Makes sense to me. Re: YoYo's point about it being too much work, we recently changed the "Jap" parameter in the "names in other languages" template to be "Jpn" instead, since the former being used to abbreviate "Japanese" is often discouraged due to it being considered a racial slur. While the current Japanese and Korean parameters used here are nowhere near as problematic in that regard, they would be no less of a hurdle to change.
3. LinkTheLefty (talk) Per PaperSplash. The argument doesn't hold water when there was already a semi-recent change that made page history navigation a bit more troublesome with no byte benefit.

Oppose: jp & kr

1. YoYo (talk) seems a little unnecessary and pedantic, this would be an update to about 95% of pages at minimum that has no real visual indicator outside of the source code. we recently had a proposal to rename the "ref needed" template and that didn't succeed for more or less the exact same reasoning I'm giving here.
2. Altendo (talk) This will definitely clog Recent Changes for no good reason. No one will even be able to tell the difference because the change isn't visible on pages, unlike page titles or renaming a template to account for a newly-made template. Changing the names or parameters of templates without any valid justification has been discouraged; I wouldn't mind switching this to a {{#switch: {{{1}}}|}} template, though.
3. Camwoodstock (talk) While this would be trivially automated with PorpleBot, this just feels like change for change's sake. In the absence of the argument where one abbreviation used was literally a slur, we feel like it's probably fine to just let this one slide, since fixing it would needlessly break old page revisions.
4. Waluigi Time (talk) This doesn't seem like very compelling reasoning to make editors adapt to a template change and break so many old revisions (again). Is this something users are notably struggling with?
5. Technetium (talk) Per all.
6. Colin's world 3 YT (talk) Per all. A small change that's has no real effect on the visuals of the page that only makes Porplebot make thousands of changes will just clog up the recent changes and do literally nothing else.

Comments (ISO 639-compliant)

@PaperSplash I would argue there's a pretty large difference between changing something because it resembles a derogatory and offensive term and something that would be changed simply because it would feel nice, the difference here is necessity vs preference, and thus my point becomes relevant again. - YoYo (Talk) 11:09, October 4, 2025 (EDT)

Given the opposing voters' concerns regarding making unnecessarily massive changes, would it be better to just leave the "incorrect" ones alone and add the "correct" ones as alternate parameters to those languages?
—Stache (talk) 19:11, October 4, 2025 (EDT)

That would be good, and I think I suggested that in my vote. @Jdtendo's only got 30 minutes to update this proposal though, so he doesn't have that much time left to do so. EDIT on 20:00, October 6, 2025 (EDT): However, it's too late now. Maybe this can be done in a future proposal... Altendo 19:30, October 6, 2025 (EDT)

I don't think having different names for the same parameter is better than the current situation. I think it would just cause more confusion. Jdtendo^(T|C) 00:11, October 7, 2025 (EDT)

You know what I would suggest instead? Maybe do it so “ja” and “ko” are alternate parameters while keeping the current ones? While we’re at it we should add a second parameter for Latin American Spanish here going by “es-419.” —CarlosYoshiBoi (talk) 19:27, October 7, 2025 (PDT)

I just said that above in response to Stache's comment, but it's too late to update this proposal. Altendo 09:44, October 8, 2025 (EDT)

Sorry, didn’t see it above. Maybe just add it in another proposal? —CarlosYoshiBoi (talk) 07:06, October 8, 2025 (PDT)

@Waluigi Time re:"Is this something users are notably struggling with?" - For me at least, unmatched language codes have tripped me up a few times, and I know I've corrected more than a few. LinkTheLefty (talk) 17:56, October 8, 2025 (EDT)

Would you also want the other parameter names to match the IETF language tags used by {{cite}}? (e.g., "en-gb" with a dash, "es-419", "zh-hans"...) Jdtendo^(T|C) 02:10, October 9, 2025 (EDT)

I don't see why it differed in the first place other than the cite template being newer and picking up other standards. Same with "NIOL" had that proposal passed. LinkTheLefty (talk) 05:35, October 9, 2025 (EDT)

Upon reflection, I feel like this proposal's scope is too narrow as it is: a proposal for using the same language tags as {{cite}} for all parameters and not just "ja" and "ko" would have been more worthwhile. Also, I realize that this proposal fails to address some concerns. Maybe I will make a reworked version of this proposal at a later date, but in the meantime, I request that this proposal be canceled. Jdtendo^(T|C) 08:17, October 9, 2025 (EDT)