Update needed: Russian
- Done. Thanks so much for taking the time to help out the wiki! :D (talk) 17:05, June 27, 2016 (EDT)
Update needed: Taiwan
- You can use ChiT parameter for Traditional Chinese. vmario97 (talk) 05:12, March 25, 2020 (EDT)
Traditional vs. Simplified Chinese
Is there a way to control whether or not to split the Chinese field into Simplified and Traditional? While most of the names are just converted between the two systems, some New Horizons names are very different between the two (see Giant Trevally and Dace). Also, when the name is the same between the two, is there a better way to toggle the Hong Kong flag other than just copy-pasting the exact same text from "zh" to "zh-t"? Langswitch (talk) 07:12, May 20, 2020 (EDT)
- Hm, well the idea was, if Simplified = Traditional, to only use the Simplified param - we don't use both EU / US Spanish or French (or English even) unless there are differences. It is true that sometimes the fish and bugs names are very different in the american/european case as well. This is my fault because I was used to working with villagers and they have the same names in both Simplified and Traditional and I didn't think of other uses so I suggested to merge the rows into one. Oops. I'd still prefer for them to be merged for the sake of villager pages, but perhaps there could be a special Traditional2 parameter? Paviinka(Message me!) 08:12, May 20, 2020 (EDT)
- Yeah, the translations are a little finicky with New Horizons. The challenge is that in most cases, they are the same (haven't run into any bugs that have different names, and there are plenty where the actual Chinese characters don't change between Simplified and Traditional), but when they're different, they can be really different (Dace in particular comes to mind, since the definition also changes). I was thinking if there might be a way to adjust the layout based on whether or not we have, say, a zht-r field, since it's very rare (in general, not just in NH) for something to be written differently but both be pronounced the same and have the same definition. We could maybe have just one entry if it's there and two if it isn't? I'm just spitting ideas here though; I don't know how complex the actual encoding will get here. Langswitch (talk) 19:00, May 20, 2020 (EDT)
Standardization of 'meaning' fields
I wanted to start a discussion around the proper way to use the template's 'meaning' fields, or the fields that display a foreign language's English meaning or translation. The main point of confusion that I've seen, is that in some instances when the name is either very similar to the English name (and English meaning/translation can be easily inferred), or when it is identical to the English name (such as a non-localized game title that remains in English), a dash "-" is input in the 'meaning' parameter for a translation. I wanted to see if we could reach some agreement as to what to do in these cases. Should we use a dash, or should we just input the English name for both the foreign language input and meaning (e.g.
es-m=xyz) or should we include a dash in the meaning parameter field if it matches the foreign language input (e.g.
es-m=-)? And what about in cases where it is close, but not identical (Example: https://nookipedia.com/w/index.php?title=Welcome_Horizons&diff=prev&oldid=410030) (talk) 12:00, October 21, 2020 (EDT)
- I think the meaning field should always be filled in, even if the foreign language name is a direct translation of English name. Given its use elsewhere on the wiki (and in general), a dash may convey that a word doesn't translate to an English word, or that we do not have one filled in yet. I think the only case where the meaning shouldn't be filled in (or filled in with a dash) is if the name is identical to the English name, and not translated in the first place (like many of the games' titles). ~ AlexBot2004 (Talk) 15:52, October 27, 2020 (EDT)