text:
Help:Redirect

(To go to an interwiki redirect click http://meta.wikimedia.org/w/wiki.phtml?redirect=no&title=X and change the page name (here X) in the address bar of the browser. Type it in canonical form, i.e., starting with a capital, and with underscores for spaces.)

For policy on the use and abuse of redirects on the English Wikipedia see en:Wikipedia:Redirect.

See also: PageRedirect, Disinfopedia: redirect policy

What is a redirect?
A redirect is a page with no other content than something of the form

 * 1) REDIRECT link in internal link style

If the link is to an existing page in the same project, going to the redirect (by means of a link, the URL, or the Go button) results in the new page, just like following the link, except that the browser shows the original URL, and the new page shows a redirection message below the title.

For example, if somebody browses to: http://meta.wikipedia.org/wiki/redirection, or follows a link to redirection, then they will end up at this page instead, and the top of the page will look like:

  Help:Redirect  (Redirected from Redirection) (etc)

If the link is to a non-existing page in the same project, one simply arrives at the redirect page.

If the link is to a page in another project, going to the redirect results in following the link, regardless of existence (a project does not retrieve information about existence of pages on another project, but just sends through). The browser shows the new URL.

Purposes of a redirect

 * Finding a page
 * Conveniently going to a page
 * Conveniently linking indirectly to a page, without the need for a piped link. For this purpose, making the stem (the common first part) of a collection of strongly related terms a redirect reduces the need for having many redirects. E.g. categor can be used for category, categories, categorical. Note that having the other redirects anyway is even better; also a piped link is in some respects even better than relying on a redirect, see Comparison with piped link.
 * Allowing a link title independent of the eventual link target; one creates a page whose name is the desired link title, and which redirects to the desired target page. See e.g. w:Template:Ft, containing ft, with the page 30.48 cm redirecting to Foot (unit of length). The link title "30.48 cm" informs in the hover box about the unit "ft" even without following the link to the article about this unit.

Due to redirects, after renamings and merges, old URLs in links, bookmarks, search engines, etc., still lead to the appropriate page.

The move tool
When a page is renamed/moved with the Renaming (moving) a page function, a redirect is automatically created from the old to the new name, and also one for the corresponding talk page.

If the new page name is occupied by a redirect with only one edit in its history, it is replaced by the page being moved. If the redirect has more than one history entry, then it must either be deleted by an administrator or moved to another name. This move will leave behind a new redirect with no edit history, which can then be replaced by the desired page move. It might be desirable to delete the moved redirect.

How do I create a redirect?
If you're creating a new redirect, start a new page, write #REDIRECT pagename (or #redirectpagename ) at the top of the page, where pagename is the name of the target page. Here is an example. If you're replacing an existing page with a redirect, for example after merging a duplicate page, go to the page, edit it, and replace the existing text with #REDIRECT pagename.

Extra text after the #REDIRECT command and link, on the same line, can serve as explanatory text. It is only shown when viewing the redirect page itself.

Extra lines of text are automatically deleted on Save (not yet on Preview).

The page will not redirect if there is anything on the page before the redirect. Also, there must be no spaces between the # and the REDIRECT. Consider copying the #REDIRECT pagename text into the edit summary so that people know that you have created a redirect.

After you create a redirect, you get sent to a page with the string "&redirects=no" in the URL. Thus the just created redirect page is shown, not the page to which it redirects. To see your redirect working, use your address bar to delete that part of the URL. Alternatively, create a link on another page to your redirect, and then follow that link.

When creating new redirects, bear in mind that creating too many redirects can clutter up the search results page, which can hinder users. Also, don't spend too much time creating redirects - often it's more important to spend time improving the quality of the target page. A piped link is another way to make a link to a page with a name which does not occur in the first page.

How do I change a redirect?
Click on a link to the redirect page. Then look for the " " link at the top of the page you've been redirected to. You will be taken to a page looking something like:

  Pagename  From {project name} ...
 * 1) REDIRECT target page

Then click Edit this page. You can then either change the target of the redirect, or replace the redirect with a brand new page.

Another way to do the same thing: Go to the target page, and click "What links here". This will show you all the back-links from that page, including redirects. To change a redirect, click on it, and then click on Edit this page as above.

These things do not work for redirects to other projects or to Special pages. Use http://{project domain name}/w/wiki.phtml?title=...&redirect=no (for projects outside Wikimedia the "w/" is not always used).

Here on Meta, go to http://meta.wikipedia.org/w/wiki.phtml?title=Redirection&redirect=no and change the page name (here Redirection) in the address bar of the browser.

How do I delete a redirect?
Administrators can delete redirects in the same way as any other page. There may be project-specific guidelines on when this is appropriate.

Inter-wiki redirects and redirects to Special pages
It is also possible to set up redirects between MediaWiki wikis, such as between Wiktionary and Wikipedia. Simply append the language code and the page name to the word "Wikipedia" (or other WikiMedia projects: Wikibooks, Wikitext?, Wikiquote?, Wikisource?, ...?) with colons. To link to the Wikipedia article for dog from an article in wiktionary, one would use dog. For example dog. As a redirect: #REDIRECT dog

However, compared with redirects within a MediaWiki wiki there are restrictions and drawbacks: http://{project domain name}/w/wiki.phtml?title=...&redirect=no
 * The message "Redirected from ..." is not shown.
 * Editing the redirect page is cumbersome, one has to use
 * "What links here" does not work across wiki's; this applies also to redirects, so one can not see which page(s) redirect(s) to a given page.
 * Being led to an other wiki without explicit request may be confusing.

In order to change an inter-wiki redirect (perhaps restoring previous content), manually go to a URL like http://{project domain name}/w/wiki.phtml?title=my_title&redirect=no, but replace "my_title" with the title of the page in question. You can then view page history, edit the page, etc, in the normal fashion. This is tedious, but it is the only way of doing this, currently.

The same applies to redirects to Special pages.

To avoid these problems, consider direct interwiki links (or direct links to Special pages) without redirect, or a "non-automatic redirect": a page with "See ...", e.g. en:Wikipedia:Enhanced Recent Changes. This requires an extra click to use, but is less confusing and the redirect page itself is easier to go to (to edit, to apply "What links here" and to discuss it on its Talk page).

If you use a "real" interwiki redirect anyway, put on the page to which the redirect points links to such redirect pages, using a URL with "redirect=no". This is not possible in the case redirect-to-Special.

Alternatively a page like en:Wikipedia:What it thinks it is - go to interwiki redirect page itself can additionally be made, a redirect page to en:Wikipedia:What it thinks it is which is an interwiki redirect page; linking to the first-mentioned page leads you to the interwiki redirect page, making use of the fact that redirection is not recursive. Other examples are Be bold - go to interwiki redirect page itself and the page "Image Go To A Random Page .png ″ go to redirect-to-Special page itself" on Wikibooks: http://wikibooks.org/wiki/Image_Go_To_A_Random_Page_.png_%E2%80%93_go_to_redirect-to-Special_page_itself

There are plans to adjust the software so as to reduce the complications.

Double redirects
As a simple way to avoid problems with infinite recursion, in the case one is redirected within the same project to another redirect page, the second redirect is not applied.

Redirects to an anchor
An example of this: This currently is not possible. You will still be redirected to definitions but you will not be sent to the #G anchor.
 * 1) REDIRECT definitions

Images linking to a page
An image can link to a page of choice instead of the image description page by putting a redirect as "image description". The actual image description then has to be put on the Talk page.

For clarity it may be useful to add a text near the image, which can be made a link to the same page. Thus clicking on the text and on the image has the same effect.

However, when arriving at the target page, not only is the message (Redirected from File:xxxxx.xxx) displayed, but so is the image itself. This may not be the effect sought. As an alternative navigable images provides image anchored navigation in projects that allow embedding images in external link style.

If the main function of the image is just being a symbol for the link, then, before uploading, give it a name describing that function rather than describing the image itself.

See e.g. the two images on wikibooks:Main Page:Français.

Redirect or link to edit page
When B is a subtopic of A, and B does not have its own article, one may be tempted to do the following:

 * redirect B to A
 * link A to B as invitation or preparation for creating an article

Both make sense, but not combined, that results in an indirect self-link. The first seems more useful. If one really wants both, one could put something like: "Write article about: Rhoon Poortugaal".

Anyway, if the text about B is short, it can better be added to A.

title: Help:Redirect


text:
Template:Ed

[ Edit ]

ja:Template:Ed

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

title: Template:Ed


text: Template:Hc

title: Template:Hc


text:
Help:Renaming (moving) a page

There are several reasons why you might wish to rename a page (one that you have found or created):

 * The title has been misspelled.
 * The title does not follow the wiki's naming conventions (such as Naming conventions or Wikinews:Style guide).
 * The scope of the article has been reduced, extended or otherwise changed.

The terms "rename" and "move" mean the same in this context. They just refer to different models for picturing the operation:

 * rename: keep the page but give it another name. The page history is now attached to the new name; a new page with the old name is created, which redirects to the new name. The page history of the new page records the renaming.

 * move: move the contents and the page history to a new page. Change the old page into a redirect; change the page history into one that only records the renaming.

Since the system marks the page with the old name as new page, it applies the first of the two models. This model avoids "changing the history", a kind of "historical revisionism". An oddity is that the renaming itself, which can be considered an important event in the history of the page, is not recorded as such; it is recorded indirectly, namely in the history of the redirect page.

How to
Note that you have to be logged in to rename a page this way; regarding the set preferences:
 * 1) there is no button for this in the nostalgia skin;
 * 2) the button is in the quickbar, so this must be on.

With the correct page displayed, click on the "Move" tab near the top of the page. You'll be asked for a new name for the page, and given the option to also move the page's talk page. NOTE: Unless you know what you're doing, it's safest to say yes. Click the "move page" button and the page will be renamed to the new title. The old title will become a redirect page, so any links to the old title will still go to the new page. However, note that double redirects (pages that redirect to the original page), will not automatically follow to the new page, so you will have to refer them manually (as explained below)

