text:
MediaWiki talk:Recentchangestext

This message on other sites, and in other languages on this site
Note that interlanguage links show up differently on a talk page like this.

Adding a tickbox to only show the edits that are the most recent
G'day, I do frequent the recent changes page a fair bit but am always manually checking if the listed edits have a [ rollback ] tag as around 90%+ edits that are not the most recent are because they have already been reverted / resolved. Can this become an actual function to enable to hide non-current edits? I feel it would be useful for other edittors without Rollback permissions or another alternative — IVORK Discuss 04:29, 1 March 2018 (UTC)
 * Support. I personally would find this extremely useful. — MrConorAE (👤U | 💬T | 📝C) 04:56, 10 November 2020 (UTC)
 * @ 👤U Maybe I'm misunderstanding, but is there not already a check box to only show "Latest Revision" down below the Minor edit filter? Back in 2018 when IVORK made that request it was probably not a thing, but it's there now (and, yes, it's very useful). Matt Deres (talk) 13:38, 10 November 2020 (UTC)
 * , indeed there is! How have I not seen that? Thanks so much. :D — MrConorAE (👤U | 💬T | 📝C) 18:49, 10 November 2020 (UTC)

Click 'diff' or 'hist' to open in a new tab please
I've been monitoring Recent Changes for some time now, and I would really welcome not having to right-click either 'diff' or 'hist' each time to get the results to display in a new tab. A simple mouse click ought to do it. It seems very unlikely that editors reviewing Recent Changes would want to intentionally leave that page, only to return and wait for their settings to reload after each check. So a simple click to open either a new tab or a new widow would be a very welcome enhancement to the interface. Nick Moyes (talk) 23:09, 10 June 2018 (UTC)
 * Just to add, that for mobile users the problem is terrible. For the last 18 months (since I first posted this) I've been predominantly editing via a mobile or a tablet. There's obviously no mouse on a mobile, and trying to tap the correct link on a tiny screen often results in the wrong change being selected, and having to go back and reload RecentChanges every single time basically stops me wanting to contribute to anti-vandalism whilst away from my home PC. Nick Moyes (talk) 09:18, 6 February 2020 (UTC)
 * Support, but for the time being you can middle click on a mouse to open any link in a new tab. Yeenosaurus   (talk) 🍁 04:46, 22 June 2018 (UTC)
 * Also support - this would be very useful. — MrConorAE (👤U | 💬T | 📝C) 18:54, 10 November 2020 (UTC)

Span markup causing lint error and suppressing display
Prior to the two edits of Roan Kattouw (WMF) of 6 December 2017, the wikitext was

displaying as
 * This is a list of recent changes to pages linked from a specified page (or to members of a specified category). Changes to pages on your watchlist are shown with a green bullet.

Following those two edits, the wikitext is

displaying as
 * Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on your Watchlist are shown in bold with a green bullet.

There are two problems.
 * 1) There is a missing end tag lint error for   because there are 4   and only 3  . The missing   could presumably go at the end.
 * 2) the   markup suppresses display. At least in my universe, all I see is
 * Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category).

This is bizarre. What is going on? —Anomalocaris (talk) 10:04, 6 May 2019 (UTC)
 * (clarification: this is about MediaWiki:Recentchangeslinked-summary, whose talk page redirects here for some reason)
 * Whoops, sorry about the missing  tag. I've fixed it, thanks for pointing it out.
 * As for the markup suppressing the display, what's going on here is that the sentences in the span tags are only visible if you've got certain gadgets enabled. For example, if you have the "Display green collapsible arrows" gadget enabled, then MediaWiki:Gadget-WatchlistGreenIndicators.css will cause the text about green bullets to be shown, and if you have the "Display pages on your watchlist that have changed since your last visit in bold" gadget enabled, then MediaWiki:Gadget-WatchlistChangesBold.css will cause the text about bolding to be shown. If you have neither of those enabled, MediaWiki:Gadget-WatchlistBase.css hides all of these spans. This way, the text matches the features you have enabled: if your watchlist is configured not to show green bullets, you also don't see the part of the message that explains what the green bullets mean. Hope that makes sense, and happy to answer any follow-up questions. --Roan Kattouw (WMF) (talk) 00:25, 7 May 2019 (UTC)

 * Roan Kattouw (WMF): Thank you for the explanation and for fixing MediaWiki:Recentchangeslinked-summary, but I think you want to move the final  to after the period, because for those of us with the gadgets disabled, we see the above noted sentence, except it ends period space period. —Anomalocaris (talk) 00:40, 7 May 2019 (UTC)
 * Good catch! Fixed. --Roan Kattouw (WMF) (talk) 00:42, 7 May 2019 (UTC)
 * Roan Kattouw (WMF): All fixed now, thanks! —Anomalocaris (talk) 02:22, 7 May 2019 (UTC)

Protected edit request on 23 May 2019
Please remove

Milestones –

since Milestones is marked as historical. Thanks, --DannyS712 (talk) 19:01, 23 May 2019 (UTC)
 * Yes check.svg Done — Martin (MSGJ · talk) 12:36, 24 May 2019 (UTC)

alvin kageliza rueywa
le a e parti on voye so promine du large — Preceding unsigned comment added by Alvin kageliza (talk • contribs) 17:13, 16 July 2020 (UTC)

Interwiki (at Wikidata) not available for special page
This change (Special:Diff/565539355) makes the interwiki links disappears because the special page has no items on the wikidata. Manual interwiki links shouldn't be deleted, also, I've tested it at idwiki here. --Hidayatsrf (talk) 04:24, 3 August 2020 (UTC)
 * ❌ WP:BRD, phase 3. I don't think this is necessary, we don't put interwiki links on any of our other Special pages (e.g. Special:Watchlist, Special:NewPages), Special:Log) so don't really need these here either. —  xaosflux  Talk 14:07, 3 August 2020 (UTC)

Filter options changes
It's been a while since I've done recent changes patrol and I love the new filtering mechanism, but I have a question and a couple of requests: Just some suggestions; the tool is already much better than the ones I used previously; I really appreciate all the work that surely went into it. Please PING me with any replies. Matt Deres (talk) 17:24, 23 October 2020 (UTC)
 * Sometimes, I don't see the options regarding User Intent Predictions. The Contribution Quality, User Reg, and other options are always there (AFAICT), but the User Intent section seems to come and go. Any idea why that would be? The issue persists even if I clear my filter preferences.
 * First request: would it be possible to allow for expanding the number of returns or going back further in time? At times, I'll get "caught up" to the 50 diffs that show and there's no way for me to go back any further other than changing the filters, which somewhat defeats the purpose of the filters. Even just showing 100 or 150 instead of 50 would be great.
 * Second request: I really like the predictive filters and they seem to work pretty well, but there's another angle to finding vandalism and that is the fact that some topics are higher targets for what I'll call "Casual vandalism". These are not typically the targets of dedicated vandals, but the stuff that kids tend to mess around with. The ones that immediately come to mind are schools, dates, and towns. Everyone likes adding their friend's name as "greatest sex machine". I know our categories are maybe not perfect, but is there a way we could use them to establish a filter regarding how likely the topic of the article is as a target of poor edits?
 * - as far as I know, you can modify the number & timespan of edits to display by clicking the button on the far right of the screen that says X changes, X days. — MrConorAE (👤U | 💬T | 📝C) 19:46, 10 November 2020 (UTC)
 * - Thanks! Matt Deres (talk) 22:59, 10 November 2020 (UTC)

Filters sometimes do not appear
Sometimes, certain categories of filters do not show up when I open the recent changes page. It seems to affect the "Contribution quality predictions" and "User intent predictions" most often. Refreshing my browser's cache does not resolve the issue, but it does go away on its own. Has anyone else experienced this?

I'm mainly using Chrome. Ixfd64 (talk) 00:54, 6 December 2020 (UTC)

Suggested page layout improvements
RecentChanges is a repetitive process, and anything to minimise the unnecessary mouse movements, or keyboard and finger taps would be likely to be an improvement for everyone. The following layout suggestions would make the task a lot simpler in my view, and I propose that they be implemented: *Line up 'diff' links so that they appear directly above one another (and the same with 'hist' links). i.e. Move them to appear as two columns between the timestamp and the article title. This would avoid the need to constantly move the mouse cursor around the page to click each diff or to view other details via a Navigation Popup mouseover. On a mobile, one sometimes has to move the whole screen around when the article title is a long one in order to find the diff link before attempting to tap it. *In mobile (BUT desktop) view: Centre the timestamp with the row text - it looks terrible with the timestamp top-justified and the rest of the row text lower down (as seen in Safari on iOS).
 * Increase the spacing between between 'diff' and 'hist' links for mobile phone users in desktop mode to avoid frequent accidental tapping of the wrong link.
 * Make each clicked link open automatically in a new Tab - this would keep the main Recent Changes page open for continued monitoring. Needed for both mobile users and desktop users. First suggested here in 2018
 * In mobile view: Increase the font size of the text for 'diff' and 'hist' - these are the most important bits of the page to tap, yet are the tiniest and hardest to locate on a small screen.

