This article serves as a comprehensive guideline for ArchWiki internationalization and localization.
Non-English page titles must be of the form "Title in English (Language)" where "Language" is the localized spelling of said language. Note the space between the title and the language tag. For example: Installation guide (Nederlands). English titles should not include a language tag.
Also note that in case of sub-pages, the language tag shall be appended to each segment in the title path, so "Title (Language)/Sub-page" is wrong, while "Title (Language)/Sub-page (Language)" is correct. For example: systemd (Русский)/User (Русский). Using language tags on each segment enables proper operation of the superpage links, and in particular the last tag is added automatically in interlanguage links, plus it makes it more practical and safe for bots to detect the language of a page. "Title/Sub-page (Language)" was the previously accepted format, which is now obsolete but possibly still in use by some articles.
The root categories for every language are the only exception to this rule, as they must not repeat the language name in a suffix.
See #Languages for a list of languages and expected localized spellings.
- English titles facilitate administration; all administrators understand English, but may not be multilingual. When browsing Special:RecentChanges and other special pages, admins need to know what is being edited without resorting to external translation programs.
- Standardized article titles simplify inter-language linking.
Localized titles can and should be created, but must redirect to the English-named article as described above. Redirect titles need not include language tags. For example: Guía oficial de Instalación redirects to Installation guide (Español). Note that this is however not possible for Category pages, since categorizing a page under a redirect will not list the page under the target category.
- Localized titles improve navigability for international readers. Both the internal search feature and external search engines can utilize such redirects.
- Useful redirects facilitate internal linking.
If an article exists in more than one language, please add interlanguage links at the top of each translation:
[[de:Title]] [[en:Title]] [[es:Title]]
[[da:Main page]], and that associated to Help:Style (Português)/Formatting and punctuation (Português) is
[[pt:Help:Style (Português)/Formatting and punctuation]].
- Including inter-language links at the beginning of an article allows international readers to promptly determine whether content is available in their language, and similarly allows translators to ascertain whether an article requires translation.
In order to obtain a list of the articles with interlanguage links pointing to a specific title (language backlinks), use:
This example looks for (
[[en:Main Page]]), but for other links it is enough to change the value of
If you want to obtain a list of the articles using interlanguage links of a specific language, just omit the
This example uses German (
de), but for the other languages it is enough to change the value of
Note that API queries are always limited, so if a language has more than 500 backlinks it will be necessary to continue the search adding the
lblcontinue attribute that appears at the bottom of the list to the query string.
The following table lists all languages encountered on the wiki along with related links.
Subtags are treated case-insensitively by the MediaWiki backend. By convention, the interlanguage links on ArchWiki should use the lowercase form of the subtag. For information regarding subtags, please see:
If you want interlanguage links to be enabled for a new language hosted in wiki.archlinux.org, please open a request in Help talk:I18n. Note that a minimum number of translated articles will be required by the administrators for the request to be fulfilled. The following checklist summarizes the steps needed to add a new language:
- Notify about the new language in Help talk:I18n. Make sure to include the information needed to fill out the #Languages table.
- Create a base language category under Category:Languages and add the translated articles to it or a subcategory.
- A maintainer should update the #Languages table.
- Translate at least Main page, Arch Linux, Installation guide and General recommendations.
- Initialize a translation of Table of contents: it will then be kept up to date with a bot, see below.
- An administrator should consider the request; a maintainer should then update the #Languages table accordingly.
- An administrator should add the language prefix to Special:Interwiki and update AbuseFilter/4 and AbuseFilter/13.
- Developers should update the respective ArchWiki:Bots to support the new language.
If you want interlanguage links to be set for a new or existing language that has set up a separate wiki, please open a request in Help talk:I18n: the interlanguage links will be set as soon as possible!
Moving local languages to external wikis
Moving local languages to their own wikis is a very welcome and encouraged thing, which will get all the assistance that is needed. There are two possible procedures:
- First move all the articles to the external wiki. Once done, update the interlanguage links to point to the new domain, then fix all their target titles with the new ones. Finally, either delete the local articles, or, upon authorization from the ArchWiki:Maintenance Team, redirect them to the external wiki using the interlanguage links.
- Set up temporary interlanguage links (e.g.
[[ja-temp:Title]]) and use them to redirect the various articles to the external wiki as they are moved one by one. Once the move is complete, point the regular interlanguage links (i.e.
[[ja:Title]]) to the external wiki, and update them all with the new target titles. Next, either delete the local redirects, or, upon authorization from the ArchWiki:Maintenance Team, update them to use the regular interlanguage links. Finally, disable the temporary interlanguage links.