Page histories
The "move page" function keeps the entire edit history of the page, before and after the move, in one place, as if the page were always named that way. So, it's preferable to use this method over just cutting text out of one page and pasting it into a new one; old revisions, notes, and attributions are harder to keep track of it you do that. (But you may have to if, for instance, you're splitting a page into multiple topics. If you do, please include a note in the new pages's edit summary and talk page stating where you took the text from.)

The move itself is shown in the edit history of the page with the old title.

Moving over a redirect
If the new title already exists but is just a redirect to the old title, with just one line in the page history, the creation of the redirect, then you can rename the page. The most common case in which this applies is that of re-renaming a page back to its original name. As mentioned, this works only if the redirect that was automatically created in the first renaming, has not been edited.

The result is that the history of the page is preserved (note that you may have to refresh the history page on your browser), but without any sign of the two moves. The edit history of the page with the intermediate title shows the latest move only. The information about the first move (including user name, date and time) is lost: it is no longer in any page history or on any watchlist or Related Changes page, and not even in User contributions; only if the first move has been recent enough, then it is still available in the Recent Changes; how long depends on the edit activity on the site; e.g. one may be able to retrieve the edit lines of the last 2000 edits, which may cover months or just a few hours. To avoid loss of information, copy the edit line concerned to one of the talk pages. This has to be done before the second move, using the page history of the page with the original name; if the second move is soon enough after the first move, it can also be done afterwards, using Recent Changes.

The information about the second move is more complete in the Recent Changes than in the edit history of the page with the intermediate title: it mentions "B moved to A over redirect".

More moves back and forth are possible, and always the page history of the current title does not show any moves, and that of the other title only contains the edit line of the latest move. There is no record at all of a "move war" (except again, on Recent Changes) unless documented on the talk pages.

Earlier there was a bug, which has been fixed but not retroactively, as follows:

 * However, if the page is moved back, the edit history of the page with the intermediate title shows the latest move only, with the corresponding user name, but with the date and time of the first move(!). Accordingly, the name of the user who moved the page the first time and the date and time of the second move are lost (except that they appear in the Recent Changes).

Other notes
If the new title already exists and isn't just a redirect to the old title, with no history, the wiki will tell you that you can't rename the page. You'll either have to manually merge the two pages together, or -- only if there's no real content in the page -- ask an Administrator to have it deleted or list it on your project's "votes for deletion" page in order to make room for moving the page.

Another thing to remember is that redirects to redirects aren't automatically followed (this prevents infinite loops and spaghetti linking). Always check the What links here for your page, and if there are multiple levels of redirects, go fix the links to point to the new location directly. But this can be troublesome because your new moving might be reverted soon. Take some time to make sure there is no objection to your moving.

Avoid moving a page while the edit box of the corresponding Talk page is open: when you hit "Save page" you overwrite the redirect to the new talk page (you do not get the usual warning that the page has been edited while your edit box was open) and get a duplication of the contents of the talk page, with your latest addition added to the old instead of the new one.

It is useful to copy the message "Page ... moved to ..." to the new talk page, especially if there has been discussion about the name of the page.

Undoing a move
Normally, to undo a move from page A to page B, simply:

 * 1) move page B back to page A
 * 2) list page B (now a history-free redirect) on your project's "votes for deletion" page, or (Admins only) just delete it.

However, if page A has subsequently been edited, or the move software is behaving weirdly, only an Admin can sort things out:

 * 1) delete page A (make sure it has no useful history - you may wish to add an explicit author credit on a talk page to compensate)
 * 2) move page B to page A.
 * 3) delete page B (should be a history-free redirect to page A)

"Move wars" are highly unproductive, and leave vast numbers of pointless redirects littering the place, which some poor soul will have to fix.

Swapping two pages
To swap pages A and B, including history:
 * 1) Move page A to page C (previously non-existing)
 * 2) list A on votes for deletion, or (Admins only) just delete it.
 * 3) Move page B to page A (allowed because A is deleted)
 * 4) delete B as above
 * 5) Move page C to page B (allowed because B is deleted)
 * 6) delete C as above

Fixing cut and paste moves
Many past renamings took place before the move page function was created by our hard-working developers, and others are done by people not aware of this function. Such manual moves were done using cut and paste As a result, the page history of an article or talk page can be split among two or more different pages.

In some circumstances, Administrators are able to fix this by merging page histories.

Warning: this procedure may only be undone by a developer, spending quite silly amounts of time: to undo a merge, every single version has to be manually reassigned to the correct source page. Do not do this if you're not sure what you're doing.

Follow this procedure to merge page histories:

 * 1) suppose we wish to merge edit history from Alabama/History (old title) into History of Alabama (new title):
 * 2) Delete History of Alabama, with comment deleting to merge page histories - back soon.
 * 3) Move Alabama/History to History of Alabama, using the move tool.
 * 4)  undelete the History of Alabama article.
 * 5) Edit History of Alabama to restore the most recent version.

fr:Aide:Comment renommer une page hu:Wikihírek:Hogyan mozgass át lapokat?

title: Help:Renaming (moving) a page


text:
User talk:Angela

Moving page help
hehe, thanks :)Lyellin 21:22, 17 Nov 2004 (UTC)

links at wikinews
Halló Angela, at Help:Formula I could see that some links below the "toolbox" where generated. See. At en: I could see that it is not just copying a page from meta. There some of the links required adjustement too. Regards  en:User:Gangleri T 21:34, 21 Nov 2004 (UTC)

 * Yes I know. All the help pages need fixing. They're currently direct copies from Meta. A decision needs to be made about whether to replicate the templates here or just remove them from the help pages. They may also need some rewriting to make them more applicable to Wikinews. Angela 22:13, 21 Nov 2004 (UTC)

UK, & Germany
Hey Anglea! Great to see UK & Ireland and Germany already have a following - there about an hour old! CGorman 22:51, 19 Feb 2005 (UTC)

Thanks Angela!
I have to focus on another major project for the moment, and may be able to invest a lot of time again at the end of summer... - Amgine 20:31, 19 Mar 2005 (UTC)

Darn
Your crap didn't make it into the story. You perhaps could have done something about that. -Edbrown05 05:16, 13 March 2007 (UTC)
 * No, you couldn't do anything about it as someone cited as a source, except what you did after the fact, with a nasty edit comment. Welcome to news, where your opinion doesn't count. -Edbrown05 06:07, 13 March 2007 (UTC)
 * The problem was that someone was falsely citing my post as a source when it was not one to make it look like their false statements were sourced when in fact they were not. I never said I wanted my opinions in there and I don't know why you got that idea. Angela

Blog snippet
Absolutley, I think that it would be very useful for that purpose. I'll be on IRC later, and we can discuss it in detal. Thunderhead - (talk - email - contributions) 22:14, 24 October 2007 (UTC)
 * Sorry, read archives incorrectly :) Thunderhead - (talk - email - contributions) 22:18, 24 October 2007 (UTC)

title: User talk:Angela


text:
Help:Preferences

The preferences dialog allows you to personalize some aspects of a MediaWiki wiki. They will apply only when you are logged in.

Logging in and setting preferences are done separately on each wiki. You may find it convenient to specify the same preferences on each wiki that you use, but this is not necessary.

User data
User data Your email*: o Disable e-mail from other users Your nickname (for signatures): Change password Old password: New password: Retype new password: o Remember password across sessions for giving you attribution for your work. without you having to reveal your email address to them, and it can be used to send you a new password if you forget it.
 * Real name (optional): if you choose to provide it this will be used
 * Email (optional): Enables people to contact you through the website

 * Your e-mail: You may optionally register your e-mail address (it will not be shown publicly on the site). This will enable you to reset your password by clicking the "Mail me a new password" box on the log in screen, if you forget it. Additionally, it will enable other registered users to send e-mail to you from the "E-mail this user" link on your user page unless you've checked the disable box (see below).
 * Disable e-mail from other users: If you check this, users will not be able to send you e-mail by way of the "E-mail this user" feature.

Your nickname
Although your username is not necessarily your real name and could therefore be called a nickname, the term "nickname" is used here for a name you may optionally specify, different from your username, for when you enter your signature with  or. However, there is even more versatility. The software enters   in front and   in the back of your signature. So entering   as your signature will also include a link to your talk page.

Also you can add a separator, so that the signature looks something like this: — Name | Talk. The code   in front of whatever you put in this box can be effectively cancelled putting   at the front of your nick. Thus you can put e.g.  .

You can also include font tags, images, and templates, but until version 1.4 a signature with a template can not be used more than five times on one page. Note that changes in the images and templates are retroactive, which on one hand may be confusing, but on the other hand, to rectify annoying signatures, may be convenient. To avoid retroactivity, use a new image or template name.

Check the rules of your project (for the English Wikipedia, see Wikipedia:Username policy) and note that:
 * using another nickname than your username is confusing (the page history shows your username, not your nickname)
 * if you show your username as an image, or with letters replaced by special characters, even if the name is still readable, searching a talk page for your username will fail
 * excessive signatures may clutter talk pages
 * drawing excessive attention to yourself may create the impression that you find yourself more important than other people

If you use the edit toolbar for signing, remember that it gives two dashes before the four tildes.

