text:
Help:A quick guide to templates

This is a quick overview of templates. Full details can be found in Help:Template.

Templates are pages in the template namespace. This means any page beginning with "Template:", such as Template:Templatename. The content of a template can be added to a page by typing.

Templates are used to add recurring messages to pages in a consistent way, to add boilerplate messages, to create navigational boxes and to provide cross-language portability of texts.

Creating and editing templates
You start a new template in the same way you would start a normal page. The only difference is that its title must start with Template:.

Once you have made the template, you can add to the pages you want to use it on.

If the template you want to edit looks like, you would go to Template:Expand to edit it. To get there, type in the URL to your address bar, search for it, or make a link in the sandbox and click on it.

Once you are there, just click "edit" or "edit this page" and edit it in the same way you would any other page. You can add anything you would add to a normal page, including text, images and other templates. Please be aware that your edit might affect many pages, so be cautious.

FAQ

 * Can I use a template in more than one project? : No, if you want to use it on two different language Wikipedias, for example, you would need to create it twice.
 * Are templates case sensitive? : Yes, except usually the first letter.
 * Can I add parameters? : Yes, see Help:Template for instructions.
 * How many templates can I use in a page? : As many as you like, but you can't use the same one more than 5 times.
 * I edited the template, so why didn't the page it is used on change? : There are some caching bugs. Refreshing by pressing Ctrl and F5 often helps.
 * Can I move a template to a new name? : Yes, this works in exactly the same way as normal page moves. When a page called for inclusion is a redirect page, the redirect target is included instead.

Examples

 * w:en:Template:Stub: an often used message
 * w:en:Template:Europe: a navigational template
 * w:cy:Template:Dosbarthiad biolegol: a template with parameters
 * w:en:Template:Familia and fr:Modèle:Familia: cross-language templates
 * w:eo:Ŝablono:El: a small, often used image
 * Wikibooks:Template:GeneralChemTOC: a horizontal menu bar

title: Help:A quick guide to templates


text:
Kmart to buy Sears for US$11 billion

November 17, 2004

Discount retailer Kmart Corp. announced Wednesday morning it will buy department store operator Sears, Roebuck & Co.. The deal is to cost $11.5bn and will lead to the creation of the third-largest U.S. retailer, after Wal-Mart and Home Depot, and replacing Target at number three.

The new company, which is to be called Sears Holdings and be based near Chicago, will have $55 billion in annual revenue and nearly 3,500 retail stores. Edward Lampert, the chairman of Kmart, will become the chairman of the new company, while Alan Lacy, current chairman and chief executive of Sears will be the new chief executive. Sears CEO Alan Lacy, speaking about the deal, promised up to $500 million a year in savings within three years from improved efficient, greater purchasing power and possible store closures. The stores will retain their current names.

The purchase will allow the two stores to sell each other's brands, including Craftsman Tools, Kenmore, and Lands' End from Sears, and Martha Stewart and Joe Boxer brands from Kmart. The move is considered a boon for Sears, which until recently has confined itself to malls, and can now sell its products in the many Kmart locations.

Shares of both companies soared after the announcement, Sears was up 22 percent on Wednesday, whilst Kmart gained 15 percent.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Kmart to buy Sears for US$11 billion


text:
Help:Edit summary

When editing an article, there is a small field labeled "Summary" under the main edit-box. It looks like this:

 * Edit Summary-2.png

Most projects highly recommend to use it to its full capacity, to summarize the changes made.

Capacity
The capacity is one line of 200 characters, with horizontal scrolling. A copy action of more, results in the rest falling off. Insertions do not work if the line is full, one has to delete text at the end (or elsewhere) first to make room. An insertion action of e.g. 10 characters in a line of 195 characters results in the first 5 characters being inserted.

Edit summary
The text in the edit summary box will appear in black italics on the Recent changes page, in the page revision history (see below), and on the Diff page.

In the case of a small addition to an article it is highly recommended to copy the full text of this addition to the summary field, giving a maximum of info with a minimum of effort. Put "ft" in front, as abbreviation of "full text"; this way the reader knows that checking the edit further does not make sense. These kinds of edits with this code "ft" allow checking of Recent changes, Page history and User contributions (see below) very efficiently, both for the user and for the servers.

If the addition is more than 200 characters, so it does not fit fully in the edit summary box, you should write a short summary of the changes you have introduced into the article. For an addition of e.g. 400 characters you can also save time by simply copying that into the summary field, the excess will fall off, and the first 200 characters will usually be acceptable as a crude "summary".

Unfortunately one can copy only one "line" (in the sense of the text until a newline) into the edit summary box. The contents of further lines can be pasted at the end of the line. Thus e.g. a bulleted "see also" list is cumbersome to put in the edit summary box. One possible workaround for a new list is putting the list on one line, separated by the asterisks for the bullets, copying it to the edit summary box, and then, in the main edit box, putting the newlines before the asterisks.

In addition to a summary of the change itself, the summary field may also contain an explanation of the change; note that if the reason for an edit is not clear, it is more likely to be reverted, especially in the case that some text is deleted. To give longer explanation, use the Talk page and put in the edit summary "see Talk".

After saving the page the summary can not be edited, an extra reason to avoid spelling errors.

An important guideline is always fill summary field. Even a short summary is better than no summary. An edit summary is even more important if you delete any text, otherwise people may think you're being sneaky. Also, mentioning a change but not another one can be misleading to someone who finds the other one more important; add "and misc." to cover the other change(s).

In addition to the distinction major/minor change, accurate summaries help people decide whether it is worthwhile for them to check a change. We've found that summaries often pique the interest of wikipedians with an expertise in the area. This may not be as necessary for "minor changes", but "fixed spelling" would be nice even then.

In the case of important omissions or errors in the edit summary, you can make a dummy edit just to put the correction in the edit summary.

Section title as automatic edit summary
When applying the section editing feature the section title is automatically inserted as initial version or first part of the edit summary. Put more details after this text. In the case that you provide a long summary yourself you can delete the section title in order to stay within the limit of 200 characters.

When inserting a section by applying section editing on the section before or after it, delete the automatic edit summary to avoid confusion.

Since MediaWiki version 1.3 (May 2004), the automatic part of the summary is no longer surrounded by "="-signs, but it appears in grey text, with the manually typed part being in black text. The old style remains in edits from that time.

Abbreviations
See Edit summary legend for a list of commonly used abbreviations in edit summaries.

"Post a comment" feature
When starting a new thread on a Talk page, optionally the "Post a comment" feature can be used. Then the edit summary is automatically the same as the new section header.

Places where the edit summary appears
The edit summary appears on the diff page, as well as in the following lists:

 * Lists of edits that the system can produce (containing some or all of their edit metadata):
 * all edits from a given time and/or up to a given number: Recent changes
 * for a given page: Page history
 * by a given user: User contributions
 * real time: see Wikipedia IRC channels

 * Lists of pages that have been changed, from a selection of pages:
 * from a user's list of watched pages, from a given amount of time ago: Watchlist (logged in users only)
 * from the pages linked from a given page, from a given amount of time ago and/or up to a given number: Related changes

 * These show the edit summary of the last edit. Since one is typically interested in all recent changes in these articles, with all edit summaries, these features are used in conjunction with the page histories of the articles shown.

 * List of new pages: shows the edit summary of the creation.

Searching
The Wikimedia search function can not search edit summaries, and they are not indexed by external search engines.

Upload summary
When uploading an image one can supply an upload summary, see image description page. It serves as edit summary for the creation of the image description page (in the case that the file name of the image is new) and as second part of the automatically created edit summary of the upload log (the first part giving the file name).

Rendering of wikitext; URLs
Text in edit summaries renders internal links, including piped links, and interwiki links, even when enclosed within and. Therefore, copying wikitext in the edit summary box may be preferable to copying text from the preview, except when one wants to save space.

Other wikitext coding is not interpreted.

When copying an external link from the preview into the edit summary box then, depending on the operating system, the "printable version" is copied, i.e. how it is normally rendered, and in addition, between parentheses, the URL; hence the same information as in the wikitext, but in a different format, and in addition the possible sequential number.

da, de, fr, ja

title: Help:Edit summary


text:
Help:Edit toolbar

In compatible browsers, an edit toolbar is automatically displayed with the edit box, provided that this has been set in the preferences. The functions are partly a typing aid, partly a reminder of required formats.

It works best with Internet Explorer, Mozilla, and Firefox.

Example of how to use it:

To make a piece of text an internal link, select it and press the third button.

In Mozilla and IE you get a select+click formatting, and if you click without a selection, it inserts sample text at the cursor. In other browsers, clicking on the button presents an explanation for each feature in an infobox.

If you do not want to display the toolbar, you can obtain some of the functionality of them using the Edit toolbar bookmarklets instead.

All of the toolbar options, and further editing options, are available in Bananeweizen's Firefox extension.

List of functions
(apart from the last two, these pieces of wikitext are obtained after selecting "abc")

abc abc abc [abc]

abc
$$abc$$ abc< /nowiki> --~

title: Help:Edit toolbar


text:
Help:Calculation

The software does not allow calculations, but one can use a piped link to a calculation with Google's calculator, with the label as answer, to demonstrate the numbers used in the computation. This way one can check for consistency, see the result with a higher accuracy, and also conveniently update the result.

E.g., in the case of the population density in the Netherlands:

482/km², giving 482/km².

With a suitable browser the evaluated expression pops up, so the link is useful even without following it.

Suppose that someone updates the population figure but not the density, than the next person can see that the density is not based on the latest figure, replace the first number, press Preview, follow the link, copy the new result to the link label, and save. Thus the update requires a minimum of effort.

Unfortunately, the result 482 has to be entered manually and consistency is not automatically maintained.

Without putting the result on the page
Alternatively, the user has to follow the link to see the result. Using Template:Popd is convenient and there is no redundancy, hence no worry about consistency:

gives:

title: Help:Calculation


text:
Template:Popd

 * Population:
 * Area: km&sup2
 * Population density (people/km&sup2)

title: Template:Popd


text:
Category:November 17, 2004

it:Categoria:17 novembre 2004

title: Category:November 17, 2004


text:
Help:Editing

General
To edit a MediaWiki page, click on the "Edit this page" (or just "edit") link at one of its edges. This will bring you to a page with a text box containing the wikitext: the editable source code from which the server produces the webpage.

The edit link of a page showing an old version leads to an edit page with the old wikitext. This allows restoring the old version. However, the edit link of a diff page gives the current wikitext, even if the diff page shows an old version below the table of differences.

