Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://translatewiki.net/wiki/Translating:MediaWiki below:

Translating:MediaWiki - translatewiki.net

MediaWiki is open source wiki software on which this site runs, and which can be translated here. Support for translating hundreds of MediaWiki extensions is also available.

Translators may add MediaWiki to their babel box or include {{User MediaWiki}} to add themselves to Category:MediaWiki translators.

A brief explanation of the most essential terms used in this document:

MediaWiki

The software that powers Wikipedia and many other websites. It allows people to edit pages in collaboration.

Wikimedia

The organization that maintains Wikipedia, Wikidata, and several other websites, as well as the MediaWiki software.

Message

A translatable string.

Message documentation

While translating, documentation about the message is shown on the sidebar next to the translation. It is also known as "qqq" in MediaWiki developers' jargon.

For a more detail glossary of basic MediaWiki terms, see Translating:MediaWiki/Basic glossary.

You made some changes here? This is what happens then and how long it takes to take effect.

Export threshold

Messages do not start to be exported to MediaWiki until at least 13% of the core MediaWiki messages in that language have been translated (used to be 18%): under such amount, the export scripts automatically skip the language in question and developers won't add support for the language on MediaWiki. The threshold corresponds to the number of all most used messages in MediaWiki or more; see also Translatewiki.net languages.

Wikimedia sites—Wikipedia, Wikidata, Wikisource, Wikivoyage, etc.

Interface message changes should be reflected in projects once per week along with the usual deployments.

Everything else

New translations are shipped with each new MediaWiki release (1.x) and usually with maintenance releases too (1.x.y). There are only a few releases per year, and many sites do not update often.

MediaWiki is one of the few software packages that allow its users to translate it using itself. Thanks to translatewiki.net, however, localising it is even easier and more efficient. In addition to the general advantages of this wiki, compared to local translation:

• Your translations are used on every MediaWiki wiki, this includes every Wikimedia wiki, see #Translation flow.
• You can translate new messages faster than on a local wiki.
  We always have the latest version of the software. This means new messages show up much faster than on any other wiki and you have more time to translate them before they arrive to your wiki. This can also mean translatewiki.net uses an unstable version, but problems are usually solved quickly.
• The only drawback is that your translations will not show up on your local wiki immediately, but after a few days to weeks; or, if you are using a release version, after the next update. However, for the previous point, there's no reason to be in a hurry: just check new messages regularly and translate them in time.
  See FAQ#How is the work done on translatewiki.net connected to other wikis?.

All MediaWiki extensions are supported as long as they are in Wikimedia's Git repository or in GitHub and their developers are supportive enough of translators.

If you don't want your extension to be added to translation, because you're going to soon change many messages completely or to delete the extension altogether, please state it clearly somewhere so that we don't add it when it's still too soon. In both cases, cc Raymond to a changeset on gerrit if you feel your extension's case might have been neglected.

• For an English glossary of MediaWiki specific terminology see Meta-wiki.
• MediaWiki translation supports plural rules, grammar functions and gender. See also the general Localisation guidelines.
• Contacts:
  • For MediaWiki core and main extensions: none defined, see mw:Developers/Maintainers and mw:Gerrit/Navigation#System messages.
  • For Semantic MediaWiki extensions: Kghbln.

Translators of other projects can ignore this list.

