Template talk:Langtable: Difference between revisions
From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
(→Meaning row: new section) Tag: Mobile edit |
No edit summary |
||
| Line 2: | Line 2: | ||
Should we formally disallow character specific etymologies from the Meaning row? Just my thought from what Rdrfc said in Charizard's page. [[User:Raffina H.-207|<span style="color:deepskyblue">Raffina H.-207</span>]] 07:09, July 9, 2020 (EDT) | Should we formally disallow character specific etymologies from the Meaning row? Just my thought from what Rdrfc said in Charizard's page. [[User:Raffina H.-207|<span style="color:deepskyblue">Raffina H.-207</span>]] 07:09, July 9, 2020 (EDT) | ||
:It's not that etymologies are not interesting, but I think that for SmashWiki they are a bit out of scope. I linken it to origin game specific trivia, as opposite to Smash related trivia; they might be neat to read about, but they still belong on [Game]Wiki and not on SmashWiki. They can also occasionally cause minor trouble when editors won't agree on what is the correct etymology, which is something that I would rather avoid here. In the sample tables that I put on this page I think I made a good example about what I am talking about: "Villager" and its variants are common nouns so it is useful to write the direct translation on its side, while "Rosalina" and its variants are proper nouns and therefore translating them is improper and giving their etimologies not useful for our scope. I do also think that we should aim to fill the template completely on every page, rather than only listing names that are different (this will give the reader the guarantee that the table is not incomplete), while I am not sure about how we should handle Asian names for NPCs (which wouldn't appear in a battle UI with an "official" romanization). There are a bunch of things to tackle there that I think should be addressed and codified early in the template's lifespan. | |||
Revision as of 08:36, July 9, 2020
Meaning row
Should we formally disallow character specific etymologies from the Meaning row? Just my thought from what Rdrfc said in Charizard's page. Raffina H.-207 07:09, July 9, 2020 (EDT)
- It's not that etymologies are not interesting, but I think that for SmashWiki they are a bit out of scope. I linken it to origin game specific trivia, as opposite to Smash related trivia; they might be neat to read about, but they still belong on [Game]Wiki and not on SmashWiki. They can also occasionally cause minor trouble when editors won't agree on what is the correct etymology, which is something that I would rather avoid here. In the sample tables that I put on this page I think I made a good example about what I am talking about: "Villager" and its variants are common nouns so it is useful to write the direct translation on its side, while "Rosalina" and its variants are proper nouns and therefore translating them is improper and giving their etimologies not useful for our scope. I do also think that we should aim to fill the template completely on every page, rather than only listing names that are different (this will give the reader the guarantee that the table is not incomplete), while I am not sure about how we should handle Asian names for NPCs (which wouldn't appear in a battle UI with an "official" romanization). There are a bunch of things to tackle there that I think should be addressed and codified early in the template's lifespan.
