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 should be stored on  pages with the Translation/Store template, as seen here. Within the 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. ). 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 through the Translation/Store template instead.

Translation/Store Template
The Translation/Store template appears as follows:

In practice, the Translation/Store template would look like this:

If you are positive that a name does not exist in a given language, simply add  to the language's field.

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 LANS: page from. The LANS: 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:

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:

The variables and Translation Page template code for the example above are:

To reduce the space taken by the variables, the variables given should be separated by an HTML comment between each line.

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 (Finnish would be listed before German, though they would be listed as   and   respectively). The exceptions to this order are British English and Japanese, 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:

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.

Nomenclature Template
The Nomenclature template draws directly from the Translation/Store template and displays whatever is stored for the page's Series term. For the LANS: page, this is what displays:

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  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,, 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.

Meanings
For the Translation/Store template, 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  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.