• First translate the most often used messages.
• Complete the core messages.
• Check if you should translate any optional messages in core.
• Do a consistency check (terminology, formal/informal) on your localisation.
• Translate special page names, magic words and namespaces on [[Special:AdvancedTranslate]] (temporarily disabled; see the section #AdvancedTranslate in this document and phab:T109235)
• Translate the extension messages used in Wikimedia wikis. There are more than 10,000 messages there, so for your convenience they are further subdivided into groups: main, advanced, media, fundraising, technical, etc.
• After completing an extension, it's recommended to check whether there are any optional messages that should be translated. (Click "..." at the top of the translation interface and check the "Optional" box.) If they will be the same in your language as in English, don't translate them.
• Translate the remaining extension messages.
• Do a consistency check (terminology, formal/informal) on your localisation between core messages and extension messages
• Start maintaining your language's localisation on a regular basis. At least once per week is recommended.

Read on if you want to know more. Reading on is not required, although advised for a proper understanding of more advanced localisation features. You could spend a few days translating, though, and come back when you think you need more information.

Every message is identified by a unique key. A message key is a string. In the translation interface, the key appears above the source message as MediaWiki:message-key/language-code. On translatewiki, the message key is also used as the title of the wiki pages on which the source message and the translations are stored.

Most of the time, the translators don't need to deal directly with message keys. However, they are sometimes necessary. Here are the main reasons for using them:

1. If you use a wiki in your language and you see a missing or a wrong translation and you want to fix it as directly as possible, you can find the precise message key by adding the string ?uselang=qqx to the URL of the wiki page. For example, if you're looking at the article Bali at the Indonesian Wikipedia and you see that something is not translated, go to the page https://id.wikipedia.org/wiki/Bali?uselang=qqx, and you'll see message keys instead of actual translations: instead of "Masuk log" you'll see "(pt-login)". Use that key to go the corresponding page in translatewiki: MediaWiki:Pt-login/id.
   • If the page's URL already has a question mark, then instead of ?uselang=qqx, write &uselang=qqx; for example, editing the same article is done on the URL https://id.wikipedia.org/wiki/Bali?veaction=edit, and to see it with keys instead of messages, go to the URL https://id.wikipedia.org/wiki/Bali?veaction=edit&uselang=qqx.
2. If there is an issue with a message, such as missing documentation, unclear English formulation, or anything else, you should report this message to the developers using the Support page or Phabricator. When reporting, it's essential to mention the message key. If you use the Ask for more information link in the translation interface, the key will be mentioned automatically in the bug report, but sometimes you may have to use it manually.

On most wikis there is a page called Special:AllMessages. It helps you examine all the messages and their translations and local modifications. Administrators should regularly check that page and remove unnecessary local customizations.

Many messages use symbols such as ==, ===, [[]], {{}}, *, #, and so on. This is wiki syntax, also known as "wikitext" or "wiki markup". This is not a requirement, but it is recommended to be familiar with some wiki syntax by editing a few pages on another wiki site, such as Wikipedia, before translating MediaWiki messages at translatewiki.

Here are the most common and basic elements of wiki syntax that you should know:

[[target]]

Square brackets create a link to the word in the brackets.

[[target|text]]

When a pipe (|) is used in a link, the link will point to page whose name appears before the pipe (target), and the readers will see the text that appears after the pipe (text). Usually, the "text" should be translated to your language, but the target must remain in English, especially if the target is a special page such as [[Special:RecentChanges]]. If in doubt, check the documentation.

==, ===, ====

Repeated equal marks in the beginning and the end of the line are used to create page section headings. Simply copy them to the translation, and translate the text of the heading itself to your language. Make sure that the same number of equal signs appears in the beginning and the end of the line, and that it's the same as in the source message.

{{template}}, {{magicword}}, {{#magicword:parameter1|parameter2}}

In wiki sites curly braces are most often used for inserting templates, pieces of text that are stored once and are included repeatedly on many pages. They are also occasionally used for "magic words". In messages on translatewiki templates are not used frequently, however many messages include magic words. The most frequent magic words in messages are {{plural}} and {{gender}}. For more information, see the section on magic words on this page. If a magic word begins with #, it must appear in the translation. Usually, the names of templates and magic words must remain in English, but parameters can often be translated. When in doubt, check the message documentation or ask at Support.

*

When the asterisk (*) appears in the beginning of a line, it creates an item in a bullets list.

#

When the number sign (#), also known as hash mark, octothorp, hex, pound, etc., appears in the beginning of a line, it creates an item in a numbered list.

Most of what you will be translating is English text. However, some parts will be more technical: these are "variables" and "magic words". Here are the main ones that you need to know.

Many messages must show things that are not known during the time of the translation. The value is known only when the message is shown to the user ("run time"). Common examples of things that are shown instead of $1, $2, $3, etc. are usernames, page names, file names, and various numbers. They are known variables, parameters, or placeholders.

The documentation explains what will these variables be replaced with. Examples:

• The message is "You received a message from $1" and the documentation says: "$1 is a username". When the message is shown to a user who received a message from the user Amire80, the message will say "You received a message from Amire80".
• The message is "There are $1 pages in the category $2" and the documentation says: "$1 is the number of pages and $2 is a category name", then when you look at the category "19th-century Russian monarchs", the message will say "There are 7 pages in the category 19th-century Russian monarchs".

Put these variables in the place where the corresponding words or numbers appear in your language. It doesn't have to be the same as in English.

Note that you must always use the Western Arabic numerals: 1 2 3 4 5 6 7 8 9 0. If your language uses different numerals, such as ١ ٢ ٣, १ २ ३, ߁ ߂ ߃, etc. remember to switch your keyboard and use the Western Arabic numerals 1 2 3, etc., in variables with the dollar sign ($).

If you see something like $1 {{PLURAL:$1|page|pages}} in a translatable message, this means that the word will be shown according to the value of the variable $1. Note that you must not change the PLURAL:$1 part, but you must translate the page|pages part which gives a list of translated plural forms.

Different languages have different grammatical rules for plural forms. English has one form (singular) for the number 1, and the plural form is used for zero and for all the other numbers: 0 pages, 1 page, 2 pages, 10 pages, etc. Polish uses singular for number 1, and different plural forms for numbers 2, 3, 4, and numbers from 5 and up. The translation to Polish will be $1 {{PLURAL:$1|strona|strony|stron}}; note that there are three forms, and not two, like in English. The output, depending on the number, will be:

• when $1 is 1: 1 strona
• when $1 is 2: 2 strony
• when $1 is 4: 4 strony
• when $1 is 5: 5 stron

The rules are defined in a standard called CLDR, which has information about many languages. If information about plural forms in your language is not defined, or if it is defined incorrectly, see the page CLDR for tips about how it can be fixed.

If your language has no plural forms at all, then simply write something like $1 {{PLURAL:$1|page}}, or $1 page{{PLURAL:$1|}} (with an empty list of forms when the invariable term is already placed elsewhere outside this special markup, but you must keep at least {{PLURAL:$1|}} to avoid a validation error where this code is required by the Translate UI in the translated message for the target language). Plural forms are given in parameters after the first pipe character | as a list of items, one for each form, and are also separated by pipes:

• The text for the plural form given in each one item may be prefixed by a distinctive "selector" keyword or numeric value, followed by an equal sign=. These selectors can only be used only once in the list of plural forms.
  • The following selectors are recognized: one (or 1, singular), two (or 2, dual), few (paucal), many (also used for fractions if they have a separate class), other (or in last position with no selector), or zero (or 0); reserved keywords used as selectors must also remain in English.
  • The selector zero (or 0) is special and only supported in a few languages, and only with an explicit selector specified before the text of the translated form.
  • Note that the forms selected by zero, one or two do not necessarily mean that the numeric value is exactly 0, 1 or 2: the rules used to map one or more values to each any plural selector are language-specific and may only consider some digits in the numeric value; some values may also behave differently if they are integers and non-integers, or if there are decimals explicitly presented in the numeric value (including if they are all zeroes).
  • Some other selectors may be added (as defined in the CLDR standard) for languages needing them (see https://cldr.unicode.org/index/cldr-spec/plural-rules).
• All listed form (except the last one) that are not prefixed by an explicit selector in an item are assumed to use the implicit selectors one,two,few,many (in that order, and as appropriate in the target language, which may support only the 1st one for most common languages, or even none of them for example in some Eastern Asian languages). In Mediawiki, most selectors are implicit and mapped according to this order.
• The last given form not prefixed by an explicit selector in an item is assumed to use the implicit selector (other). This default form given is required (but its value may be empty text): it indicates the default form that will be returned (when none of the other selectors match the value specified in the 1st parameter between between PLURAL: and the 1st pipe|, using the plural rules defined for the target language). It is generally the most generic grammatical plural (for example used with large number values), but it may also be just the common singular form if there are no other suitable form, or if the terms must remain invariant according to the context of use, or if the language does not differentiate plural forms in the given terms (look at nouns, adjectives, verbs, pronouns, etc., or other alternate formulations).

For more technical information on PLURAL, see the page Plural.

Many messages depend on the grammatical gender of the users who are mentioned in them, masculine or feminine. Each logged in user can select their gender in their user preferences.

Here is an example of how gender is used in messages. The message is $1 {{GENDER:$1|mentioned}} you on {{GENDER:$1|his|her|their}} talk page, and the documentation says "$1 - user's name".

• If you use MediaWiki in English, the verb "mentioned" will be the same everywhere, because English verbs don't change with gender, but the pronoun will be chosen according to gender:
  • When user Jack, who set his gender to "he" (masculine) in the preferences, mentioned you, you will see the following: "Jack mentioned you on his talk page".
  • When user Jane, who set her gender to "she" (feminine) in the preferences, mentioned you, you will see the following: "Jane mentioned you on her talk page".
  • When user Lee, who didn't set their gender in the preferences, mentioned you, you will see the following: "Lee mentioned you on their talk page".
• If you use MediaWiki in Polish, the verb changes, but the pronoun in this sentence is the same. The translation to Polish is $1 {{GENDER:$1|wspomniał|wspomniała|wspomniał(a)}} o tobie na {{GENDER:$1|swojej}} stronie"
  • Jack wspomniał o tobie na swojej stronie.
  • Jane wspomniała o tobie na swojej stronie.
  • Lee wspomniał(-a) o tobie na swojej stronie.

If {{GENDER:parameter|forms...}}</nowiki> is used in the English message, but different gender forms are not needed in the translation to your language, just write {{GENDER:parameter|optional form}}</nowiki> with one form.

Do not translate the word GENDER and its following colon : into your language. It's a technical magic word, and it must remain in English.

For more technical information on GENDER, see the page Gender.

If you need to refer to the name of the site, you can use the magic word {{SITENAME}}. (It usually appears in the source message.)

If your language uses inflection or special punctuation, you should talk to the developers about implementing some support for it. Once this is done you can use forms like {{GRAMMAR:genitive|{{SITENAME}}}} to refer to the sitename in genitive.

You may also see HTML tags such as <strong>, <var>, <kbd>, <span>, and others in messages. You should usually copy the tags in the corresponding places in the translation. Sometimes you should translate the content inside these tags, and sometimes you should leave it as in the original message. Consult the documentation for each message.

Never translate magic words and HTML tags. They must always remain in English, as in the source message.

Links to special pages in messages must always follow the syntax: [[Special:EnglishName|Translated name]]

The "Special:EnglishName" part must stay as is. Just copy it into the translation. The "Translated name" part, after the vertical bar (|), is shown to the reader, so translate it into your language in a way that will look natural and convenient as a link target and a part of a sentence. If there is no vertical bar (|) followed by link text in the original message, add them in the translation.

Subpage names that appear after a slash (/) after the special page name must also be left untranslated. Take the following message as an example: [[Special:Log/delete|Deletion log]]. Don't translate "Special:Log/delete", but do translate "Deletion log". For example, when translating into Russian, write like the following: [[Special:Log/delete|Журнал удалений]].

Every page on a MediaWiki site belongs to a namespace.

The main namespace, also known as the content space or the article space, includes the main content pages of the site. For example, on Wikipedia the encyclopedic articles are in the main namespace, on Wikivoyage the tour guide pages are in the main namespace, and so on. Other namespaces are for pages of discussions, help, documentation, user pages, and so on. See details below.

The name of the namespace appears in the beginning of the page, except for the pages in the main namespace. For example, all the pages in the Help namespace have names such as "Help:Editing", "Help:Uploading", and so on.

Pages in most (but not all) namespace can have a corresponding talk page, and these talk pages are in namespaces of their own. The talk namespace of the main namespace is called simply "Talk", the talk namespace of the Help namespace is called "Help talk", and so on.

Namespace names can be translated. If they aren't translated, they will appear in the fallback language. English namespace names can always be used in links to pages instead of the translated names.

Avoid namespace names that are identical to language codes in any letter case. This will create ambiguity with interlanguage links.

The translated namespace names must be consistent with the translations of the same words in MediaWiki messages.

In the tables below, only the translation of the names in the "Namespace name" column is needed. The explanation is provided only for the convenience of the translators.

The namespaces that are used on all MediaWiki sites:

The following namespaces are used in extensions that are installed on many wikis, and should be translated as well:

Namespaces can also have aliases, meaning that multiple different translated strings can point to the same namespace.

Namespace names are not supported by the standard translation interface in translatewiki.net, but you can get them translated by using one of the following options:

• file a request on Support,
• directly request it on Phabricator (file a bug for the MediaWiki extension in question), or
• [with some command-line skills] do it yourself with gerrit.

If the sitename at your project is not localized, you should contact the other contributors at your project and find consensus about translation, then open a request at Phabricator; see m:Requesting wiki configuration changes.

On MediaWiki, much more can be localised: see mw:Manual:Language#What can be localised.

Languages with translation completion less than 0% are not committed to version control. If the project consists of multiple message groups, the limit is applied to each group separately.

Wikimedia Gerrit

Translation updates are exported to version control every day

GitHub

Translation updates are exported to version control every Monday and Thursday. (Export threshold is 25 %)

The numbers shown below are cached and may not show the latest status. See this stats page for always up-to-date statistics.

Add yourself to map See also: Category:MediaWiki translators — all users that registered their participation in their user page (including those not indicating their location).

• Translating:Group statistics
  • Translating:MediaWiki/Most often used messages – explains how this message group is defined.
  • Translating:MediaWiki/skins
  • Translating:MediaWiki/extensions
    • Main Wikimedia extensions – explains how this message group is defined.
  • Translating:MediaWiki/New languages
• Attributions for MediaWiki translation

• Group statistics in time – gives an overview of the number of languages that pass translation milestones in time (discontinued October 2010).
• Current version installed on translatewiki.net: 1.45.0-alpha

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4