Guidelines:Translations
Overview
Translations are the series of pages where foreign names and terms are stored and later used for retrieval with the Nomenclature template. The listing of available translation pages can be found here.
Data:Translations Pages
Names and terms are stored on "Data:Translations" pages using the {{Translation/Store}} template. Translation data pages are always separated by game, and further with subcategories of translations. For example, the translations for Breath of the Wild are stored on subcategories under the Data:Translations/BotW page.
Subcategories
Subcategories are created by adding word to the end of the page name after the game abbreviation. For example, Data:Translations/BotW/Items. At the top of each subcategory, a header and table will outline the use of the specific data page. All Data:Translation pages should have at least five subcategories. These include:
/Characters/Enemies/Items/Locations/Miscellaneous
/Characters is used for storing non-hostile NPCs. For example, Darunia from Ocarina of Time would be considered a character. However, if an NPC starts as non-hostile, but later becomes a hostile Enemy, it would be instead stored on /Enemies pages. The opposite is where an NPC starts as a hostile Enemy, but later because friendly to the player; hostile NPCs that become friendly will be considered a character. This is especially true for characters like Volga from Hyrule Warriors, who starts as an Enemy to the player, but later joins the party and becomes a playable character. Playable characters will always be stored in /Characters even if they were hostile beforehand. In addition, Animals that are named and are non-hostile will be considered characters. For example, Link from The Wind Waker.
/Enemies, as explained above, is used for storing all NPCs that are hostile to the player. However, if an NPC was first hostile but later becomes a playable character, it will be put in /Characters. Furthermore, Objects that deal damage to the player, known as Traps, are stored here.
/Items is used for storing Items and Objects. As explained above, if an Object deals damage to the player, than it is considered a Trap and will be stored in /Enemies instead. This includes Lava and Floor Spikes.
/Locations is used for storing places, simple as that. This is where Dungeons are stored.
/Miscellaneous is used for storing everything that doesn't fall into the first four categories. This includes background music, Mini-Games, and interface elements like the HUD. The translation for the game's name, like "Breath of the Wild", is also stored here, along with the name of any DLC for the game.
Translation/Store Template
The Translation/Store template appears as follows:
{{Translation/Store||
|enBr= |enBrM= |enBrR=
|ja= |jaM= |jaR=
|zhT= |zhTM= |zhTR=
|zhS= |zhSM= |zhSR=
|cs= |csM= |csR=
|da= |daM= |daR=
|nl= |nlM= |nlR=
|fi= |fiM= |fiR=
|frC= |frCM= |frCR=
|frF= |frFM= |frFR=
|de= |deM= |deR=
|hu= |huM= |huR=
|it= |itM= |itR=
|ko= |koM= |koR=
|he= |heM= |heR=
|no= |noM= |noR=
|pl= |plM= |plR=
|ptB= |ptBM= |ptBR=
|ptP= |ptPM= |ptPR=
|ru= |ruM= |ruR=
|esL= |esLM= |esLR=
|esS= |esSM= |esSR=
|sv= |svM= |svR=
}}
In practice, the Translation/Store template would look like this:
{{Translation/Store|BotW|Link
|enBr= Link|enBrM= |enBrR=
|ja= {{Romanize|リンク|Rinku}}|jaM= |jaR=
|zhS= |zhSM= |zhSR=
|zhT= |zhTM= |zhTR=
|cs= |csM= |csR=
|da= |daM= |daR=
|nl= Link|nlM= |nlR=
|fi= |fiM= |fiR=
|frC= Link|frCM= |frCR=
|frF= Link|frFM= |frFR=
|de= Link|deM= |deR=
|he= {{Romanize|לינק|línk}}|heM= |heR= {{Cite web|quote= ז'אנר: אקשן, הרפתקאות<br/><br/>שחקנים: 1<br/><br/>הצילו את הנסיכה והעולם כולו<br/><br/>היכנסו לנעליו של האביר לינק במסעו להציל את הנסיכה זלדה ולהביס את האפלה שמאיימת להשתלט על העולם. היכנסו לעולם פתוח, יפהפה ומסקרן, וגלו את האוצרות והסכנות החבויים בתוכו. במשחק הזה אתם<br/><br/>מחליטים איך לחקור, איך לשרוד ולאן ללכת. הנופים המרהיבים, העלילה המרגשת והגישה הייחודית לנוסחת העולם הפתוח זיכתה את Breath of the Wild בתואר "משחק השנה של 2017", שממשיך להיות בין המשחקים הנמכרים ביותר ל-Switch גם ב-2019 |author= Nintendo |published= n.d. |retrieved= May 10, 2019 |url= https://www.nintendo.co.il/items/2265215-THE-LEGEND-OF-ZELDA-BREATH-OF-THE-WILD |title= THE LEGEND OF ZELDA : BREATH OF THE WILD - משחקים ל-Switch |site= Official Israel Site |type= }}
|hu= |huM= |huR=
|it= Link|itM= |itR=
|ko= |koM= |koR=
|no= |noM= |noR=
|pl= |plM= |plR=
|ptB= |ptBM= |ptBR=
|ptP= |ptPM= |ptPR=
|ru= |ruM= |ruR=
|esS= Link|esSM= |esSR=
|esL= Link|esLM= |esLR=
|sv= |svM= |svR=
}}
If you are positive that a name does not exist in a given language, simply add N/A to the language's field.
Within the Translation/Store template, all names and terms derived from non-Latin alphabets must make use of the {{Romanize}} template and must be accompanied by a transliteration of the given text (e.g. {{Romanize|リンク|Rinku}}). The third field in the Romanize template should not be used to provide a translation for the name or term in that language, as this is done automatically by Translation/Store template instead.
Meanings
For the meanings section, you should apply a translation wherever appropriate. There are however situations where the meaning field must be handled carefully, such as being left blank or left with stock text.
In the event the meaning of a name is equivalent to the English name, you simply add Same as English. as the meaning. This does not apply in the case of names for characters. In this case, simply leave the meaning field blank. When explaining meanings of foreign words, you should always italicize the foreign words given and follow up with the meaning of the word in English in parentheses. Do not make use of quotation marks for these.
Translating Names
Translations of the names or terms may be translated from the original language, though any stylizations of names or terms which are not English loanwords should be retained as a transliteration of the name in the original language. It is acceptable to omit a period from the translation portion of the Translate/Store template if they are translations of the given text and not an explanation concerning the translation. Explanations must be separated from direct translations by one line.
When providing translations, you should not use a literal translation if the sense of the given name in the American English version follows the spirit of the name. If the original name is synonymous with the American English name or is otherwise the same as the American English name, you should input Same as English. as the meaning. You should not apply this to other languages (for example, writing "Same as Japanese." is irrelevant and should be avoided). This also does not apply to proper names, as those names must be retained as transliterations instead (for instance, the Japanese name for the Yiga Clan, イーガ団 (Īga-dan), should be formatted as Īga instead of Yiga).
As a general rule: if one of the translations for the name of the subject in Japanese is equivalent to the word(s) used in the English name, you should use that word instead of any synonyms. Names that are entirely made-up and do not actually have a real-world equivalent should not be translated based on the English name.
| Subject | Original Text | Literal Translation | Final Translation |
|---|---|---|---|
| Deplian Badlands |  エウンポ高地 (Eunpo Kōchi)
|
Eunpo Plateau or Eunpo Highlands
|
Eunpo Highlands As the Deplian Badlands aren't a plateau, the closest approximation to the meaning is "highlands" instead. |
| Farore | フロル (Furoru)
|
Furoru | Furoru As "Farore" isn't an actual name or word in English, the English name for this character is only an interpretation of the Japanese name. It is not possible to prove how reflective this is of the original name, Furoru, so "Farore" is not an appropriate translation for the Japanese name. |
| Richard | リチャード (Richādo)
|
Richard | Richard As Richādo is a direct equivalent of the English name Richard, it is acceptable to translate it as "Richard". |
| Tarin |  Tarkin
|
Tarkin | Tarkin |
| Yiga Clan | イーガ団 (Īga-dan)
|
Īga Gang or Īga Group
|
Īga Group |
| Zora River | ゾーラ川 (Zōra Gawa)
|
Zōra River | Zōra River Though the English term is Zora, this is not the case in Japanese. Zōra and Zora are very similar, but not the same. |
Translation Pages
Translation Page Template
By using the Translation/Store template to store these names and translations, we can apply these to two other pages. In this instance, this storage affects the Chamber Dungeon page from Link's Awakening for Nintendo Switch. The Chamber Dungeon page makes use of the Nomenclature template (found below). On the Link's Awakening (Nintendo Switch) Translations/Locations page, it causes the following to display:
| Location |  EnglishBR | Japanese |    ChineseTR |  Czech |
|---|---|---|---|---|
 | Chamber Dungeon | パネルダンジョン (Paneru Danjon) | 嵌板迷宮 (Qiànbǎn Mígōng) |
| Location |  Danish |  Dutch | FrenchCA |  FrenchEU |
|---|---|---|---|---|
| | Chamber Dungeon | Donjon-mosaïque | Donjon-mosaïque |
| Location |  Finnish |  German |  Hungarian |  Italian |
|---|---|---|---|---|
| | Kammer-Labyrinth | Labirinto a tessere |
| Location |  Korean |  Norwegian |  Polish |  PortugueseEU |
|---|---|---|---|---|
| | 던전의 패널 (Deonjeon-ui Paeneol) | Chamber Dungeon | Chamber Dungeon |
| Location |  Russian |  SpanishEU |  SpanishLA |  Swedish |
|---|---|---|---|---|
| | Панельное подземелье (Panel'noye podzemel'ye) | Mazmorra de salas | Mazmorra de salas |
The corresponding template to make this display is the Template:Translation Page template. In order to make a Translation page function, there are certain conditions that have to be met. The first of which is the presence of the Translation Page template. The raw Translation Page template looks like this:
{{Translation Page
|game=
|filetype=
|header=
|tab1=
|tab2=
|tab3=
|tab4=
|tab5=
|subjects= }}
- game — The game's initialism. In the example above, the initialism used was
LANS. - filetype — The file suffix of the files that display in the subject column. Accepted types include:
Artwork,Render,Model,Sprite,Screenshot. These are often dependent on the kind of subject being displayed. Locations will likely use screenshots, whereas items are more likely going to make use of sprites. - header — The header for the subject column. These are often congruent with the header of the section that the template is placed in, but can usually share the same page classification (pages for characters can simply display
Character). - tab1 — The
tabfields display the languages listed (using the ISO 639-1 format). To simplify things, these are defined through variables at the top of each page which control the list of languages per variable. This allows us to quickly move around languages in the event that new languages are revealed for a given game. Though most language codes are separated by their alphabetical English name (with exception of British English and Japanese), further details on the ordering of language codes can be found below. - subjects — The list of subjects you wish to display, in singular case, alphabetical order, and separated by commas.
The variables and Translation Page template code for the example above are:
{{#vardefine:Table 1|enBr, ja, zhT, cs}}
{{#vardefine:Table 2|da, nl, frC, frF}}
{{#vardefine:Table 3|fi, de, hu, it}}
{{#vardefine:Table 4|ko, no, pl, ptP}}
{{#vardefine:Table 5|ru, esS, esL, sv}}
{{Translation Page
|game= LANS
|filetype= Render
|header= Location
|tab1= {{#var:Table 1}}
|tab2= {{#var:Table 2}}
|tab3= {{#var:Table 3}}
|tab4= {{#var:Table 4}}
|tab5= {{#var:Table 5}}
|subjects= Chamber Dungeon }}
To reduce the space taken by the variables, the variables given should be separated by an HTML comment between each line (<!-- and -->).
Nomenclature Template
The {{Nomenclature}} template draws directly from the {{Translation/Store}} and displays whatever is stored for the page's Series term. To use the Nomenclature template, type {{Nomenclature}}. To call for a nomenclature table for a page different than the one for the page that you are currently on, use {{Nomenclature|NAME OF PAGE}}.
For the Chamber Dungeon page, this is what displays:
 Names in Other Regions  | ||
|---|---|---|
| Language | Names | Meanings |
| EnglishBR | Chamber Dungeon (LANS) | |
| Japanese | パネルダンジョン (Paneru Danjon) (LANS) | Panel Dungeon |
| ChineseTR | 嵌板迷宮 (Qiànbǎn Mígōng) (LANS) | |
| Danish | Chamber Dungeon (LANS) | |
| FrenchCA | Donjon-mosaïque (LANS) | |
| FrenchEU | Donjon-mosaïque (LANS) | |
| German | Kammer-Labyrinth (LANS) | Chamber Labyrinth |
| Italian | Labirinto a tessere (LANS) | Cards labyrinth |
| Korean | 던전의 패널 (Deonjeon-ui Paeneol) (LANS) | Panel Dungeon |
| Norwegian | Chamber Dungeon (LANS) | |
| PortugueseEU | Chamber Dungeon (LANS) | |
| Russian | Панельное подземелье (Panel'noye podzemel'ye) (LANS) | Panel dungeon |
| SpanishLA | Mazmorra de salas (LANS) | |
| SpanishEU | Mazmorra de salas (LANS) | |
| This table was generated using translation pages. To request an addition, please contact a staff member with a reference. | ||
Order of Languages
The order that languages should be listed in templates and listings follows the alphabetical order of the English names for the languages, though they are usually listed with their ISO 639-1 code (Finnish would be listed before German, though they would be listed as fi and de respectively). The exceptions to this order are British English (enBr) and Japanese (ja), which are to be prioritized due to their importance and relation to the American English canon. A full list of accepted languages and their ISO 639-1 codes are in order as follows:
| Language | ISO 639-1 code |
|---|---|
 North American English
|
enAm 
|
| British English
|
enBr |
| Japanese
|
ja |
 Simplified Chinese
|
zhS |
| Traditional Chinese
|
zhT |
| Czech
|
cs |
| Danish
|
da |
| Dutch
|
nl |
| Finnish
|
fi |
| Canadian French
|
frC |
| European French
|
frF |
| German
|
de |
 Modern Hebrew
|
he |
| Hungarian
|
hu |
| Italian
|
it |
| Korean
|
ko |
| Norwegian
|
no |
| Polish
|
pl |
 Brazilian Portuguese
|
ptB |
| European Portuguese
|
ptP |
| Russian
|
ru |
| European Spanish
|
esS |
| Latin American Spanish
|
esL |
| Swedish
|
sv |
When applying the languages in order to the Translation Page template, you should do your best to split them as evenly as possible (if there are 15 languages present, divide the list into three tabs of five languages each). In the event that an even number is not possible, do your best to keep all except the final tab even, leaving the last tab as an irregular list. If there are five or less languages present in total, you do not need to divide the languages at all.