After adding to or changing the wikitext it is useful to press "Show preview", which produces the corresponding webpage in your browser but does not make it publicly available yet (not until you press "Save"). Errors in formatting, links, tables, etc., are often much easier to discover from the rendered page than from the raw wikitext.

If you are not satisfied you can make more changes and preview the page as many times as necessary. Then write a short edit summary in the small text field below the edit-box and when finished press "Save". Depending on your system, pressing the "Enter" key while the edit box is not active (i.e., there is no typing cursor in it) may have the same effect as pressing "Save".

You may find it more convenient to copy and paste the text first into your favorite text editor, edit and spell check it there, and then paste it back into your web browser to preview. This way, you can also keep a local backup copy of the pages you have edited. It also allows you to make changes offline, but before you submit your changes, please make sure nobody else has edited the page since you saved your local copy (by checking the page history), otherwise you may accidentally revert someone else's edits. If someone has edited it since you copied the page, you'll have to merge their edits into your new version (you can find their specific edits by using the "diff" feature of the page history). These issues are handled automatically by the Mediawiki software if you edit the page in your web browser.

See also MediaWiki architecture.

Dummy edit and null edit
If the wikitext is not changed no edit will be recorded and the edit summary is discarded.

A dummy edit is a change in wikitext that has no effect on the rendered page, such as changing the number of newlines at some position from 0 to 1 or from 2 to 3 or conversely (changing from 1 to 2 makes a difference, see below). This allows an edit summary, and is useful for correcting a previous edit summary, or an accidental marking of a previous edit as "minor" (see below).

To refresh the cache of some item in the database a lesser kind of dummy edit, called a null edit, may be sufficient: one that does not cause any change in the wikitext, and no entry in the history, in Recent Changes, etc.: this can be done by opening the edit window and saving; a section edit is sufficient. See also A category tag in a template; caching problem.

Minor edits
When editing a page, a logged-in user has the option of flagging the edit as a "minor edit". This feature is important, because users can choose to hide minor edits in their view of the Recent Changes page, to keep the volume of edits down to a manageable level.

When to use this is somewhat a matter of personal preference. The rule of thumb is that an edit of a page that consists of spelling corrections, formatting, and minor rearranging of text should be flagged as a "minor edit". A major edit is basically something that makes the entry worth revisiting for somebody who wants to watch the article rather closely. So any "real" change, even if it is a single word, should be flagged as a "major edit".

The reason for not allowing a user who is not logged in to mark an edit as minor is that vandalism could then be marked as a minor edit, in which case it would stay unnoticed longer. This limitation is another reason to log in.

The wiki markup
In the left column of the table below, you can see what effects are possible. In the right column, you can see how those effects are achieved. In other words, to make text look like it looks in the left column, type it in the format you see in the right column.

You may want to keep this page open in a separate browser window for reference. If you want to try out things without danger of doing any harm, you can do so in the Sandbox.

Sections, paragraphs, lists and lines
Summarizing the effect of a single newline: no effect in general, but it ends a list item or indented part; thus changing some text into a list item, or indenting it, is more cumbersome if it contains newlines, they have to be removed; see also w:Wikipedia:Don't use line breaks.

Character formatting
See also

Templates
Some part of a page may correspond in the edit box to just a reference to another page, in the form, referring to the page "Template:name" (or if the name starts with a namespace prefix, it refers to the page with that name; if it starts with a colon it refers to the page in the main namespace with that name without the colon). This is called a template. For changing that part of the page, edit that other page. Sometimes a separate edit link is provided for this purpose. A convenient way to put such a link in a template is with a template like m:Template:ed. Note that the change also affects other pages which use the same template.

Page protection
In a few cases the link labeled "" is replaced by the text "" (or equivalents in the language of the project). In that case the page cannot be edited.

Position-independent wikitext
Wikitext for which the result does not depend on the position in the wikitext page:

 * interlanguage links (see also above) - the mutual order is preserved, but otherwise the positions within the page are immaterial
 * category specification - ditto
 * ,, see Help:Section

Separating edits
When moving or copying a piece of text within a page or from another page, and also making other edits, it is useful to separate these edits. This way the diff function can be usefully applied for checking these other edits.

Error message
If, due to server problems, a save command results in an error message, either the saving has failed, or just the confirmation. Check e.g. My Contributions to find out.

title: Help:Editing


text:
Help:Editing toolbar

In compatible browsers, an edit toolbar is automatically displayed with the edit box, provided that this has been set in the preferences. The functions are partly a typing aid, partly a reminder of required formats.

It works best with Internet Explorer, Mozilla, and Firefox.

Example of how to use it:

To make a piece of text an internal link, select it and press the third button.

In Mozilla and IE you get a select+click formatting, and if you click without a selection, it inserts sample text at the cursor. In other browsers, clicking on the button presents an explanation for each feature in an infobox.

If you do not want to display the toolbar, you can obtain some of the functionality of them using the Edit toolbar bookmarklets instead.

All of the toolbar options, and further editing options, are available in Bananeweizen's Firefox extension.

List of functions
(apart from the last two, these pieces of wikitext are obtained after selecting "abc")

abc abc abc [abc]

abc
$$abc$$ abc< /nowiki> --~

title: Help:Editing toolbar


text:
Help:Enhanced recent changes

The preferences can be set to use the Enhanced Recent Changes feature (not for all browsers) instead of the classical Recent Changes. It groups recent changes per day by article, displays the titles of the changed articles in order from new to old latest change, or in the case of hiding minor edits, latest major change (send ideas for improvement to Magnus Manske, the author of this feature).

Multiple edits on the same day to a single article are grouped together on the Recent Changes screen. All the edits except for the most recent one are hidden, but can be revealed by clicking on the blue arrow next to the article. This option uses JavaScript, and won't work in every browser (see Browser issues with MediaWiki).

Composition of lines
(For the pages Wikipedia:Upload log, the corresponding pages on Wiktionary and Wikibooks, and perhaps a few more pages some links are not present).

Pages for which there is only one edit
The line shows:
 * time (the date is not shown here, it is in a header)
 * linked page
 * the link cur to the last edit made (even in the case that an edit has been made after loading the Enhanced Recent Changes, in which case it is not the edit shown! See below.)
 * hist linking to the page history
 * user, linked to his or her user page
 * Talk, linking to the user talk page
 * edit summary

Pages for which there are multiple edits
The top line, which is the only one shown before clicking on the arrow, shows:
 * time
 * linked page
 * number of edits
 * the link changes to the cumulation of changes, including the edits made after loading the Enhanced Recent Changes
 * Link Page history
 * the users, linked to their user pages

The lines per edit show:
 * time, linked to the page version then created
 * the link cur to the cumulation of all changes after this one, including the edits made after loading the Enhanced Recent Changes
 * the link last to this edit
 * user, linked to his or her user page
 * Talk, linking to the user talk page
 * edit summary

Exceptions for the first edit line (about the last edit to the page at the time of loading the Enhanced Recent Changes)
 * the link cur is to the last edit made (even in the case that an edit has been made after loading the Enhanced Recent Changes, in which case it is not the edit shown! Use of this link is not recommended, use "last" instead. See also below.)
 * the link last is to the cumulation of this change and those made after loading the Enhanced Recent Changes.

Examples
The default recent changes looks like this:
 * (diff) (hist) . . MediaWiki User's Guide: Editing mathematical formulae; 10:06 . . 111.222.33.44 (Talk) (Add examples)
 * (diff) (hist) . . M MediaWiki User's Guide: Editing mathematical formulae; 10:04 . . Anthere (Talk) (links)
 * (diff) (hist) . . N MediaWiki User's Guide; 10:04 . . Brion VIBBER (Talk) (New page)
 * (diff) (hist) . . Endnotes moved to Footnotes; 10:03 . . Maveric149 (Talk)

Enhanced recent changes shows changes to one page on the same line, with an arrow next to it:

http://www.wikipedia.org/upload/Arr_r.png 10:06 MediaWiki User's Guide: Editing mathematical formulae (2 changes; Page history)  [ 111.222.33.44; Anthere ] N. 10:04 MediaWiki User's Guide (cur; hist). . Brion VIBBER (Talk) (New page)  .. 10:03 Endnotes moved to Footnotes (cur; hist). . Maveric149 (Talk)

Clicking this arrow expands the entry so you can see all the changes made:

http://www.wikipedia.org/upload/Arr_d.png 10:06 MediaWiki User's Guide: Editing mathematical formulae (2 changes; Page history)  [ 111.222.33.44; Anthere ] . . . . . . 10:06</tt> (cur; last). . 111.222.33.44 (Talk) (Add examples) . . .. . <tt>M</tt> <tt>10:04</tt> (cur; last). . Anthere (Talk) (links) <tt>N</tt>  <tt>10:04</tt> MediaWiki User's Guide (cur; hist). . Brion VIBBER (Talk) (New page)  .. <tt>10:03</tt> Endnotes moved to Footnotes (cur; hist). . Maveric149 (Talk)

Complication
A confusing bug is the following: a "cur" link, that at the time of loading the Enhanced Recent Changes page corresponds to the last edit to a page, works differently if one clicks on this link after a new edit was made: one sees the new edit, not the one to which the line on the Enhanced Recent Changes page corresponds (and neither the cumulation of both, as the other cur links do). Thus, when trying to keep track of all changes, one misses that.

In the case that there are several changes to the page listed, one will usually use the "changes" link, and otherwise one can use the "last" link next to the buggy "cur" link.

However, if only one change is listed there is no "last" link. In that case it is useful to note the time of the listed change, and after clicking on "cur" check whether the table of differences gives an earlier time on the left, as it should. If it gives the same or a later time, one is looking as a later change, missing one or more. In that case get the revision history to get the cumulation of changes from the one one has not seen yet.

Common installation error
In projects outside Wikimedia it may happen that during installation one forgets (or perhaps it is missing in the installation instructions?) to copy three little image files:

http://www.wikipedia.org/upload/Arr_r.png http://www.wikipedia.org/upload/Arr_r.png

http://www.wikipedia.org/upload/Arr_d.png http://www.wikipedia.org/upload/Arr_d.png

http://www.wikipedia.org/upload/Arr_.png http://www.wikipedia.org/upload/Arr_.png (blank)

to the corresponding directory. As a result the enhanced Recent Changes are more cumbersome to use.

Next page: Using the Related Changes function >