Password
To change your password, enter your old password, the new password, and the new password a second time. (If you're merely changing the other preferences, you do not need to enter your password.)

 * Remember password across sessions. Enabling this feature will place a HTTP cookie in your browser's cache, which will allow MediaWiki to recognize you each time you visit the page. You will not have to log in each time you visit.

If you want to use remember my password you have to change your password if it was generated by Mediawiki and emailed to you. This is a security feature but very often causes trouble for new users.

Quickbar settings

This selection only works in the Classic and Cologne Blue skins (see below). In Monobook there is a left panel anyway; in Nostalgia there is none.

This is the list of links to the various special pages. You may optionally have it appear at the right or left side of each page. There's no option yet to have it appear at the top or bottom of the page.

The "fixed" quickbar will appear at the top corner of the page, while the "floating" quickbar will appear at the top corner of the browser window instead of scrolling with the article text. Floating quickbars may not float correctly on old or mobile browsers.

The Quickbar must be enabled to allow you access to some features such as moving (renaming) a page, and in the case of Classic, also to arrive at the Special Pages, unless you type the URL.

Skin
Skin O Classic O Nostalgia O Cologne Blue O MonoBook O MySkin

A MediaWiki skin is a style of page display. There are differences in the HTML code the system produces (but probably not in the page body), and also different style sheets are used.

The default is the new Monobook skin; what was called Standard is here in the preferences called Classic (not to be confused with the even older Nostalgia), but the system uses "wikistandard" in the naming of css files.

Links at the edges of the page are in different positions. Some links are not present in every skin. In Nostalgia some links are in a drop-down menu instead of directly visible.

Cologne Blue has a fixed font size unless one specifies in the browser "ignore font sizes specified in the webpage"; even then the line height is fixed; therefore this skin is hardly suitable for a large font.

In Monobook the width of the panel on the left is dependent on the font size. Therefore, with a large font, the width of the main part of the page is smaller than with other skins.

For Classic with a quickbar and a large font a CSS setting to reduce the size of the quickbar text may be necessary. This depends on the project, specifically on the length of the longest word in the quickbar. If that does not fit in the designated width, there are complications depending on the browser. In Internet Explorer the quickbar overlaps the main text and a vertical line which is intended to separate the two, crosses the main text. In some other browsers the problem does not arise if the quickbar is on the right.

Since there is word wrapping but no wrapping within a word, the longest word and not the longest full label is the criterion:

 * "contributions" - English and French Wikipedia and Meta - short, large font is possible
 * "Beobachtungsliste" - German Wikipedia - long - large font is hardly usable
 * "Foutenrapportage" - Dutch Wikipedia - ditto
 * "Gebruikersbydraes" - Afrikaans - ditto

To use the full width of the screen for the main text, use Classic without quickbar or Nostalgia. The drawback is that links are missing to the special pages and your user page, respectively.

Warning: Broken links!

Screenshots:
 * Cologne Blue
 * Nostalgia
 * Classic

See also Help:User style, and for developments and discussions, Skins.

Rendering math
Rendering math o Always render PNG o HTML if very simple or else PNG o HTML if possible or else PNG o Leave it as TeX (for text browsers) o Recommended for modern browsers o MathML if possible (experimental) MediaWiki allows you to enter mathematical equations as TeX code. These options let you control how that code is rendered into PNG images.
 * Always render PNG: Always make a PNG image from the TeX code.
 * HTML if very simple or else PNG: If the TeX code is very simple, like "x = 3", render it as HTML. For more complex code, render as PNG.
 * HTML if possible or else PNG: This option tries really hard to use HTML, but if it's too complicated, then it renders it as PNG. This option does not show a^{b^c} correctly! It shows the c at base level, which is not just a matter of being ugly, but it makes formulas wrong!. A workaround is to add "\,\!": a^{b^{\,\!2+2}}. With the current settings you get $$a^{b^c}$$ and $$a^{b^{\,\!c}}$$
 * Leave it as TeX: Don't convert the TeX code, just show it. This is primarily for text-based browsers like Lynx.
 * Recommended for modern browsers. If you use a web browser that was released in the past year or so, use this option.

 * MathML if possible (experimental)

Date format
The following is rendered depending on preferences:

2001-01-15 January 15, 2001 15 January 2001 2001 January 15 2001-01-15 January 15 15 January

With your current preference setting on this project the seven are rendered as follows:

 * 2001-01-15
 * January 15, 2001
 * 15 January 2001
 * 2001 January 15
 * 2001-01-15
 * January 15
 * 15 January

By default the rendering is as usual for links. However one can specify as preference that all of the first five are rendered the same, in the 2nd, 3rd, 4th or 5th way. If the 4th or 5th way is selected, the 6th and 7th line are not affected. If the 2nd or 3rd way is selected, the 6th and 7th line are rendered accordingly, without the year.

Note that using this date formatting feature in section headers complicates section linking. Conversely, if you want to be able to use links like November_2004, in the calendar at the upper right of the month pages on Wikipedia, or links elsewhere to the section about a particular day (if they also use the default format), you cannot use the date formatting feature.

See also Dynamic dates and Manual_of_Style_(dates_and_number).

Editing
Editing Rows:          Columns: o Edit box has full width o Show edit toolbar o Show preview before edit box and not after it o Add pages you edit to your watchlist o Mark all edits minor by default

 * Rows, Columns. Here you can set up your preferred dimensions for the textbox used for editing page text.
 * Edit box has full width. If this box is checked, the edit box (when you click "Edit this page") will be the width of the browser window, minus the quickbar width.
 * Show edit toolbar. In compatible browsers, a toolbar with editing buttons can be displayed.
 * Show preview before edit box and not after it. If you select this option, the preview will be displayed above the exit box when you click the "Show preview" button while editing a page.
 * Add pages you edit to your watchlist. If this option is selected, any articles that you create or modify will be automatically added to your watchlist.
 * Mark all edits minor by default. This option automatically selects the "This is a minor edit" checkbox when you edit pages.

Time zone
Time zone Server time is now: 06:34 Local time display: 08:34 Offset*:
 * Enter number of hours your local time differs from server time (UTC).

 * Time diff. This is the number of hours to be added or subtracted from UTC to find your time zone. This time zone is used when calculating displayed page update timestamps, and may become temporarily incorrect from time to time if you observe daylight saving time -- don't forget to update it to match your local time, because the Wiki doesn't know where you are or precisely when you celebrate DST. (Also, the server's clock may be slightly offset from reality, much as Wikipedia articles may be.) A scattering of typical (and possibly incorrect!) time diff values are below. If yours isn't listed, try this link or add and subtract a few hours as needed.
 * -10 Hawaii, western Aleutians (DST -9) (Hawaii-Aleutian Standard Time)
 * -9 (DST -8) All of Alaska, except for western Aleutians (Alaska Standard Time)
 * -8 (DST -7) California; Washington; almost all of Oregon, Nevada, and British Columbia (Pacific Standard Time)
 * -7 (DST -6) Colorado, Arizona (no DST except for Navajo Nation), Alberta (Mountain Standard Time)
 * -6 (DST -5) Chicago, most of Mexico, Central America, Saskatchewan (Central Standard Time)
 * -5 (DST -4) New York, Toronto, Quebec (Eastern Standard Time)
 * -4 (DST -3) Canada's Maritime Provinces, plus most of Labrador
 * -3.5 (DST -2.5) Newfoundland
 * -3 (DST -2) Brasilia, Buenos Aires, most of Greenland
 * -2 (DST -1) Mid-Atlantic
 * -1 (DST 0) Azores, Cape Verde Islands
 * 0 (DST 1) United Kingdom, Republic of Ireland, mainland Portugal, Iceland (no DST), Casablanca, Monrovia (no DST)
 * 1 (DST 2) most of Europe, West Central Africa (no DST)
 * 2 (DST 3) Bucharest, Kiev, Cairo, Johannesburg (no DST), Finland, Jerusalem
 * 3 (DST 4) Moscow, Kuwait, Baghdad, Tehran, Nairobi (no DST)
 * 4 Abu Dhabi, Baku
 * 4.5 Kabul
 * 5 Islamabad
 * 5.5 India
 * 5.75 Nepal
 * 6 Sri Lanka, etc.
 * 6.5 Rangoon
 * 7 Bangkok, Hanoi, Jakarta
 * 8 People's Republic of China, Taiwan, Western Australia, Ulaan Bataar, Singapore, Manila
 * 9 Japan, Seoul
 * 9.5 (DST 10.5) South Australia and Northern Territory (no DST)
 * 10 (DST 11) Queensland (no DST), New South Wales, Victoria, Tasmania, Guam (no DST), Vladivostok
 * 11 Magadan (DST 12), Solomon Islands, New Caledonia
 * 12 Pago Pago, New Zealand (DST 13)

The time is displayed in local time, according to the set preferences, in:
 * Recent changes
 * Related changes
 * Page history, Image history
 * User contributions
 * New pages
 * "This page was last modified" at the bottom of pages
 * Special:Imagelist

The UTC time is applicable:
 * In the signing of Talk pages
 * In the Upload log
 * In referring to non-localized events, including things that happen on the wiki.

Keep this in mind when copying an excerpt from Recent Changes, a revision history listing, etc. to a Talk page. Convert manually to UTC or temporarily set the preferences to a zero offset before producing the revision history etc. to be copied.

Recent changes and stub display
Number of titles in recent changes: o Hide minor edits in recent changes o Enhanced recent changes (not for all browsers) Threshold for stub display:
 * Number of titles on recent changes: You may select the number of changes which will be shown by default on the Recent Changes and Watchlist page. Once on those pages, links are provided for other options.
 * Hide minor edits in recent changes. Registered users may choose to mark edits as being minor (meaning fixes too trivial for trusting users to check up on). It applies to Recent Changes and Enhanced Recent Changes, but not to the Watchlist. It also affects Related changes, but currently in an odd way: if the last edit of a page linking to the current page was minor, then neither that nor the last major change is shown.
 * Enhanced recent changes (not for all browsers). Group recent changes per day by article, display 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.
 * Threshold for stub display: see Stub feature.

Search result settings
Hits to show per page: Lines to show per hit: Characters of context per line: Search in these namespaces by default:(Main) Talk User User talk Meta Meta talk Image Image talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Hilfe Hilfe Diskussion Aide Discussion Aide Hjælp Hjælp diskussion Helpo Helpa diskuto Hjälp Hjälp diskussion Ayuda Ayuda Discusión Aiuto Discussioni aiuto ヘルプ ヘルプ‐ノート NL Help Overleg help Pomoc Dyskusja pomocy Ajuda Aju
 * Hits to show per page: You may choose the number of results returned on each page of search results.
 * Lines to show per hit is somewhat cryptic; specifying a number n means: "do not show any context if the search term occurs beyond line n in the page"; here a paragraph, as well as the blank line between two paragrahs, each count as one "line"; line breaks in the source, even when not affecting the lay-out of the page (and even when not directly visible in the edit box of the article), affect the line count. Setting the parameter to 5000 or more gives context for every occurrence.
 * Characters of context per line: the number of characters of context per occurrence; however, the context is anyway restricted to the "line" (see above) it occurs in. To get the whole line, put a large number like 5000.
 * Search in these namespaces by default:shows a list of all namespaces (not the same in all projects; also a useful indicator what MediaWiki version is used), allowing one to select which ones are searched by default; see also Namespaces searched.

Misc settings
Show hoverbox over wiki links Underline links Format broken links like this (alternative: like this?). Justify paragraphs Auto-number headings Edit pages on double click (JavaScript) Enable section editing via [edit] links Enable section editing by right clicking on section titles (JavaScript) Show table of contents (for pages with more than 3 headings) Disable page caching
 * Show hoverbox over wiki links. This option determines whether a link title is put in the HTML code. The result depends on the browser: putting the mouse pointer over a link often displays this title in a hover box. However, some browsers show the URL anyway, so a link title may be superfluous. If enabled, the link title is the page name in the case of an internal link, the page name with prefix in the case of an interwiki link, and the URL in the case of an external link.
 * Underline links. Normally, link text will be underlined. Optionally, you may request that links not be underlined, although your browser may not respect this setting. Normally links that are not underlined can still be recognized by color. However, one can then not distinguish between two consecutive words being a single link or two links, without pointing at the words with the cursor. There is some discussion of changing the default here: see Link style vote
 * Format broken links  like this . An internal link to a non-existing pages is automatically a link to the edit page. By default the link label of b and a|b is "b", just like for links to existing pages. Alternatively the link label is a question mark inserted after "b", like this: The weather in London?. This helps if you have trouble seeing colors or if the colors are overridden in your browser settings. The appearance of the link is further determined by the style specified for css selectors "a.new" and "a.new:hover" (the example on the preferences page wrongly uses class="internal" for the question mark). Internal links to pages which do not yet exist currently appear on your browser like this: the weather in London. Normally, this is underlined and in red. With the trailing question mark link one can then not distinguish between a single word being linked or a phrase of more than one word, without pointing at the question mark with the cursor. Also, remember that the question mark does not mean that the information is uncertain.
 * Justify paragraphs. If set, article paragraphs will be formatted to avoid jagged line endings. If unset, the paragraphs will be formatted as-is.
 * Auto-number headings. This adds hierarchical outline-style numbering to headers in articles.
 * Edit pages on double click. If this box is checked, you can double-click on a page to edit it. This option requires Javascript to be enabled in your browser.
 * Enable section editing via [edit] links
 * Enable section editing by right clicking on section titles (JavaScript)
 * Show table of contents (for articles with more than 3 headings)
 * Disable page caching. This turns off page caching. This is useful if you're experiencing problems of seeing outdated versions of pages, but this comes at a cost of longer loading times.

Browser preferences
Browsers usually also allow you to specify preferences, e.g. font size and font type. The standard skin is compatible with your browser setting of font size and font type. The Cologne Blue skin has most text in a fixed font size, ignoring your browser setting. Some browsers, e.g. IE, allow you to specify that font size specified in the web page is ignored. In that case the font size in Cologne Blue is as specified in the browser, but with the line height not adjusted accordingly. Therefore a large font gives a messy result.

Providing your own CSS
Cascading Style Sheets are used to configure MediaWiki's visual appearance. You can specify your own CSS definitions and overwrite the default settings. See Help:User style.

pt:Ajuda:Preferências

title: Help:Preferences


text:
Help:User contributions

User contributions are lists of edits that a particular user has done.

Listing the edits of a particular user

 * if it is a user with a user page: bring up the user page, click "User contributions" in the sidebar or bottom bar.
 * if it is a user with a login name but without a user page: clicking on the name in Recent Changes or Page History brings up an edit box for a user page; press Cancel and click "User contributions" in the sidebar or bottom bar.
 * if it is a user without a login name, two methods are:
 * click on the IP address in Recent Changes or Page History
 * put the IP address in the search box and press Go

URL
Also, you can copy the URL:

http:// {wiki's_domain_name}/w/wiki.phtml?title=Special:Contributions&target=XX

(for this wiki) http://meta.wikimedia.org/w/wiki.phtml?title=Special:Contributions&target= (your user name)

or

http:// {wiki's_domain_name}/w/wiki.phtml?title=Special:Contributions/XX

where XX is the user name or IP address.

If you make a link you can also use the shorter form Special:Contributions/XX.

In both cases the local version of "Special" must be used.

With interwiki link e.g. en:Special:Contributions/XX.

Composition of the lines
The edits are shown from new to old. There is one line per edit, showing time, date, an M if the edit was marked "minor", the page name, and the edit summary (but not a marking for "new").

An edit is marked "(top)" if, at the time of producing the list, there are no more recent edits by anybody to the article concerned. Sysops also have a rollback link on these lines, see MediaWiki User's Guide: Reverting a page to an earlier version.

Due to this last item, applying "User contributions" to oneself is not only useful for refreshing one's memory and easily accessing pages one has been working on again, but also for finding out whether there have been any subsequent edits. Thus "watching" a recently edited article can be done by looking on one's user contributions list for edits without "(top)" or "(rollback)", which have not been followed by subsequent edits by oneself.

Also shown

 * the creation of a new page

Not shown
Not shown are:
 * edits of a page that has been deleted afterwards (unless it has been restored)
 * the deletion or restoration (undeletion) of a page (if the user is a sysop)

Privacy
Check the privacy policy, if any, of the site you use; for Wikimedia: draft privacy policy

title: Help:User contributions


text:
Help:Section editing demo

Section editing can be turned on by user preference. With the preference chosen, an [edit link] appears to the right of each section demarcated by a heading. For example, with the preference on, there appear two [edit] links on the righthand of this page.

This page is for demonstrating and testing.

Second section
This is the second section.

Third section
Third section.

Currently there is no link for editing the part before the first heading, but the URL works, e.g. for this page:

http://meta.wikimedia.org/w/wiki.phtml?title=Help:Section_editing&action=edit&section=0

It can be obtained conveniently by using an edit link and changing the number of the section to zero.

title: Help:Section editing demo


text:
Help:Special characters

- Other languages: de, es, fr, ja, sv

Systems for character encoding
Each MediaWiki project uses either of the following two systems for character encoding:

 * ISO-8859-1 - The Wikipedias in English, Dutch, Danish, and Swedish.
 * one byte per character
 * special characters that are not available in the limited character set are stored in the form of a multi-character code; there are usually two or three equivalent representations, e.g. for the character € the named character reference &euro; and  the decimal character reference &#8364; and the hexadecimal character reference &#x20AC;. The edit box shows the code, the webpage the character; unavailable characters which are copied into the edit box are first  displayed as character, and automatically converted to their decimal codes on Preview or Save.
 * the most common special characters, such as é, are in the character set, so code like &eacute;, although allowed, is not needed.
 * Unicode (UTF-8) - The other projects: the non-western Wikipedias, many western Wikipedias including French, German, and Spanish (but not the largest), the Wiktionaries, Meta, Wikibooks, Wikisource, Wikiquote
 * a variable number of bytes per character
 * special characters, including CJK characters, can be treated like normal ones; not only the webpage, but also the edit box shows the character; in addition it is possible to use the multi-character codes; they are not automatically converted in the edit box.

Note that Special:Export, at least within the English Wikipedia, exports using UTF-8 even though the database is encoded in ISO 8859-1.

To find out which character set applies in a project, copy e.g. ☉ (this should be a circle with a dot inside) into the edit box; if it is still there after pressing Preview, the project uses UTF-8. On other projects it should be converted to &#9737; in the edit box and show as ☉ in the page (but see also below on browser capabilities).

Also, in the HTML source of a page, near the top there is either

or

 . The Esperanto Wikipedia uses UTF-8, but a character like Ŝ is in the edit box automatically converted into the alternative notation Sx, because in some browsers it may not display in the edit box, even if it displays in the webpage, and Sx, whether resulting from this conversion or just typed, is rendered as Ŝ.

Plans to convert all languages to UTF-8? Problems with UTF-8?

Ways to enter special characters
Many characters not in the repertoire of standard ASCII will be useful—even necessary—for wiki pages, especially for foreign language textbooks. This page contains recommendations for which characters are safe to use and how to use them. There are three ways to enter a non-ASCII character into the wikitext:

 * 1) Enter the character directly from a foreign keyboard, or by cut and paste from a "character map" type application, or by some special means provided by the operating system or text editing application.  The web server should then be configured to announce which 8-bit character set is being used.
 * 2) Use an HTML named character entity reference like  .  This is unambiguous even when the server does not announce the use of any special character set, and even when the character does not display properly on some browsers. However it may cause difficulties with searches (see below).
 * 3) Use an HTML numeric character entity reference like  .  Unfortunately some old browsers incorrectly interpret these as references to the native character set.  It is, however, the only way to enter Unicode values for which there is no named entity, such as the Turkish letters.  Note that because the code points 128 to 159 are unused in both ISO-8859-1 (??? 128-159 are used in ISO-8859-1, but not ISO 8859-1) and Unicode, character references in that range such as   are illegal and ambiguous, though they are commonly used by many web sites.

