Search translations

The action specified, <kbd>$1</kbd>, is not recognised.

Delete <kbd>Main Page</kbd>.

Delete <kbd>Main Page</kbd> with the reason <kbd>Preparing for move</kbd>.

Get page information about the pages returned for a search for <kbd>meaning</kbd>.

Unrecognised topic {{PLURAL:$2|name|names}} for the <kbd>growtharticletopic:</kbd> keyword: $1

Unrecognised topic {{PLURAL:$2|name|names}} for the <kbd>articletopic:</kbd> keyword: $1

There seems to be a problem with your login session;
this action has been cancelled as a precaution against session hijacking.
Please resubmit the form.

Input to MediaWiki should be NFC-normalised UTF-8. MediaWiki may attempt to convert other input, but this may cause some operations (such as [[Special:ApiHelp/edit|edits]] with MD5 checks) to fail.

Parameters that take multiple values are normally submitted with the values separated using the pipe character, e.g. <kbd>param=value1|value2</kbd> or <kbd>param=value1%7Cvalue2</kbd>. If a value must contain the pipe character, use U+001F (Unit Separator) as the separator ''and'' prefix the value with U+001F, e.g. <kbd>param=%1Fvalue1%1Fvalue2</kbd>.

Some parameter types in API requests need further explanation:

Deprecated in favour of [[Special:ApiHelp/flow+lock-topic|action=flow&submodule=lock-topic]].

Unrecognised token "$2" at character $1.

Action header tab text colour

Action header tab border colour

The provided NetworkSession authorisation token failed to authenticate.

The specified action was not recognised.

Action header selected tab text colour

Action header new tab text colour

Adds customisable &lt;select&gt; for inserting text via database fetching

No approved grant was found for that authorisation token.

Use a different licence

Limit page images to a certain licence type

Developers should use the form below to request a token for a new OAuth 2.0 client (see the [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth extension documentation] for more details). After submitting this form, you will receive a token that your application will use to identify itself to MediaWiki. Depending on what capabilities you request, an OAuth administrator might need to approve your application before it can be authorised by other users.

A few recommendations and remarks:
* Try to use as few scopes as possible. Avoid scopes that are not actually needed now.
* Versions are of the form "major.minor.release" (the last two being optional) and increase as scope changes are needed.
* You can use a project ID to restrict the consumer to a single project on this site (use "*" for all projects).

'$1' is not a recognised project.

Use colourblind-friendly scheme

'''Discouraged:''' WebAuthn (Web Authentication) is a web standard published by the World Wide Web Consortium (W3C). WebAuthn is a core component of the FIDO2 Project under the guidance of the FIDO Alliance. The goal of the project is to standardise an interface for authenticating users to web-based applications and services using public-key cryptography. [https://en.wikipedia.org/wiki/WebAuthn Read more]. Please note that you will need to login to the same wiki where you originally registered your verification device. You also have to configure your browser to accept cookies from all the other sister wikis. If you do not know how to do this, you might not be able to login. This method is therefore not advisable for most users right now.

Developers should use the form below to propose a new OAuth 1.0a consumer (see the [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth extension documentation] for more details). After submitting this form, you will receive a token that your application will use to identify itself to MediaWiki. Depending on what capabilities you request, an OAuth administrator might need to approve your application before it can be authorised by other users.

A few recommendations and remarks:
* Try to use as few grants as possible. Avoid grants that are not actually needed now.
* Versions are of the form "major.minor.release" (the last two being optional) and increase as grant changes are needed.
* Please provide a public RSA key (in PEM format) if possible; otherwise a (less secure) secret token will have to be used.
* You can use a project ID to restrict the consumer to a single project on this site (use "*" for all projects).