title: Help:Enhanced recent changes


text:
Help:Downloading pages

Downloading a MediaWiki page
Webpage shows the possibilities for saving a local copy of a webpage. Alternatively (or in addition) one can copy the wikitext, i.e. the text in the edit box (the source code within the database).

Information in the webpage but not in the wikitext:

 * images
 * content of templates referred to
 * values of variables
 * existence at the time of saving of linked internal pages
 * date and time of the last edit before saving
 * in the Image namespace (image description pages): the image itself, the image history and the list of pages linking to the image
 * in the Category namespace: the lists of subcategories and pages in the category.

Information in the wikitext but not in the webpage:

 * comments (even though HTML also allows comments)

See also XML export, MediaWiki architecture.

Downloading some linked pages
When saving a local copy of some MediaWiki pages, note the following.

A link to e.g. the train article in Wikipedia is given in the HTML-code as /wiki/Train. This refers to http://en.wikipedia.org/wiki/Train. Depending on the browser (settings) the former may be changed into the latter when saving the page. To avoid this, apply View Source and save that.

Put the copy in folder C:\wiki (another drive letter is also possible, but wiki should not be a subfolder) and do not use any file name extension. This way the links work. Inconvenient is that you can not open a file in a folder listing by clicking on it, because of the lack of a file name extension.

A problem with saving the source code is that images are not saved automatically with the page. Saving them separately in a place corresponding to the HTML code is cumbersome, e.g. the first image of the train article would have to be C:/upload/thumb/c/c2/250px-Tile_Hill_train_550.jpg

If the images are more important than the mutual links, then use the browser option to save the webpage with images.

Of course variations are possible by changing the HTML-code oneself, e.g. changing http://en.wikipedia.org to C: and/or adding the file name extension .htm.

On some sites outside Wikimedia, instead of "\wiki" another folder has to be used, see MediaWiki User's Guide: URLs.

When downloading pages from different sites to the same folder \wiki on the same drive, note that a page name can only be used once.

title: Help:Downloading pages


text:
Help:EasyTimeline syntax

The EasyTimeline feature produces an embedded image from wikitext. The image can be a one-dimensional diagram (horizontally or vertically), or a two-dimensional one. The name "EasyTimeline" refers to the possibility to apply the feature with a time scale horizontally or vertically, possibly with another parameter in the other direction, but there are also various other possiblities.

See also EasyTimeline, EasyTimeline examples.

Introduction
Graphical timelines can be produced by providing a script between special tags:

EasyTimeline will then be invoked to render a PNG image and (optionally) a clickable map.

Disclaimer: Even when EasyTimeline is designed for ease of use, a complicated graphical timeline is a non-trivial affair. A simple timeline may take half an hour to compose (or even less, when a suitable example is taken as a basis). Large timelines may take a few hours for composition and fine-tuning. However, adding to or correcting a timeline, no matter how complex, should be a relatively straightforward affair, even for contributors who have no expert knowledge of the syntax described here.

Feel free to ask the author of EasyTimeline for advice.

Available commands
The script commands define:
 * Overall layout: ImageSize, PlotArea, Colors, BackgroundColors, AlignBars
 * Interpretation and presentation of dates and periods: DateFormat, Period, ScaleMajor, ScaleMinor, TimeAxis
 * Events, periods and descriptive texts: PlotData, TextData
 * How to order, divide, and name groups of events and periods: BarData, Legend, DrawLines
 * Shorthands for pieces of script code that occur multiple times: Define

The following commands are mandatory: ImageSize, PlotArea, Period and TimeAxis. At least one of the following commands is required: PlotData and/or TextData. Either or both can occur multiple times. All other commands are optional.

Case: Commands and their attributes can be specified in lower, upper or mixed case. Please try to be consistent in applying case as this will further readability, e.g. use mixed case for all commands and lowercase for all attributes.

General syntax rules
A script can contain commands and comments. Each command is followed by one or more attributes.

Commands
Commands should start on the first position of a line. Some commands can be followed by multiple lines of data and/or options. These extra lines should start with at least one space or be completely empty (the latter is useful for visually grouping related data lines).

Commands have the one of the following forms, depending on the type of command:

Command = attribute(s) DateFormat = dd/mm/yyyy Command name = attribute(s) Color Jp = value:red legend:Japan

Command = attribute(s)  attribute(s)  etc. PlotData = fontsize:XS width:20 bar:Japan from:start till:19/02/1945 color:JT bar:Japan from:19/02/1945 till:14/03/1945 color:AI

Comments
Single and multi line comments can be specified:
 * Text following the hash sign # will be regarded as a comment
 * Text between #> and <# will also be regarded as a comment. Comments can span multiple lines, when tagged this way.

Examples: Dateformat = dd/mm/yyyy # European date format

Period = from:01/09/1939 till:02/09/1945 #> this chart will show the complete duration of World War II <#

Attributes
When several attributes can be specified for a certain command, they are notated as 'name:value' pairs. When several values can be specified for one attribute they have to be enclosed between parentheses.

Examples: AlignBars = justify Color SB = value:rgb(0.8,0,0.7) legend:Sea_Battles

Parameters vs data items
Most commands only accept attributes that are specified on the same line.

Data blocks: some commands, like BarData, PlotData, TextData, Colors expect a data block consisting of one or more data lines. Data lines should start with one or more spaces. A data block is considered complete when a line starting with a non-space is encountered (exception: empty lines are ignored, they may be used to group related data lines within a block).

Attributes in a data block can conceptually be divided into parameters and data items. Data blocks can contain parameters and data items intermingled.

Data items: in data lines attributes text, from, till and at always apply only to the line in which they occur.

Parameters: in data lines attributes like color and fontsize have different implications depending on the context. If these parameters occur on a line without data items, they set new defaults for the data lines that follow. If they appear on a line mixed with data items they apply only to that line, thus overruling a default that was previously set.

Example:

 * 1) In this example two sets of bars are drawn, in red and blue respectively,
 * 2) but in each set one bar (marking war periods) will be drawn in green.

PlotData = color:red fontsize:S                              # set defaults bar:USSR from:1919 till:1922 text:Lenin           # red bar bar:USSR from:1922 till:1953 text:Stalin          # red bar bar:USSR from:1939 till:1945 text:WWII color:green # green bar bar:USSR from:1953 till:1964 text:Krushchev       # red bar color:blue                                        # change default color bar:US from:1913 till:1921 text:Wilson            # blue bar bar:US from:1917 till:1918 text:WWI color:green   # green bar bar:US from:1921 till:1923 text:Harding           # blue bar

even when the previous line does not start with a space<#
 * 1) > this multiline comment does not end command PlotData,

bar:US from:1923 till:1929 text:Coolidge          # blue bar

TextData =                                          # now PlotData is considered complete tabs:...etc

Special characters

 * #, #>, <# (hash, hash+"greater than", "less than"+hash): see Comments
 * ~ (tilde) in texts means: line break
 * ^ (caret) in texts means: tab
 * _ (underscore) in texts means: space
 * $ (dollar sign) precedes any user defined constant

Command Reference
For each command the valid attributes are listed. Some commands and/or attributes are optional (O).

For some commands certain attributes are mutually exclusive (will be explained where applicable).

AlignBars
Bars will always be drawn at equal distances. This command specifies whether the bars should be spaced as much apart as possible, or some white space should be reserved between the left/top side of the chart and the first bar or between the last bar and the right/bottom side of the chart.

 * early (default) : The first bar will be placed on the leftmost/topmost position of the chart ('glued' to the axis), leaving space between the last bar and right/bottom side of the chart.
 * late : Opposite from early: the last bar will be placed as far to the right/bottom side of the chart as possible, leaving space between the axis line (left/top side of chart) and the first bar.
 * justify : The first and last bars will be placed as far apart as possible, leaving no empty space on either side of the chart. When only one bar is present, justify will be interpreted as "centered".

BackgroundColors
This command allows the specifiction of background colors for various parts of the chart. Any color ids specified should be defined first using Colors.
 * canvas (O) : Specify a background color for the whole image.
 * bars (O) : Specify a background color for all bars.

Examples: BackgroundColors = bars:darkgrey

BackgroundColors = canvas:lightgrey bars:darkgrey

BackgroundColors = canvas:lightgrey

BarData
This is an optional command which if present determines which bars will be drawn on the chart and in which order. If it is omitted then bars will be drawn in order of their appearance in command PlotData.

For complex timelines with many bars, usage of this command is recommended:
 * It will ease reordering of the displayed data.
 * Bar names specified in PlotData can be validated against this list, thus preventing typing errors.

 * bar : defines the bar id. Other commands (notably PlotData) will expect this id for reference. This will also be the label to be shown along the axis, unless attribute text is present. The bar id should not contain any spaces: use underscores instead, these will be converted to spaces, as with article titles.
 * text (O) : When specified this specifies the text to be presented along the axis, instead of the bar id. See also rules for text input. The text may include one embedded link (see Note 1).
 * link (O) : Specify a web link (see Note 1) (URL). The label along the axis will be shown as a blue clickable link.

Notes
 * 1) Either use attribute link, or an embedded link in attribute text, not both.

Examples: BarData = bar:Japan bar:US      text:"United States"  # refer in PlotData to bar "US" but show "United States" bar:China   text:China        # label China will be shown as blue clickable link to the English Wikipedia article about China

The following lines produce the same output (only reference in PlotData changes): bar:US           text:United_States

bar:US           text:"United States" link:http://www.wikipedia.org/wiki/United_States

bar:United_States                     link:http://www.wikipedia.org/wiki/United_States

Colors
This command allows colors to be defined and coupled to an id (identification tag). Other commands will refer to colors with the id specified here. This command expects one or more color definitions, each on a separate indented line.

 * id :Other commands will use this id to specify text, bar or background colors.
 * value : Actual color definition. Color values can be either be specified as:
 * predefined color constant, for which 32 predefined color names are recognized (see the Ploticus color page where all these constants are defined).
 * rgb (red,green,blue): specify 3 numbers between 0 (minimal) and 1 (maximal)
 * hsv (hue, saturation, value): specify 3 numbers between 0 and 1
 * gray (value): specify a number between 0 (black) and 1 (white)
 * legend (O) : Specifies the text that should be displayed in the legend for this color. If this attribute is omitted no entry will appear in the legend at all. See Text Input for rules.

Example: Colors = id:war      value:red   legend:War Period id:peace    value:blue  legend:Peace Time id:treaty   value:rgb(0.6,0,0.6) id:lightgrey value:gray(0.9) id:darkgrey value:gray(0.1)