I'm sure the layout and functionality of this page didn't used to be this poor. Maybe it's my imagination, but nothing I see in the current, illogical layout seems to offer anything like the efficient process it once was. I would welcome other Change Patrollers' feedback on these proposals. Nick Moyes (talk) 19:58, 29 December 2021 (UTC)
 * Note: I've struck some of my comments because I'd not realised my long standing favourite settings had been hijacked when I accidentally clicked on another user's settings at a Teahouse post and they changed mine to the awful layout seen when Group results by page is ticked in the settings here. That makes me think it could be helpful if one could somehow save one's preferred filter settings without them being accidentally lost in this way. Nick Moyes (talk) 21:37, 29 December 2021 (UTC)
 * None of these suggestions are realizable on this page. WP:VPT/WP:VPPRO and/or WP:PHAB for them as a start. I'll leave some comments anyway:
 * Increase spacing and size for mobile users of diff/hist: Mobile users (https://en.m.wikipedia.org/wiki/Special:Watchlist) have a much friendlier layout by default for watchlist and recent changes. I would guess you're using a desktop skin at mobile resolution as a result?...
 * New tabs: Bad for accessibility. If you need it, middle click or right click and so on. I'm sure it'd be a trivial user script as well.
 * Being hijacked by another's settings is a feature-bug to some degree, but already has a Phabricator task somewhere. I am pretty sure filed it.
 * In general, changes to this areas are hard to realize because of the multitude of settings that change what is sent to the browser (I vastly prefer group results by page as a particular example) and layouts of interest (mobile vs. desktop) and the fact that recent changes and watchlist have quite a bit of shared code. Izno (talk) 01:07, 4 January 2022 (UTC)
 * (Increasing the size and spacing of those elements can also be done in a local skin.css page.) Izno (talk) 01:18, 4 January 2022 (UTC)
 * @Nick Moyes, it sounds like you got bit by T202916. There's a user script in the comments that aggressively re-fixes your prefs (every single time you load any page at all). Whatamidoing (WMF) (talk) 19:07, 4 January 2022 (UTC)
 * Oh, I can so relate to the angst in that Phab report! I still can't fathom what actual point there is to "Group results by page". I see absolutely no difference to content, other than an enhanced, shitty page layout. Yes, I edit on mobile, but always in desktop view (and sometimes under the bedsheets when I can't sleep at night!) Trivial user scripts may be trivial to some people, but to this mere mortal they're still magical pixie dust that I adore when someone else makes them. Prioritising accessibility over common-sense functionality is a proverbial pain in the a... Nick Moyes (talk) 01:33, 5 January 2022 (UTC)
 * Well, after reading the Phab ticket's description, you might have come to the conclusion that I have at least a slight preference for the One True™ format, aka the format that was the default when I was a new editor.
 * I agree with you that user scripts are basically magic. It is not reasonable to expect even experienced editors like us to be able to write them.  One of the perks of this job is having a couple of devs I can whine at.  If I'm annoying enough, they will sometimes write me a script to make me be quiet.  If you look at m:User:Whatamidoing (WMF)/global.js, then the ones labeled "// Happiness //", "//Blame this one on Ed//", "//David L said not to use this //", and "// nowiki button for the 2017WTE" were all made because I whined about a problem.  (Happiness is probably redundant to enabling DiscussionTools in Special:GlobalPreferences now.  Ed's will give you a URL to an exact comment (not just a section), and could be useful to any experienced editor.  David's adds the Special Character tool to the Reply tool's toolbar, to get me to quit whining about T249072.  The nowiki button (written by Matma Rex) adds a nowiki option to the 2017WTE's character formatting menu.  Feel free to copy any of them that sound useful to you.)
 * Whatamidoing (WMF) (talk) 16:42, 5 January 2022 (UTC)
 * Whatamidoing (WMF) (talk) 16:42, 5 January 2022 (UTC)

Filtering New articles
Possible I've missed it but is there a way to filter redirects from appearing when one hopes to look at newly created articles? If there's not an explicit way to do so, is there a workaround, like only seeing page creations above a certain size? Thanks! — Mainly 15:55, 30 January 2022 (UTC)

Interface protected edit request on 31 May 2022
Change the text to  on MediaWIki:Recentchanges-summary. TOPaner (talk) 10:27, 31 May 2022 (UTC)
 * ❌ if we were going to go back to mediawiki default, we wouldn't hard code that here. That being said, I don't think that is an improvement. So now we're at WP:BRD step 3, feel free to continue discussing below - if a consensus emerges for a change, reactivate the edit request above. — xaosflux  Talk 15:00, 31 May 2022 (UTC)

Question about the filters
Generally speaking, the first two filters at the top of the list are regarding quality (good versus problematic) and intention (good faith versus bad). However, sometimes when I check RC, the intention options are not available. Why is this? Matt Deres (talk) 20:45, 15 April 2023 (UTC)

title: MediaWiki talk:Recentchangestext


text:
Lenne

The Lenne is a tributary of the river Ruhr in the Sauerland hills, western Germany. It has caused flooding in recent years.

Having its source on top of the Kahler Asten near Winterberg in an intermittent spring at an elevation of 2,687 ft, the Lenne ends after a course of 129 km flowing into the Ruhr river near the city of Hagen. With an average discharge of 25 m³/s near its mouth, it is the main tributary of the Ruhr.

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

title: Lenne


text:
Allan Hills 84001

Allan Hills 84001 (ALH84001 ) is a fragment of a Martian meteorite that was found in the Allan Hills in Antarctica on December 27, 1984, by a team of American meteorite hunters from the ANSMET project. Like other members of the shergottite–nakhlite–chassignite (SNC) group of meteorites, ALH84001 is thought to have originated on Mars. However, it does not fit into any of the previously discovered SNC groups. Its mass upon discovery was 1.93 kg.

In 1996, a group of scientists found features in the likeness of microscopic fossils of bacteria in the meteorite, suggesting that these organisms also originated on Mars. The claims immediately made headlines worldwide, culminating in U.S. president Bill Clinton giving a speech about the potential discovery. These claims were controversial from the beginning, and the wider scientific community ultimately rejected the hypothesis once all the unusual features in the meteorite had been explained without requiring life to be present. Despite there being no convincing evidence of Martian life, the initial paper and the enormous scientific and public attention caused by it are considered turning points in the history of the developing science of astrobiology.

History and description
ALH 84001 was found on the Allan Hills Far Western Icefield during the 1984–85 season, by Roberta Score, Lab Manager of the Antarctic Meteorite Laboratory at the Johnson Space Center.

ALH84001 is thought to be one of the oldest Martian meteorites, proposed to have crystallized from molten rock 4.091 billion years ago. Chemical analysis suggests that it originated on Mars when there was liquid water on the planet's surface.

In September 2005, Vicky Hamilton, of the University of Hawaii at Manoa, presented an analysis of the origin of ALH84001 using data from the Mars Global Surveyor and 2001 Mars Odyssey spacecraft orbiting Mars. According to the analysis, Eos Chasma in the Valles Marineris canyon appears to be the source of the meteorite. The analysis was not conclusive, partly because it was limited to areas of Mars not obscured by dust.

The theory holds that ALH84001 was blasted away from the surface of Mars by the impact of a meteor about 17 million years ago, and fell on Earth about 13,000 years ago. These dates were established by a variety of radiometric dating techniques, including samarium–neodymium (Sm–Nd), rubidium–strontium (Rb–Sr), potassium–argon (K–Ar), and carbon-14 dating. Other meteorites that have potential biological markings have generated less interest because they do not contain rock from a "wet" Mars; ALH84001 is the only meteorite originating when Mars may have had liquid surface water.

In October 2011, it was reported that isotopic analysis indicated that the carbonates in ALH84001 were precipitated at a temperature of 18 C with water and carbon dioxide from the Martian atmosphere. The carbonate carbon and oxygen isotope ratios imply deposition of the carbonates from a gradually evaporating subsurface water body, probably a shallow aquifer meters or tens of meters below the surface.

In April 2020, researchers reported discovering nitrogen-bearing organics in Allan Hills 84001.

A later study in January 2022 concluded that ALH84001 did not contain Martian life; the discovered organic molecules were found to be associated with abiotic processes (i.e., "serpentinization and carbonation reactions that occurred during the aqueous alteration of basalt rock by hydrothermal fluids") produced on the very early Mars 4 billion years ago instead.

Hypothetical biogenic features
On August 6, 1996, a team of researchers led by NASA scientists including lead author David S. McKay announced that the meteorite may contain trace evidence of life from Mars. This was published as an article in Science a few days later. Under a scanning electron microscope, structures were visible that some scientists interpreted as fossils of bacteria-like lifeforms. The structures found on ALH84001 are 20–100 nanometres in diameter, similar in size to theoretical nanobacteria, but smaller than any cellular life known at the time of their discovery. If the structures had been fossilized lifeforms, as was proposed by the so-called biogenic hypothesis of their formation, they would have been the first solid evidence of the existence of extraterrestrial life, aside from the chance of their origin being terrestrial contamination.

The announcement of possible extraterrestrial life caused considerable controversy. When the discovery was announced, many immediately conjectured that the fossils were the first true evidence of extraterrestrial life—making headlines around the world, and even prompting President of the United States Bill Clinton to make a formal televised announcement to mark the event.

McKay argued that likely microbial terrestrial contamination found in other Martian meteorites does not resemble the microscopic shapes in ALH84001. In particular, the shapes within ALH84001 look intergrown or embedded in the indigenous material, while likely contamination does not. While it has not yet conclusively been shown how the features in the meteorite were formed, similar features have been recreated in the lab without biological inputs by a team led by D.C. Golden. McKay says these results were obtained using unrealistically pure raw materials as a starting point, and "will not explain many of the features described by us in ALH84001." According to McKay, a plausible inorganic model "must explain simultaneously all of the properties that we and others have suggested as possible biogenic properties of this meteorite." The rest of the scientific community disagreed with McKay.

In January 2010, a team of scientists at Johnson Space Center, including McKay, argued that since their original paper was published in November 2009, the biogenic hypothesis has been further supported by the discovery of three times the original amount of fossil-like data, including more "biomorphs" (suspected Martian fossils), inside two additional Martian meteorites, as well as more evidence in other parts of the Allan Hills meteorite itself.

However, the scientific consensus is that "morphology alone cannot be used unambiguously as a tool for primitive life detection." Interpretation of morphology is notoriously subjective, and its use alone has led to numerous errors of interpretation.

Features of ALH84001 that have been interpreted as suggesting the presence of microfossils include:

 * The structures resemble some modern terrestrial bacteria and their appendages. Though some are much smaller than any known extant Earth microbes, others are of the order of 100–200 nm in size, within the size limits of Pelagibacter ubique, the most common bacterium on Earth, which ranges from 120 to 200 nm, as well as hypothetical nanobacteria. RNA organisms, which are expected to have lived on Earth during the time period when ALH84001 was ejected from Mars, may also have been as small or smaller than these structures, as modern RNA viruses and viroids are often as little as a few dozen nanometers. Some of the structures are even larger, 1–2 microns in diameter. The smallest structures are too small to contain all the systems required by modern life.
 * Some of the structures resemble colonies and biofilms. However, there are many instances of morphologies that suggested life and were later shown to be due to inorganic processes.
 * The meteorite contains magnetite crystals of the unusual rectangular prism type, and organized into domains all about the same size, indistinguishable from magnetite produced biologically on Earth and not matching any known non-biological magnetite that forms naturally on Earth. The magnetite is embedded in the carbonate. If found on Earth it would be a very strong biosignature. However, in 2001, scientists were able to explain and produce carbonate globules containing similar magnetite grains through an inorganic process simulating conditions ALH84001 likely experienced on Mars.
 * It contains polycyclic aromatic hydrocarbons (PAHs) concentrated in the regions containing the carbonate globules, and these have been shown to be indigenous. Other organics such as amino acids do not follow this pattern and are probably due to Antarctic contamination. However, PAHs are also regularly found in asteroids, comets and meteorites, and in deep space, all in the absence of life.

In popular culture
The 2001 mystery-thriller novel Deception Point by Dan Brown, about a discovered meteorite that seems to prove the existence of extraterrestrial life, was inspired by ALH84001.

title: Allan Hills 84001


text:
Wikipedia:Manual of Style/Dates and numbers