Generally speaking, Western European languages such as Spanish, French, and German pose few problems. For specific details about other languages, see: Turkish. (More will be added to this list as contributors in other languages appear.)

For the purpose of searching, a word with a special character can best be written using the first method. If the second method is used a word like Odiliënberg can only be found by searching for Odili, euml and|or nberg; this is actually a bug that should be fixed—the entities should be folded into their raw character equivalents so all searches on them are equivalent. See also Help:Searching.

ISO-8859-1 Characters
The following extended ASCII characters are safe for use in all Wiki pages. The table below shows the character itself, lists the code for each character in hexadecimal and decimal, shows the HTML entity name, and gives the common name of the character.

These characters are a subset of the most common extended ASCII character set in use on the Internet, ISO 8859-1. MediaWiki pages are identified by the server as containing ISO-8859-1 text. The characters above are a subset selected to improve compatibility with other machines.

For example, the Apple Macintosh is in common use on the Internet, is not limited to any specific language, and its native character set (which is not ISO-8859-1) contains many of the common international characters. Many Macintosh browsers will correctly translate ISO text into the native character set, as long as the characters used are available. So the table above is the subset of ISO-8859-1 characters that are also available on the native Macintosh character set. (This is the situation up through Mac OS 9.x, at any rate; Mac OS X appears to use Unicode as its native encoding.)

