Manual:Magic words/hu



A varázsszavak olyan változók, amelyekkel wikisztringeket rendelhetünk funkciókhoz. A változók és az értelmezőfunkciók is erre támaszkodnak. Minden, az ehhez az azonosítóhoz rendelt szöveg helyén a funkció visszatérési értéke fog megjelenni. A sztringek és az azonosító közti kapcsolatot a $magicWords változó tartalmazza, amely a $wgExtensionMessagesFiles segítségével betölthető fájlban található. Both variables and parser functions use this technique. All text mapped to that ID will be replaced with the return value of the function. The mapping between the text strings and the ID is stored in the variable  in a file that can be loaded using.

Az alapértelmezett varázsszavakat a tartalmazza.

Hogyan működnek a varázsszavak
Whenever MediaWiki finds text between double braces it must decide whether XXX is a variable, parser function, or template. To do so, it asks a series of questions:


 * 1) Egy varázsszó azonosítója-e? A MediaWiki első lépésként a   szövegben szereplő „XXX-et” a $magicWords tábla alapján megpróblája varázsszóként értelmezni.
 * 2) *Ha nincsen hozzárendelt azonosító, akkor a szoftver az „XXX” karaktersort sablonként értelmezi.
 * 3) Változó-e? Ha egy varázsszóhoz tartozik a szöveg, a szoftver ellenőrzi, hogy vannak-e paraméterei.
 * 4) * Ha nincsenek, a MediaWiki ellenőrzi, hogy az azonosító változóként van-e deklarálva; ezt a  segítségével teszi meg. Ezzel a módszerrel a szoftver egyrészt a változók nyers listáját nyeri ki (lásd: Segítség:Változók), másrészt az egyedi változókhoz rendelt hookokat (MagicWordwgVariableIDs). To check this, it retrieves the list of magic words serving by calling  . This method gets its list of variable IDs from a hard coded list of variable IDs (see ) and from a list of custom variable IDs provided by all functions attached to the hook.
 * 5) **Ha az azonosító változóként lett azonosítva, a MediaWiki meghívja az esemény nevéhez rendelt funkciókat, majd a varázsszó megtalálásakor annak értékét adja vissza.
 * 6) Is it a parser function? If there are any parameters or if the magic word ID is missing from the list of variable magic word IDs, then MediaWiki assumes that the magic word is a parser function or template.  If the magic word ID is found in the list of parser functions declared via a call to , it is treated as a parser function and rendered using the function named  .  Otherwise, it is presumed to be a template.
 * 1) Is it a parser function? If there are any parameters or if the magic word ID is missing from the list of variable magic word IDs, then MediaWiki assumes that the magic word is a parser function or template.  If the magic word ID is found in the list of parser functions declared via a call to , it is treated as a parser function and rendered using the function named  .  Otherwise, it is presumed to be a template.
 * 1) Is it a parser function? If there are any parameters or if the magic word ID is missing from the list of variable magic word IDs, then MediaWiki assumes that the magic word is a parser function or template.  If the magic word ID is found in the list of parser functions declared via a call to , it is treated as a parser function and rendered using the function named  .  Otherwise, it is presumed to be a template.

{{note|1= By convention:


 * The magic words called variables are capitalised, case-sensitive and do not have space characters.
 * Parserfunctions are prefixed with a hash sign ( {{# ), are case insensitive and do not include space characters.

This is however a convention and one not consistently applied (for historic reasons).


 * Variables do not have space characters, but some translations of variables in other languages DO have spaces
 * Variables generally are capitalised and case-sensitive, but some parser functions also use this convention.
 * Some parser functions start with a hash sign, but some do not.

Where possible you should follow the conventions when defining or translating magic words. Magic words are higher in priority than templates, so any magic word defined, will block the usage of that defined name as a template. Following the conventions avoids adding more and more potential collisions. }}

Defining magic words
For magic words to do their magic we must define two things:


 * a mapping between wiki text and a magic word ID
 * a mapping between a magic word ID and some php function that interprets the magic word.

Mapping wiki text to magic word IDs
The variable $magicWords is used to associate each magic word ID with a language-dependent array that describes all the text strings that mapped to the magic word ID. Important: This only sets up the back end i18n mapping, you still have to write other code to make MediaWiki use the magic word for anything. Also, make sure that you initialize  as an empty array before adding language-specific values or you will get errors when trying to load the magic word and will need to rebuild your localization cache before it will work.

The first element of this array is an integer flag indicating whether or not the magic word is case sensitive. The remaining elements are a list of text that should be associated with the magic word ID. If the case sensitive flag is 0, any case variant of the names in the array will match. If the case sensitive flag is 1, only exact case matches will be associated with the magic word ID. Thus the format is

This association is created by $magicWords in a file registered using.

In the example below, a Spanish MediaWiki installation will associate the magic word ID 'MAG_CUSTOM' with "personalizado", "custom", "PERSONALIZADO", "CUSTOM" and all other case variants. In an English MediaWiki only "custom" in various case combinations will be mapped to 'MAG_CUSTOM':

File :

In part of the extension.json file:

Note that "ExampleMagic" is a different to the key you would use for a plain internationalization file (normally just the title of the extension, i.e. "Example"). "Magic" has been appended deliberately so one does not overwrite the other.

In inline PHP
You can associate magic words inline in PHP rather than through a i18n file. This is useful when defining hooks in  but should not be done in extensions.

Associating a magic word ID with a PHP function
The mechanism for associating magic word IDs with rendering functions depends on whether the magic word will be used as a parser function or a variable. For more information, please see:



Localisation

 *  See Help:Magic words#Localisation for help. 

You can read more on definition and usage of magic words for localisation at Manual:Messages API, Manual:Language#Namespaces; Avoid  in messages.

Behavior switches (double underscore magic words)
Behavior switches are a special type of magic word. They can be recognized by their use of double underscores (rather than double braces). Example:

These magic words typically do not output any content, but instead change the behavior of a page and/or set a page property. These magic words are listed in and also at Help:Magic words#Behavior switches. The effect of most standard behavior switches is defined in. If no specific effect is defined, the magic word will simply set a page property in the page_props table. This can also be checked later by testing if  is null or the empty string

Custom behavior switch
Here is an example extension implementing a custom __CUSTOM__ behavour switch

custom/extension.json - This is minimal, a real extension would fill out more fields. custom/custom.i18n.php

custom/MyHooks.php