You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in or create an account, your edits will be attributed to your username, along with
other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision |
Your text |
| Line 9: |
Line 9: |
|
| |
|
| : I agree (also because Slidon just sounds cooler) {{User:MawioMawiolol/sig}} 06:17, January 25, 2024 (EST) | | : I agree (also because Slidon just sounds cooler) {{User:MawioMawiolol/sig}} 06:17, January 25, 2024 (EST) |
| ::Additionally, was there even a discussion prior to renaming it to "Suraidon"? --{{User:FanOfYoshi/sig}} 12:29, January 25, 2024 (EST)
| |
| :::There was [[MarioWiki:Proposals/Archive/64#Clarify_stance_on_Japanese-derived_internal_names|this proposal]] I created that passed, but I didn't consider instances where the internal name is the ''same'' as the Japanese name. I guess the move to Suraidon follows the proposal? (With the way I worded it, I mean.) I wouldn't be opposed to a follow-up proposal where Japanese-name priority is only applicable to enemies that don't have a romanization of their final Japanese name as their internal name, though... [[User:DrippingYellow|DrippingYellow]] ([[User talk:DrippingYellow|talk]]) 23:50, January 25, 2024 (EST)
| |
| ::::Whether internal names can in some cases be considered as official romanizations remains an open question, but now that we have an official English name for this enemy, we certainly won't rename this page back to Slidon. {{User:Jdtendo/sig}} 03:01, January 26, 2024 (EST)
| |