<!-- PLEASE MAKE MINOR CHANGES TO THIS TEXT ALSO TO THE EQUIVALENT TEXT AT MOS. MORE SIGNIFICANT CHANGES, ESPECIALLY TO THE ACTUAL STYLE RECOMMENDATIONS, NEED TO BE FLAGGED AT THE WT:MOS TALK PAGE BEFORE IMPLEMENTATION HERE AND AT MOS, UNLESS THEY INVOLVE SECTIONS HERE THAT HAVE NO EQUIVALENT AT MOS (e.g. GEOGRAPHICAL COORDINATES).

FORMATTING: This page makes heavy and very particular use of a lot of specific formatting. To avoid confusion concerning the proper formatting of units, symbols, values, variables, code, etc., please observe the following markup conventions on this page: - Use to mark up positive examples or required text. - Use to mark up negative examples or deprecated items. - Use to mark up items that may or may not be applied depending on context. - Use to mark up items that are very rarely applied – dubious, deprecated, disputed, only used in one context (this template may not be needed on this page but is available). - Use double quotes to mark up words-as-words, "scare-quoting", and quoted sources, but not for unusual purposes. Italics are used heavily on this page for many other things, so do not use them for words-as-words. - Use to mark up emphasis. - Reserve plain italic only for conventional stylistic, non-semantic use of italics (e.g. for titles of major published works, foreign phrases, etc.; see above about words-as-words). - Use bold to mark up inline headers. - Use to mark up strong emphasis (rarely needed;  will usually suffice). - Use  (or   if needed) to mark up code examples, including individual special characters. Do not use ; this element no longer exists in HTML5. - Use to mark up variables and variable input, not, ..., or other markup. - Use to illustrate or name templates (or use undefined if nested inside  ). - Use ... in running prose to indicate editor input choices for templates (not necessary in actual code examples inside ) - Use ... in running prose to indicate example code output that should be monospaced, if the need arises. - Use spaced en dashes, not run-together em dashes, especially with markup examples, so the dash cannot be confused as being part of the example. - Use for cross-references to other sections or pages. This produces consistent formatting, and helps identify cross-references in the code for periodic checking against "advice forking". - Avoid italicization other than as specified above. - Avoid - in or near examples; should probably only be used inside tables, when width is a concern. - Do not mark up mention of units and the like outside the context of advice about their use. Example: 'Use m for "minute" only where there is no danger of confusion with meter' ["meter" is not marked up here per this convention; "m" is marked up with for conditional use; "minute" is double-quoted for words-as-words use]. -->

This page guides the presentation of numbers, dates, times, measurements, currencies, coordinates, and similar items in articles. The aim is to promote clarity, cohesion, and consistency, and to make the encyclopedia easier and more intuitive to use. For numbers, dates, and similar items in Wikipedia article titles, see the "Naming conventions (numbers and dates)" guideline.

Where this manual gives options, maintain consistency within an article unless there is a good reason to do otherwise. The Arbitration Committee has ruled that editors should not change an article from one guideline-defined style to another without a substantial reason unrelated to mere choice of style; edit-warring over optional styles is unacceptable. If discussion fails to resolve the question of which style to use in an article, defer to the style used by the first major contributor.

Quotations, titles, etc.
Quotations, titles of books and articles, and similar "imported" text should be faithfully reproduced, even if they use formats or units inconsistent with these guidelines or with other formats in the same article. If necessary, clarify via [bracketed interpolation], article text, or footnotes.

Non-breaking spaces
Guidance on the use of non-breaking spaces ("hard spaces") is given in some sections below, but not all situations in which hard spaces (nbsp or ) or  may be appropriate are described.

Statements likely to become outdated
Except on pages that are inherently time-sensitive and updated regularly (e.g. the "Current events" portal), terms such as now, today, currently, present, to date, so far, soon, upcoming, ongoing, and recently should usually be avoided in favor of phrases such as during the 2010s, since 2010, and in August 2020. Wording can usually be modified to remove the "now" perspective: not she is the current director but she became director on 1 January 2024; not 2010–present but beginning in 2010 or since 2010. Terms likely to go out of date include best known for, holds the record for, etc. For current and future events, use phrases such as as of July 2024 or since the beginning of 2024 to signal the time-dependence of the information; use the template as of (or updated) in conjunction. Relative-time expressions are acceptable for very long periods, such as geological epochs: Humans diverged from other primates long ago, but only recently developed state legislatures.

Dates, months, and years

 * These requirements do not apply to dates in quotations or titles;.
 * Special rules apply to citations;.
 * See also Overview of date formatting guidelines.

Formats

 * Dates, years, and other chronological items should be linked only when they are relevant to the subject and likely to be useful to a reader; this rule does not apply to articles that are explicitly on a chronological item, e.g. 2002, 19th century.
 * For issues related to dates in sortable tables, and, or consider using.
 * Phrases such as Fourth of July (or JulyFourth, but not July4th), Cinco de Mayo, Seventh of March Speech, and Sete de Setembro are proper names, to which rules for dates do not apply (A typical Fourth of July celebration includes fireworks).

Strong national ties to a topic
For any given article, the choice of date format and the choice of national variety of English (see ) are independent issues.
 * Articles on topics with strong ties to a particular English-speaking country should generally use the date format most commonly used in that nation. For the United States this is (for example) July 4, 1976; for most other English-speaking countries it is 4 July 1976.
 * Articles related to Canada may use either format with (as always) consistency within each article.
 * In topics where a date format that differs from the usual national one is in customary usage, that format should be used for related articles: for example, articles on the modern US military, including biographical articles related to the modern US military, should use day-before-month, in accordance with US military usage.

Retaining existing format

 * If an article has evolved using predominantly one date format, this format should be used throughout the article, unless there are reasons for changing it based on the topic's strong ties to a particular English-speaking country, or consensus on the article's talk page.
 * The date format chosen in the first major contribution in the early stages of an article (i.e., the first non-stub version) should continue to be used, unless there is reason to change it based on the topic's strong ties to a particular English-speaking country, or consensus on the article's talk page.
 * Where an article has shown no clear sign of which format is used, the first person to insert a date is equivalent to "the first major contributor".

Era style

 * The default calendar eras are Anno Domini (BC and AD) and Common Era (BCE and CE). Either convention may be appropriate for use in Wikipedia articles depending on the article context. Apply with regard to changes from one era to the other.
 * Use either the BC–AD or the BCE–CE notation consistently within the same article. Exception: do not change direct quotations, titles, etc.
 * An article's established era style should not be changed without reasons specific to its content; seek consensus on the talk page first (applying ) by opening a discussion under a heading using the word era, or another similarly expressive heading, and briefly stating why the style should be changed.
 * BCE and CE or BC and AD are written in upper case, unspaced, without a full stop (period), and separated from the numeric year by a space (5BC, not 5BC). It is advisable to use a non-breaking space.
 * AD appears before or after a year (AD106, 106AD); BCE, CE, and BC always appear (106CE, 3700BCE, 3700BC).
 * In general, omit CE or AD, except to avoid ambiguity or awkwardness.
 * Typically, write The Norman Conquest took place in 1066 not 1066CE or AD1066.
 * But Plotinus lived at the end of the 3rd century AD (not simply at the end of the 3rd century) may avoid confusion unless the era is clear from context.
 * One- and two-digit years may look more natural with an era marker (born in 2 AD or born January 15, 22 CE, not born in 2 nor January 15, 22).
 * Ranges beginning in BC / BCE should specify the ending era: write 450 to 200 BCE or 450 BC to 200 BC or 450 BCE to 200 CE, but not 450 BCE to 200.
 * Uncalibrated (BCE) radiocarbon dates: Calibrated and uncalibrated dates can diverge widely, and some sources distinguish the two only via BCE or BC (for calibrated dates) versus bce or bc (uncalibrated). When feasible, avoid uncalibrated dates except in direct quotations, and even then ideally give the calibrated date in a footnote or square-bracketed note – [3250BCE calibrated], or at least indicate the date type – [uncalibrated]. This also applies to other dating systems in which a calibration distinction is drawn.
 * BP or YBP: In scientific and academic contexts, BP (Before Present) or YBP (years Before Present) are often used. (Present in this context by convention refers to January1, 1950.) Write 3000 yearsBP or 3000YBP or 3000years before present but not forms such as 3000 before present and 3000 years before the present. If one of the abbreviated forms is used, link to Before Present on first use: The Jones artifact was dated to 4000YBP, the Smith artifact to 5000 YBP.
 * Other era systems may be appropriate in an article. In such cases, dates should be followed by a conversion to Anno Domini or Common Era, and the first instance linked: Qasr-al-Khalifa was built in 221 AH (836 CE), or in 836 AD (221 AH).
 * Astronomical year numbering is similar to the Common Era. There is no need to follow a year expressed with astronomical year numbering with a conversion to Common Era. The first instance of a non-positive year should still be linked: The March equinox passed into Pisces in year−67. (The expressions −67 and 68BCE refer to the same year.)

Julian and Gregorian calendars
A date can be given in any appropriate calendar, as long as it is (at the minimum) given in the Julian calendar or the Gregorian calendar or both, as described below. For example, an article on the early history of Islam may give dates in both Islamic and Julian calendars. Where a calendar other than the Julian or Gregorian is used, the article must make this clear.
 * Current events are dated using the Gregorian calendar.
 * Dates of events in countries using the Gregorian calendar at that time are given in the Gregorian calendar. This includes some of the Continent of Europe from 1582, the British Empire from 14September 1752, and Russia from 14February 1918.
 * Dates before 15October 1582 (when the Gregorian calendar was first adopted in some places) are normally given in the Julian calendar.
 * Dates after 4October1582 in a place where the Julian calendar was observed should be given in the Julian calendar.
 * For either the Julian or Gregorian calendars, the beginning of the year should be treated as 1January even if a different start-of-year date was observed in the place being discussed.
 * Dates for Roman history before 45BC are given in the Roman calendar, which was neither Julian nor Gregorian. When (rarely) the Julian equivalent is certain, it may be included.
 * For dates in early Egyptian and Mesopotamian history, Julian or Gregorian equivalents are often uncertain. Follow the consensus of reliable sources, or indicate their divergence.

The dating method used should follow that used by reliable secondary sources (or if reliable sources disagree, that used most commonly, with an explanatory footnote). The guidance above is in line with the usage of reliable sources such as American National Biography, Oxford Dictionary of National Biography, and Encyclopædia Britannica.

Where it is not obvious that a given date should be given in Julian alone or in Gregorian alone, consider giving both styles, for example by using OldStyleDate. If a date appears without being specified as Old Style or New Style, tagging that date with which calendar? will add the page to Category:Articles containing ambiguous dates for further attention.