Microsoft Windows standard code page 1252 set is a superset of ISO-8859-1, so these characters will be readable as is on Windows machines. The most common Latin character sets other than ISO-8859-1 are MS-DOS (pre-Windows) code page 437, Macintosh Roman, and other ISO sets such as ISO-8859-2. The number of pre-Windows MS-DOS machines with web browsers is small and they are often dedicated-purpose machines that wouldn't be using MediaWiki anyway, so it is reasonably safe to sacrifice compatibility with them for the sake of needed foreign characters. Other ISO sets are generally intended to be read by other browsers using those same sets in the same country, and so those pages should use a language-specific set.

These characters can be entered either as HTML named character entity references such as &agrave;, directly from foreign keyboards, or with whatever facilities are available to the Wiki author for entering these characters. For example, Wiki authors using Windows machines can enter these by holding down the Alt key while typing the 4-digit decimal code of the character on the numeric pad of the keyboard. It is important that all 4 digits (including the leading 0) be typed; typing a 3-digit code will enter characters from the obsolete code page 437. Wiki authors using Macintosh machines should take care to either use special facilities to enter these in ISO-8859-1 format rather than with the native character set, or else use HTML named character entity references. Note that some Windows users may have trouble with versions of Microsoft Internet Explorer that use "Alt-Left-Arrow" and "Alt-Right-Arrow" for page movement. These will interfere with entering codes that contain the digits 4 and 6. Use HTML named character entity references in this case.

The characters from the table above can be used directly as 8-bit characters in all Wiki pages, and are sufficient for all pages primarily in English, Spanish, French, German, and languages that require no more special characters than those (such as Catalan). These are also generally safe to use in titles, except for a few characters like double quotes, less than and greater than, and a few others.

Unsafe characters
Note especially what is missing here from the full ISO-8859-1 set: The broken bar ( [¦]¹), soft hyphen (  []¹), superscript digits (  [²]¹ and [³]¹), vulgar fractions (  [¼]¹ [½]¹ [¾]¹), Old English (and Icelandic and Old Norse language) eth and thorn (  [Ð]¹ [ð]¹ [Þ]¹ [þ]¹), and multiply sign (  [×]¹). These should be considered unsafe (and adequate substitutes are available for most of them).

Special care should be taken with characters that do exist in the native character set of popular machines but not in the above set. These are not safe, even though they may display correctly to you when you use them. Characters from Windows code page 1252 not in ISO-8859-1 include the euro sign ( [€]¹), dagger and double dagger (  [†]¹, [‡]¹), bullet (  [•]¹), trade mark sign (  [™]¹), typeset-style punctuation (see below), per mille sign (  [‰]¹), some Eastern European caron-accented letters, and the oe ligatures. Characters from the Macintosh Roman set not in ISO-8859-1 include dagger and double dagger, bullet, trade mark sign, a few math symbols such as infinity ( [∞]¹) and not equal (  [≠]¹), a few commonly-used Greek letters such as pi (  [π]¹), ligatures like oe and fl, typeset-style punctuation, per mille sign, and lone accents such as the breve, ogonek, and caron.

HTML 4.0 defines named character entities for some Latin characters not in ISO-8859-1 that are used by popular languages, such as OE ligature ( [Œ]¹ [œ]¹), uppercase Y with diaeresis (  [Ÿ]¹), and some Eastern European accented characters like   [š]¹. These are also unsafe; though if they entered as HTML named character entity references, they may display on some machines.

In short, don't assume that it is safe to use a special character just because it looks correct on your machine. Use the ones from the table above, and read and understand how to use others shown below.

 * ¹ sample in square brackets to see if they work on your configuration

Possibly usable non-ISO characters
Some characters not listed as safe above may still be usable when entered as named HTML character entity references, because web browsers will recognize them and render them correctly, perhaps by switching to alternate fonts as needed. All of these should be considered less safe to use than those above, but only in the sense that they may not display properly, though in the form of HTML character entity references they are unambiguous, and preserve data integrity.

For many of these, adequate substitutes and workarounds are available, and should be used when the value of making the text available to users of older computers and software exceeds the value of good presentation to those with newer software (in the judgment of the author or editor).

Typeset-style Punctuation
Absent from the ISO-8859-1 character set, but commonly used and present in both Macintosh Roman and Windows code page 1252 character sets, are proper English quotation marks and dashes. These can be entered as character entity references, and should appear correctly on most machines running recent software. Even on ISO-based machines such as Unix/X, browsers should be able to interpret these references and make appropriate substitutes using plain ASCII straight quotes and hyphens. (Mozilla does this correctly, for example.) These references were not present in older versions of HTML, so may not be recognized by older software. Since using these characters maintains data integrity even on those machines that may not display them correctly, it should be considered safe to use these unless proper display on old software is critical. German "low-9" quotation marks are a similar case, but are less commonly translated by browsing software, and so are not quite as safe. The table below shows these characters next to a capital letter "O" for better visibility:

Many web sites targeted for a Windows-using audience use code page 1252 references for these characters: for example, using  for the em dash. This is not a recommended practice. To ensure future data integrity and maximum compatibility, recode these as named references such as. If you really want to use a number, you can use.

Be aware that if you edit text in a separate word processor or other program to cut and paste into your browser, and it "automatically" converts quotes to the left and right "smart quotes" for you, you may unknowingly mangle markup, either your own or already existing, by replacing the standard quotes in HTML tags & properties with the smart quotes, which will cause the tags to fail in various ways. Furthermore, some people consider the extra encoding of smart quotes, fancy "&rsquo;" apostrophes used in possessives and contractions, etc., to be a waste of bytes that could be put to better use, and will replace them with the standard single characters at will.

Set your wordprocessor options such as Auto Edit and Auto Correction such that undesired replacements do not occur.

Greek letters and math symbols
Compare &nabla; and $$\nabla$$, giving ∇ and $$\nabla$$, respectively. Depending on preferences, the second may be the same as the first (HTML rendering), or an image. The HTML symbol depends on the font size and type, the image has a fixed size in terms of pixels. The color of symbol and background in the first case are those of text in general, according to the settings, and for the image they are black on white.

 * Note: much of the text below regarding mathematical symbols is obsolete now that MediaWiki supports embedded TeX within pages. Non-trivial mathematical equations are probably best notated in TeX using the MediaWiki math tags. See the page MediaWiki User's Guide: Editing mathematical formulae for more on this.

Web standards for writing about mathematics are very recent (In fact MathML 2.0 was just released in February of 2001.), so many browsers made before these standards were in place try to compensate by at least allowing characters commonly used in mathematics, including most of the Greek alphabet. These are necessarily entered as character entity references. Browsers often render these by switching to a "Symbol" font or something similar.

Upper- and lowercase Greek letters simply use their full names for character entities. These should, of course, only be used for occasional Greek letters in primarily-Latin text. (Large quantities of Greek-language text should be written using an editor with native UTF-8 Unicode support to facilitate editing and reduce page bloat). Here are a few samples:

Other common math symbols

Many of the symbols in the Windows "Symbol" font commonly used for rendering mathematics (such as the expandable bracket parts) are not present on most other machines, and not even present in Unicode 3.1 or as HTML named entities (though they are planned for Unicode 3.2). These are used by products such as TtH to render equations. You should be aware that if you use these symbols, you are restricting your audience to Windows users (Whether or not that's acceptable is a judgement you will have to make as an author.). (Disputed section)

Other common symbols
Some characters such as the bullet, Euro currency sign, and trade mark sign are special cases. They are likely to be understood and rendered in some way by many browsers. Because they are important for international trade, many computers specifically add them to fonts at some non-standard location and render them when requested, or else render them in special ways that don't require them to be present in a font. See below for how your browser renders these:

Other somewhat less commonly used symbols include these:

These should be considered unsafe to use except perhaps on pages intended for a specific audience likely to have very up-to-date software on popular machines. Even then, in some cases, IE 6.0 does not show the diamond symbol above. The regular diamond ♦ displays in IE 5 but not 6. The alternative code for the red diamond ♦, which works in IE 6 but not 5, is &diams;.

Unicode
The official character set of HTML 4.01 is the ISO 10646 Universal Character Set, which is equivalent to the character set defined by Unicode. Many browsers, though, are only capable of displaying a small subset of the full UCS repertoire.

Numeric character entity references are the only way to enter these characters into a Wiki page at present.

There are two ways:
 * decimal, e.g.  giving   Й  on your browser
 * hexadecimal, in this case  giving   Й .

These should be the same. However, decimal encoding will increase the number of browsers on which they will work. shows for all possible values whether they work and how they look in your browser, using decimal code.

For example, the codes  display on your browser as Й, ק, and م, which ideally look like the Cyrillic letter "Short I", the Hebrew letter "Qof", and the Arabic letter "Meem", respectively. It is unlikely that your computer has all of those fonts and will display them all correctly unless you have a Macintosh or have installed the fonts, though it may display a subset of them. Because they are encoded according to the standard, though, they will display correctly on any system that is compliant and has the characters available.

These characters should not be used in MediaWiki pages unless they make no difference to the understanding of the text, and are just extra information.

See Unicode and HTML for character entities tables.

Advanced Entities
The following additional entities are available. On some browsers, these are converted to Unicode equivalents.

[table missing]

Special Note: The Del symbol ("nabla;"), among others, is not supported on Windows 95 or 98. On the English Wikipedia it has been uploaded as an image, and can there be referenced as, or here and some other projects as http://en.wikipedia.org/upload/d/db/Del.gif , and looks like this: http://en.wikipedia.org/upload/d/db/Del.gif. On projects where this does not work, upload a copy of the image to that project.

However, the del symbol is usually found in formulæ which are better facilitated using MediaWiki User's Guide: Editing mathematical formulae.

Hieroglyphs
E.g. gives   See Help:WikiHiero syntax.

This is not dependent on browser capabilities, because it uses images on the servers.

Browser differences
Not all characters are displayed in all browsers. Also, since the font in the edit box may well be different from that of the rendered page, the browser may show the characters properly in one of the two areas and not in the other. For each, try to choose fonts which show all characters you need.

In the case of ISO-8859-1 encoding, special characters in the edit box are converted to code that consists of the common characters &, #, digits and a semi-colon, which are always displayed properly.

The HTML source code anyway shows the codes of both the characters that are displayed and those that are not. The HTML source code of a preview webpage also shows these for the wikitext.

Note that as a reader, it is best to use a browser with maximum capabilities, but as an author the least capable of the common browsers is a better guideline.

Alternatives include using a similar, more common symbol, or using an image, e.g. &: http://eo.wikipedia.org/upload/d/db/Ikono_tero_malgranda.png.

Also you can describe the character.

title: Help:Special characters


text:
Help:Table

MediaWiki supports different types of table syntax:
 * 1) XHTML
 * 2) HTML and wiki  syntax
 * 3) pipe-syntax