DateFormat
This command defines how dates, specified in other commands, should be interpreted.

Valid dateformats are:

 * dd/mm/yyyy : Dates are interpreted as day/month/year
 * Note: this format is only allowed for dates starting from 01/01/1800

 * mm/dd/yyyy : Dates are interpreted as month/day/year
 * Note: this format is only allowed for dates starting from 01/01/1800

 * yyyy : this deals with integers from -9999 to +9999

Example: DateFormat = mm/dd/yyy

Define
This command allows definition of text constants, i.e. shorthands for pieces of script code that occur multiple times. Text constants should always start with a $ (dollar sign).

Example: Define $broad      = width:30 Define $narrow     = width:10 Define $bardefaults = $broad fontsize:S

DrawLines
Some timelines extend over several clearly distinct periods. A line demarcating these periods may serve as a visual aid.

Lines specified here will be drawn over the whole width/length of the chart (depending on the orientation defined by TimeAxis).

 * at : Specify the date/year where the line should be drawn, in compliance with the specified DateFormat.
 * color : Specify the color in which the line should drawn.
 * Note: The color id specified should be defined first with command Colors.

Example: LineData= at:start     color:red at:end       color:red at:07/12/1941 color:red

ImageSize (mandatory)
This command defines the overall size of the final image. Specify values in absolute measurements.
 * width : Width of final image: maximum is 1600 pixels
 * height : Height of final image: maximum is 1200 pixels

Example: ImageSize = width:800 height:600

Legend
A legend will only be shown when this command is present. There are several ways to define the appearance and position of the legend. Some attributes are mutually exclusive (see below).

 * orientation (O) : Specify hor[izontal] or ver[tical] (default).
 * Restriction: orientation = 'horizontal' and position = 'right' are mutually exclusive

 * position (O) : Defines placement of the legend relative to the chart area. Specify top, bottom (default) or right.
 * Restriction: orientation = 'horizontal' and position = 'right' are mutually exclusive

 * columns (O) : Specify 1, 2, 3 or 4. When this attribute is omitted the number of columns is determined as follows:
 * Orientation horizontal : Attribute columns does not apply here. All entries will be on the same line.
 * Orientation vertical :
 * Position right : All entries will be in one column
 * Position top or bottom : The number of columns depends on the number of entries to be shown: 1-5 entries: 1 column, 6-10 entries: 2 columns, 11 or more entries: 3 columns.

Tip: you may consider omitting the following parameters at first, and only add them when defaults settings are not satisfactory.
 * columnwidth (O) : Defines the distance between columns. You can specify an absolute distance or a relative distance (as percentage of the page width).
 * Restriction: this parameter is ignored when columns = 1 is defined or implied.

 * left (O) : Defines the distance between the left side of the legend and the left side of the page. You can specify an absolute distance or a relative distance (as percentage of the page width).
 * top (O) : Defines the distance between the top of the legend and the bottom of the page. You can specify an absolute distance or a relative distance (as percentage of the page height).

Examples: Legend = orientation:vertical position:bottom columns:3 columnwidth:140

Legend = orientation:horizontal position:bottom

Legend = left:100 top:120 columns:3

Period (mandatory)
Defines the time period that will be displayed in the chart. Both parameters are mandatory. Specify dates in compliance with specified DateFormat.
 * from : Timeline starts here. The specified value can be referenced as start in commands like PlotData and TextData.
 * till : Time ends here. The specified value can be referenced as end in other commands.

Example: Period = from:01/09/1939 till:02/09/1945

PlotArea (mandatory)

 * width : Specify value in absolute or relative measurements.
 * height : Specify value in absolute or relative measurements.
 * left : Margin between left side of image and left side of plot area. Specify value in absolute or relative measurements.
 * bottom : Margin between bottom of image and bottom of plot area. Specify value in absolute or relative measurements.

Examples: PlotArea = width:640 height:420 left:160 bottom:120

PlotArea = width:80% height:70% left:20% bottom:20%

PlotData
Used to define bars (symbolizing a time period), and add text next to these bars on a specific position.

For texts which are not related to a certain period or date/year or which require extensive formatting use command TextData.

Attributes text, at, from and till always apply only to the line on which they occur. All other attributes, when not combined with one these four, act as default for the remainder of the command block or until a new default is specified, and may be overruled for a single line. See Parameters vs Data Items for more info and an example.

PlotData accepts a lot of attributes, some of which are mutually exclusive. These attributes can be grouped as follows:
 * Positional attributes
 * Bar related attributes
 * Text attributes
 * Marker attribute

Positional attributes

 * at : Specifies at which date/year a text should be positioned. Depending on attribute align the text either starts, ends or is centered at this position. Use date/year format as specified in DateFormat or specify start or end which refers to time frame defined by command Period.
 * NB: This attribute can not be combined with attributes from or till.

 * from : Specifies at which date/year a bar should start. Use date/year format as specified in DateFormat or specify start which refers to time frame defined by command Period.
 * NB: This attribute should be used in combination with attribute till and can not be combined with attribute at.

 * till : Specifies at which date/year a bar should end. Use date/year format as specified in DateFormat or specify end which refers to time frame defined by command Period.
 * NB: This attribute should be used in combination with attribute from and can not be combined with attribute at.

 * shift : Specifies a horizontal and vertical displacement in absolute measurements for a text. This allows:
 * Texts to be shifted to avoid overlaps
 * Placement of text beside a bar, instead of on top of it.

Examples: PlotData= bar:Japan from:start     till:19/02/1945 color:JT bar:Japan from:19/02/1945 till:14/03/1945 color:AI bar:Japan from:02/09/1945 till:end       color:AO

at:07/12/1941 shift:(0,-15) text:"<-- WW2 reaches Asia"

Bar related attributes

 * bar : Specifies to which bar all other attributes apply.
 * When command BarData has not been used, bars will be drawn in the order in which they occur in any PlotData data block. The id specified here will also be the text presented along the axis, next to the bar.
 * When command BarData has been used, bars will presented in the order specified there, also the bar id specified here will be validated against that list. Also the text presented along the axis will depend on the definition in BarData.

 * color : Specifies the color is which the bar should be drawn.
 * The color id specified should be defined first with command Colors.

 * width : Specifies the width of the bar in absolute or relative measurements.

Example: BarData= id:US text:United States id:SB text:Sea Battles

Colors= id:US value:blue legend:United_States id:SB value:rgb(0.8,0,0.7) legend:Sea_Battles

PlotData= width=0.3                                                           # see note 1 bar:SB    from:07/08/1942 till:09/02/1943 text:Guadalcanal color:SB # see note 2 bar:US    from:start      till:end color:US                         # see note 3 bar:Midway from:start     till:end color:US                         # see note 4 bar:US    at:07/12/1941   text:7/12 Pearl Harbour                   # see note 5 Notes:
 * 1) this line establishes a default bar width for the remainder of the data block
 * 2) this line specifies a bar to be drawn and a text to placed on it at the same time
 * 3) bar US will be drawn before bar SB, even when specified after it, because command BarData determines the sequence
 * 4) bar Midway will be rejected because it is not declared with command BarData
 * 5) the last line will not result in a bar being plotted, it merely specifies on which bar the text should be placed

Text attributes

 * text : Defines a text that should be plotted on or near a bar. The anchor position can be defined either explicitly with attribute at, or implicitly with attributes from and till. In the latter case the text will be positioned in the middle of the defined bar segment. See also Text Input for rules
 * The text may include embedded links (see Notes 1 & 2) for use in clickable maps.

 * textcolor (O) : Defines the color of the text. The color id specified should be defined first with command Colors. When not specified color black will be assumed.
 * fontsize (O) : Specify a point size between 6 and 30, or (preferably) one of tags XS, S (default), M, L or XL. See Font Support for more details.
 * align (O) : Specify center (default), left or right.
 * link (O) : Specify a web link (see Note 1) (URL) for use in clickable maps. The text will be shown as a blue clickable link.

Notes
 * 1) Either use attribute link, or an embedded link in attribute text, not both.
 * 2) On PNG images only one clickable link will be shown per text segment (text with line breaks (~) constitutes several segments).

Example: PlotData= bar:US at:07/12/1941 align:left textcolor:black fontsize:XS text:7/12 Pearl Harbour

produces the same result as:

PlotData= bar:US at:07/12/1941 align:left textcolor:black fontsize:XS text:"7/12 Pearl Harbour" link:http://www.wikipedia.org/wiki/Pearl_Harbour

Marker attribute

 * mark : Places a marker in a bar at the specified position. Specify as mark:(symbol, color). The only value for symbol supported to date is line. The color id specified should be defined first with command Colors. When not specified color black will be assumed.

Example: PlotData= bar:test width:15 color:red from:1900 till:2000 at:1990 mark:(line,white)

will be shown as:

ScaleMajor
This command divides the timeline into smaller periods, either
 * Graphically, through thin vertical or horizontal lines in the chart
 * Textually, through stubs in the time axis, below or to the left of the chart
 * Both graphically and textually

Note: the orientation of the lines and/or placement of the stubs depends on the orientation of the TimeAxis.

 * gridcolor (O) : Defines the color for the grid lines. When this attribute is omitted no grid lines will be drawn.
 * Note: The color id specified should be defined first with command Colors.

 * unit (O) : Specifies the unit by which the grid spacing is incremented. Specify day, month or year (default).
 * Note: When DateFormat yyyy is specified, only unit year is allowed.

 * increment (O) : Specifies the numbers of units by which the grid spacing is incremented. Default is 1.
 * start (O) : Specifies where the first grid line and/or stub should be displayed. Defaults to start of defined Period.

Examples: ScaleMajor = gridcolor:red start:1940

ScaleMajor = gridcolor:red unit:month increment:3 start:01/09/1939

ScaleMinor
This command defines a further subdivision of the timescale. See ScaleMajor for syntax.

Example: ScaleMajor = grid:red unit:year  increment:1 start:01/01/1940 ScaleMinor = grid:blue unit:month increment:3 start:01/10/1939