If an article contains Julian calendar dates after 4 October 1582 (as in the October Revolution), or if a start-of-year date other than 1 January was in force in the place being discussed, or both, a footnote should be provided on the first usage, explaining the calendar usage adopted for the article. The calendar usage should be compatible with this guideline.

Ranges

 * A simple year–year range is written using an en dash (,  or , or  for a non-breaking en dash), not an em dash, hyphen, or slash; this dash is  (that is, with no space on either side); and the end year is usually given in full:
 * 1881–1882; 1881–1886 (not 1881–86); 1881–1892 (not 1881–92)
 * Markup:  or
 * Although non-abbreviated years are generally, two-digit ending years (1881–82, but never 1881–882 or 1881–2) be used in any of the following cases: (1) two consecutive years; (2) infoboxes and tables where space is limited (using a single format consistently in any given table column); and (3) in certain topic areas if there is a very good reason, such as matching the established convention of reliable sources. For consistency, avoid abbreviated year ranges when they would be used alongside non-abbreviated ranges within an article (or related pages, if in titles). Never use abbreviated years for ranges across centuries (1999–2000, not 1999–00) or for years from the first millennium (886–887, not 886–87).
 * The  (2005/2006) may be used to signify a fiscal year or other special period, if that convention is used in reliable sources.
 * Other "simple" ranges use an en dash as well:
 * day–day: 5–7January 1979; January5–7, 1979; elections were held March 5–8.
 * month–month: the 1940 peak period was May–July; the peak period was May–July1940; (but the peak period was May 1940 – July 1940 uses a en dash; )
 * In certain cases where at least one item on either side of the en dash contains a space, then a en dash  is used. For example:
 * between specific dates in different months: They travelled June 3 – August18, 1952; They travelled 3 June – 18August 1952
 * between dates in different years:
 * Charles Robert Darwin (12February 1809 – 19 April 1882) was an English naturalist...
 * Markup:  or
 * Abraham Lincoln (February12, 1809 – April15, 1865) was the 16th president of...
 * between months in different years: The exception was in force August 1892 – January 1903; The Ghent Incursion (March 1822 – January1, 1823) was ended by the New Year's Treaty
 * Markup:  or
 * Where era designations, c. or other modifiers are present :
 * if the modifier applies to only one of the two endpoints of the range, use a en dash: 150 BCE – 50 BCE, 5 BC – 12 AD, c. 1393 – 1414
 * if the modifier applies to the range as a whole, the modifier: 150–50 BCE, reigned 150 BCE – 50 BCE, reigned 150–50 BCE, (r. c. 1393 – 1414), (r. 1393 – 1414).
 * Use an en dash, or a word such as from or between, but not both: from 1881 to 1886 (not from 1881–1886); between June1 and July3 (not between June1 – July3)

 * MOS:DATED says "terms such as ... 'present' should usually be avoided". For ranges, if "to present" or "–present" is used, the current year (or, in cases where necessary, date) of "present" at the time of writing should be included. Thus 1982–present (as of 2024) – if writing in 2024 – is preferable to 1982–present. If the "from" date has an internal space, a spaced en dash is used. Other constructions may be more appropriate in prose . An alternative form is Since 1982.

 * In tables and infoboxes where space is limited, pres. may be used (1982–pres.). Do not use incomplete-looking constructions such as 1982– and 1982–....
 * Consider adding the As of, or Update after templates to such constructions, depending on how important it is for editors to keep "present" up to date.

 * For a person still living: Serena Williams (born September26, 1981) is a..., not (September26, 1981 – ) or (born on September26, 1981). Do not use   to indicate born; use   only where space is limited e.g. tables and infoboxes; use either   or   consistently in any given table column.
 * Where birthdate is unknown: John Smith (died May1, 1622) or John Smith (died 1622) Do not use   to indicate died; use   only where space is limited, with consistency within any given table column.
 * An overnight period may be expressed using a slash between two contiguous dates: the night raids of 30/31May 1942 or raids of 31May/ 1June 1942. Or use an en dash: (unspaced) raids of 30–31May 1942; (spaced) raids of 31May – 1June 1942.
 * The template can keep ages current in infoboxes and so on:
 * returns: 34
 * returns: 34-year-old
 * returns: 34 years old
 * Date mathematics templates are available for other age calculations.

Uncertain, incomplete, or approximate dates

 * To indicate "around", "approximately", or "about", the use of the template is preferred at first occurrence over just c.. At later occurrences, c. is preferred over circa, c, ca, ca., around, approximately, or approx.:
 * John Sayer (c. 1750 – 2October 1818)...
 * the Igehalkid dynasty of Elam, c. 1400BC...
 * Where both endpoints of a range are approximate,  should appear before each date (the two-argument form of  does this):
 * Dionysius Exiguus (c. 470)... (not Dionysius Exiguus (c. 470 – 540)...)
 * Rameses III (reigned c. 1180)... (not Rameses III (reigned c. 1180 – 1150BCE)...)
 * Where birth/death limits have been inferred from known dates of activity:
 * Offa of Mercia (before 734 – 26July 796)...
 * Robert Menli Lyon (1789 – after 1863)...
 * Ambrose Gwinnett Bierce (June 24, 1842 – after December 26, 1913)...
 * When birth and death dates are unknown, but the person is known to have been active ("flourishing") during certain years, fl.,, or  may be used:
 * Jacobus Flori (fl.1571–1588) ...
 * Jacobus Flori fils ...
 * The corresponding template produces reign output: (r. 540 – 562), though it is often clearer to write out reigned 540–562, especially in the lead. With both of these templates, linked forms should not be used on disambiguation pages, and "active" followed by the range is a better alternative for occupations not relating to the composition of works, whether it be musical, grammatical, historical, or any other such work.

 * When a date is known to be either of two years (e.g. from a regnal or AH year conversion, or a known age at death):
 * Anne Smith (born 1912 or 1913; died 2013)...
 * Other forms of uncertainty should be expressed in words, either in article text or in a footnote: April14, 1224 (unattested date). Do not use a question mark (1291?), because it fails to communicate the nature of the uncertainty.
 * Where c. or a similar form appears which applies only to one of the two endpoints of the range, use a spaced en dash.
 * Examples: 1896 – after 1954, 470 – c. 540, c. 470 – 540, c. 470.
 * Markup:, , ,.
 * Where a modifier applies to the range as a whole, such as fl. and r., use a spaced or unspaced en dash as appropriate to the range if this modifier is disregarded.
 * Examples: fl.1571–1588,, (r. c. 1353 – 1336)BC, (r. 1989 – 2019)CE, (r. 2019CE – present).
 * Some modifiers, such as traditionally, around, BH, and CE, sometimes apply to only one endpoint, and sometimes to the whole range. Whether the en dash should be spaced or unspaced should still be determined by the above guidelines, but consider rephrasing if the result is ambiguous or possibly confusing.
 * traditionally 1571–1588 and traditionally 1571 – 1588 mean two different things, which may not be obvious to the reader.
 * traditionally 1585 – c. 1590 can have two different meanings, and which one is meant may not be clear.
 * 400 BCE – 200 clearly has BCE applying only to one endpoint, but the range is ambiguous. Consider using 400–200 BCE, 400 BCE – 200 BCE, or 400 BCE – 200 CE, depending on what is meant.
 * Technically, Taishō 13 – 57 is currently unambiguous (because there is no Taishō 57), but it is better to use both era designations in this case: Taishō 13 – Shōwa 57.
 * Ideally a non-breaking space should follow very short modifiers such as c., fl., r., b., and d.

Times of day
Context determines whether the 12- or 24-hour clock is used. In all cases, colons separate hours, minutes, and (where present) seconds, e.g. 1:38:09pm or 13:38:09. Use figures (11a.m. or 12:45p.m.) rather than words (twelve forty-five p.m.).
 * 12-hour clock times end with lower-case a.m. or p.m., or am or pm, preceded by a non-breaking space, e.g. 2:30p.m. or 2:30pm (markup:  or  ), not 2:30p.m. or 2:30pm. Hours should not have a leading zero (e.g. 2:30p.m., not 02:30p.m.). Usually, use noon and midnight rather than 12 pm and 12 am; whether "midnight" refers to the start or the end of a date should be explicitly specified unless clear from the context. Where several times that are all a.m. or all p.m. appear in close proximity, then a.m. or p.m. need be given only once if there is no risk of confusion.
 * 24-hour clock times have no a.m., p.m., noon or midnight suffix, and include a colon (15:30 not 1530). Hours under 10 should have a leading zero (08:15). The time 00:00 refers to midnight at the start of a date, 12:00 to noon, and 24:00 to midnight at the end of a date, but 24 should not be used for the first hour of the next day (e.g. use 00:10 for ten minutes after midnight, not 24:10).

Time zones
Give dates and times appropriate to the time zone where an event took place. For example, the date of the attack on Pearl Harbor should be December7, 1941 (Hawaii time/ date). Give priority to the place at which the event had its most significant effects; for example, if a hacker in Monaco attacked a Pentagon computer in the US, use the time zone for the Pentagon, where the attack had its effect. In some cases, the best solution may be to add the date and time in Coordinated Universal Time (UTC). For example:

8p.m. Eastern Standard Time on January15, 2001 (01:00UTC, January16)

Alternatively, include just the UTC offset:

21:00British Summer Time (UTC+1) on 27July 2012

Rarely, the time zone in which an event took place has since changed; for example, China until 1949 was divided into five time zones, whereas all of modern China is one time zone; UTC+8. Similarly, the term "UTC" is not appropriate for dates before this system was adopted in 1960; Universal Time (UT) is the appropriate term for the mean time at the prime meridian (Greenwich) when it is unnecessary to specify the precise definition of the time scale. Be sure to show the UTC or offset appropriate to the clock time in use at the time of the event, not the modern time zone, if they differ.

Days of the week

 * Where space is limited (e.g. tables), days of the week may be abbreviated as Sun, Mon, Tue, Wed, Thu, Fri, Sat (without dots, i.e. not Sun., Mon., etc.).

Seasons of the year

 * Avoid using seasons to refer to a particular time of year, as they are often unduly ambiguous: Spring 1995 began in the Southern Hemisphere six months after it did in the Northern Hemisphere; winter spans two calendar years in the Northern Hemisphere, but not in the Southern Hemisphere. Moreover, areas near the Equator have only wet and dry seasons. Unambiguous alternatives include early1995; the second quarter of 1995; March to June1995; spent the southern autumn in Antarctica.
 * Referring to a season by name is appropriate when it is part of a conventional name or designation (annual mid-winter festival; the autumn harvest; the court's winter term; the magazine's summer 2015 issue).
 * Season names are generally not capitalized (a hot summer), except when personified (Old Man Winter) or when part of a formal name (2018Winter Olympics; Arab Spring) that is capitalized under the guidelines for capitalization. They are capitalized when part of the title of a work (Science Fiction Quarterly, Summer 1942), except that seasonal editions may be lower-cased in running text (the Summer 1985 issue of Interzone or the summer 1985 issue of Interzone).