All three are supported by MediaWiki and create valid HTML output.

See also HTML element#Tables. Note however that the,  ,  , and   elements are currently not supported in MediaWiki.

Overview
Sample table

Pros Can be previewed/debugged with any XHTML editor

Can be formatted for easier reading

Well-known

Can be previewed/debugged with any HTML editor

Can be formatted for easier reading

Well-known

Takes less space than XHTML Easy to write

Easy to read

Takes little space

Cons Tedious

Takes a lot of space

Difficult to read quickly

Confusing, especially for people with little HTML experience

Poorly formed

Poorly delimited

Generally odd looking

Unfamiliar syntax

Rigid structure

Cannot be indented

XHTML HTML & Wiki-td Wiki-pipe

Guide to the pipe syntax
The pipe syntax, developed by Magnus Manske, substitutes pipes ( | ) for HTML. There is an on-line script which converts html tables to pipe syntax tables.

The pipes must start at the beginning of a new line, except when separating parameters from content or when using  to separate cells on a single line. The parameters are optional.

Tables
A table is defined by which equals and, or the first parameter gets ignored.

Rows

 tags will be generated automatically for the first row. To start a new row, use |- which results in
 Parameters can be added like this: |- params which results in

Note:
 *
 tags will be automatically opened at the first  equivalent
 *
 tags will be automatically closed at
 and
 equivalents

Cells
Cells are generated either like this: |cell1 |cell2 |cell3 or like this: |cell1||cell2||cell3 which both equal cell1	cell2	cell3	 so "||" equals "newline" + "|"

Parameters in cells can be used like this: |params|cell1||params|cell2||params|cell3 which will result in

Appearance

Mélange
Here's a more advanced example, showing some more options available for making up tables. You can play with these settings in your own table to see what effect they have. Not all of these techniques may be appropriate in all cases; just because you can add colored backgrounds, for example, doesn't mean it's always a good idea. Try to keep the markup in your tables relatively simple -- remember, other people are going to be editing the article too! This example should give you an idea of what is possible, though.

Source code

Appearance

Simple example
generates

Advanced example
Note the floating table to the right.

Nested table
gives a nested table

Nested tables have to start on a new line.

Text next to a table
You can use align=right, text after the table code appears to the left of the table. However, do not put preformatted text, it may overlap the table because it does not wrap.

text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text

To prevent this, use  :

text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text  text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text

Decimal point alignment
A method to get columns of numbers aligned at the decimal point is as follows:

gives

In simple cases one can dispense with the table feature and simply start the lines with a space, and put spaces to position the numbers:

432.1 43.21   4.321

title: Help:Table


text: Help:Template

title: Help:Template


text:
Help:Turkish characters

The Turkish alphabet contains six letters not present in ISO 8859-1, and that will therefore present problems for Wikipedia use: Dotted uppercase "I", dotless lowercase "i", upper- and lowercase "G" with breve accent, and upper- and lowercase "S" with cedilla.

Turkish computers may use character set ISO 8859-9 ("Latin 5"), which is identical to Latin 1 except that the rarely-used Icelandic characters "eth", "thorn", and "y with acute accent" are replaced with the needed Turkish characters. If you are reading Turkish text in Wikipedia, when you see these Icelandic characters they are probably meant to be the Turkish ones (users with Turkish computers may or may not see them properly). If you are entering Turkish text into Wikipedia, be aware that the Wikimedia server identifies web pages as ISO 8859-1, and there is no way to override this, so even if these characters appear correct to you, they are not properly encoded from the point of view of a non-Turkish Wiki reader.

You can check what your browser displays for these six positions in the standard ISO set here: Ð Ý Þ ð ý þ should appear as Eth, Y-acute, Thorn, eth, y-acute, thorn. If your system is using the Turkish 8859-9 set and ignoring the server instructions, these will appear as G-breve, I-dot, S-cedilla, g-breve, dotless-i, s-cedilla. Ironically, if these characters do appear to you as Turkish letters, it means they are incorrectly encoded.

Further, HTML 4.0 does not specify named character entities for these characters, so they cannot be entered into Wikipedia text in any portable way except 16-bit Unicode numeric character entity references, which only work in recent browsers, despite being the official standard. Consider anglicizing these characters. If you really must enter Turkish words with these characters into Wikipedia, to maintain data integrity at the expense of readability, use the following codes (the characters themselves appear after each code so you can see what your browser does with them):

These codes will probably appear correctly on most current browsers, but fail in archaic versions, even though they are according to standards. They are, however, totally unambiguous, and so will appear correctly as users upgrade to more compliant software. IE 5.0 on Windows NT, for example, does display these using the standard supplied Unicode fonts, as do Mozilla and Opera. Their incorrect appearance on older browsers such as Netscape may be acceptable in some situations, such as when an anglicized name is followed by a parenthesized Turkish equivalent as extra information not crucial to the article itself.

See also meta:MediaWiki User's Guide: Creating special characters

Next page: Creating Romanian characters >

title: Help:Turkish characters


text:
Help:Go button

The Go button appears on all MediaWiki pages in the standard skin, next to the search button. The function of the go button is to display a page directly, instead of first having to select it from the search result page. In other words, it allows you to quickly navigate from page to page without following links.

Use
To view a page, just enter its name in the search field and click "Go". The Go button is more complex than it looks. It works as follows (each time, only continuing if there is no match):

 * 1) Check existence of the page exactly as it is entered, e.g. Test Page and Test page are different pages (but most projects have case-insensitivity of the first character of the whole page name, and in the case of a namespace prefix, of the first character after that).
 * 2) Try all lower case (with the first letter capitalized), e.g. if you type "TEST PAGE", Test page and not Test Page would be displayed.
 * 3) Try the version with all words capitalized.
 * 4) Try the all upper case version.
 * 5) Try a case insensitive title search that also matches partial page titles. If there are several matches, priority is as follows: 1) main namespace, 2) talk pages for main namespace, 3) user pages, 4) user talk pages, 5) {project name}* pages, 6) {project name} talk pages, 7) image pages, 8) image talk pages. That is, for example, if both a talk page with the title and a normal page exist, the normal page is viewed.
 * 6) *Stopwords are ignored in this title search.
 * 7) *Prefixes like "User:" and "{project name}:" are currently treated as words in the title search, but not in the previous matching routines, where they are treated as proper namespace prefixes.
 * 8) Carry out a full text search as if you clicked the "Search" button; see Help:Searching.

If you use the Go button wisely, it will allow you to quickly jump to your most frequently used pages. It is also a good idea to use it for unambiguous searches -- if a direct match fails, it will always fall back to the normal search anyway, and if it succeeds, you are immediately taken where you want to go. In general, the go button generates little server load, and therefore usually remains functional even if the fulltext search is deactivated for performance reasons.

Special features
A special feature is that applying Go on an IP number gives the User contributions of that IP.

* This is a parameter you set while configuring MediaWiki.

title: Help:Go button


text:
Help:URL

URLs in external links
External links can start with " http:// " or " ftp:// "; "file://" does not work.

In external links, all symbols of the URL must be among: A-Z a-z 0-9 ._\/~%-+&#?!=@. If a URL contains a different character it should be converted; for example, ^ has to be written %5e, the hexadecimal ASCII value with a percent sign in front. A blank space can also be converted into an underscore.

Conversion:

"  #   $   %   &   '   *  ,   :   ;   <   >   [   ^   `   {   |   } %22 %23 %24 %25 %26 %27 %2a %2c %3a %3b %3c %3e %5b %5e %60 %7b %7c %7d

For the other characters either the code or the character can be used in internal and external links, they are equivalent. The system does a conversion when needed. E.g.

%C3%80_propos_de_M%C3%A9ta

is rendered as %C3%80_propos_de_M%C3%A9ta, almost like À propos de Méta, which leads to this page on Meta with in the address bar the URL

http://meta.wikipedia.org/wiki/%C3%80_propos_de_M%C3%A9ta

while http://meta.wikipedia.org/wiki/À_propos_de_Méta leads to the same.

URLs of pages within the projects
See en:Wikipedia:URLs; everything works the same, except that the domain names vary:

 * www.wikipedia.org
 * meta.wikipedia.org
 * wiktionary.org
 * quote.wikipedia.org
 * wikibooks.org
 * sources.wikipedia.org
 * sep11.wikipedia.org
 * test.wikipedia.org
 * xx.wikipedia.org with xx the language code, see The provisional portal of Wikipedia

In projects outside Wikimedia the "w/" in URLs like http://www.wikipedia.org/w/wiki.phtml?title=Main_Page&action=history is sometimes not used, sometimes different, e.g.:
 * http://www.disinfopedia.org/wiki.phtml?title=Disinfopedia_Main_Page&action=history
 * http://www.wikitravel.org/wiki/wiki.phtml?title=Main_Page&action=history

The default is /wiki/wiki.phtml, with in DefaultSetting.php :

$wgScriptPath = "/wiki"; $wgScript    = "{$wgScriptPath}/wiki.phtml";