TextData
Used to define a text block that can be positioned anywhere on the chart.
 * text : The actual text. See also Text Input for rules. The text may include embedded links (see Notes 1 & 2).
 * pos : Defines the top-left corner of the text block in absolute or relative measurements. Define as pos:(x,y).
 * link (O) : Specify a web link (see Note 1) (URL) for use in clickable maps. The label along the axis will be shown as a blue clickable link.
 * textcolor (O) : Defines the color of the text. The color id specified should be defined first using Colors. When not specified, the color is black.
 * fontsize (O) : Specify a point size between 6 and 30, or (preferably) one of tags XS, S (default), M, L or XL (see Font Support for more details).
 * tabs (O) : Defines position and alignment for tab character: ^ (caret). Specify multiple tab settings as tabs: (x1-a1,x2-a2,x3-a3, etc..) where
 * xn is the horizontal displacement in absolute measurements from the left side of the text
 * an is the alignment for the text segment (specify center, left or right)

Notes:
 * lineheight (O) : Defines spacing between consecutive lines in absolute measurements. Specify a value up to 40 pixels or 0.4in. When not specified a default lineheight will be based on the font size currently in use.
 * 1) Either use attribute link, or an embedded link in attribute text, not both.
 * 2) On PNG images only one clickable link will be shown per text segment (text with tabs (^) constitutes several segments).

Example: TextData = pos:(20,67) textcolor:black fontsize:S tabs:(10-right,14-left,50-left,90-left,230-left) text:^1^1940^27/9^Germany,Italy and Japan sign Tripartite Pact text:^10^1944^1-22/7^Bretton Woods 44 nations establish text:^^^^^IMF and World Bank will be shown as:

TimeAxis
Defines the orientation of the time axis, and textual representation of stubs along that axis.
 * format (O) : Specify in which format dates should be presented along the time axis.
 * Currently only format yyyy (default) is supported. More formats may follow.

 * orientation (O) : Specify hor[izontal] (default) or ver[tical].

Example: TimeAxis = orientation:horizontal format:yyyy

Presets
At the moment two presets are available:
 * Preset = TimeVertical_OneBar_UnitYear
 * Preset = TimeHorizontal_AutoPlaceBars_UnitYear

Not clear if whether there is documentation about them.

Scales for size and position
Absolute measures may be used for specifying sizes, positions and position shifts, measured in pixels.

Example: PlotArea = width:800 height:600 left:50 bottom:50

Relative measures may be used for specifying sizes and positions. Specify a number between 0 and 100, immediately followed by a % (percentage) sign. For horizontal measurements the percentage is related to image width, for vertical measurements to image height.

The first coordinate is horizontal from left to right, the second is vertically upward.

Example: PlotArea = width:80% height:80% left:10% bottom:5%

Text Input
Text input is subject to a few rules:

1 No unicode is allowed yet. See also font support.

2 When text should contain spaces, either specify these by using underscores or place the text between double quotes.
 * Exception: when the text attribute is the last attribute on a line, spaces are allowed (no confusion will arise where the text stops and the next attribute starts, that is—to be precise—when no colons occur in the text).

Example: (the following are all equivalent)

BarData = text:Japanese_mandate_since_1914 bar:Marshalls

BarData = text:"Japanese mandate since 1914" bar:Marshalls

BarData = bar:Marshalls text:Japanese mandate since 1914

3 In data lines following command TextData two characters have special meaning:
 * ~ (tilde) means line break
 * ^ (caret) means tab

Example showing line breaks: TextData = .. text:Generated for Wikipedia~Version 1.1 - 2 Januari 2004

 * 1) will be shown as:
 * 2)  Generated for Wikipedia
 * 3)  Version 1.1 - 2 Januari 2004
 * 1)  Version 1.1 - 2 Januari 2004

Example showing tabs: TextData = tabs:(4-right,12-right,14-left,34-left) text:^1^1940^27/9^Berlin Ger,It,Jap sign Tripartite Pact text:^10^1944^1-22/7^Bretton Woods 44 nations establish text:^^^^^IMF and World Bank

 * 1) will be shown as:
 * 2)      1    27/9 Berlin Ger,It,Jap sign Tripartite Pact
 * 3)     10  1-22/7 Bretton Woods 44 nations establish
 * 4)                                    IMF and World Bank
 * 1)                                    IMF and World Bank

Clickable maps
Both output formats available in MediaWiki, i.e. PNG and SVG, can contain clickable links. Texts shown in blue, and bars, may then be clicked, to surf to another web page.

Links can be specified with commands BarData, PlotData and TextData, either with attribute link, or as embedded links, via attribute text.

Embedded links
Embedded links are links that are (part of a) displayable text, specified with attribute text. Their counterpart are explicit links (URL only) which are defined with attribute link.

Both type of links can be specified with commands BarData, PlotData and TextData and are used for clickable maps.

In embedded links, internal link style is as usual, interwiki link style does not work, external link style is as usual with single brackets, but here with a pipe instead of a space. Blank spaces and underscores in the url should be written as %20.

Examples: text:example Help:Link internal link will be shown as: text:Link will be shown as:

text:|Rembrandt van Rijn paints Night Watch will be shown as:

Attempt to use interwiki link style:

text:Main_Page and similar with nl: and m: give:

The third one to Meta-Wikipedia works properly, except from Meta itself, the other links work like Main_Page (internal page, the prefix is ignored) or e.g. /w/Main_Page (gives File not found), depending on the URL of the referring page (e.g. different for a preview page and a diff page).

Font Support
No unicode is allowed yet. No font type can be specified yet.

Five font tags are predefined which will render at slightly different sizes in PNG and SVG images to produce optimal readability for both platforms. It is advised to use these tags instead of numbers whenever possible. They are: XS=eXtra Small, S=Small (default), M=Medium, L=Large, XL=eXtra large

This documentation is originally a wikified version of the original EasyTimeline documentation.

title: Help:EasyTimeline syntax


text:
User:CGorman

   UTC, Monday, 29 July About Me
 * Nationality: Irish
 * ID No.: 86
 * Main Pages Sports, Economy and business, Ireland
 * Currently Reading: 1984 by George Orwell
 * My Blog

Regularly Read
 * Irish Independent
 * The Sunday Times
 * Fortune Magazine
 * The Economist
 * Business Plus
 * BBC News Online
 * Westmeath Examiner
 * Westmeath Topic

Other Wiki Personas
 * MetaWiki
 * Wikipedia
 * Wikibooks
 * Wikisource
 * Wikiquote
 * Wiktionary

I'm not too active here at the moment because i'm working on a number of things...

Hey! I'm from Mullingar, Ireland and have been an active member of Wikinews since 17th November 2004. I believe whole heartedly in Wikinews in the long term and think it really could become a top news source. I am particularly interested in the Economy, Business, Music, Sport, (particularly swimming and GAA) and in general current events.

I am a member of the Welcommittee, so if you need help settling in to life as a Wikinewsies just drop a note on my talk page. I am also an Administrator. Im also a regular on wikipedia.

To date, i've made in excess of 5,750 edits to Wikinews and written over 140 individual news articles. I have the 3rd highest number of edits overall on Wikinews. For a list of the articles i've written see My Article Contributions.

As a group, Wikinewsies have penned a total of  articles since the project began - that means i've written about 1 in 20 wikinews stories, or 5% of the total!

NB Links/tools

 * Alphabetical list of Wikinewsies
 * Irish Wikinewsies
 * Edit Counter
 * Wikistats
 * Welcommittee
 * Water cooler
 * Awareness statistics
 * My Sandbox
 * Contributions
 * Country of the Week
 * Story preparation
 * Article distribution
 * Writing contest
 * Modelling Wikinews' growth
 * User:CGorman/Categories

Templates/Codes/Commands...
/msg nickserv identify

Wikinewsies worth knowing
I've got to say Wikinews is developing into a genuinely nice community, it is friendly, helpful, interesting and quite international. Some of the characters that make it so are listed below so that I can easily contact them.

 * Amgine - sailor Canadian - good techie
 * The bellman - Aussie with a bit o' humour
 * Carlosar - Very active Brazilan
 * Cspurrier - Computer consultant
 * Dan100 - Hard working, headstrong UK writer
 * Davodd - former professional journalist, good with the wikinews stats Gone
 * David Vasquez - Entusiastic writer Gone
 * Edbrown05 - New, but very entusiastic
 * Eloquence - Our own local version of Jimmy Wales!
 * IlyaHaykinson - Good techie
 * Kevin Baas
 * NGerda - hosts Audio Wikinews
 * Pingswept - The only optimist around here besides me on a rainy day.
 * Ronline - Our local Romanian reporter
 * Ryan524
 * Simeon - another Aussie, hard worker
 * Teeks99 - Aerospace engineer
 * VF - quite new, but proving himself in the Writing Contest

Awards!

fr:Utilisateur:CGorman

title: User:CGorman


text:
Help:Custom namespaces

If you want to add a custom namespace, you need to do the following:

 * 1) Pick the names of your namespace and it's talk page. Also pick numbers.
 * Note: Even numbers are for the main namespaces, odds for the talk pages. Custom pages start at 100.
 * Important: Do not include spaces in the name, use an underscore instead

 * 1) Goto /includes/DefaultSettings.php and copy the variables $wgExtraNamespaces, $wgNamespacesWithSubpages , and $wgNamespacesToBeSearchedDefault into LocalSettings.php
 * 2) Add to $wgExtraNamespaces the name of your namespace and it's talk page, as it would appear in a link.
 * Example:

$wgExtraNamespaces = array(100 => "Foo",              101 => "Foo_Talk");
 * 1) If you want subpages, add it to $wgNamespacesWithSubpages
 * Example:

$wgNamespacesWithSubpages = array( -1 => 0, 0 => 0, 1 => 1, 2 => 1, 3 => 1,              4 => 0, 5 => 1, 6 => 0, 7 => 1,                8 => 0, 9 => 1, 10 => 0,11 => 1,               100 => 1, 101 => 1 );
 * 1) If you want the new namespace (or it's talk page) searched by default, set $wgNamespacesToBeSearchedDefault
 * Example:

$wgNamespacesToBeSearchedDefault = array( -1 => 0, 0 => 1, 1 => 0, 2 => 0, 3 => 0,               4 => 0, 5 => 0, 6 => 0, 7 => 0,                8 => 0, 9 => 1, 10 => 0, 11 => 1,                100 => 1, 101 => 1 );

title: Help:Custom namespaces


text:
Help:Common words, searching for which is not possible

Some words cannot be searched for, because they are deemed too common. The following is a full list of those words. They are written as links, so that at least pages with a single common word as title can be found through this list.

If the exact title of an article is known or guessed, the Go button can be used; this feature is not affected by the above-mentioned restriction.

 * 1-1
 * a
 * a's
 * able
 * about
 * above
 * according
 * accordingly
 * across
 * actually
 * after
 * afterwards
 * again
 * against
 * ain't
 * all
 * allow
 * allows
 * almost
 * alone
 * along
 * already
 * also
 * although
 * always
 * am
 * among
 * amongst
 * an
 * and
 * another
 * any
 * anybody
 * anyhow
 * anyone
 * anything
 * anyway
 * anyways
 * anywhere
 * apart
 * appear
 * appreciate
 * appropriate
 * are
 * aren't
 * around
 * as
 * aside
 * ask
 * asking
 * associated
 * at
 * available
 * away
 * awfully
 * b
 * be
 * became
 * because
 * become
 * becomes
 * becoming
 * been
 * before
 * beforehand
 * behind
 * being
 * believe
 * below
 * beside
 * besides
 * best
 * better
 * between
 * beyond
 * both
 * brief
 * but
 * by
 * c
 * c'mon
 * c's
 * came
 * can
 * can't
 * cannot
 * cant
 * cause
 * causes
 * certain
 * certainly
 * changes
 * clearly
 * co
 * com
 * come
 * comes
 * concerning
 * consequently
 * consider
 * considering
 * contain
 * containing
 * contains
 * corresponding
 * could
 * couldn't
 * course
 * currently
 * d
 * definitely
 * described
 * despite
 * did
 * didn't
 * different
 * do
 * does
 * doesn't
 * doing
 * don't
 * done
 * down
 * downwards
 * during
 * e
 * each
 * edu
 * eg
 * eight
 * either
 * else
 * elsewhere
 * enough
 * entirely
 * especially
 * et
 * etc
 * even
 * ever
 * every
 * everybody
 * everyone
 * everything
 * everywhere
 * ex
 * exactly
 * example
 * except
 * f
 * far
 * few
 * fifth
 * first
 * five
 * followed
 * following
 * follows
 * for
 * former
 * formerly
 * forth
 * four
 * from
 * further
 * furthermore
 * g
 * get
 * gets
 * getting
 * given
 * gives
 * go
 * goes
 * going
 * gone
 * got
 * gotten
 * greetings
 * h
 * had
 * hadn't
 * happens
 * hardly
 * has
 * hasn't
 * have
 * haven't
 * having
 * he
 * he's
 * hello
 * help
 * hence
 * her
 * here
 * here's
 * hereafter
 * hereby
 * herein
 * hereupon
 * hers
 * herself
 * hi
 * him
 * himself
 * his
 * hither
 * hopefully
 * how
 * howbeit
 * however
 * i
 * i'd
 * i'll
 * i'm
 * i've
 * ie
 * if
 * ignored
 * immediate
 * in
 * inasmuch
 * inc
 * indeed
 * indicate
 * indicated
 * indicates
 * inner
 * insofar
 * instead
 * into
 * inward
 * is
 * isn't
 * it
 * it'd
 * it'll
 * it's
 * its
 * itself
 * j
 * just
 * k
 * keep
 * keeps
 * kept
 * know
 * knows
 * known
 * l
 * last
 * lately
 * later
 * latter
 * latterly
 * least
 * less
 * lest
 * let
 * let's
 * like
 * liked
 * likely
 * little
 * look
 * looking
 * looks
 * ltd
 * m
 * mainly
 * many
 * may
 * maybe
 * me
 * mean
 * meanwhile
 * merely
 * might
 * more
 * moreover
 * most
 * mostly
 * much
 * must
 * my
 * myself
 * n
 * name
 * namely
 * nd
 * near
 * nearly
 * necessary
 * need
 * needs
 * neither
 * never
 * nevertheless
 * new
 * next
 * nine
 * no
 * nobody
 * non
 * none
 * noone
 * nor
 * normally
 * not
 * nothing
 * novel
 * now
 * nowhere
 * o
 * obviously
 * of
 * off
 * often
 * oh
 * ok
 * okay
 * old
 * on
 * once
 * one
 * ones
 * only
 * onto
 * or
 * other
 * others
 * otherwise
 * ought
 * our
 * ours
 * ourselves
 * out
 * outside
 * over
 * overall
 * own
 * p
 * particular
 * particularly
 * per
 * perhaps
 * placed
 * please
 * plus
 * possible
 * pppoe
 * presumably
 * probably
 * provides
 * q
 * que
 * quite
 * qv
 * r
 * rather
 * rd
 * re
 * really
 * reasonably
 * regarding
 * regardless
 * regards
 * relatively
 * respectively
 * right
 * s
 * said
 * same
 * saw
 * say
 * saying
 * says
 * second
 * secondly
 * see
 * seeing
 * seem
 * seemed
 * seeming
 * seems
 * seen
 * self
 * selves
 * sensible
 * sent
 * serious
 * seriously
 * seven
 * several
 * shall
 * she
 * should
 * shouldn't
 * since
 * six
 * so
 * some
 * somebody
 * somehow
 * someone
 * something
 * sometime
 * sometimes
 * somewhat
 * somewhere
 * soon
 * sorry
 * specified
 * specify
 * specifying
 * still
 * sub
 * such
 * sup
 * sure
 * t
 * t's
 * take
 * taken
 * tell
 * tends
 * th
 * than
 * thank
 * thanks
 * thanx
 * that
 * that's
 * thats
 * the
 * their
 * theirs
 * them
 * themselves
 * then
 * thence
 * there
 * there's
 * thereafter
 * thereby
 * therefore
 * therein
 * theres
 * thereupon
 * these
 * they
 * they'd
 * they'll
 * they're
 * they've
 * think
 * third
 * this
 * thorough
 * thoroughly
 * those
 * though
 * three
 * through
 * throughout
 * thru
 * thus
 * to
 * together
 * too
 * took
 * toward
 * towards
 * tried
 * tries
 * truly
 * try
 * trying
 * twice
 * two
 * u
 * un
 * under
 * unfortunately
 * unless
 * unlikely
 * until
 * unto
 * up
 * upon
 * us
 * use
 * used
 * useful
 * uses
 * using
 * usually
 * v
 * value
 * various
 * very
 * via
 * viz
 * vs
 * w
 * want
 * wants
 * was
 * wasn't
 * way
 * we
 * we'd
 * we'll
 * we're
 * we've
 * welcome
 * well
 * went
 * were
 * weren't
 * what
 * what's
 * whatever
 * when
 * whence
 * whenever
 * where
 * where's
 * whereafter
 * whereas
 * whereby
 * wherein
 * whereupon
 * wherever
 * whether
 * which
 * while
 * whither
 * who
 * who's
 * whoever
 * whole
 * whom
 * whose
 * why
 * will
 * willing
 * wish
 * with
 * within
 * without
 * won't
 * wonder
 * would
 * wouldn't
 * x
 * y
 * yes
 * yet
 * you
 * you'd
 * you'll
 * you're
 * you've
 * your
 * yours
 * yourself
 * yourselves
 * z
 * zero


text:
Help:Category

Categories provide automatic indexes, that are useful as table of contents. Together with links and templates they structure a project.

For a complete/alphabetical list of categories, see Special:Categories. Categories at Main page is like this page but bigger and more general. Category:top_level is hierarchical

Note: Categories work only in MediaWiki version 1.3 and later.

How to add a category, and include a page in a category
Just link to the category name, in the namespace "Category" ex: and it is done.

Linking to a category
If you want to link to a category without the current article being added to it you should use the following link form foobarnowiki (ctrl-click)">Category: foobar (where foobar is the category name), note the extra : before Category.

Subcategories
Categories themselves can also be specified to belong to another category. When displaying the page of a category to which other categories belong, a separate automatically generated, alphabetical list of subcategories is also produced.

For example you could edit and add the link. The Soccer category would then be a subcategory of the Sports category.

Categories to which a page belongs
Pages, including categories, can belong to more than one (other) category. The categories to which a page belongs are displayed in a fixed place, depending on the skin (the bottom for Monobook, the upper right corner for Standard), regardless of where in the wikitext they are specified.

Existing categories
You can see currently used categories for each project with Special:Categories, for Wikipedia en:Special:Categories. It produces a list of all categories, including those which contain subcategories or pages, but have no additional text. In that case a link to the category page shows up as link to a non-existing page that leads to the edit page. Avoiding this complication is an additional reason for entering in a category page at least a link to the main article on the field and a reference to a higher category to which it belongs.

Setting sort keys
If you want the article, in the list of articles in the category, to be positioned alphabetically by something other than its name you should use the following link form: foobarnowiki (ctrl-click)"> (where foobar is the category name and sort key is the value to sort by).

For example to add an article called Albert Einstein to the category "people" and have the article sorted by "Einstein, Albert" ("Einstein" is the 1st sort key and "Albert" the 2nd) you would type " ".

The sort keys are case sensitive, so The_Foobarnowiki (ctrl-click)"> is sorted before The_Foobarnowiki (ctrl-click)">.

A category tag in a template; caching problem
If a template contains the code indicating that it is in a category, this does not only put that template in the category, but also the pages that include the template. For example, this page includes Template:Hh and as a result is in Category:English documentation.

The page that contains the template correctly lists the categories to which it belongs. However, adding or deleting a category tag in the template does not add or delete the listings on the category page of pages that use the template, until some edit is made in the page that uses the template.

In other words:

 * lists of categories a page is in, are up-to-date
 * lists of pages in a category are based on the situation just after the last edit of the pages

Since adding or removing a category or template tag is obviously an edit there is only a complication when a page is indirectly added to or deleted from a category, through a change in a template the page uses.

In order to update a page in such cases, use "action=purge", in a URL like

Relation with "What links here"
A category is somewhat like a "What links here" page with regard to the special category links.

However, "What links here" tends to be a by-product of links that are useful anyway (although links may be put with this use in mind), while category links are put specially to produce a category page.

Linking from a test page, user page, etc. to a category is considered to pollute the category, while regular links from such pages showing up in "what links here" is considered harmless.

Category listings are alphabetical, for "What links here" this typically applies for the first part only, for the pages already linking to the given page at the time of the last rebuilding of the link tables in the database.

Applying "What links here" and "Related Changes" to a category
For the "What links here" and "Related Changes" features, only the links in the editable part of the page count, not the links to the pages in the category.

Conventions and project-specific settings
Each page is typically in at least one category. It may be in more, but it may be wise not to put a page in a category and also in a more general category.

Each category, except one top-level category, is typically in at least one higher level category.

Check the conventions in a project and make yourself familiar with the categories in use before assigning pages and subcategories to categories and before creating new categories.

For category names the usual rules for case-sensitivity of page names apply: they are case-sensitive beyond the first character, but in most projects the first character is case-insensitive. So be aware that you create a new category if the capitalization beyond the first character is not the same.

How categories are implemented
Each of the pages in the Category namespace represents a so-called category, a kind of grouping of related pages. For example, this page belongs to "Category:English documentation". When a page belongs to one or more categories, this information appears at the bottom of the page (or in the upper-right corner, depending on the skin being used).

The page of the category contains text that can be edited, like any other page, but when displaying the page, the last part of what is displayed is an automatically generated, alphabetical list of all pages in that category, in the form of links (in fact ASCII order, see Help:Special pages).

For a complete list of categories, see Special:Categories. Individual wikis may have their own top-level categories, such as Category:Main page or Category:Fundamental in Wikipedia. For categories in Meta-Wiki, see Categories.

New categories can be created and edited in the same way as any other regular page¹, but when displayed, an automatically generated, alphabetical list of all pages in that category appears at the bottom.

You can assign a category to an article simply by adding " categoryname (ctrl-click)"> Category:categoryname" to the article's wikitext source. Substitute the actual name of the category in place of categoryname.

To be specific, in order to add an article called "Albert Einstein" to the category "People", you would edit the article and add " Category:People" (no quotes) into its page source somewhere. Exactly where doesn't matter, but the Wikipedia policy, for example, is to put it after the article text, but before any interlanguage links.

Category page note
You can include the template template:category note into the category page's description,  which can link to your top level category and include basic help.

title: Help:Category


text: Template:Category note

title: Template:Category note


text:
Sainsbury's posts first ever loss

November 17, 2004

Sainsbury's, the UK supermarket chain, announced on Wednesday that it had made its first ever loss. For the six months to 9 October, it reported a pre-tax loss of £39m ($72m), compared with a profit of £323m the previous year.

Excluding £168m of exceptional items, such as the clearance of surplus merchandise, Sainsbury's made a pre-tax profit of £131m for the first half of its financial year. The company had made a profits warning earlier in the year. The company's shares actually rose slightly on the news. This is due to the absence of any surprises - shareholders were expecting results in line with these.

Sainsbury's chief executive Justin King admitted the firm had been failing to properly stock its shelves after struggling with faulty distribution systems. This problem however is only one of a series of problems that has plagued Sainsbury's in recent years. Once the UK's largest supermarket chain, Sainsbury's has been overtaken by both Tesco and Asda in recent years.

title: Sainsbury's posts first ever loss


text:
User:Angela

Angela may also be found at: Wikipedia, Meta, Commons, Wikimedia, Wikibooks, Wikia.

Useful links: UK, Australia, Review guidelines, Article stage tags, Water cooler, Workspace, Content guide, Style guide, Interviews, Wikimedia, Google

title: User:Angela


text:
Talk:Sainsbury's posts first ever loss

This article has been submitted for review by the Wikinews community. The review period is currently a minimum of 8 hours for regular articles and 4 hours for urgent stories. An article needs to find consensus - no objections - in the following categories in order to be accepted for publication. If the review period elapses without comments, the article may be published. See also Article stages for information on what constitutes a valid objection.

Please comment on any of the following issues:

 * Neutrality: All factual claims need to be attributed or sourced. On-topic information which is relevant to the article should be added. Off-topic information should NOT be added to "balance out" an article.
 * Accuracy: All facts should be verifiable. Factual claims which are attributed to a person or group, but considered false by another person or group can remain in the article as long as the controversy is accurately represented.
 * Legality: Does the article violate any laws of the state of Florida in the United States? Specifically, does it violate other people's copyright, in text or images? Please make sure that no images have been directly copied from a non-free source without permission, and that any brief text quoted from a non-free source is attributed accurately. Use Google News and Google Search and pick individual phrases from the article to verify this.
 * Writing: Is it well-written and understandable?
 * Policies: Does the article comply with Content guide and Style guide?'''
 * Comprehensiveness: Relevant information on the topic should be included, while keeping in mind timeliness. Given that an almost infinite amount can be said about any topic, objections in this category carry less weight than those in other categories.

Comments
Add your comments below.

Nice article. Perhaps an addition of some background on Sainsbury's, but it could be published now. Lyellin 23:19, 17 Nov 2004 (UTC)

Comprehensiveness
My objection: I don't know Sainsbury's supermarket chain because I dont live in UK. So, I dont know what Sainsbury is by its title. A little change in the title would be welcome. Something like: Sainsbury's UK supermarket chain makes first ever loss would be correct? --carlosar 01:25 Nov 18 2004 (UTC)
 * I don't know Sainsbury's either, but as long as it's in a business section, I don't think it matters - as I said on the Kmart-Sears page, I think the alternatives are too unwieldy. This is the sort of title you'd expect from a regular news service. Ambi 13:03, 18 Nov 2004 (UTC)
 * Maybe you are right. It is ok for me. carlosar Nov 18 17:59:32 UTC 2004

Same title in BBC News. Trouble?
The article's title here and in BBC News are the same. Any trouble? --carlosar Nov 18 17:41:58 UTC 2004

 * Good point, i'll move it to Sainsbury's posts first ever loss CGorman 18:18, 18 Nov 2004 (UTC)

title: Talk:Sainsbury's posts first ever loss


text:
Talk:Kmart to buy Sears for US$11 billion

This article has been submitted for review by the Wikinews community. The review period is currently a minimum of 8 hours for regular articles and 4 hours for urgent stories. An article needs to find consensus - no objections - in the following categories in order to be accepted for publication. If the review period elapses without comments, the article may be published. See also Article stages for information on what constitutes a valid objection.

Please comment on any of the following issues:

 * Neutrality: All factual claims need to be attributed or sourced. On-topic information which is relevant to the article should be added. Off-topic information should NOT be added to "balance out" an article.
 * Accuracy: All facts should be verifiable. Factual claims which are attributed to a person or group, but considered false by another person or group can remain in the article as long as the controversy is accurately represented.
 * Legality: Does the article violate any laws of the state of Florida in the United States? Specifically, does it violate other people's copyright, in text or images? Please make sure that no images have been directly copied from a non-free source without permission, and that any brief text quoted from a non-free source is attributed accurately. Use Google News and Google Search and pick individual phrases from the article to verify this.
 * Writing: Is it well-written and understandable?
 * Policies: Does the article comply with Content guide and Style guide?'''
 * Comprehensiveness: Relevant information on the topic should be included, while keeping in mind timeliness. Given that an almost infinite amount can be said about any topic, objections in this category carry less weight than those in other categories.

Comments
Add your comments below.

Writing
Someone check English, please. --carlosar 01:15 Nov 18 2004 (UTC)
 * No problems that I can see. Superb. Ambi 12:52, 18 Nov 2004 (UTC)

Comprehensiveness
A objection: If I dont live in USA I don't know what Kmart and Sears are. I better title would be welcome.--carlosar 01:15 Nov 18 2004 (UTC)
 * That's a very good point; I'm not sure how to solve it without making the title very unwieldly. Should it say "Retailers Kmart, Sears to merge"? "American retailer Kmart to buy Sears"? --Golbez 09:14, 18 Nov 2004 (UTC)
 * I prefer the current title (and I come from a country where Sears doesn't operate). The alternatives are too unwieldy. The issue would be solved somewhat by putting it in a business section on the main page. Ambi 12:52, 18 Nov 2004 (UTC)


text:
User:Elian

see meta:User:Elian and de:Benutzer:Elian

title: User:Elian


text: User talk:Elian

title: User talk:Elian


text:
Talk:CRS analyses al Qaeda statements

This article has been submitted for review by the Wikinews community. The review period is currently a minimum of 8 hours for regular articles and 4 hours for urgent stories. An article needs to find consensus - no objections - in the following categories in order to be accepted for publication. If the review period elapses without comments, the article may be published. See also Article stages for information on what constitutes a valid objection.

Please comment on any of the following issues:

 * Neutrality: All factual claims need to be attributed or sourced. On-topic information which is relevant to the article should be added. Off-topic information should NOT be added to "balance out" an article.
 * Accuracy: All facts should be verifiable. Factual claims which are attributed to a person or group, but considered false by another person or group can remain in the article as long as the controversy is accurately represented.
 * Legality: Does the article violate any laws of the state of Florida in the United States? Specifically, does it violate other people's copyright, in text or images? Please make sure that no images have been directly copied from a non-free source without permission, and that any brief text quoted from a non-free source is attributed accurately. Use Google News and Google Search and pick individual phrases from the article to verify this.
 * Writing: Is it well-written and understandable?
 * Policies: Does the article comply with Content guide and Style guide?'''
 * Comprehensiveness: Relevant information on the topic should be included, while keeping in mind timeliness. Given that an almost infinite amount can be said about any topic, objections in this category carry less weight than those in other categories.

Comments
Add your comments below.

Accuracy
The article contradicts itself in terms of dates - it says that the article was written on the 17th, and that the report was released "today", and then goes ahead to state that the report was released on the 16th. Otherwise it isn't bad. Ambi 12:46, 18 Nov 2004 (UTC)

 * Sorry, the newsletter was 17th and report 16th. I changed it all to the report's release date.

Comprehensiveness

 * A better title would be welcome (what is CRS?). --carlosar 01:15 Nov 18 2004 (UTC)
 * "Congressional Research Service analyses al Qaeda statements" seems too long for a headline. CRS is clearly defined in the first paragraph. Added (CRS) for the quick reader. --119 03:52, 18 Nov 2004 (UTC)
 * Are the references right? It seems Secrecy News, 17 November 2004 and "Al Qaeda: Statements and Evolving Ideology " are the same source (it seems it has been written in a wrong way). --carlosar 01:15 Nov 18 2004 (UTC)
 * Secrecy News is a newsletter which brought to light the release of this document. "Al Qaeda: Statements..." is the document itself. --119 03:52, 18 Nov 2004 (UTC)

 * I think the article is acceptable. carlosar Nov 18 17:41:58 UTC 2004

title: Talk:CRS analyses al Qaeda statements


text:
Talk:Brazilian President meets President of South Korea

Writing
Somewhat awkward writing in places. Nearly there, however. Ambi 12:45, 18 Nov 2004 (UTC)

Comprehensiveness
You need to change the articles` title to reflect the division of Korea. --Ce garcon 04:42, 17 Nov 2004 (UTC)
 * It think it is OK now.--carlosar 01:25 Nov 18 2004 (UTC)


text:
Talk:Russian Tatars not allowed to use Latin alphabet

Neutrality
Good --119 05:44, 18 Nov 2004 (UTC)

Accuracy
Good --119 05:44, 18 Nov 2004 (UTC)
 * It needs to be renamed/moved; they are Tatars, not Tartars. What's the procedure for that? --Golbez 20:51, 18 Nov 2004 (UTC)
 * It can just be moved. Lyellin 22:41, 18 Nov 2004 (UTC)

Comprehensiveness
Brief but seems alright --119 05:44, 18 Nov 2004 (UTC)
 * Agreed. Ambi 13:01, 18 Nov 2004 (UTC)

Superb.I am a Bulgarian and can tell you that every one Bulgarian want to preserve the sacred Slavonic alphabet (azbuka).I feel happy, because the Russian brothers care about our common Cyrillic alphabet too.


text:
Help:Diff

A diff is the difference between two versions of page. It can be viewed by clicking cur or last in the page history or on the Recent Changes page. The diff is also shown during an edit conflict so you can see exactly what you need to reintegrate.

How it looks
The two versions are shown side-by-side. The old version is yellow and the new version is green. In left-to-right languages, the old version on the left. This is reversed in right-to-left languages. Text removed is shown in red on the old version. New text is shown in red on the new version.

The diff shows differences per line. Some editors find that adding manual line breaks improves the diff function.

As well as showing the difference between versions, the diff page has links to the user page and talk page of the user of edited both the last and current version. A link to the users' contributions lists are also shown. For sysops, a rollback button is shown allowing them to revert from the new version to the old one. This is only shown when viewing the diff between the recent version of a page and the last version by an author other than the one of the most current version.

edit summaries are also shown on the diff page. These appear in the row beneath the user names. If the user has used links in their edit summary, these act as links on the diff page as well.

This example shows the top of the diff page, with the links described above.

When moving or copying a piece of text within a page or from another page, and also making other edits, it is useful to separate these edits. This way the diff function can be usefully applied for checking these other edits.

Width
After the table of differences, the latest of the two compared versions is shown fully.

In the case of the Classic skin with quickbar, the diff page does not have the quickbar, to provide more space. Therefore the diff page is also useful for viewing the page on full screen width, without changing the preferences.

With the Monobook skin the panels on the left are also on the diff page.

Page widening is more likely on a diff page, because there are two columns, but also because URLs (long ones are often the cause of page widening) are not hidden.

External link

 * http://cvs.sourceforge.net/viewcvs.py/wikipedia/phpwiki/newcodebase/DifferenceEngine.php

title: Help:Diff


text:
Help:Related changes

The "Related changes" feature lists the last change in each article linked to from the current page, provided that it is recent enough, and not more than the number specified in the preferences. Its header is "Recent changes" with subheader "(to pages linked from "xxx")".

Options
If you have the option "Hide minor edits" enabled in your user preferences and the last change to a page was Minor, then the page will not show up, even if there have been not-Minor changes in the last days!

See also Help:Preferences under "Hide minor edits".

Caveats
Note that for links to redirects, only a change in the redirect is given, not a change in the target article. In this regard a direct link to the target article is superior.

The "Related changes" feature neither lists changes in images or sound files nor in image description pages (regardless of which of the three linking methods (image, :image or media) is used.

When applying the feature to a subpage, the automatic link to the parent page is ignored, i.e., changes in the parent page are not listed unless there is also an explicit link to it.

title: Help:Related changes


text:
Help:Special pages

The namespace "Special:" consists of "special pages". These have no corresponding wikitext; they are created by the software on demand. Some depend on the preferences that have been set, e.g. classic or enhanced Recent Changes, and the number of titles in Recent Changes and the watchlist, etc.

Alphabetic listing order
In the case of alphabetic lists of pages, ASCII order is used. In particular, a-z come after A-Z. The blank space within a page name is treated as an underscore, and therefore comes after the capitals, and before the lower case letters. However, a "blank space" after the name comes before any character. Sometimes a special character looks like a regular letter, but has a special code anyway.

Thus we have the order PC, PCX, PC Bruno, PCjr, Κύρια Σελίδα.

For the allowed characters in the lower range the order is:

 * !%&'-./[0-9]:;?[A-Z]_[a-z]

Other special characters come at the end.

Special pages for all users

 * Special pages : Special:Specialpages : A list of the other special pages
 * Preferences : Special:Preferences : Set your user preferences. (MediaWiki User's Guide: Setting preferences)
 * My watchlist : Special:Watchlist : Show the pages you are watching. (Watchlist help)
 * Recent changes : Special:Recentchanges : The latest edits in the project. The header is Project:Recentchanges, e.g. for Wikipedia en:Wikipedia:Recentchanges; links to Recent Changes of many language versions of Wikipedia are in Recentchanges/All languages; see also Recent changes help
 * Upload file : Special:Upload : Upload a file to the wiki. (Upload help)
 * Image list : Special:Imagelist : List of images uploaded that can be sorted by size or date
 * User list : Special:Listusers : A list of all registered users.
 * Admins list : Special:Listadmins : A list of all Administrators
 * Statistics : Special:Statistics : total number of pages and users
 * Random page : Special:Randompage : redirects to a random page from the main namespace which is not a redirect
 * Orphaned pages : Special:Lonelypages : Orphaned articles
 * Uncategorized pages : Special:Uncategorizedpages : Pages without category tags (note that after adding a tag to a page refreshing this page does not immediately reflects the change)
 * Unused images : Special:Unusedimages
 * Wanted pages : Special:Wantedpages : Most wanted articles
 * Short pages : Special:Shortpages - pages in the main namespace, with size (of the wikitext excluding that of templates used) in bytes, in order of increasing size
 * Long pages : Special:Longpages - pages in the main namespace, with size in bytes, in order of decreasing size
 * New pages : Special:Newpages : new pages in the main namespace - newest pages in the main namespace, with creation date and time, current size, user who created the page, and first edit summary, in reverse order of creation
 * Oldest pages : Special:Ancientpages - pages in the main namespace, with creation date and time, in order of creation
 * Dead-end pages : Special:Deadendpages : Pages without any outgoing links.
 * All pages : Special:Allpages : All pages by title : pages in the main namespace in alphabetical order; may be temporarily disabled.
 * List of blocked IP addresses and usernames : Special:Ipblocklist : Blocked IPs and usernames
 * Book sources : Special:Booksources : en:Wikipedia:ISBN
 * Categories : Special:Categories
 * Export pages : Special:Export : Exports the source of individual wiki pages, optionally with their histories, in a thin XML wrapper which includes metadata (time, etc).
 * Version : Special:Version : The version of the software the site is currently running
 * Wikimedia Board of Trustees election : Special:Boardvote : Voting software for the now finished elections

Restricted special pages

 * Block user : Special:Blockip : Sysop only. Used to block or unblock users, IPs and ranges of IPs.
 * Restore deleted page : Special:Undelete : Sysop only. One way to undelete a page.
 * Make a user into a sysop : Special:Makesysop : Bureaucrat only.
 * Lock database : Special:Lockdb : Developer only. Puts the wiki in read only mode.
 * Unlock database : Special:Unlockdb : Developer only. Puts the wiki in read/write mode.
 * Show process list : Special:ShowProcesslist : Developer only.

Currently unavailable special pages

 * SQL query : Special:Asksql : Sysop only. Database interface for running queries. Currently disabled.
 * All system messages : Special:Allmessages : Displays all pages in the MediaWiki namespace. Currently disabled.
 * Unicode Converter : Special:UnicodeConverter : Converts Unicode to HTML entities : Not currently available outside of the test wiki
 * Import pages : Special:Import : Sysop only. Imports a page from another wiki. Currently disabled.
 * Popular pages : Special:Popularpages : The most visited pages. Currently disabled.
 * Maintenance page : Special:Maintenance : Currently disabled.

Logs

 * Block log - blocks and unblocks
 * Deletion log - deleted and undeleted pages
 * Protection log - protected and unprotected pages
 * Upload log - list of images uploaded

Linking to a Special page
Special pages can be linked to as usual, like Special:Recentchanges, except when they have parameters, then the full URL has to be given, like an external link, for example  last 10 changes  produces last 10 changes.

A redirect to a Special page may be problematic, see Help:redirect.

Spelling of text in URLs depends on the language of the particular server, e.g. "Special" in English, "Speciaal" in Dutch, "Spezial" in German, "Speciális:" in Hungarian and "מיוחד:" in Hebrew.

title: Help:Special pages


text:
Help:What links here

Every page has a link labelled "What links here" (or, more generally, labelled with the text in mediawiki:whatlinkshere).

This backlink facility can be used to see which other pages in the same project contain a link to a given page.

Limitations

 * not listed are subpages that just have an automatic link to a page
 * not more than 500 pages are listed; if there are more, there is no indication that the list is not complete; only by copying the list to an editor that can count lines and concluding that there are 500 on the list, one can find out that it is likely that there are more; it is recommended to add to the text in MediaWiki:Linkshere, as has been done here on Meta and on the English Wikipedia: "(up to 500 are shown)".

Cases of transclusion

 * in the case of a template, referral to it is treated as link
 * a link from a template is only treated as such, not as link from the pages that show the link because they refer to the template
 * in the case of an image, using it in a page is listed in the third section of the image description page, but not in "What links here" of that page

Other uses
This facility works also for a page that does not exist. The What links here button is also on the edit page on which one arrives when following a broken link.

One can also use a link of the form Special:Whatlinkshere/John Smith, or equivalently (here on Meta) http://meta.wikimedia.org/w/index.php?title=Special:Whatlinkshere&target=John_Smith

The feature can also be applied to itself and other special pages, e.g.:

 * http://meta.wikimedia.org/w/index.php?title=Special:Whatlinkshere&target=Special%3AWhatlinkshere
 * http://meta.wikimedia.org/w/index.php?title=Special:Whatlinkshere&target=Special%3ARecentchanges
 * http://en.wikipedia.org/w/index.php?title=Special:Whatlinkshere&target=Special%3AWhatlinkshere
 * http://en.wikipedia.org/w/index.php?title=Special:Whatlinkshere&target=Special%3ARecentchanges

Order
When the link tables in the database are rebuilt, the lists are alphabetically ordered. However, adding a link subsequently causes it to be added to the end, and thus these occur in chronological order.

title: Help:What links here