Commons:Localization

From Wikimedia Commons, the free media repository
Jump to: navigation, search

Shortcut: COM:I18N· COM:INT

Other languages:
català • ‎English • ‎日本語 • ‎polski • ‎русский • ‎svenska • ‎中文

Wikimedia Commons is an international and thus multilingual project. While English is the default, the project is intended to be used and useful for users of every language. Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text. The internationalization and localization effort on Commons has several components.

  1. Software
    1. The MediaWiki software (and the extensions to it used by Commons)
    2. Customisable parts of the MediaWiki interface
    3. User scripts (especially gadget scripts, installable via your Preferences)
  2. Content
    1. Project pages
    2. Content pages (files, categories, galleries)
    3. Templates used on content pages and project pages


Software[edit]

MediaWiki default messages[edit]

MediaWiki is the software that Commons is run on. Translations of the MediaWiki interface (translations supplied with the installation of MediaWiki) are created on Translatewiki; please follow the link to contribute.

To check translatewiki localizations of a particular MediaWiki message, visit translatewiki:Special:Translations/MediaWiki: and enter the name of the MediaWiki message. To find the name of a particular MediaWiki message, visit the Commons page showing the message and add ?uselang=qqx to the URL. Reloading the page should then replace all message text with the name of the message producing that text. (Example using Commons:Localization)

MediaWiki messages can be accessed within Commons (eg in a template) via {{int:messagename}}, eg {{int:edit-conflict}} to access MediaWiki:edit-conflict. Localized versions of MediaWiki messages are stored in subpages named with the relevant language code, eg MediaWiki:edit-conflict/de and MediaWiki:edit-conflict/fr. Non-existent messages (including misspelling of actual messages) will display in angle-brackets (<message name>), such as the common mistake of coding "{{int:license}}" as "{{int:licensing}}" (which displays the incorrect result in angle-brackets as: <licensing>).

For a list of some MediaWiki messages which may be useful in templates, see Commons:Localization/useful MediaWiki messages. See also mw:Localisation and its system messages. See also Category:Internationalization templates using MediaWiki messages.

Commons MediaWiki: namespace custom messages[edit]

The text of default messages supplied with the installation of MediaWiki can be overridden locally.[1] In addition, completely new messages can be created in the MediaWiki: namespace for purposes of localization. In both cases, such "custom messages" will only be available on Commons' installation of MediaWiki.

User scripts[edit]

Content[edit]

About localization text in images see Translation text in images. For localization read below.

Project pages[edit]

Project pages (in the Commons: and Help: namespaces) are important to translate. If a new user visits Commons, s/he may not know much about Commons and its purpose. Project pages explain the scope of Commons, what content is appropriate and what content not, how uploading works and what rules are to be observed.

Important pages to translate:

Content pages[edit]

Content pages are categories, galleries, and file description pages. Localization of these has two elements:

  1. Standard text elements. These should normally be included via appropriate content templates. For example, a category may include the template {{See also}}, which provides the text "see also" in various languages. In a few cases, standard text elements that are part of the MediaWiki software can be accessed directly, using the construction {{int:mediawiki-message-name}}.
  2. Non-standard text elements. These are included directly on the page, but should be wrapped in translation templates so that if/when translations are added, the software can distinguish them. The usual means are the simple language templates or the {{LangSwitch}} or {{mld}} templates.

Content templates[edit]

Templates are strings of text that occur on dozens, thousands or even millions of pages. By translating the most widely used templates you can greatly extend the usefulness of Commons pages to speakers of your language who do not speak English or who do feel more comfortable in their native tongue. Template:Information for example is used on more than two million file description pages. It's just some short strings of text, but it can greatly help to make the information on the description pages be more accessible. (Not all templates can be translated, some don't need translation, because they are language-neutral).

If a template is already internationalised, it should be clear how to add a new language localization. (The template documentation should make this clear, or it may be obvious when you look at the template in edit mode.) If a template is not yet internationalised, see the section below.

The ten most used translatable templates (times used as of September 10 2009):

  1. Template:Information ‎(4,027,372 links)
  2. Template:Self ‎(1,811,453 links)
  3. Template:GFDL ‎(1,769,152 links)
  4. Template:Own (1,062,140 links)
  5. Template:Cc-by-sa-3.0-migrated ‎(1,014,619 links)
  6. Template:PD-old (722,305 links)
  7. Template:PD-self ‎(712,987 links)
  8. Template:Cc-by-sa-3.0 ‎(466,637 links)
  9. Template:BookNaviBar ‎‎(393,842 links)
  10. Template:Cc-by-sa-3.0,2.5,2.0,1.0 ‎(382,389 links)

Content internationalization methods[edit]

The major methods for internationalization are

  1. Autotranslate, using the {{Autotranslate}} template, which uses subpages in the standard /xx language code format to store localizations
  2. LangSwitch, using the {{LangSwitch}} template, which stores localizations within the page or template being translated.
  3. Simple list, using a header linking to different language versions of a page.
  4. Language templates, using the individual templates listed at Commons:Language templates
  5. Multilingual tags are templates devoted to translating a particular message, without providing any formatting, for re-use in multiple templates.
  6. MediaWiki messages - in a few cases, standard text elements that are part of the MediaWiki software can be accessed directly, using the construction {{int:mediawiki-message-name}}

Content templates with complex layouts tend to use {{Autotranslate}}, whilst simpler ones use {{LangSwitch}}. Content pages largely use LangSwitch or language templates, with a handful of MediaWiki messages. The "simple list" method is generally used only by project pages. Multilingual tags and most MediaWiki messages are normally used only by templates. For templates, {{TemplateBox}} facilitates creating a documentation page, including providing a standard explanation of how to localise the template for a new language version, given the specified internationalization method.

An additional method is demonstrated by {{talkbox}}, which supports the construction of talkpage templates (eg {{permprot}}). Here, the translations are stored in subpages of the calling template, and {{talkbox}} switches the content as needed. The approach is similar to autotranslate, but the setup of the subpages is slightly different, and there is no /layout subpage.

Autotranslate[edit]

Further information: Help:Autotranslate

Other[edit]

Notes[edit]

  1. "Default messages" includes those which are supplied as part of MediaWiki, and the additional wm- messages (eg MediaWiki:wm-license-information-description) provided by mw:Extension:WikimediaMessages.

See also[edit]

Help[edit]