There may be other variations, compare:
 * http://www.wikipedia.org/wiki/Vancouver
 * http://www.wikitravel.org/en/article/Vancouver

Old versions of pages
All old versions of all pages are numbered (with oldid) approximately in the order of becoming an old version, i.e. in chronological order of the next edit of the same page.

 * http://meta.wikimedia.org/w/wiki.phtml?title=Help:Link&oldid=53587 - normal link to old page
 * http://meta.wikimedia.org/w/wiki.phtml?title=Help:Link&oldid=53588 - number and name do not correspond; correct name is given, but without prefix
 * http://meta.wikimedia.org/w/wiki.phtml?title=Help:Lin&oldid=53587 - non-existing page name; becomes link to edit page
 * http://meta.wikimedia.org/w/wiki.phtml?oldid=53587 - no page name in the URL; correct name is given, but without prefix

New pages
New pages are numbered (with curid) chronologically.

 * http://meta.wikimedia.org/w/wiki.phtml?title=x&curid=9906 - gives the page with correct full name

See also Multiple titles.

Edit
Examples:

 * Edit the whole page: http://meta.wikimedia.org/w/wiki.phtml?title=Help:URL&action=edit
 * Edit the 5th section: http://meta.wikimedia.org/w/wiki.phtml?title=Help:URL&action=edit&section=5
 * Add at the end: http://meta.wikimedia.org/w/wiki.phtml?title=Help:URL&action=edit&section=1000 (use large section number)
 * Ditto with "Post a comment" feature: http://meta.wikimedia.org/w/wiki.phtml?title=Help:URL&action=edit&section=new

Purge
In some cases of caching problems, to update a page it can help to use "action=purge", in a URL like

title: Help:URL


text:
Help:User style

The user can customize: fonts, colors, positions of links in the margins, and many other things! This is done through custom stylesheets stored in subpages of the user's "User" page.

 * If you want a quick change, that someone else made, you may also be interested in Skins.

General
For each user-definable style, a skin is first selected, and a corresponding style sheet (CSS). For each skin, the user can make various choices regarding fonts, colors, positions of links in the margin, etc. Css is specified with reference to selectors : HTML elements, classes and id's specified in the HTML code. Accordingly, what the possibilities are for each skin can be seen by looking at the HTML source code of a page, in particular looking at these classes and id's: the more there are, the more versalitity there is.

For example in the English Wikipedia, the defaults are in

 * http://en.wikipedia.org/style/monobook/main.css and en:MediaWiki:Monobook.css
 * http://en.wikipedia.org/style/wikistandard.css and en:MediaWiki:Standard.css
 * http://en.wikipedia.org/style/cologneblue.css and en:MediaWiki:Cologneblue.css
 * http://en.wikipedia.org/style/nostalgia.css and en:MediaWiki:Nostalgia.css
 * en:MediaWiki:Myskin.css

and here on wikinews we have:

 * http://en.wikinews.org/style/monobook/main.css and MediaWiki:Monobook.css
 * http://en.wikinews.org/style/wikistandard.css and MediaWiki:Standard.css
 * http://en.wikinews.org/style/cologneblue.css and MediaWiki:Cologneblue.css
 * http://en.wikinews.org/style/nostalgia.css and MediaWiki:Nostalgia.css
 * MediaWiki:Myskin.css

The files in the style directory are for a given skin probably the same in each project. The name of the style directory is set on installation, see LocalSettings.php.

In the monobook skin, you can now change any aspect of the UI specified in http://en.wikipedia.org/style/monobook/main.css and en:MediaWiki:Monobook.css or similar using your own Javascript or CSS. The changes are in a subpage of your user page called monobook.css and monobook.js.

Also you can change the classic skin; your subpages should be named User:username/ standard.css and User:username/ standard.js (and similar for the other skins).

Just enter some css/js in that page. The preview works here in a special way: it allows viewing of the margins of the page (not the contents) on the basis of the style info in the page, provided that the skin used is the skin for which the page applies. This has limitations. E.g., one can preview how links in the margin will look, but these may not be of all the types one would want to check. After saving, while still on the page or while on any other page, do a forced reload (shift-reload/ctrl-f5) to get the new files.

The HTML source contains lines like

 @import "/style/wikistandard.css"; @import "/w/wiki.phtml?title=User:username/standard.css&action=raw&ctype=text/css";

for the project-wide CSS for the particular skin (in this case here on Meta referring to /style/wikistandard.css ) and the personal JS and CSS for a particular skin.

For "MySkin" there is no main.css applicable. The applicable personal css page is User:username/ myskin.css (all lowercase!).

See also Help:Sitewide css wiki page.

Css in user subpages vs. css in a local file
In addition to the above, or alternatively, a local CSS can be set on the browser. If one uses multiple browsers, each can be set to a different CSS. Each applies to the whole world wide web, not just a MediaWiki project (and does not depend on being logged in). However, a setting only affects other webpages if they use the same class name; e.g. a setting for the selector a.extiw affects fewer pages on the web than one for h2.

For lines of CSS which should be different on different MediaWiki projects, e.g. for a different background color for easy distinction, clearly the local CSS can not be used; at least these lines should be put in the user subpages.

Some computers, e.g. in internet cafes, do not allow users to set preferences for the browser. In that case the user subpages allow the setting of a user style anyway.

When the browser has been set to the option to ignore the font size specified in the webpage or external CSS, CSS lines regarding font size have to be put in the local CSS.

Css selectors
The css selectors, expressed in terms of elements, classes and id's, relevant for the style of the page body include:

 * a - note that "a" is not always a link, in particular, the "Special page" tab is not (see Help:Namespace)
 * a:link, a:visited - together these are all the links, as opposed to "a" elements which are just anchors - example: help:index
 * a#contentTop
 * a.external - http://example
 * a.extiw – interwiki link in page body - example
 * a.image – link from full image to image description page
 * a.internal – link to file itself (Media:), and links from thumbnail and magnifying glass icon to image description page (note that color and font size specified for a.internal are only applicable in the first case) - [[Media:example]]
 * a.new example
 * body.ns-0, ..., body.ns-15 (namespaces)
 * div#bodyContent
 * div#column-content
 * div#editsection
 * div#globalWrapper
 * div#tocindent
 * div.tocline
 * h1.firstHeading
 * h2
 * h3
 * img.tex TeX image
 * small - example
 * table.toc

Normal internal links are not in class internal (they used to be, and still are on sites that use an older version of the software, e.g. ); they can be styled referring to a:link and a:visited in general, after which styling of a.extiw etc. can provide for exceptions to this general style for links.

For interlanguage links:

 * #p-lang a

One may also have the style depend on the value of an attribute, e.g. with the selectors:

 * a[title ="User:username"]
 * a[title ="pagename"]
 * a[href ="full url "]

to color-code or highlight particular users (including oneself) and/or links to particular pages (like the bolding of watched pages on Recent Changes). This works in Opera, but not in IE. See also Help:Watching pages.

The watchlist and Recent Changes use two classes:

 * autocomment example
 * new (see below)

The page history has classes autocomment and:

 * user
 * minor

Thus the font specified for user applies in the page history, but not in the watchlist or Recent Changes.

Edit page
example example
 * Edit box: textarea#wpTextbox1
 * Edit summary box: input#wpSummary

Template parameters
A class or id can be a template parameter, an element as template parameter does not work.

Samples
/* make the background behind the content area and the tabs a light grey */
 * 1) content, #content table
 * 2) p-cactions ul li a { background: #f5f5f5; }

/* stop background image from scrolling with content area */ body { background-attachment: fixed; }

/* replace the book in the background with something else */ body { background: Purple; }

/* changes the colour of pre areas */ pre { background: White }

/* change the logo */
 * 1) p-logo a { background: url(http://en.wikipedia.org/upload/wiki.png) 35% 50% no-repeat !important; }

/* don't use any logo, move the boxes onto that area instead */
 * 1) p-logo { display: none }
 * 2) column-one { padding-top: 0; }

/* suppress the person icon by your username */ li#pt-userpage { background: none }

/* use browser prefs for text size and font */ body, #globalWrapper { font: inherit !important; }

/* always underline links */ a { text-decoration: underline; }

/* change colour of unselected tabs */
 * 1) p-cactions ul li a { background: #C7FDC7; }

/* change colour of selected tabs */
 * 1) p-cactions ul li.selected a { background: white; }

/* change border colour of selected tabs */
 * 1) p-cactions li.selected { border-color: #aaaaaa; }

/* tab bottom not removed on hover */
 * 1) p-cactions li a:hover { z-index: 0; text-decoration: none; }
 * 2) p-cactions li.selected a:hover { z-index: 3; }

/* style the search box and the buttons below it */ input.searchButton { background-color: #efefef !important; border: 1px outset !important; }
 * 1) searchInput { border: 1px inset !important; }

