Talk:Gōrumondo

Name
Should we rename this into Gorumondo? I know there have been supports here, but not too much to move the page. -- 12:12, 1 March 2019 (EST)
 * I also feel that Mini Iga should have the same treatment, given that its internal filename is romanized. -- 09:57, 3 March 2019 (EST)
 * The romanization would suggest that Minīga is one word, not two, which is what the filename suggests. Anyway, I support renaming on the grounds of source priority exception (ie. Garigari is already the name for Grinder). If there's no objections, let's do that. LinkTheLefty (talk) 10:02, 3 March 2019 (EST)
 * For Mini Iga, i didn't say to rename it into its direct romanization, i just wanted to say that much like Karikari and Kamikami, Mini Iga's internal filename is a total romanization. Garigari isn't the enemy's english name either. I fear the game might haven't got a Prima for the names... -- 10:05, 3 March 2019 (EST)
 * As a general rule of thumb, if it's legible to an English reader and doesn't require a translation, then chances are, it's English. Though neither of those are real romanizations of the Japanese name. LinkTheLefty (talk) 16:06, 8 March 2019 (EST)
 * But they were still not given names by the translators, which while it doesn't matter so much for the JB enemies, does matter in cases where the entity is a variant of an established entity. If, say, a metal-shelled Troopa enemy was internally named as "Iron Noko," while it contains an English loanword, it wouldn't be as much of an English name, due to using the original JP name for Troopa. Doc von Schmeltwick (talk) 16:15, 8 March 2019 (EST)
 * I'm mainly referring to how "Minī" became "Mini" in this case, not whenever established Japanese names are used internally (e.g. "Kobu Pakkun"). LinkTheLefty (talk) 16:40, 8 March 2019 (EST)
 * This was specifically in response to the "legible to an English reader" thing. Doc von Schmeltwick (talk) 16:58, 8 March 2019 (EST)
 * That's why I mentioned "doesn't require a translation" as well - Noko and the like might be legible, but still need a Japanese-to-English translation to be fully understood/appreciated. I think that's a fair way to measure it. LinkTheLefty (talk) 17:04, 8 March 2019 (EST)
 * @Doc von Schmeltwick, what do you think about the Bakky enemies and Kiba Pig Poppo? -- 04:08, 10 March 2019 (EDT)
 * I prefer "Pig Poppo" over "Buta Poppo," personally. Bakky I can go either way on, but it's still better than the "Bucky" the article was titled before. Doc von Schmeltwick (talk) 04:55, 10 March 2019 (EDT)
 * Though, "Kiba" in the internal filename was just romanized, and also. What do you mean by going either way on? -- 05:00, 10 March 2019 (EDT)
 * I mean I don't care particularly whether it's "Bakky" or "Bakkī," since unlike with the Petapeta thing the file name is an actual romanization of the JP name, and not just some vaguely-similar thing. Doc von Schmeltwick (talk) 05:47, 10 March 2019 (EDT)
 * Japanese developers almost always use Nihon-shiki or Kunrei-shiki over Hepburn, and by those standards (or really any), Bakky would not be considered a romanization; if anything, its roots are more grounded in English than Keese. Now, I'd understand if we want to add an another language template to the Kiba Pig Poppo article due to the untranslated word, but I suggest not changing the name itself. LinkTheLefty (talk) 07:25, 10 March 2019 (EDT)
 * Kiba Pig Poppo used the direct english word in the first place as the article's name "Tusk Butapoppo" instead of say, "Kiba Butapoppo" or "Kiba Butta Poppo", which IMO, the latter it should have been in the first place. -- 07:29, 10 March 2019 (EDT)
 * Tusk Butapoppo was changed for a reason; we have an official source that uses Kiba Pig Poppo which, while a partial translation, is nonetheless easier for casual readers to understand than Kiba Buta Poppo. LinkTheLefty (talk) 07:37, 10 March 2019 (EDT)
 * I was actually asking why the creator of the article used "Tusk" instead of "Kiba". -- 09:15, 10 March 2019 (EDT)