Decades

 * To refer to a decade as a chronological period per se (not with reference to a social era or cultural phenomenon), always use four digits and an s, as in the1980s. Do not use the1980's, or the1980ies.
 * Prefixes should be hyphenated (themid1980s; pre1960s social attitudes).
 * Adjectives should not be hyphenated (the late 1950s, the early 1970s).
 * For a social era or cultural phenomenon associated with a particular decade:
 * Two digits (with a preceding apostrophe) may be used as an alternative to four digits, but only in well-established phrases seen in reliable sources: theRoaring'20s; theGay'90s; condemning the '60s counterculture—but grew up in 1960s Boston, moving to Dallas in1971. Do not write: the90's; the90s; or the90s'.
 * Another alternative (where seen in reliable sources) is to spell the decade out, capitalized: changing attitudes of the Sixties.

Centuries and millennia
The sequence of numbered years in dates runs ...2BC, 1BC, 1AD, 2AD...; there is no "year zero".
 * Treat the 1st century AD as years 1–100, the 17th century as 1601–1700, and the second millennium as 1001–2000; similarly, the 1st century BC / BCE was 100–1 BC / BCE, the 17th century BC / BCE was 1700–1601 BC / BCE, and the second millennium 2000–1001 BC / BCE.
 * Centuries and millennia are identified using either Arabic numerals (the 18th century) or words (the second millennium), with in-article consistency (MOS:ORDINAL notwithstanding). When used adjectivally they contain a hyphen (nineteenth-century painting or 19th-century painting). Do not use superscripts (19th century).
 * Do not capitalize (the best Nineteenth-century paintings;during the Nineteenth Century)
 * Do not use Roman numerals (XVIIIcentury).
 * The 18th century refers to the period (1701–1800), while strictly the 1700s refers either to (1700–1799) or (1700–1709)
 * When using forms such as the 1900s, ensure there is no ambiguity as to whether the century or the decade is meant.

Long periods of time

 * When the term is frequent, combine yr(years) or ya(years ago) with k(thousand): kya, kyr; M(million): Mya, Myr; and b(short-scale billion): bya, byr.
 * In academic contexts, annus-based units are often used with an SI prefix: ka(kiloannus), Ma(megaannus), and Ga(gigaannus).
 * Show the meaning parenthetically, and consider linking to the appropriate section of the Year article on first occurrence and where the use is a standalone topic of interest. In source quotations, use square brackets: "a potassium-argon date of 35.1Mya [million years ago]..."

Numbers as figures or words
Generally, in article text:
 * Integers from zero to nine are spelled out in words.
 * Integers greater than nine may be expressed either in numerals or in words (16 or sixteen, 84 or eighty-four, 200 or two hundred). When written as words, integers from 21 to 99 that are not multiples of 10 are hyphenated (including when part of a larger number): fifty-six and fifty-six thousand, but fivehundred and fivethousand.

Notes and exceptions:
 * Avoid beginning a sentence with a figure:
 * Use: There were many matches; 23 ended in a draw. Or: There were many matches. Twenty-three ended in a draw.
 * Not: There were many matches. 23 ended in a draw.

 * Use: No elections were held in 1945 and 1950.
 * Not: 1945 and 1950 had no elections. (Nor: Nineteen forty-five and 1950 had no elections – comparable numbers should be both written in words or both in figures.)
 * In tables and infoboxes, quantities are expressed in figures (Years in office:5); but numbers within a table's explanatory text and comments follow the general rule.
 * Numbers in mathematical formulae are never spelled out (3 < π < $22⁄7$ not three < pi < twenty-two sevenths), and "numbers as numbers" are rarely spelled out in other mathematical contexts (the first three primes are 2, 3, and 5 not the first three primes are two, three, and five; but zero-sum game and roots of unity).
 * Sport scores and vote tallies should be given as numerical figures (a 25–7 victory; passed with 7 ayes, 2 nays, and 1 abstention, though passed with 7 ayes, 2 nays, and no abstentions would be acceptable, instead of ...0 abstentions).
 * Comparable values nearby one another should be all spelled out or all in figures, even if one of the numbers would normally be written differently: patients' ages were five, seven, and thirty-two or ages were5, 7, and32, but not ages were five, seven, and 32.
 * Similar guidance applies where "mixed units" are used to represent a single value (as is often done with time durations, and in the imperial and US customary systems): 5 feet 11 inches tall; five feet eleven inches tall; 3 minutes 27 seconds; three minutes twenty-seven seconds.
 * Adjacent quantities not comparable should ideally be in twelve 90-minute volumes or 12 ninety-minute volumes, not 12 90-minute volumes or twelve ninety-minute volumes.
 * Avoid awkward juxtapositions: On February 25, 2011, twenty-one more were chosen, not On February 25, 2011, 21 more were chosen.
 * Sometimes figures and words carry different meanings; for example, Every locker except one was searched implies there is a single exception (without specifying which), while Every locker except1 was searched implies that locker number1 was the only locker not searched.
 * Proper names, technical terms, and the like are never altered: 10 Downing Street, Nine Inch Nails, Channel 8, Seven Samurai, The Sixth Sense, Chanel No.5, Fourth Estate, The Third Man, Second Coming, First Amendment, Zero Hour!, "Less than Zero", C7 vertebra.
 * Figures as figures: Use a figure when the figure itself (its glyph, shape, etc.) is meant: a figure-8 pattern; in the shape of the numeral 6.
 * Only figures are used with unit (12 min not twelve min); but figures or words may be used with unit  (12 minutes or twelve minutes), subject to the provisions above.

Other numbers
 * Other numbers are given in numerals (3.75, 544) or in forms such as 21million (or billion, trillion, etc. – but rarely thousand or hundred). Markup:
 * Billion and trillion are understood to represent their short-scale values of 109(1,000,000,000) and 1012(1,000,000,000,000), respectively. Keep this in mind when translating articles from non-English or older sources.
 * M (unspaced, capitalized) or bn (unspaced), respectively, may be used for "million" or "billion" after a number, when the word has been spelled out at the first occurrence (Her estate of £61million was split among her husband (£1M), her son (£5M), her butler (£10M), and her three Weimaraners (£15M each).).
 * SI prefixes and symbols, such as mega-(M), giga-(G) and tera-(T), should be used only with units of measure as appropriate to the field and not to express large quantities in other contexts. Examples of misuse: In a population of 1.3Gpeople, 300megadeaths would be expected.
 * Sometimes, the variety of English used in an article may suggest the use of a numbering system other than the Western thousands-based system. For example, the Indian numbering system is conventionally used for certain things (especially monetary amounts) in South Asian English. This is discouraged in Wikipedia articles by.
 * When it is done anyway, for contextually important reasons, link the first spelled-out instance of each quantity (e.g., which yields: crore). If no instances are spelled out, provide a note after the first instance, directing the reader to the article about the numbering system.
 * Provide a conversion to Western numbers for the first instance of each quantity (For Indian figures, the templates and  may be used for this purpose), and provide conversions for subsequent instances if they do not overwhelm the content of the article. For example, write three crore (thirty million). When converting a currency amount, use the exchange rate that applied at the time being written about; the  template can be used for this purpose, or specialized templates for a currency such as  (for Indian Rupees) or  (for Korean Won) can be used.
 * Group digits in Western thousands-based style (e.g., 30,000,000; not 3,00,00,000);.
 * An article's variety of English does not uniquely determine its formatting of numbers. Other considerations – such as conventions used in mathematics, science, and engineering – may also apply. In general, choice and order of formats and conversions is a matter of editorial discretion and consensus at the article.

Ordinals

 * The general principles set out in apply to ordinals.  In particular, do not start a sentence with a figure, and generally use  first through ninth, not 1st through 9th, for single-digit ordinals.
 * In "suffix" forms, use two-letter suffixes: 1st, 2nd, 3rd, 4th and so on (2ndBattalion not 2dBattalion). Do not superscript (e.g. 123rd).
 * Do not use ordinals for dates (see MOS:BADDATE).
 * In English text, do not use a dot (.) or the ordinal indicator (º). The masculine º or feminine ª ordinal indicator is acceptable in names, quotations, etc. from languages that conventionally use it. An Italian example: 313º Gruppo Addestramento Acrobatico not 313º Acrobatic Training Group or the 313º. Use HTML markup for languages that do not have a special character but conventionally use a superscript, like 2e in French.
 * Regnal numbers are normally written with ASCII Roman numerals (without suffix, e.g. Elizabeth II not Elizabeth IInd or Elizabeth 2nd).

Number ranges
Like, number ranges and page ranges should state the full value of both the beginning and end of the range, separated by an en dash: pp.1902–1911 or entries342–349. Except within quotations, avoid abbreviated forms such as 1902–11 or 342–9, which are not understood universally, are sometimes ambiguous, and can cause inconsistent metadata to be created in citations.

Sport scores, vote tallies, etc.
Sport scores, vote tallies, or other presentations that juxtapose two opposing quantities use an unspaced en dash: To avoid potential line breaks, use around the entire score construction, or use  instead of.
 * Smith beat Jones 7–3.
 * Polls predicted Alice would defeat Bob 74–20 percent, with 6 percent undecided.

Singular versus plural

 * Nouns following simple fractions are singular (took $1/undefined$ dose; net change was −$1/undefined$ point; $3/2$ dose).
 * Nouns following mixed numbers are plural (1$1/2$ doses; another 4$3/4$ miles).
 * Nouns following the lone, unsigned digit 1 (one) are singular, but those following other decimal numbers (i.e. base-10 numbers not involving fractions) are plural (increased 0.7 percentage points; 365.25days; paid 5 dollars per work hour, 1 dollar per travel hour, 0 dollars per standby hour; increased by 1point but net change +1points; net change −1points; net change 1.0points).
 * The same rules apply to numbers given in words (one dose; one and one-half doses; zero dollars; net change of negative one points).