/* standard link colors */ a { color: #0000FF; } a:visited { color: #7F007F; } a:active, a.new { color: #FF0000; } a.interwiki, a.external { color: #3366BB; } a.stub { color: #772233; }

/* put scrollbar on pre sections instead of ugly cutoff/overlap in firefox */ pre { overflow: auto; }

Rounded corners in Mozilla
/* make a few corners round, only supported by moz/firefox/other gecko browsers for now */ -moz-border-radius-topleft: 1em; -moz-border-radius-topright: 1em; } -moz-border-radius-topleft: 1em; -moz-border-radius-bottomleft: 1em; } div.pBody { -moz-border-radius-topright: 1em; -moz-border-radius-bottomright: 1em; }
 * 1) p-cactions ul li, #p-cactions ul li a {
 * 1) content {

/* same following the css3 draft specs, any browsers supporting this? */ border-radius-topleft: 1em; border-radius-topright: 1em; } border-radius-topleft: 1em; border-radius-bottomleft: 1em; } div.pBody { border-radius-topright: 1em; border-radius-bottomright: 1em; }
 * 1) p-cactions ul li, #p-cactions ul li a {
 * 1) content {

Rounded corners/tabs links

 * Moz: see the rules above
 * http://www.vertexwerks.com/tests/sidebox/ -- sidebox formatting
 * http://www.alistapart.com/articles/slidingdoors2/ -- rounded tabs with rollover effect
 * http://www.alistapart.com/articles/customcorners/ -- another variant for rounded box corners
 * http://alistapart.com/articles/customcorners2/, Demo of this
 * http://www.alistapart.com/articles/mountaintop/ -- even weirder corner variants
 * http://www.virtuelvis.com/gallery/css/rounded/ -- simple freestyle variant using the :before and :after pseudo-elements (only css2 browsers, not in IE)

Print view tweaks
/*
 * Place all print-specific rules in an @media print block.

/* save ink and paper with very small fonts */ @media print { #footer, #content, body { font-size: 8pt !important; } h1 { font-size: 17pt } h2 { font-size: 14pt } h3 { font-size: 11pt } h4 { font-size: 9pt } h5 { font-size: 8pt } h6 { font-size: 8pt; font-weight: normal; } }

/* Advanced things: using :before and :after it's possible to add formatting this here adds the full href of a link after it (not needed in the current version): */ @media print { #content a:link:after, #content a:visited:after { content: " ( " attr(href) " ) "; } }

Make the user toolbar a sidebox
Tested to work in Camino and Safari. /* Transform the user toolbar into a sidebox */ position:relative; z-index:3; width: 11.6em; }
 * 1) p-personal {

width: 10.7em; border: none; margin: 0 0 0.1em 0em; float: none; overflow: hidden; font-size: 95%; background: White; border-collapse: collapse; border: 1px solid #aaaaaa; padding: 0 0.8em 0.3em .5em; }
 * 1) p-personal .pBody {

line-height: 1.5em; list-style-type: square; list-style-image: url("/style/monobook/bullet.gif");
 * 1) p-personal ul {

font-size:95%; margin: 0 0 0 1.5em; padding:0; text-align:left; text-transform: none; }

display: list-item; padding:0; margin: 0 0 0 0; margin-bottom: 0.1em; }
 * 1) p-personal li {

/* suppress the person icon by your username */ /* needed if not already in place */ li#pt-userpage { background: none } See the monobook main.css for the full styles in use by default.

Make the quickbar float / sideboxes have fixed position
''Kludgy version available. See talk page.''

Monobook menus with serif fonts in the content area
I've hacked together a q&d combinaton of monobook menus with serif fonts in the text area; there are some quirks and bugs (some because the css scheme of wikipedia doesn't seem to be soo thoughtful), but if you want to give it a try or have a look, go to and copy the first part. No warranty; works on Netscape7/Win98 for me ... -- Tillwe 14:05, 30 May 2004 (UTC)

Update (01.06.04): Now also displays table formated things more or less correctly. -- Tillwe 17:45, 1 Jun 2004 (UTC)

Moving category links
Moves category links in the upper right corner of content area, and paints them gray -- Tillwe 21:22, 31 May 2004 (UTC)
 * Small fix --Ævar Arnfjörð Bjarmason 22:05, 15 Jun 2004 (UTC)

/******************************************************************/ /* moving catlinks to the right                                  */ /******************************************************************/

/* move the catlinks box */ position:absolute; z-index:1; /* border: 1px solid #aaaaaa; background: #fafaff; */ right:1em; top:-0.25em; width:10.5em; float:right; margin: 0.2em; padding:0.2em; }
 * 1) catlinks {

/* format the catlinks itself */ p.catlinks { color: #aaaaaa; font-family: Verdana,sans-serif; font-size:67%; line-height: 1.5em; text-align:left; text-indent:0; text-transform: none; white-space:normal; margin: 0.2em; }

display: inline; }
 * 1) p-personal h5 {

/* format links in the catlinks (as distinguished from ":" and "|") */ p.catlinks a { color:#888888; }

Diff view styling
/* don't use a smaller font */ td.diff-addedline, td.diff-deletedline, td.diff-context { font-size: 100% };

/* underline just the text that's different */ span.diffchange { text-decoration:underline; }

External links on css

 * http://www.csszengarden.com/ -- inspiration
 * http://css-discuss.incutio.com/ -- highly concentrated info, very comprehensive
 * http://www.alistapart.com/ -- great articles
 * http://www.positioniseverything.net/ -- some entertaining ie bugs and more

Javascript
As mentioned above, the page to add is called monobook.js in this case. Want to have the same links as in the tabs also at the bottom of the page? - Clone it onload and drop it somewhere near the bottom. Want to add personal links/boxes/whatever ? You can do it.

Duplicate edit links at the bottom of the content area
See User Styles/bottom tabs

Changing access keys
These are now defined/set from js, you can easily customize them by changing some elements in the 'ta' array (see ). Example line: ta['ca-nstab-main'] = new Array('c','View the content page'); Just change 'c' to something else to change the access key. To disable all access and tooltips, drop ta = false; in your monobook.js.

Moving categories to top
The following code moves the category box to the top of the article. Of course, you might want to apply some CSS to make it look prettier:

function catsattop { var cats = document.getElementById('catlinks'); var bc = document.getElementById('bodyContent'); bc.insertBefore(cats, bc.childNodes[0]); }

An alternative that, when coupled with an appropriate stylesheet, will put the text up at about the same line as the title:

function categoryToTop { var thebody = document.getElementById('contentTop'); var categories = document.getElementById('catlinks');

if (categories != null) { categories.parentNode.removeChild (categories); thebody.parentNode.insertBefore(categories, thebody); } }

Some CSS to go with that...

/* move the catlinks box */ right:1em; top:-0.25em; max-width: 50%; /* this limits the box size, but doesn't set strictly */ float: right; margin: 0.5em; padding: 0.2em; }
 * 1) catlinks {

/* format the catlinks itself */ p.catlinks { font-size:67%; text-align:left; text-indent:0; text-transform: none; white-space:normal; margin: 0.2em; }

External links on JS

 * http://www.quirksmode.org/ -- see the Javascript and DOM section
 * http://www.alistapart.com/
 * http://www.quirksmode.org/dom/domform.html -- form cloning (might be possible to upload a few images at once using this, also a good starting point for the structure cloning)
 * http://www.quirksmode.org/dom/links.html -- more links with good summaries

title: Help:User style


text:
Wikinews talk:Style guide

Refactors
Discussions which have been implemented in the style guide have been refactored out. Please create a new section to discuss new changes and ideas.

 * 15 May 2005
 * Title Capitalization poll, reference vs. source, date vs. dateline vs. byline, date format and templates, use of subpages, use of fullstops in abbreviations, non-internet reference/original notes, names/titles of people, POV issues, spelling, sections, currencies, wide range of updates w/o discussion and w/discussion, citing wires.

From Talk:China detains and beats mourners for Zhao Ziyang
In an article, the use of links are defined as follows:
 * See also
 * Links to related Wikinews, Wikipedia articles, Wikisource documents, Commons and Upload files
 * Sources (used in article)
 * Online articles or sites - these are by nature ephemeral and may change, move, or disappear
 * Witnesses and personal observations - these are elements of Original reporting and should be archived online under Talk:Article name/Notes
 * References
 * Texts - should be cited using Author, Title of work, Publisher, copyright and year of publication, ISBN if available
 * Periodical artical (Journals, magazines, newspapers, etc.) cite Author, Title of article, Title of periodical, Volume and/or issue, Publisher, additional identifying characteristics if known.
 * External links
 * Online articles or sites which contain related subject matter. Wikinews does not take any responsibility for nor imply support or a relationship with external sites

Article length
See discussion about this at Water_cooler/policy

Proposal
flag Recognising the role factcheck articles play in many news organisations' content, I propose Wikinews allow there be 'analysis' articles. Not OR or synthesis, which certainly incorporate elements of original research & layout, but rather taking apart an issue, cutting it into FAQs and verifying contentious remarks. In short, this is synthesising and verifying existing remarks without necessarily a focal point.

Ex of questions for trend in Country X that wouldn't necessarily make a full story (unemployment is high; crime spike; Covid cases):

Why? / What about Country Y, Country Z? / What have politicians done about it? / What have the government promised? / What has the opposition said?

This, I understand, will benefit people looking toward longer, more holistic articles with more context than anything. --JJLiu112 (talk) 05:23, 3 April 2022 (UTC)
 * Apologies for the delayed comment. I think this is an interesting idea that is worth exploring, given that we need to breathe new life into Wikinews. My guess is that you were thinking of something like https://www.bbc.co.uk/news/60679290, where the BBC takes a current matter and looks at the surrounding issues? If so, I fully support this idea. If not, please could you clarify your suggestion? [24Cr][talk] 20:01, 14 June 2022 (UTC)
 * Yes, exactly. I was thinking of citing them, but I know great examples too as long-form articles, for example by France 24 and thejournal.ie. JJLiu112 (talk) 20:16, 14 June 2022 (UTC)
 * Then I fully support this. Can you write up a proposal for voting on at the Water Cooler? [24Cr][talk] 20:20, 14 June 2022 (UTC)
 * Seconded, think this is a good idea. LivelyRatification (talk) 22:10, 14 June 2022 (UTC)

"Sex, gender, and pronouns" section is baffling
Assuming that the "order of priority" is highest first (i.e. 1 is most important) then it's saying, to determine the sex/gender, ideally (#1) "use subject's preference), but in the absolute worst case (#4) "use the known sex/gender of the individual". And yet the "sex/gender of the individual" is precisely what the policy is dealing with, so #4 seems the most relevant. 2A00:23C5:FE56:6C01:3061:C90F:25B0:9A32 (talk) 12:29, 20 August 2023 (UTC)
 * Yes, #1 would be highest. It is standard to prioritize the subject's preference (the AP Stylebook recommends it, The Other Place has ). But I find #4's existence confusing because I don't understand how it differs from #1, given sources would likely be following the subject's preference. Looking at the 2010 discussion that prompted the addition of this section, it looks like Tempo, at least, was interpreting that as how a government describes a person, possibly conflicting with the person's self-description. Anyway, I invite Amgine, who drafted this list, to shed light here. Heavy Water (talk) 18:19, 20 August 2023 (UTC)

title: Wikinews talk:Style guide