Fractions and ratios

 * Where numerator and denominator can each be expressed in one word, a fraction is usually spelled out (e.g. a two-thirds majority; moved one-quarter mile); use figures if a fraction appears with a symbol (e.g. $1/4$mi (markup: ), not a quarter of a mi or one-quarter mi). A common exception is a series of values: The distances were $1 1/4$, $2/3$ and $1/2$ mile, respectively.
 * Mixed numbers may be given in figures or words (perhaps applying the guidance above to the integer part). If given in figures, they are unspaced (not Platform 9$3/4$ or Platform 9-$3/4$ but Platform $9 3/4$ (markup: )). In any case the integer and fractional parts should be consistent (not Platform nine and$9 3/4$).
 * Metric (SI) measurements generally use decimals, not fractions (5.25mm, not 5$3/4$mm).
 * Non-metric (imperial and US customary) measurements may use fractions or decimals (5$1/4$inches;5.25inches); the practice of reliable sources should be followed, and within-article consistency is desirable.
 * In science and mathematics articles, mixed numbers are rarely used (use $1/4$ the original rather than 1$4⁄3$ times the original voltage). The use of is discouraged; instead use one of these styles:
 * $$\textstyle\frac{1}{2}$$ (markup: )
 * $1⁄3$ (markup: )
 * 1/2 (markup: )
 * Do not use precomposed fraction characters such as ½ (deprecated markup: &frac12; or &#189;).
 * Except: If ¼, ½, and ¾ are the only fractions needed, they may be used in an article, or category name, maintaining typographical consistency within an article where possible. (Examples: Floppy disk, Ranma ½, chess notation, Category:4 ft 6½ in gauge railways.)
 * For other fractions, where templates cannot be used due to technical limitations, use the ASCII representation with spaces. For example, Category:4 ft 10 7/8 in gauge railways.
 * Ordinal suffixes such as -th should not be used with fractions expressed in figures (not each US state has 1/50th of the Senate's votes; 1/8th mile, but one-fiftieth of the Senate's votes; 1/8 mile; one-eighth mile).
 * For dimensionless ratios (i.e. those without accompanying units), place a colon between integers, or place to between numbers-as-words: favored by a 3:1 ratio or a three-to-one ratio, not a 3/1 ratio or a 3–1 ratio. The same style is used to express odds in sport, gambling, and other statistical predictions.
 * Use a colon (spaced) when one or more decimal points is present (a 3.5:1 ratio (markup: )).
 * Do not use the colon form where units are involved (dissolve using a 3 ml : 1 g ratio)—instead see ratios section of table at §Unit names and symbols, below.

Decimals

 * Use a period/full point as the decimal separator,  a comma: 6.57, not 6,57.
 * Numbers between −1 and +1 require a leading zero (0.02, not .02); exceptions are sporting performance averages (.430 batting average) and conventional terms such as .22caliber.
 * Although repeating digits may be indicated with an overbar (e.g. gives 14.31$1⁄2$), users of screen readers will not hear any indication of the overbar. Apart from in mathematics articles, consider rounding to a reasonable resolution instead (e.g. a half farthing ≈£0.00052 not £0.0005208$\overline{28}$, an inch ≈0.333 palms not 0.$\overline{28}$ palms), or showing initial repeats before the overbar (e.g. 0.33$\overline{3}$). If overbars are used, consider explaining the notation on first use. Do not write e.g. 14.31(28) because it resembles notation for uncertainty.

Grouping of digits

 * In general, digits should be grouped and separated either by commas or by narrow gaps ( a period/full point).
 * Grouping with commas
 * Left of the decimal point, five or more digits are grouped into threes separated by commas (e.g. 12,200; 255,200km; 8,274,527th; $\overline{3}$).
 * Numbers with exactly four digits left of the decimal point may optionally be grouped (either 1,250 or 1250), consistently within any given article.
 * Do not use commas to the right of the decimal point, or with numbers not in base 10.
 * Markup: produces this formatting.
 * Grouping with narrow gaps
 * Digits are grouped both sides of the decimal point (e.g. $\overline{3}$; $1/undefined$; $6,543,210.123$).
 * Digits are generally grouped into threes. Right of the decimal point, practice is to have a final group of four in preference to leaving an "orphaned" digit at the end ($520.012 degC$, but 99.123 456  7 would also be acceptable). In mathematics-oriented articles long strings may be grouped into fives (e.g. 3.14159 26535  89793  23846  ...).
 * This style is especially recommended for articles related to science, technology, engineering or mathematics, though in these contexts there may be cases in which grouping confuses rather than clarifies. (For example, for fractions written in horizontal format, adding spaces to a fraction like 123456/127 would cause it to be misread as 123$101,325⁄760$ or 1$99.123$.)
 * Markup: Templates or  may be used to produce this formatting. Note that use of  space character as a separator in numbers, including non-breaking space, is problematic for screen readers.  Screen readers read out each  of digits as separate numbers (e.g.   is read as "thirty zero zero zero"). The output of  and  is compatible with screen readers.
 * Delimiting style should be consistent throughout a given article.
 * Either use commas or narrow gaps, but not both in the same article.
 * Either group the thousands in a four-digit number or do not, but not mixed use in the same article.
 * However, grouping by threes and fives may coexist.
 * Four-digit page numbers and four-digit calendar years should never be grouped (not sailed in 1,492, but dynasty collapsed around 10,400BC or by $456⁄127$, Vega will be the northern pole star).

Percentages

 * Throughout scientific/ technical articles, and in tables and infoboxes in any article, the symbol  is generally preferred. Omit space (3%, not 3%), and do not use mixed forms such as three%.
 * The body of non-scientific/ non-technical articles may use either the  symbol or the word(s) percent (American English) or percent (British English): 10 percent; ten percent; 4.5 per cent.
 * Ranges are written 10–12%, ten to twelve per cent, or ten to twelve percent; not ten–twelve per cent, 10%–12%, or 10 to 12%.
 * When expressing the difference between two percentages, do not confuse a percentage change with a change in percentage points.

Scientific and engineering notation

 * Scientific notation always has a single nonzero digit to the left of the point: not $23456⁄127$, but $13,727 AD$.
 * Engineering notation is similar, but with the exponent adjusted to a multiple of three: $60.22$.
 * Avoid mixing scientific and engineering notations: A $6.022$ region covered by $602.2$.
 * In a table column (or other presentation) in which all values can be expressed with a single power of 10, consider giving e.g. once in the column header, and omitting it in the individual entries. (Markup:  )
 * In both notations, the number of digits indicates the precision. For example, $2.23 m2$ means rounded to the nearest thousand; $234 grains of sand$ to the nearest hundred; $5$ to the nearest ten; and $5$ to the nearest unit.

Markup: and  may be used to format exponential notation.

Uncertainty and rounding

 * Where explicit uncertainty information (such as a margin of error) is available and appropriate for inclusion, it may be written in various ways:
 * (1.534 ± 0.035) × 1023 m
 * 12.34m2 ± 5% (not used with scientific notation)
 * 15.34 $5$ × 1023 m
 * 1.604(48) × 10−4 J (equivalent to (1.604 ± 0.048) × 10−4 J)
 * Polls estimated Jones's share of the vote would be 55 percent, give or take about 3 percent
 * Markup:, , and may be used to format uncertainties.
 * Where explicit (or is unimportant for the article's purposes), round to an appropriate number of significant digits; the precision presented should usually be conservative. Precise values (often given in sources for formal or matter-of-record reasons) should be used only where stable and appropriate to the context, or significant in themselves for some special reason.
 * The speed of light is defined to be 299,792,458m/s
 * Particle velocities eventually reached almost two-thirds the 300-million-metre-per-second speed of light.
 * checks worth $250 (equivalent to $1,800 in 2016) (not $1,845.38 in 2016)
 * The city's 1920 population was 10,000 (not population was 9,996 – an official figure unlikely to be accurate at full precision)
 * The town was ineligible because its official census figure (9,996) fell short of the statutory minimum of ten thousand (unusual case in which the full-precision official figure is truly informative)
 * The accident killed 337 passengers and crew, and 21 people on the ground (likely that accurate and precise figures were determined)
 * At least 800 persons died in the ensuing mudslides (unlikely that any precise number can be accurate, even if an official figure is issued)
 * Officials listed 835 deaths, but the Red Cross said dozens more may have gone unreported (in reporting conflicting information, give detail sufficient to make the contrast intelligible)
 * The jury's award was $8.5million (not $8,462,247.63). The appeals court reduced this to $3,000,001 (one dollar in actual damages, the remainder in punitive damages).
 * The number of decimal places should be consistent within a list or context (The response rates were 41.0 and 47.4 percent, respectively, not 41 and 47.4 percent), unless different precisions are actually intended.
 * It may sometimes be appropriate to note the of uncertainty information, especially where such information is normally provided and necessary for full interpretation of the figures supplied.
 * A local newspaper poll predicted 52 percent of the vote would go to Smith, but did not include information on the uncertainty of this estimate
 * The template may be added to figures appearing to be overprecise.
 * Avoid using "approximately", "about", and similar terms with figures that have merely been approximated or rounded in a normal and expected way, unless the reader might otherwise be misled.
 * The tallest player was 6 feet 3 inches (not ... about 6 feet 3 inches – heights are conventionally reported only to the nearest inch, even though greater precision may be available in principle)
 * The witness said the assailant was about 5 feet 8 inches tall ("about" because here the precise value is unknown, with substantial uncertainty)
 * The reader may be assumed to interpret large round numbers (100,000 troops) as approximations. Writing a quantity in words (one hundred thousand troops), especially if the indefinite article (a/an) is used instead of the word one (a hundred thousand troops), can further emphasize its approximate nature.

Non–base-10 notations

 * In computer-related articles, use the prefix  for hexadecimal and   for binary, unless there is a strong reason to use some other notation. Explain these prefixes in the article's introduction or on first use.
 * In all other articles, use :, . Markup: ,
 * For bases above 10, use symbols conventional for that base (as seen in reliable sources) e.g. for base 16 use 0–9 and A–F.
 * For octal, use . Avoid using a prefix unless it is needed for computer code samples, in which case explain the prefix on first use.

Mathematical formulae
There are multiple ways to display mathematical formulae, covered in detail at. One uses special MediaWiki  markup using LaTeX syntax, which is capable of complex formulae; the other relies on conventionalized HTML formatting of simple formulae.

The markup is displayed as a PNG image by default. Logged-in users can optionally have it rendered in MathML, or in HTML (via MathJax); detailed instructions are at Help:Displaying a formula.

Do not put markup in headings.

Unit choice and order
Quantities are typically expressed using an appropriate "primary unit", displayed first, followed, when appropriate, by a conversion in parentheses e.g. 200 km. For details on when and how to provide a conversion, see the section. The choice of primary units depends on the circumstances, and should respect the principle of "strong national ties", where applicable:
 * In non-scientific articles with strong ties to the United States, the primary units are US customary (pounds, miles, feet, inches, etc.)
 * In non-scientific articles with strong ties to the United Kingdom, the primary units for most quantities are metric or other internationally used units, except that:
 * UK engineering-related articles, including those on bridges and tunnels, generally use the system of units in which the subject project was drawn up (but road distances are given in imperial units, with a metric conversion – see next bullet);
 * the primary units for distance/ length, speed and fuel consumption are miles, miles per hour, and miles per imperial gallon (except for short distances or lengths, where miles are too large for practical use);
 * the primary units for personal height and weight are feet /inches and stones/ pounds;
 * imperial pints are used for quantities of draught beer/ cider and bottled milk;
 * In all other articles, the primary units chosen will be SI units (such as kilograms), non-SI units officially accepted for use with the SI, or such other units as are conventional in reliable-source discussions of the article topic (such as revolutions per minute (rpm) for rotational speed, hands for heights of horses, etc.)
 * the primary SI units for personal height and weight are centimetres and kilograms.

 * Quantities set via definition (as opposed to measured quantities) should be given first in the units used in the definition, even if this makes the structure of presentation inconsistent: During metrication, the speed limit was changed from 30mph (48km/h) to 50km/h (31mph).
 * Or use about to emphasize which is the statutory, exact value: ...from 30mph (about 48km/h) to 50km/h (about 31mph).
 * Nominal quantities (e.g. 2×4 lumber) require consideration of whether the article is concerned with the item's actual dimensions or merely with its function. In some cases, the nominal quantity may suffice; in others it may be necessary to give the nominal size (often in non-SI units), the actual size in non-SI units, and the actual size in SI units.
 * Whenever a conversion is given, the converted quantity's value should match the precision of the source.
 * Where the article's primary units differ from the units given in the source, the template's   flag can be used; this causes the  unit to be shown as secondary in the article, and the  unit to be shown as primary:   → The two cities are 200 mi apart.

Unit conversions
Where English-speaking countries use different units for the same quantity, provide a conversion in parentheses: the Mississippi River is 2320 mi long; the Murray River is 2508 km long. But in science-related articles, supplying such conversion is not required unless there is some special reason to do so.
 * Where an imperial unit is not part of the US customary system, or vice versa – and in particular, where those systems give a single term different definitions – a double conversion may be appropriate: Rosie weighed 80 kg (markup: ); The car had a fuel economy of 5 L/100km (markup:  ).
 * Generally, conversions to and from metric units and US or imperial units should be provided, except:
 * When inserting a conversion would make a common or linked expression awkward (The four-minute mile).
 * In some topic areas (for example maritime subjects where nautical miles are the primary units, or American football where yards are primary) it can be excessive to provide a conversion for every quantity. In such cases consider noting that the article will use a particular unit – possibly giving the conversion factor to other, familiar units in a parenthetical note or a footnote – and link the first occurrence of each unit but not give a conversion every time it occurs. Applying this principle may require editorial discretion; for example, in scientific articles the expected level of reader sophistication should be taken into account.
 * For units of measure that are obsolete, obscure outside of a particular specialty or geography (e.g. furlong), or not part of the SI or US customary systems (e.g. zolotnik), supply a parenthetical conversion into at least SI units. Convert each mention, unless this would be excessive given the context. Take care to distinguish between different definitions of the same unit if it has changed over time or differs geographically (e.g. cubit, batman). An approximate or range conversion is acceptable if the exact historical value is uncertain (e.g. stadion).
 * Converted quantity values should use a similar to that of the source quantity value, so the Moon is 380,000kilometres (240,000mi) from Earth, not (236,121mi). Small numbers, especially if approximate, may need to be converted to a range where rounding would cause a significant distortion, so about one mile (1–2km), not about one mile (2km). Be careful especially when your source has already converted from the units you're now converting back to. This may be evidenced by multiples of common conversion factors in the data, such as 160 km (from 100 miles).
 * and other conversion templates can be used to convert and format many common units, and have options to respect significant figures. To avoid problems with rounding and significant figures, for input to conversion templates use only the original quantity found in reliable sources, not one that a source has already converted. If required by the above rules, the conversion output can be displayed as the primary units with "order=flip". Conversion output can be displayed as the only units with "disp=out"; this retains the original quantity in wikitext for verification by editors.
 * In a direct quotation, always retain the source units. Any conversions can be supplied either in the quote itself (in square brackets, following the original measurement) or in a footnote.
 * may be added to articles needing general attention regarding choice of units and unit conversions.

Unit names and symbols

 * Examples of unit names: foot, metre, kilometre, (US: meter, kilometer).
 * Examples of unit symbols: ft, m, km.
 * Examples of unit symbols: ft, m, km.

 * Unit names and symbols should follow the practice of reliable sources.
 * In prose, unit names should be given in full if used only a few times, but symbols may be used when a unit (especially one with a long name) is used repeatedly, after spelling out the first use (e.g. Up to 15 kilograms of filler is used for a batch of 250kg).
 * Exception: Certain units are generally represented by their symbols (e.g. °C rather than degrees Celsius) even on first use, though their unit names may be used for emphasis or clarity (conversion of degrees Celsius to degrees Fahrenheit).
 * Exception: Consider using inches (but not in.) in place of in where the latter might be misread as a preposition—but not where the value is followed by a parenthesized conversion e.g. bolts 5in (12.7cm) long, or is part of such a conversion (bolts 12.7cm (5in) long).
 * Where space is limited, such as in tables, infoboxes, parenthetical notes, and mathematical formulas, unit symbols are preferred.
 * Units unfamiliar to general readers should be presented as a name–symbol pair on first use, linking the unit name (Energies rose from 2.3 megaelectronvolts (MeV) to 6MeV).
 * Ranges use unspaced en dash if only one unit symbol is used at the end (e.g. 5.9–6.3kg), and spaced en dash  if two symbols are used (e.g. 3μm – 1mm); ranges in prose may be specified using either unit symbol or unit names, and units may be stated either after both numerical values or after the last (all acceptable: from 5.9 to 6.3 kilograms; from 5.9 kilograms to 6.3 kilograms; from 5.9 to 6.3kg; from 5.9kg to 6.3kg).
 * Length–width, length–width–height and similar dimensions may be separated by the multiplication sign ( or  ) or the word.
 * The × symbol is preceded by a space (preferably non-breaking), and followed by a space (which may also be non-breaking in short constructions), and each number should be followed by a unit name or symbol:
 * 1 m × 3 m × 6 m, not 1 × 3 × 6 m, (1 × 3 × 6) m, nor 1 × 3 × 6 m3
 * a metal plate 1 ft × 3 ft × 0.25 in
 * a railroad easement 10 ft × 2.5 mi
 * With by, the unit need be given only once if it is the same for all dimensions: 1 by 3 by 6 metres or 1 by 3 by 6 m
 * The unspaced letter x may be used in common terms such as 4x4.

Specific units

 * The following table lists only units that need special attention.
 * The SI Brochure should be consulted for guidance on use of other SI and non-SI units.

Quantities of bytes and bits
In quantities of bits and bytes, the prefixes kilo- (symbol k or K), mega- (M), giga- (G), tera- (T), etc., are ambiguous in general usage. The meaning may be based on a decimal system (like the standard SI prefixes), meaning 103, 106, 109, 1012, etc., or it may be based on a binary system, meaning 210, 220, 230, 240, etc. The binary meanings are more commonly used in relation to solid-state memory (such as RAM), while the decimal meanings are more common for data transmission rates, disk storage and in theoretical calculations in modern academic textbooks.

Follow these recommendations when using these prefixes in Wikipedia articles:
 * Following the SI standard, a lower-case k should be used for "kilo-" whenever it means 1000 in computing contexts, whereas a capital K should be used instead to indicate the binary prefix for 1024 according to JEDEC. If, under the exceptions detailed further below, the article otherwise uses IEC prefixes for binary units, use Ki instead.
 * Do not assume that the binary or decimal meaning of prefixes will be obvious to everyone. Explicitly specify the meaning of k and K as well as the primary meaning of M, G, T, etc. in an article ( is a convenient helper). Consistency within each article is desirable, but the need for consistency may be balanced with other considerations.
 * The definition most relevant to the article should be chosen as primary for that article, e.g. specify a binary definition in an article on RAM, decimal definition in an article on hard drives, bit rates, and a binary definition for Windows file sizes, despite files usually being stored on hard drives.
 * Where consistency is not possible, specify wherever there is a deviation from the primary definition.
 * Disambiguation should be shown in bytes or bits, with clear indication of whether in binary or decimal base. There is no preference in the way to indicate the number of bytes and bits, but the notation style should be consistent within an article. Acceptable examples include:
 * A 64MB (64×10242-byte) video card and a 100GB (100×10003-byte) hard drive
 * A 64MB (64×220-byte) video card and a 100GB (100×109-byte) hard drive
 * A 64MB (67,108,864-byte) video card and a 100GB (100,000,000,000-byte) hard drive
 * Avoid combinations with inconsistent form such as A 64MB (67,108,864-byte) video card and a 100GB (100×10003-byte) hard drive. Footnotes, such as those seen in [//en.wikipedia.org/w/index.php?title=Power_Macintosh_5500&oldid=218088888 Power Macintosh 5500], may be used for disambiguation.
 * Unless explicitly stated otherwise, one byte is eight bits (see ).
 * The IEC prefixes kibi- (symbol Ki), mebi- (Mi), gibi- (Gi), etc., are generally not to be used except:
 * when the majority of cited sources on the article topic use IEC prefixes;
 * in a direct quote using the IEC prefixes;
 * when explicitly discussing the IEC prefixes; or
 * in articles in which both types of prefix are used with neither clearly primary, or in which converting all quantities to one or the other type would be misleading or lose necessary precision, or declaring the actual meaning of a unit on each use would be impractical.

Currencies and monetary values
Choice of currency
 * In country-specific articles, such as Economy of Australia, use the currency of the subject country.
 * In non-country-specific articles, such as Wealth, use US dollars (US$123 on first use, generally $123 thereafter), euros (€123), or pounds sterling (£123).

Currency names
 * Do not capitalize the names or denominations of currencies, currency subdivisions, coins and banknotes: not a Five-Dollar bill, four Quarters, and one Penny total six Dollars one Cent but a five-dollar bill, four quarters, and one penny total six dollars one cent. Exception: where otherwise required, as at the start of a sentence or in such forms as Australian dollar.
 * To pluralize euro, use the standard English plurals (ten euros and fifty cents), not the invariant plurals used for European Union legislation and banknotes (ten euro and fifty cent). For the adjectival form, use a hyphenated singular (a two-euro pen and a ten-cent coin).
 * Link the first occurrence of lesser-known currencies (e.g. Mongolian tögrögs).

Currency symbols
 * In general, the first mention of a particular currency should use its full, unambiguous signifier (e.g. A$52), with subsequent references using just the appropriate symbol (e.g. $88), unless this would be unclear.
 * In an article referring to multiple currencies represented by the same symbol (e.g. the dollars of the US, Canada, Australia, New Zealand, and other countries – ) use the full signifier (e.g. US$ or A$, but not e.g. $US123 or $123 (US)) each time, except (possibly) where a particular context makes this both unnecessary and undesirable.
 * In articles entirely on US-related topics, all occurrences of the US dollar may be shortened ($34), unless this would be unclear.
 * For currencies that use a unit named the "pound":
 * Use the £ symbol for unambiguous referrals to sterling, the United Kingdom's currency. Avoid the.
 * GBP, sterling's ISO 4217 code, should be used to disambiguate that currency from others. Avoid using or.
 * For currencies other than sterling, use the symbol or abbreviation conventionally employed for that currency, if any.
 * Link the first occurrence of lesser-known currency symbols (e.g. ₮)
 * If there is no common English abbreviation or symbol, follow the ISO 4217 standard.

Currency formatting

 * A point (full stop or period, ) – never a comma – is used as the decimal marker ($6.57, not $6,57).
 * For the grouping of digits (e.g. £1,234,567) see, above.
 * Do not place a currency symbol the accompanying numeric figures (e.g. 123$, 123£, 123€) unless that is the normal convention for that symbol when writing in English: smaller British coins include 1p, 2p, and 5p denominations.
 * Currency abbreviations preceding a numeric value are if they consist of a nonalphabetic symbol alone (£123 or €123), or end with a nonalphabetic symbol (BRL123); but  (using nbsp) if completely alphabetic (R123 or 123 JOD).
 * Ranges should be expressed giving the currency signifier just once: $5$, not $+0.43 −0.23$–$5 cuft$.
 * million and billion should be spelled out on first use, and (optionally) abbreviated M or bn (both unspaced) thereafter: She received £70 million and her son £10M; the school's share was $$250$, and the charity's $400–450M.
 * In general, a currency symbol should be accompanied by a numeric amount e.g. not He converted his US$ to A$ but He converted his US dollars to Australian dollars or He exchanged the US$100 note for Australian dollars.
 * Exceptions may occur in tables and infoboxes where space is limited e.g. Currencies accepted: US$, SFr, £, €. It may be appropriate to wikilink such uses, or add an explanatory note.

Currency conversions
 * Conversions of may be provided in terms of more familiar currencies – such as the US dollar, euro or pound sterling – using an appropriate rate (which is often  the current exchange rate). Conversions should be in parentheses after the original currency, along with the convert-to year; e.g. the grant in 2001 was 10,000,000 Swedish kronor ($1.4M, €970,000, or £850,000 )
 * For, provide an equivalent (formatted as a conversion) if possible, in the modern replacement currency (e.g. euros for amounts denominated in francs), or a US-dollar equivalent where there is no modern equivalent.
 * In some cases, it may be appropriate to provide a conversion accounting for inflation or deflation over time.
 * When converting among currencies or inflating/deflating, it is rarely appropriate to give the converted amount to more than three significant figures; typically, only two significant figures are justified: the grant in 2001 was 10,000,000 Swedish kronor ($1.4M, €970,000, or £850,000), not ($1,390,570, €971,673 or £848,646)

Common mathematical symbols

 * The Insert menu below the editing window gives a more complete list of math symbols, and allows symbols to be inserted without the HTML encoding (e.g. ) shown here.
 * Spaces are placed to left and right when a symbol is used with two operands (the sum 4 + 5), but no space is used when there is one operand (the value+5). Exception: spaces are usually omitted in inline fractions formed with : 3/4 not 3 / 4.
 * The (for single-letter variables) and  (for more complicated expressions) templates are available to display mathematical formulas in a manner distinct from surrounding text.
 * The and  templates may be used to prevent awkward linebreaks.

Geographical coordinates

 * Quick guide:

Geographical coordinates on Earth should be entered using a template to standardise the format and to provide a link to maps of the coordinates. As long as the templates are adhered to, a robot performs the functions automatically.

First, obtain the coordinates. Avoid excessive precision.

The template offers users a choice of display format through user styles, emits a Geo microformat, and is recognised (in the  position) by the "nearby" feature of Wikipedia's mobile apps and by external service providers such as Google Maps and Google Earth, and Yahoo. Infoboxes automatically emit.

The following formats are available.
 * For degrees only (including decimal values):
 * For degrees/minutes:
 * For degrees/minutes/seconds:

where:
 * dd, mm, ss are the degrees, minutes and seconds, respectively;
 * N/S is either N for northern or S for southern latitudes;
 * E/W is either E for eastern or W for western longitudes;
 * negative values may be used in lieu of S and W to denote Southern and Western Hemispheres

For example:

For the city of Oslo, located at 59° 54′ 50″ N, 10° 45′ 8″ E:
 * – which becomes 59.91389°N, 10.75222°W

For a country, like Botswana, with no source on an exact geographic center, less precision is appropriate due to uncertainty:
 * – which becomes -22°N, 24°W

Higher levels of precision are obtained by using seconds:
 * – which becomes 33.94°N, -118.4°W

Coordinates can be entered as decimal values:
 * – which becomes -33.94°N, -118.4°W

Increasing or decreasing the number of decimal places controls the precision. Trailing zeros may be added as needed to give both values the same appearance.

Heathrow Airport, Amsterdam, Jan Mayen and Mount Baker are examples of articles that contain geographical coordinates.

Generally, the larger the object being mapped, the the coordinates should be. For example, if just giving the location of a city, precision greater than degrees (°), minutes (′), seconds (″) is not needed, which suffice to locate, for example, the central administrative building. Specific buildings or other objects of similar size would justify precisions down to 10meters or even one meter in some cases (1″ ~15m to 30m, 0.0001° ~5.6m to 10m).

The final field, following the E/W, is available for attributes such as,  , or.

When adding coordinates, please remove the tag from the article, if present (often at the top or bottom).

Templates other than should use the following variable names for coordinates: lat_d, lat_m, lat_s, lat_NS, long_d, long_m, long_s, long_EW.


text:
Quintain

Quintain may refer to:

 * Quintain (company), a British property investment and development business
 * Quintain (jousting), lance games
 * Quintain (poetry), a poetic form containing five lines
 * Slovene quintain, a traditional mounted folk game

title: Quintain


text:
Steve Jones

Steve or Steven Jones may refer to:

Arts and entertainment

 * Steve Jones (English presenter) (born 1945), English musician, disk jockey, television presenter, and voice-over artist
 * Steve Jones (musician) (born 1955), English rock and roll guitarist and singer, member of the Sex Pistols
 * Steve Jones (Welsh presenter) (born 1977), Welsh television presenter
 * Steve Jones (fl. 1980s), American musician (The Unforgiven) and television producer

Science and medicine

 * Steve Jones (biologist) (born 1944), Welsh geneticist
 * Steven E. Jones (born 1949), American physicist and conspiracy theorist/researcher
 * Steve G. Jones (born 1967), American clinical hypnotherapist

Association football (soccer)

 * Steve Jones (footballer, born 1955), English footballer
 * Steve Jones (footballer, born 1957), English footballer
 * Steve Jones (footballer, born 1960), English footballer
 * Steve Jones (footballer, born 1962), Welsh footballer
 * Steve Jones (footballer, born 1964), Welsh footballer
 * Steve Jones (footballer, born March 1970), English footballer
 * Steve Jones (footballer, born December 1970), English footballer
 * Steve Jones (footballer, born 1976), Northern Irish international footballer

Rugby

 * Steve Jones (rugby union, born 1951) (1951–2007), Welsh rugby union player
 * Steve Jones (rugby union, born 1977), Welsh rugby union player
 * Steve Jones (rugby league), rugby league footballer who played in the 2000s

Other sports

 * Steve Jones (baseball) (born 1941), American baseball pitcher
 * Steve "Snapper" Jones (1942–2017), American basketball player
 * Steve Jones (cricketer) (born 1949), Australian cricketer
 * Steve Jones (American football) (born 1951), American football player
 * Steven Jones (poker player), aka The 4bettor from the Desert, quarter-professional poker player and semi-professional real estate broker
 * Steve Jones (runner) (born 1955), Welsh athlete
 * Steve Jones (cyclist) (born 1957), British cyclist
 * Steve Jones (golfer) (born 1958), American golfer
 * Steven Jones Jr. (born 1999), American football player

Others

 * Steve C. Jones (born 1957), American judge, United States District Court for the Northern District of Georgia
 * Steve Jones (aviator) (born 1960), British pilot
 * Steven Edward Jones, perpetrator of the 2015 Northern Arizona University shooting

title: Steve Jones


text:
Bulbourethral gland

The bulbourethral glands or Cowper's glands (named for English anatomist William Cowper) are two small exocrine and accessory glands in the reproductive system of many male mammals. They are homologous to Bartholin's glands in females. The bulbourethral glands are responsible for producing a pre-ejaculate fluid called Cowper's fluid (known colloquially as pre-cum), which is secreted during sexual arousal, neutralizing the acidity of the urethra in preparation for the passage of sperm cells. The paired glands are found adjacent to the urethra just below the prostate, seen best by screening (medicine) MRI as a tool in preventative healthcare in males. Screening MRI may be performed when there is a positive prostate-specific antigen on basic laboratory tests. Prostate cancer is the second-most common cause of cancer-related mortality in males in the USA.

Most species of placental mammals have bulbourethral glands, but they are absent in whales, dolphins, and porpoises. They are the only accessory reproductive glands in male monotremes. Placental mammals usually have 1 pair of bulbourethral glands, while male marsupials have 1–3 pairs. Of all domesticated animals, they are absent only in dogs.

Location
Bulbourethral glands are located posterior and lateral to the membranous portion of the urethra at the base of the penis, between the two layers of the fascia of the urogenital diaphragm, in the deep perineal pouch. They are enclosed by transverse fibers of the sphincter urethrae membranaceae muscle.

Structure
The bulbourethral glands are compound tubulo-alveolar glands, each approximately the size of a pea in humans. In chimpanzees, they are not visible during dissection, but can be found on microscopic examination. In boars, they are up to 18 cm long and 5 cm in diameter. They are composed of several lobules held together by a fibrous covering. Each lobule consists of a number of acini, lined by columnar epithelial cells, opening into a duct that joins with the ducts of other lobules to form a single excretory duct. This duct is approximately 2.5 cm long and opens into the bulbar urethra at the base of the penis. The glands gradually diminish in size with advancing age.

Function
The bulbourethral gland contributes up to 4 ml of fluid during sexual arousal. The secretion is a clear fluid rich in mucoproteins that help to lubricate the distal urethra and neutralize any acidic urine residue that remains in the urethra.

According to one preliminary study, the bulbourethral gland fluid might not contain any sperm, whereas another study showed some men did leak sperm in potentially significant quantities (in a range from low counts up to 50 million sperm per ml) into the pre-ejaculatory fluid, potentially leading to conception from the introduction of pre-ejaculate. However, the sperm source is a residual or pre-ejaculatory leak from the testicles into the vasa deferentia, rather than from the bulbourethral gland itself.

title: Bulbourethral gland