Misplaced Pages

talk:Manual of Style/Dates and numbers: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages talk:Manual of Style Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 00:09, 11 September 2008 editGreg L (talk | contribs)Extended confirmed users, Pending changes reviewers31,897 edits Comments on poll itself: Please let us make progress here and stop vandalizing this page← Previous edit Latest revision as of 15:02, 9 January 2025 edit undoPeter coxhead (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, Pending changes reviewers, Rollbackers, Template editors204,328 edits Acceptable Date Format: Month Year: agree with others, perfectly acceptable 
Line 1: Line 1:
{{talkheader|sc1=WT:DATE|sc2=WT:MOSDATE}}
{{Calm}}
{{WikiProject banner shell|
{{WikiProject Manual of Style}}
}}
{{User:MiszaBot/config {{User:MiszaBot/config
|archiveheader = {{aan}}
|maxarchivesize = 250K
|maxarchivesize = 800K
|counter = 108
|algo = old(5d) |counter = 163
|minthreadsleft = 2
|archive = Misplaced Pages talk:Manual of Style (dates and numbers)/Archive %(counter)d
|minthreadstoarchive = 1
|algo = old(60d)
|archive = Misplaced Pages talk:Manual of Style/Dates and numbers/Archive %(counter)d
}} }}
{{User:HBC Archive Indexerbot/OptIn
{{Misplaced Pages talk:Manual of Style (dates and numbers)/Archive box}}
<!--{{Misplaced Pages talk:Manual of Style (dates and numbers)/Archive box B}}--> |target=Misplaced Pages talk:Manual of Style/Dates and numbers/Archive index
{{Misplaced Pages talk:Manual of Style (dates and numbers)/Archive box D}} |mask1=Misplaced Pages talk:Manual of Style/Dates and numbers/Archive <#>
|mask2=Misplaced Pages talk:Manual of Style/Dates and numbers/Archive zero
|mask3=Misplaced Pages talk:Manual of Style/Dates and numbers/Archive B<#>
|mask4=Misplaced Pages talk:Manual of Style/Dates and numbers/Archive D<#>
|leading_zeros=0
|indexhere=yes }}
{{Misplaced Pages talk:Manual of Style/Dates and numbers/Archive box}}
{{tmbox|image=] |text=It has been '''{{age in days|2024|6|18}} days''' since the outbreak of the latest dispute over date formats.|small=yes}}


== Recent edits ==


A string of edits by ] and ]. introducing and removing changes to {{slink|Misplaced Pages:Manual of Style/Dates and numbers|Common mathematical symbols}}, raise issues that I believe should be discussed.
''Please centralize discussion on date formats to be used after autoformatting is removed in the section on ] instead of forking out new topics.''


#The most recent change, ], has the comment {{tq|This page does not cover matrix operations.}}, however, I do not see anything in the article to support a restriction to numerical operations.
#The most recent change reinstates the link to ], despite the comment.
#There seems to be disagreement on the division sign.


The questions that I wish to raise are
== Is BC/AD POV? ==


#Should that section mention {{tl|tmath}} or {{tag|math}}?
I personally do not think the BC/AD system implies a belief in Jesus as the Lord anymore than Thursday implies a belief in Thor...however, on the ] page people have mentioned that it is POV- is it? ] (]) 23:36, 2 September 2008 (UTC)
#Are vector operations within the scope of the article? Regardless of the answer, the dot and cross products should be treated consistently.
#Should there be two new rows for dot and cross product?
#Should there be a row for ]?
#Is ] unhelpful since it has three forms?
#Should the ] ({{Unichar|F7}}) be deprecated in favor of ] ({{Unichar|2f}})?
#Should {{Unichar|2215}} be explicitly deprecated in favor of Slash?
#Should the use of "x" and "*" as multiplication signs be explicitly deprecated in favor of {{unichar|D7}}?
#Should that section show the {{Stylized LaTeX}} markup for characters in addition to the HTML ]?
-- ] (]) 10:52, 27 September 2024 (UTC)
:
:# I think the page should be devoted to general articles, and &lt;math&gt; should be reserved for advanced math and science articles.
:# Vector operations are not currently in the scope of the project page, and I'm not thrilled about adding them.
:# Dot product and cross product should certainly not be addressed in the same row as any scalar operation. The multiplication dot should certainly not be linked to the "Dot product" article nor should the multiplication cross be linked to the "Cross product" article.
:# Tensor products should not be covered in this project page because they're too advanced.
:#<li value=7> I'm not willing to spend 5 or minutes figuring out what this line means.
:# The asterisk as a multiplication sign should be limited to articles about computer languages that use it as such.
:# LATEX should not be mentioned, since we don't use it in Misplaced Pages. This isn't a style manual for writing outside of Misplaced Pages.
::] (]) 19:45, 27 September 2024 (UTC)
:Tbh, I wondered what this extensive list is doing in the MOS in the first place. ] does it better. It really needs to be reduced to cover only those symbols that have a styling issue: scalar division and multiplication.
:* The grade-school division sign should be formally deprecated, for reasons explained at ].
:* The 'ordinary' slash (002F) should be preferred over 2215, same logic as straight quotes and curly quotes.
:* I prefer {{unichar|00D7}} over x, for biology as well as math but maybe that needs debate.
:] (]) 20:04, 27 September 2024 (UTC)
:Comments:
:*I see no good reason to prohibit using a ] to express division. That seems absolutely fine. The ] article seems to say it might be confusing in Italian, Russian, Polish, Danish, Norwegian, or Swedish, but this is the English Misplaced Pages. We use ]s as ]s also, and we use ]s as a ] too, although that might be confusing in other languages.
:*I also see no good reason to prohibit using an asterisk for multiplication; it seems well-understood, easy to type, unambiguous, and common in practice. I agree with not using "x" for multiplication, although I think it's OK to express "by" relationships for 2x4 lumber, 4x8 sheets of plywood, and 4x4 trucks.
:*<big><nowiki><math>x</math></nowiki></big> (i.e., <big><math>x</math></big>) looks different from <big><nowiki>''x''</nowiki></big> (i.e., <big>''x''</big>), and those look different from <big><nowiki>{{math|''x''}}</nowiki></big> (i.e., <big>{{math|''x''}}</big>), at least on my screen, and seeing mixtures of those in the same article can be a bit annoying (especially if they are near each other).
:—⁠ ⁠] (]) 21:46, 7 October 2024 (UTC)
:: Asterisk means ] (which is somewhat related to the idea of "multiplication" but should not be confused with the usual multiplication). Its use as a substitution for "×" or "⋅" is a bad habit from the old days of poor technology (but it was never used as such in professional typesetting) and has no excuse nowadays. — ] (]) 22:12, 7 October 2024 (UTC)
::: Convolution would only be a matter to consider in very mathematically sophisticated specialized contexts. It's not something most people have ever encountered. Even for those who use it, it would often be expressed using ] or ] instead. —⁠ ⁠] (]) 22:21, 7 October 2024 (UTC)
:::: I don't think that this is a good reason to make exceptions to tolerate/promote sloppy typography (moreover, in some computer fonts the ASCII asterisk more like a superscript than a binary operator consistent with +, −, = and so on).
::::: I don't think we should feel responsible for how Misplaced Pages is rendered in all possible fonts. We should remember that everyone is supposed to be able to edit Misplaced Pages articles. In an article that isn't about mathematics, or at least isn't using it beyond the 10th grade level, ''f = 1.8 * c + 32'' seems basically OK to describe conversion from degrees C to degrees F. It's tricky enough that we tell people to pay attention to the difference between "-", "&ndash;", "&mdash;", and "&minus;", and to not use italics for the numbers in that formula, although I support those instructions. —⁠ ⁠] (]) 03:37, 8 October 2024 (UTC)
:::::Nobody should complain about otherwise good edits that include "lazy" typography. Those edits are 100% OK and a net improvement to Misplaced Pages. Other editors who care about typography and MoS can clean up the markup and character choices later. Misplaced Pages is a collaborative project. ] (]) 15:46, 8 October 2024 (UTC)
::Using an asterisk to represent multiplication is programming language syntax; I don't think this is common or even well-known among non-programmers. ] (]) 01:47, 20 October 2024 (UTC)
:::I agree we should discourage use of "*" as a multiplication symbol. I agree it's easy to type, so if one editor writes "''y'' = ''m''*''x'' + ''c''" in an otherwise correct edit, the response should not be to revert that edit, but to replace it with "''y'' = ''mx'' + ''c''" or other approved alternative. ] (]) 10:40, 20 October 2024 (UTC)
:::Using an asterisk for multiplication is absolutely known to non-programmers because that's what is used on the number pad on most keyboards in the US. --] (]) (]) 14:28, 12 November 2024 (UTC)
::::Ah, but which came first - the {{keypress|*}} key, or its use in mathematical expressions? Forty-some years ago, I was taught that in computer code, the <code>*</code> character was chosen to avoid confusion with the letter <code>x</code>, since the <code>×</code> did not exist in either of the character sets that were in use at the time - ASCII and EBCDIC. It's the same with <code>/</code> vs. <code>÷</code> and indeed <code>-</code> vs. <code>−</code>. --] &#x1f339; (]) 18:15, 12 November 2024 (UTC)
:::::{{keypress|*}} appeared on many (but not all) early typewriters. When not present it was often replaced by a fraction key (1/2, 1/4, etc) Practically every computer terminal from the 1970s onward has a {{keypress|*}} key - but that's probably due to it being used by Fortran (1957). Early teletype keyboards typically used ] encoding and did not have {{keypress|*}} - but these were more for telecommunications rather than programming. Fortran was invented at IBM and used punch cards/tape using IBM's ]. The early variations of BCDIC had {{keypress|*}}, {{keypress|-}} and {{keypress|/}} but not {{keypress|+}}. {{keypress|+}} was added soon after. My take is that BCDIC tried to encode whatever was commonly used on typewriters - subject to the limitation of using only 64 characters. Fortran then assigned functionality to whatever was in that set. {{keypress|*}} looked the most like {{keypress|x}} without being a letter, so it got the job. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 23:56, 12 November 2024 (UTC)
::::::It would really behoove participants here, instead of just speculating from the armchair, to take the radical step of doing some research to ''actually find out the answer''. {{keypress|*}} has been used, in math, to mean multiplication for three hundred years. See the bottom of p. 66 of . ]] 07:15, 13 November 2024 (UTC)
:::::::I didn't mention that paper, because I'm not in the habit of searching through 100-year-old academic journals. Now, 100-year-old ''magazines'' is a different matter, witness my stacks of boxes of '']'' back to 1902 (gaps between 1902 and 1939, complete from 1940 onward). --] &#x1f339; (]) 12:02, 13 November 2024 (UTC)
:::::] was a decade earlier than ] and ]. What the first FORTRAN compiler used was the scientific ] character set of the ], which replaced the older Percent (%) and Lozenge ({{unichar|2311}}) with parentheses. -- ] (]) 14:35, 13 November 2024 (UTC)


== Numerals in a sequence ==
:The system has been in use for longer than the modern English language has existed, so it is, for better or worse, an integral part of our language. It is no more POV than the fact that it is hard to write an English sentence about a person without indicating whether the person is male or female. Maybe BC/AD will be abandoned. Maybe English will evolve a new set of pronouns. Just wait and see. --] (]) 23:43, 2 September 2008 (UTC)
:Many people do find AD and BC POV. BCE and CE are the best alternatives as they are completely NPOV. ] (]) 01:10, 3 September 2008 (UTC)
::I dunno; "common era" implies that the Christian era is common to the whole of humanity, which seems an even more extreme point of view than just saying that Jesus can be called "Christ" or "Lord".--] (]) 08:05, 3 September 2008 (UTC)
:::Yeah, it's a bit off to call CE "completely NPOV". It is, however, a more NPOV description of that particular numbering system. The numbers are here to stay, but at least we don't have to shove "The Year of Our Lord" (AD) down anyone's throat. And let's not forget that, strictly speaking, the years are slightly off, since Jesus was born in 7-2 BC. --] (]) 10:23, 3 September 2008 (UTC)
::::As Raul's Laws say, any effort to NPOV a subject results in imposing another POV. BCE/CE is another example of this; whether CE (with its inherent worldview of political correctitude) or AD (with its lingering associations of Christianity) is more POV is a matter of taste - on which Wikipedians differ. Consensus is that we should agree to differ, and not revert war for either POV. ] <small>]</small> 18:04, 3 September 2008 (UTC)
=== Can you use both? ===
The Page states that
<blockquote>Either CE and BCE or AD and BC can be used—spaced, undotted (without periods) and upper-case. Choose either the BC/AD or the BCE/CE system, but not both in the same article. Style guides generally recommend writing AD before a year (AD 1066) and after a century (2nd century AD); however, writing AD after the year (1066 AD) is also common in practice. The other abbreviations always appear after (1066 CE, 3700 BCE, 3700 BC). The absence of such an abbreviation indicates the default, CE/AD. It is inappropriate for a Misplaced Pages editor to change from one style to another unless there is a substantive reason; the Manual of Style favors neither system over the other (see WP:BCE for past debates on this).</blockquote>
However, can you use both- as is the case on the article ] so that it says, "Jesus is thought to have been born in between 7-2 BC/BCE?" ] (]) 14:25, 3 September 2008 (UTC)
::You could also say ''Jesus is thought to have been born between the years -0006 and -0001'' if you use ISO 8601 date format. This is not only politically but mathematically correct, since in the ISO system, there is a year 0000. The History Channel humorously represents this as ''Jesus Christ: born 0000, died 0036.'' The Romans and early Christians were mathematically challenged, so they did not have a year zero in their calendar, throwing the math off by 1 year for BC dates. And, even worse, they used Roman numerals, possibly the worst number system ever invented.] (]) 18:17, 3 September 2008 (UTC)
::Why not just create a year zero with (appropriately) zero days? ] (]) 21:51, 3 September 2008 (UTC)
:::Year zero was just another ordinary year - the only problem was that the number zero hadn't been invented yet so they didn't know how to write it down. In the proleptic Gregorian calendar used in ISO 8601, the year 0000 was a leap year, so it had 366 days. The year before that was -0001, and it had 365 days.] (]) 04:21, 4 September 2008 (UTC)


'Phase 1' or Phase one'? This appears to be a case that's not explicitly covered.
== Text formatting math section merge proposal ==


The AP Stylebook recommends using figures for sequences in its section on "Numbers":
] serves no purpose at all, as it is simply rehash of ] (and in one place ]). To the extent it may say anything distinctive that point should be added to MOS/MOSNUM, but otherwise this is just a blank-and-redirect-to-MOS. See also the closely related discussion at ]. The merge-from page is inconsistent on many points with both target pages, and its talk page is evidence of a great deal of confusion being sown among editors as a result of this break-away "guideline{{" '}}s existence. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 05:31, 4 September 2008 (UTC)
"Also use figures in all tabular matter, and in statistical and sequential forms", from which I infer that for sequences, such as 'phase 1', figures should be used for clarity and consistency.


Similarly, chapter 9 of The Chicago Manual of Style advises using figures when referring to a sequence.
PS: I have edited a few bits of it to comply better with MOS/MOSNUM, but much of it is still messed up. There are probably a few points in it not presently in either of the controlling guidelines (which is why I suggested merges instead of just wiping it). One of the most important of these (one that I just added) is that variables should be marked up with <code><nowiki><var>variable</var></nowiki></code> (<var>variable</var>), not <code><nowiki>''variable''</nowiki></code> (''variable''). They both will typically visually render the same (depending upon user-side CSS), but the former actually has a semantic meaning, while the latter is just presentational hooey (notably, by the time it hits the user's browser, MediaWiki has converted the latter into <code><nowiki><span style="font-style: italic;">variable</span></nowiki></code>, not <code><nowiki><i>variable</i></nowiki></code>, because it has zero meaning at all from a content/semantics point of view). As with much else in MOS*, the average editor will ignore it and do what is convenient, but math editors (definitely not me) and cleanup gnomes (definitely me) should get this right. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 06:32, 4 September 2008 (UTC)


I propose adding similar explicit advice to this section of the MOS.
:Any objections? — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:59, 6 September 2008 (UTC)


-- ] (]) 20:10, 19 October 2024 (UTC)
:: It doesn't look like it. I support the merge, and so do all others who have commented on ]. ] (]) 06:09, 7 September 2008 (UTC)
*As usual, what's needed before something's added to MOS is examples of this being an issue on multiple articles -- see ]. Are editors not able to work this out for themselves on individual articles? Anyway, why does the word "Phase" need this in particular? Why not "Section" and "Part" and any other words like that? {{pb}}The advice from APA and CMS are great if you're making up a new sequence for your thesis, but that's not us. It's hard to imagine an article using a phrase like "Phase 1" or "Phase One" on its own -- that is, other than in imitation of the phrasing of sources. So follow the sources; for example, ] refers to ''Phase I'' and ''Phase II'' and ''Phase III''., because that's the form the Act uses. We're not going to override that in the name of consistency with other, unrelated articles. ]] 22:00, 19 October 2024 (UTC)
*:To clarify: I'm using 'Phase' purely as an example. The issue of using figures for sequences applies to any sequence. including 'Section' and 'Part' - and other examples: "Game 3", of a sequence of nine; 'Chapter 9' of a sequence of 24; 'Week 4' of a limitless sequence.
*:I raise this issue in the context of differing editorial practices in the ] article, where both figures and words have been used to reference the same phases and weeks of the inquiry. I sought guidance from the MOS and found none.
*:I'd be content to follow the sources, without adding bloat to the MOS, if I could be confident that that's an accepted stylistic convention in this instance. -- ] (]) 22:27, 19 October 2024 (UTC)
*::Such names are very often established by authoritative sources and constitute proper names; we should follow the sources rather than renaming them. Per EEng, we only need a MOS guideline if our sources don't provide clear names and either there is dissent among editors or consistency across articles would be of significant benefit. In the Post Office case, I see the phases have been titled Phase 1, Phase 2 etc by the inquiry so unless the inquiry's inconsistent, we can follow that source. Still, I see that this is a live issue at that ] article, so it would be wrong to establish a new guideline or issue some sort of MOS talk-page ruling without the knowledge of the other editor; pinging {{u|MapReader}}. ] (]) 14:56, 20 October 2024 (UTC)
*:::Between ] and ], multi-episode ''Doctor Who'' stories could have titles in any of the four combinations of (i) "Episode ..." or "Part ..."; (ii) numbers as figures or as words. The decision as to which format to use was probably in the hands of the series producer, but in our articles about each story, we give the actual title shown on screen - except that where the on-screen title is all-capitals, we reduce it to title case. Certain ''Doctor Who'' reference books do the same, so we're following the sources. --] &#x1f339; (]) 18:18, 20 October 2024 (UTC)
*::::The question raised was "differing editorial practices in the British Post Office scandal article". Sounds like a matter of internal consistency, which is different. For all manner of things -- this being one IMO -- we might not need consistency among articles, but it does look bad within articles. Surely we already have a rule addressing that general issue tho? ] (]) 13:24, 21 October 2024 (UTC)
*:::::I think we don't. In articles on TV series it's common to have expressions like "season 3" and "episode 7", which seem to go against our current wording (use words for numbers below 10). ] (]) 16:37, 21 October 2024 (UTC)
*::::::It is indeed a matter of internal consistency and it does look bad, as ] says. Within the one article (]), we have (e.g.) both "Phase 3 hearings" and "Phases five and six". Is there in fact a rule addressing this general issue? -- ] (]) 18:47, 21 October 2024 (UTC)
*::::::From ]: "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." Unless you are dealing only with series with fewer than 10 seasons each with fewer than 10 episodes, it is more in line with MOS to give all season and episode numbers in digits rather than words. --] (]) (]) 13:15, 22 October 2024 (UTC)
*:::::::True, but series with less than ten seasons aren't all that rare, and there are also miniseries with less than ten episodes. ] (]) 16:39, 22 October 2024 (UTC)
*:::::::Whether or not it's in line with MOSNUM, we frequently – I suspect in the vast majority of cases – give series/season and episode numbers in digits. I've been dipping into ]. Articles on individual episodes do routinely begin e.g. " the ninth and final episode of the first season" but with digits in the infobox. Articles on a season/series list episodes using digits, and articles on a show list series/seasons and episodes with digits, regardless of whether there are more or less than ten, in keeping with the examples in ]. Articles are often titled ''&lt;show&gt; season &lt;n&gt;'' where n is a digit, never a word, in accordance with ]. Sampling our ], I see the same treatment in titles, infoboxes, and listings.{{pb}}I very much doubt that editors would accept changes to those FAs and GAs to bring them into line with ], that FA and GA assessors will start to apply ] in such cases, that any move requests would succeed, or that ] and ] will be brought into line with the current ]. Changing ] might be easier. ] (]) 08:20, 23 October 2024 (UTC)
*::::::::I agree, a small addition to MOS:NUMERAL might be a good thing. ] (]) 17:00, 23 October 2024 (UTC)
*:::::::Your final sentence doesn't follow from your statement. It would be more in keeping with the MOS to give all in words. ] (]) 11:16, 23 October 2024 (UTC)
* Generally concur with EEng and NebY. It's clear that certain conventions adhere strongly to certain things, and these conventions will be readily apparent from the source material about those things. WP is not in a position to impose an artificial WP-invented consistency on them that makes no sense for those familiar with the subject (e.g. referring to "issue number seven" of a comic book or "the three ball" in a game of pool). Where nothing like a consistent convention can be observed for the topic at hand, then MOSNUM already provides us with a default to fall back to: use "one" through "nine", then "10" onward. This is the case with centuries, for example. There is no overwhelming source preference for either "third century BC" or "3rd century BC" in reliable sources. (Books tend to prefer the former, journals use the latter more than books do because journal publishers are more interested in compression/expediency. Scroll through first 10 pages of GScholar resuls and see how much variance there is, and how frequent the numeral style is compared to "traditional" spelling-out. That said, GScholar searches do include some books as well as journals.) Following our default system, we naturally end up with "third century BC" and "12th century BC". (Of course, our material doesn't perfectly follow this; our editors are human, not robots. Well, mostly.) <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 15:04, 24 November 2024 (UTC)


== Fractions == == μs vs us ==
''(Unicode symbols for fractions may also be used.)'' - this creates an inconsistent look - I've written a script that people who prefer to see the fraction symbols can use to change available fractions from {{tl|frac}} in their view; anyone have any thoughts on changing to officially prefer {{tl|frac}}? --] (]) 19:38, 5 September 2008 (UTC)


Which style I should use for micro seconds? Does μs "Do not use precomposed unit symbol characters"? ] (]) 04:44, 30 October 2024 (UTC)
* By “people”, I believe you are referring to “registered editors”-only, are you not? Would this tool benefit unregistered I.P. users, who comprise 99.9%+ of Misplaced Pages’s readership? I guess I don’t understand exactly what technology you have made and who can benefit from it. Please explain. <span style="white-space:nowrap;">''']''' (])</span> 22:14, 5 September 2008 (UTC)


:The 2 characters "μ" and "s" are just fine. The precomposed symbols advice is to guard against particular fonts that combine them into a single character because many software readers for the sight impaired do not know all of these symbols. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 04:53, 30 October 2024 (UTC)
:The Unicode fractions should simply be completely deprecated for WP usage. Only a tiny handful of them exist, and they do not render consistently (not only are they inconsistent with {{tl|Frac}} they are ''inconsistent with each other'' in some fonts, including the default font used under MacOS X by Mozilla browsers such as Firefox and Seamonkey). Hmm. I though I ''already'' deprecated these in MOSNUM. Am I misremembering? — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:36, 6 September 2008 (UTC) PS: I've also heard that they cause accessibility problems, as some screen readers don't recognize them. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:37, 6 September 2008 (UTC)
:But do use μ, not "u". The latter was something of an early-Internet halfassed approach, but we have Unicode now. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 15:09, 24 November 2024 (UTC)
::I think it was me who added the sentence (and indeed the whole pararaph), based on a short talk page discussion that revealed that MOSNUM didn't then contain any advice at all on representing fractions. I'd be quite happy to see the Unicode fractions deprecated.--] (]) 09:09, 7 September 2008 (UTC)


== Day, date month format ==
*Greg, anyone who has a strong enough preference for seeing ½ instead of {{frac|1|2}} that they can't stand the latter can register an account for that. The difference between this and randomly mixed date styles is that this is a legitimate stylistic choice --] (]) 12:46, 8 September 2008 (UTC)


Greetings and felicitations. I assume that such constructions as "Wednesday, 24 February" are discouraged, but I can't find it in the text or the this page's archives. (The comma seems unnecessary to me.) May I please get confirmation or refutation? —] (]) 04:28, 4 November 2024 (UTC)
Since I don't see anyone defending Unicode fractions here, and since it was me who originally added the sentence, I'm going to delete it again.--] (]) 12:57, 8 September 2008 (UTC)
*] and ] cover the allowed and disallowed formats. Unless the day of the week is ''vitally'' important then we leave it out. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 06:16, 4 November 2024 (UTC)
*:This specifically regards the "]" article, and its Konomiya Hadaka Matsuri infobox, which includes the days of the week. —] (]) 07:40, 4 November 2024 (UTC)
*::Ah, the mysterious East. ]] 08:06, 4 November 2024 (UTC)
*Salutations and hugs and kisses to you too.
**If your question is whether day-of-week should be gratuitously included with dates for no particular reason, the answer is ''No''. That is, if the day-of-week is somehow relevant to the narrative, sure, include it, but otherwise no.
**Assuming we're in some situation where (per the preceding) inclusion of day-of-week is indeed justified, maybe your question is how to append the D.O.W.
***If the date is {{nobr|''February 24''}} or {{nobr|''February 24, 2024''}}, then without doubt the right format is ''Wednesday, February 24'' or ''Wednesday, February 24, 2024''.
***According to "Elite editing" (whoever they may be -- search the text "inverted style" on that page), the corresponding answers for {{nobr|''24 February''}} and {{nobr|''24 February 2024''}} are {{nobr|''Wednesday, 24 February''}} and {{nobr|''Wednesday, 24 February 2024''}}. To me that does seem right -- {{nobr|''Wednesday 24 February 2024''}} (all run together, no commas at all) seems intolerable.
:The question naturally arises as to whether MOS should offer advice on all the above. My answer, as usual, is provisionally ''No'', per ]. ]] 08:02, 4 November 2024 (UTC)
::Looking at the article, the date is the 12th day of the Chinese year and the day of the week has no significance. I would remove the day of the week from all those dates in the infobox. For what it's worth, I spent most of the 1990s in Hong Kong/China. Major holidays based on the Chinese calendar treat the day of the week in the same way that we treat the day that Christmas falls on. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 09:18, 4 November 2024 (UTC)
:::Okay—will do. Thank you both. ^_^ —] (]) 09:21, 4 November 2024 (UTC)
:The new 18th edition of ''The Chicago Manual of Style'' gives advice about commas in dates in ¶ 6.14. When giving examples they mostly give examples with words after the end of the date so the punctuation at the end of the date is illustrated. Some examples:
:*The hearing was scheduled for 2:30 p.m. on Friday, August 9, 2024.
:*Monday, May 5, was a holiday; Tuesday the 6th was not.
:] (]) 16:56, 4 November 2024 (UTC)
:Concur with EEng on avoiding adding a rule about this, as more ]. It's just a matter of basic writing sense, basic comma usage in competent English. Our MoS's purpose is not that of ''CMoS'' or ''Fowler's'', trying to answer every imaginable usage question. Just those that have an impact on reader comprehensibility and/or recurrent editorial strife. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 15:18, 24 November 2024 (UTC)


==Spacing with percentage points==
== Concealed links ==
A question regarding spacing of percentage point (pp) usage. I have always assumed there is no space between the number and pp (e.g. 5.5pp not 5.5 pp), on the basis that you wouldn't put a space between a number and a percentage sign (5% not 5 %). There is no reference to this in the MOS, but the ] article uses it unspaced. It might be good to have it clarified in the MOS as I see regular changes adding spacing, which I am not sure is correct. Cheers, ] ]] 23:49, 5 November 2024 (UTC)
*] says "omit space". <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 23:54, 5 November 2024 (UTC)
*:Perhaps I am missing something, but as far as I can see, it says to omit space when using the percentage symbol (%) but nothing about when using pp? ] ]] 00:21, 6 November 2024 (UTC)
*::Apologies, I missed the "point" word in your question. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 01:49, 6 November 2024 (UTC)
*% is essentially a constant factor (.01), but ''pp'' is more like a unit so my intuition says it should be spaced. I note that the ] article uses a space before ''bp'' (mostly, anyway). I'll be interested to hear what others think. ]] 18:23, 6 November 2024 (UTC)
*:You've got this back to front. Percent (%) is a standard unit symbol and should be spaced, whereas pp is a made up abbreviation, meaning you can put it anywhere you want, space or unspaced. I know MOSNUM says otherwise, which is WP's prerogative. In other words, if we need a rule, let's make one up and apply it, but there's no logic involved. ] (]) 21:06, 6 November 2024 (UTC)
*Dondervogel, "Percent (%) is a standard unit symbol and should be spaced". Huh? It's not an ISO unit symbol, is it. No spacing in English, unlike French. On pp, I agree with EEng: space it. ] ] 11:10, 8 November 2024 (UTC)
*::Absolutely. When it comes to peepee, always space it . ]] 21:36, 8 November 2024 (UTC)
*:Yes, "%" is an ISO standard unit symbol. ] (]) 12:45, 8 November 2024 (UTC)
*::What is it the unit of? ] (]) 13:14, 8 November 2024 (UTC)
*:::Nothing. It's a ]. To the original q: I don't see "pp" used often, in fact rarely. It's probably better written out in full on first use, and if there are subsequent uses, follow the guidance at ]. --] &#x1f339; (]) 19:58, 8 November 2024 (UTC)
*::::It's used widely in election infoboxes where there isn't space to write it out. ] ]] 22:25, 8 November 2024 (UTC)
*:::I will answer Gawaon's valid question in two parts. The first part is a quotation from ISO 80000-1:2009 (emphasis added)
*:::*In some cases, per cent, symbol %, where 1 % := 0,01, is used as a submultiple of the coherent unit one.
*:::*EXAMPLE 4
*:::*reflection factor, r = 83 % = 0,83
*:::*Also, per mil (or per mille), symbol ‰, where 1 ‰ := 0,001, is used as a submultiple of the coherent unit one.Since the units “per cent” and “per mil” are numbers, it is meaningless to speak about, for example, percentage by mass or percentage by volume. Additional information, such as % (m/m) or % (V/V) shall therefore not be attached to '''the unit symbol %'''. See also 7.2. The preferred way of expressing, for example, a mass fraction is “the mass fraction of B is w B = 0,78” or “the mass fraction of B is wB = 78 %”. Furthermore, the term “percentage” shall not be used in a quantity name, because it is misleading. If a mass fraction is 0,78 = 78 %, is the percentage then 78 or 78 % = 0,78? Instead, the unambiguous term “fraction” shall be used. Mass and volume fractions can also be expressed in units such as µg/g = 10-6 or ml/m3 = 10-9.
*:::Notice the deliberate space between numerical value (e.g., 83) and unit symbol (%). ] (]) 22:10, 8 November 2024 (UTC)
*:::The second part is a partial retraction, quoting from ISO 80000-1:2022, which supersedes the 2009 document:
*:::* If the quantity to be expressed is a sum or a difference of quantities, then either parentheses shall be used to combine the numerical values, placing the common unit symbol after the complete numerical value, or the expression shall be written as the sum or difference of expressions for the quantities.
*:::*EXAMPLE 1
*:::*l = 12 m - 7 m = (12 - 7) m = 5 m, not 12 - 7 m
*:::*U = 230 ⋅ (1 + 5 %) V = 230 ⋅ 1,05 V ≈ 242 V, not U = 230 V + 5 %
*:::The space is still there between numerical value (5) and percentage symbol (%), but I could not find an explicit reference to "%" as a unit symbol. I'm unsure how to interpret that change, but I'll report back here if I find further clarification. ] (]) 22:16, 8 November 2024 (UTC)
*:::I found this in
*:::*In keeping with Ref. , this Guide takes the position that it is acceptable to use the internationally recognized symbol % (percent) for the number 0.01 with the SI and thus to express the values of quantities of dimension one (see Sec. 7.14) with its aid. When it is used, a space is left between the symbol % and the number by which it is multiplied . Further, in keeping with Sec. 7.6, the symbol % should be used, not the name "percent."
*:::*Example: xB = 0.0025 = 0.25 % but not: xB = 0.0025 = 0.25% or xB = 0.25 percent
*:::*Note: xB is the quantity symbol for amount-of-substance fraction of B (see Sec. 8.6.2).
*:::*Because the symbol % represents simply a number, it is not meaningful to attach information to it (see Sec. 7.4). One must therefore avoid using phrases such as "percentage by weight," "percentage by mass," "percentage by volume," or "percentage by amount of substance." Similarly, one must avoid writing, for example, "% (m/m)," "% (by weight)," "% (V/V)," "% (by volume)," or "% (mol/mol)." The preferred forms are "the mass fraction is 0.10," or "the mass fraction is 10 %," or "wB = 0.10," or "wB =10 %" (wB is the quantity symbol for mass fraction of B—see Sec. 8.6.10); "the volume fraction is 0.35," or "the volume fraction is 35 %," or " φB = 0.35," or "φB = 35 %" (φB is the quantity symbol for volume fraction of B—see Sec. 8.6.6); and "the amount-of-substance fraction is 0.15," or "the amount-of-substance fraction is 15 %," or "xB = 0.15," or "xB = 15 %." Mass fraction, volume fraction, and amount-of-substance fraction of B may also be expressed as in the following examples: wB = 3 g/kg; φB = 6.7 mL/L; xB = 185 mmol/mol. Such forms are highly recommended (see also Sec. 7.10.3).
*:::*In the same vein, because the symbol % represents simply the number 0.01, it is incorrect to write, for example, "where the resistances R1 and R2 differ by 0.05 %," or "where the resistance R1 exceeds the resistance R2 by 0.05 %." Instead, one should write, for example, "where R1 = R2 (1 + 0.05 %)," or define a quantity Δ via the relation Δ = (R1 - R2) / R2 and write "where Δ = 0.05 %." Alternatively, in certain cases,the word "fractional" or "relative" can be used. For example, it would be acceptable to write "the fractional increase in the resistance of the 10 kΩ reference standard in 2006 was 0.002 %."
*:::As with ISO 80000-1:2022, there is always a space between numerical value (e.g., 35) and the percentage symbol (%), but no mention of % as a unit symbol. ] (]) 22:38, 8 November 2024 (UTC)
*:::::{{tq|there is always a space between numerical value (e.g., 35) and the percentage symbol (%)}}{{snd}}Maybe in NIST-world, but not here on Misplaced Pages (see ]), so I don't see how any of that helps us with the issue at hand. ]] 23:29, 8 November 2024 (UTC)
*::::::I was correcting a misconception that % is not a unit symbol when it is. At least it was until 2022. I find it best not to leave incorrect statements unchallenged or they take on a life of their own. ] (]) 00:24, 9 November 2024 (UTC)
*:::::::Um, OK, but you do realize that WP does not follow NIST's advice about spacing it, yes? ]] 00:44, 9 November 2024 (UTC)
*::::::::Yep, and I wasn't trying to change that. My contributions have been to
*::::::::*correct a factual error (yours)
*::::::::*respond to questions from Tony and Gawaon
*::::::::I have not weighed in on the main thread regarding percentage points because I don't expect my opinion (based not on NIST's utterings but on the ISO standards on which they are based) to be taken seriously, so why would I waste my e-breath? ] (]) 09:41, 9 November 2024 (UTC)
*It is not conventional to space "%" in English. Nearly no publishers do this, and our MoS doesn't say to do this or incidentally illustrating doing this, so don't do this. "pp" here is a unit abbreviation for ''percentage point'' ("the unit for the arithmetic difference between two percentages)", so space it. % is not a unit abbreviation/symbol, but a quantity symbol, so it's in a different class. It's more like the ~ in "~5&nbsp;ml". That the spelled-out equivalent "approximately", like the spelled out "percent", is spaced apart from the numeral is irrelevant. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 15:24, 24 November 2024 (UTC)


== UNITSYMBOLS (1 × 3 × 6 m): “each number should be followed by a unit name or symbol” ==
The ] says:
*''Do not use piped links to years in music (e.g., do not write: ''The Beatles ''Please Please Me'' came out in <nowiki>]</nowiki>''). Instead, sparingly use parentheses after years mentioned in the article, such as ''The Beatles released ''Please Please Me'' in 1963 (see <nowiki>]</nowiki>)''.


] currently requires a unit symbol after each value when listing dimensions separated by {{char|×}} (“{{xt|1 m × 3 m × 6 m}}, not {{nobr| {{!xt|1 × 3 × 6 m}}}}”). Could we have a carveout from this rule, and allow editors to use only a final unit when writing for infoboxes, and perhaps other places where space is limited?
The ] referred to the music guideline and suggests formulas like:
*''Foo is an American political thriller that was <nowiki>]</nowiki> and starred...
*'''Snatch''' ''is a <nowiki>]</nowiki> ...


Context: {{tl|Infobox mobile phone}} currently has a preference for listing the dimensions of the product each on a separate line. This, and other parameters, can make the infobox {{em|very}} long. This is especially problematic for pages that cover multiple products or versions of a product; see dimensions in ] infobox. In order to cut down these infoboxes, we could be using a single line for all three dimensions, but the unit after each value feels unnecessary, and can cause line overflow.
Now the aircraft project is discussing the same issue at: ]. The music project and film project suggestions are not specific to just music or films. I think they have good suggestions that MOSNUM readers may find useful as options. Does anybody agree? ] (]) 20:01, 5 September 2008 (UTC)
:I'd be pleased for advice to be written into MOSNUM that the practice of piping to what looks like a single year generally be avoided. A few examples of how such pipes can be reworded might be provided, so that editors see that there are more skilful ways of linking. I'd also like MOSNUM to point out that it's unnecessary to link more than one or two "year in blah"s, since all years in blah can be accessed through just one. ] ] 04:43, 6 September 2008 (UTC)


Prior discussion: ], where the potential for confusion with actually {{em|multiplying}} values was pointed out. I think this is a minor concern in general, but worth considering in prose, or in contexts where the values could be ambiguous. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 04:17, 11 November 2024 (UTC)
:A similar issue is present in ], where years link to YYY in Ireland. I think it would be better to write in a style that gives readers a better idea of what they will find when they click on the link. --] (]) 20:26, 5 September 2008 (UTC)
::A good general rule is to make sure a masked link includes more than one word or term in the text, so that users have some reason to believe they're not just going to be transported to the article ] or whatever. ] <small>]</small> 22:34, 5 September 2008 (UTC)
:::Good point, Anderson. Maybe that should be included as advice in MOSNUM. ] ] 04:39, 6 September 2008 (UTC)
:::'''Strong support''', as it were. I do this all the time (see my edits last night/this morning (depending on your time zone) to ] for an example. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:29, 6 September 2008 (UTC)


:Where space is limited, it makes sense to present a single compound unit, equal to the product of the separate units. For the example given, the compound unit symbol would be m<sup>3</sup>. ] (]) 12:13, 11 November 2024 (UTC)
== As of ####-##-## ==
::Who ever heard of a phone advertised as 5 cc ? People are more interested in it being wide and tall but very thin. This necessitates stating each individual dimension. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 22:40, 11 November 2024 (UTC)
:::No, what Dvogel means is you'd write that a certain phone measures {{tq|{{nobr|146 x 71.5 x 7.65 mm{{sup|3}}}}}}. Having clarified that, I'm bound to say that that would, of course, confuse 99% of our readers. ]] 22:47, 11 November 2024 (UTC)
::::Gotcha. As well as confusing most readers, it would also be different to {{tq|{{nobr|1 by 3 by 6 m}}}}, which is allowed. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 23:30, 11 November 2024 (UTC)
:::::To be clear for those playing along at home, while the canonical formuations are {{tq|{{nobr|1 m by 3 m by 6 m}}}} and {{tq|{{nobr|1 m x 3 m x 6 m}}}}, MOS currently makes an exception allowing {{tq|{{nobr|1 by 3 by 6 m}}}} (specifically in the case where all the quantities are in the same unit -- in this case metres), but no corresponding exception allowing {{tq|{{nobr|1 x 3 x 6 m}}}}. While it may offend purists, I really don't see why the exception shouldn't be extended to that last case as well. Thoughts? ]] 23:39, 11 November 2024 (UTC)
::::Thank you for clarifying my intent. And for making me chuckle. LoL
::::For a 3 dimensional object, one can write either 146 mm x 71.5 mm x 7.65 mm or 146 x 71.5 x 7.65 mm<sup>3</sup>. I agree the former is clearer, but the latter uses less space, which can be a consideration. There is no difference in meaning.
::::I guess one could also write 146 x 71.5 x 7.65 mm, but then we have a length, not a volume. It would be clearer to write that length as 79.86 m. ] (]) 23:42, 11 November 2024 (UTC)
:::::{{tq|one could also write {{nobr|146 x 71.5 x 7.65 mm}}, but then we have a length, not a volume}}{{snd}}Formally perhaps, but you could say the pretty much the same about {{nobr| 146 by 71.5 by 7.65 mm}}, and yet we allow it. No one will think that {{nobr|146 x 71.5 x 7.65 mm}} means the length 79.86{{nbsp}}m (i.e. 79860{{nbsp}}mm). In context readers will understand it for what it is. I'd like to hear what others think about my proposal. ]] 23:56, 11 November 2024 (UTC)
::::::Seconded EEng's proposal - simple and clear. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 04:36, 14 November 2024 (UTC)
::::::EEng is, of course, correct. At {{tl|convert}} we sometimes are asked how the duplicate mm units can be removed to save space (the trick is to use <code>xx</code> in convert) and we tell them that omitting repeated units is ok if space is limited. May as well make it official. ] (]) 05:51, 14 November 2024 (UTC)
:::::::{{tq|EEng is, of course, correct.}}{{snd}}Of course -- . ]] 06:37, 14 November 2024 (UTC)
::::::I also support the proposal. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 05:53, 14 November 2024 (UTC)
::I thought this was a joke and burst out laughing on a train, which got me a weird look from a fellow passenger. Anyhow, I too support allowing the single unit after x symbols per EEng and John. ] </span>]] 17:31, 18 November 2024 (UTC)
::: <nowiki>:(</nowiki> <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 23:34, 18 November 2024 (UTC)
*It's tiresome to have to write (and read) units multiple times when multiplication signs are used. ] ] 09:47, 14 November 2024 (UTC)
* As the person who proposed this in the first place, I too support EEng’s proposal. I will carry on working on the infobox, and leave the written MOS to others. I imagine the purists might be happy if we left some comment or endnote about making sure the measurements are not potentially ambiguous though?
:And, for anyone who cares, there are already pages where this is in sensible use: ]. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 23:34, 18 November 2024 (UTC)


==Do we have to convert inches for wheels?==
It has been my understanding that in the case of "As of ''some-date''" (as in ]), it is recommended that the phrase DO get linked - so that people can check what might need updating using "what links here" from the ]. There is a bot removing links from ]s - likely in response to the recent change in policy re linking dates --] (]) 20:17, 6 September 2008 (UTC)
I see people adding conversions to mentions of screen sizes and wheel dimensions - is this really necessary? Even in or , automobile and bike wheels are universally referred to by inches; rim diameters are expressly . To me, adding conversions for these types of dimensions adds unnecessary clutter, harming readability for no return whatsoever. I haven't read the entire MOS today, apologies if I missed a mention of these situations. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 17:24, 13 November 2024 (UTC)
:Which bot? That needs to be stopped immediately. ] (]) 20:30, 6 September 2008 (UTC)


:It looks like sizing bike wheels in inches is not universal. I see many charts in the I-net such as that use both metric and imperial/American units for bike wheels and tires. Whether the convert template handles them correctly is another issue. ] 17:43, 13 November 2024 (UTC)
::Why should the people who make backwards use of "as of" links expect these links to be respected if they have not documented this usage anywhere that editors are likely to find it? --] (]) 21:13, 6 September 2008 (UTC)
:On the matter of wheel sizes, not all are inches. See ] and my reply. Even for a conventional non-Denovo wheel, the dimensions are a bastard mixture: "195/65 R 15" means a tyre that is 195 mm wide on a 15-inch rim. --] &#x1f339; (]) 19:10, 13 November 2024 (UTC)
::Yes, there is the Michelin TRX and the Denovo. Just as we wouldn't convert the "195" when we write 195/60 R15, I don't think we ought to convert the diameter either. I would treat all of these tire dimensions as one would nominal measurements, rather than inserting unnecessary templates. Bicycle tires, meanwhile, proved more varied than I was aware of. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 04:33, 14 November 2024 (UTC)
:::I agree with Mr.Choppers on this subject. I think wheels sizes on cars are a compromise between the USA and the rest of the world. There are metric rims on older vehicles but pretty rare on new vehicles. ] (]) 11:40, 14 November 2024 (UTC)
::::{{ping|Avi8tor}} - I was actually triggered by you converting screen dimensions, but five minutes online showed me that the modern world has indeed begun dropping the use of inches for screens. My gut was wrong. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 13:36, 14 November 2024 (UTC)
:::::Many people around the planet know only millimetres, so it makes sense to have both. I notice in France the data information on television screen size have it in both inches and millimetres. ] (]) 17:57, 16 November 2024 (UTC)
*I agree with Aviator, who didn't mention that aviation uses "feet" for altitude—needs conversion in my view. ] ] 07:30, 22 November 2024 (UTC)
*:I thought that ] is not a measure of distance but of pressure, so perhaps it should be converted to pascals first. I'm not saying one should not then convert to metres too - only that the conversion would need some care. ] (]) 22:06, 22 December 2024 (UTC)


==RfC Indian numbering conventions==
:::Yeah, that, and what on earth possible utility could there be in linking to "]"? That seems utterly pointless to me. We do not need ''links to articles'' on what happened in some year in order to flag the fact that something in an article may need to be updated! Yeesh. This is like making a link to ] in {{tl|uw-joke1}}. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:26, 6 September 2008 (UTC)
{{atop
| result = There is consensus to continue using crore and lakhs when appropriate.


Most participants also generally agreed with SchreiberBike's conditions (or a variant) - '''Always 1) link it on first use, 2) include what it is a measure of (rupees can not be assumed), 3) also include conventional numbering, and 4) allow it only in articles about the subcontinent'''.
::::You're correct, we don't need links to articles on what happened in some year, but having a mechanism for finding dated statements is useful. Apparently there is a better way: templates instead of wikilinks. "As of" links should not be removed outright, they should be replaced with templates, and it appears that this process is underway. (This has nothing to do with the date autoformatting.) See ]. ] (]) 21:37, 6 September 2008 (UTC)


However, this RFC suffered from structural issues that a precise wording isn't agreed on yet. Any changes from status quo should go through a clearer future discussion or RFC on just that.
== Date auto-formatting and linking post-change discussion ==


{{nac}} ] (]) 22:02, 24 December 2024 (UTC)
:''Please centralize discussion here instead of forking out new topics.''
}}
<!-- ] 17:01, 21 December 2024 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1734800468}}
I am revisiting an issue that was last brought up 6 years ago ] and settled without a strong consensus.


I think we should avoid using Indian numbering conventions unless it is needed for context. For instance, if we want to list the box office take of an Indian movie, don't use "crore", use "millions". This isn't about disrespecting a culture, it's about using internationally favored notation and unit conventions. We should use "millions" instead of "crore" for the same reason we favor meters over feet. There is no reason that India-related articles should be an enclave of Indian conventions. People who are not Indian will struggle with these things, it will weaken Misplaced Pages's role as an information tool for everyone.
=== Lightbot: please support latest approval ===


This is not the same thing as currency. It is appropriate to list an Indian movie's box office take in rupees. Providing a US$ conversion is optional, but a good idea since the US dollar is widely used around the world as a reserve currency. But write it as "millions of rupees", not "crores of rupees". ] (]) 16:38, 16 November 2024 (UTC)
Many of you will know of the activities of Lightbot. It has touched over 140,000 articles with edits relating to dates and units. I've made a new request for bot approval that is largely a clarification/extension of two previous approvals and has wording that should be easier to understand. The bot approvals group is not necessarily aware of what Lightbot does so I would be grateful if you could add a few words in support at ]. I would also be happy to answer any questions here or on my talk page. Regards ] (]) 12:30, 1 September 2008 (UTC)
:What's the common usage in english? ] (]) 16:45, 16 November 2024 (UTC)
::I don't think most people in the US understand what "crore" is, and would not recognize it as part of the English language. The online says it means ten million, specifically, a unit of value equal to ten million rupees or 100 lakhs. I think most people in the US would not even understand that a currency is being mentioned.
::--] (]) 17:00, 16 November 2024 (UTC)
:::Not just people in the US. Nobody outside of India can be expected to know what a crore is. ] (]) 17:15, 16 November 2024 (UTC)
:We use meters over feet? Where?
:{{tqb|In non-scientific articles with strong ties to the United States, the primary units are US customary (pounds, miles, feet, inches, etc.)}} ] (]) 17:50, 16 November 2024 (UTC)
::You get extra points for saying "US customary" and not "Imperial". 😉 ] (]) 18:20, 16 November 2024 (UTC)
:::{{smalldiv|1=imperial :3 ] (]) 18:30, 16 November 2024 (UTC)}}
:I agree with ], do not use "crore", use "millions". Misplaced Pages is for a worldwide audience. ] (]) 18:03, 16 November 2024 (UTC)
::Kinda like how US units are used for US articles, I don't see the harm in using "crore", and it's way more work to manually convert to millions every time a member of India's vast diaspora in the Global North adds "crore" to an article, not knowing our ManualOfStyle. ] (]) 18:19, 16 November 2024 (UTC)
:Except we don't favor meters over feet — we use both. That's what the ] is for.
:Speaking as a non-Indian, who can never remember what how many is a "crore": I'm fine with it, as long as the ]. ] (]) 18:18, 16 November 2024 (UTC)
:We already make an exception for ]. I see no good reason for barring a second exception. State in ] and convert to a unit non-Indians can understand (millions of ]s?). ] (]) 20:48, 16 November 2024 (UTC)
The article for the French movie '']'' lists the budget as "9.5 million", using a point as a decimal separator. In France they use commas for this, ie "9,5 million". We don't use the French notation convention for France-related articles. ] (]) 17:14, 16 November 2024 (UTC)
:Is it the French style to use that notation in English? A different unit elicits way less confusion than a reversed decimal separator meaning anyways. ] (]) 17:50, 16 November 2024 (UTC)
*'''Bad RFC'''; see ] and the rest of the guidance there too. Unsurprisingly, this has just started out as a disorganized discussion that doesn't resemble a normal RFC...you might want to just remove the tag, get some feedback, and then start a proper one in a bit (separate subsections for discussion and survey are pretty helpful too). ] (]) 18:21, 16 November 2024 (UTC)
*:{{replyto|Kurzon}} I did {{diff|Misplaced Pages talk:Manual of Style|prev|1257781055|advise you}} not to jump straight for a full-blown thirty-day formal RfC without first exhausting the suggestions at ]. --] &#x1f339; (]) 18:39, 16 November 2024 (UTC)
:This RfC is clearly improperly formatted, ]; thank you to our unregistered friend for pointing this out.
::Oh come now. It seems to be developing nicely, I doubt that any editors are swayed by the wording. it's not perfect but perfect is the enemy of good and its good enough. ] (]) 04:47, 29 November 2024 (UTC)
:::That reply was before the appropriate discussion centers were notified and before discussion started to develop. It's not just formatting; it's that there was no prior discussion. Now we're effectively having both at the same time, especially when an informal discussion could've resulted in consensus without a time-consuming process. ] (]) 16:08, 29 November 2024 (UTC)
:Consistency and clarity to our international readership are valid arguments in favor of prohibiting "crore" and "lakh". However, Aaron Liu makes good points about the fact that we allow local variation in articles with local ties, e.g. all of ]. I am unsure where I sit on this issue. I would like to see some Indian editors weigh in on this. ] </span>]] 19:58, 16 November 2024 (UTC)
::I also agree that crores are too obscure (as are lakhs), with use limited to South Asia. Feet and inches, while retrograde and infinitely useless, were used across most of the world not many generations ago. The major unit in Japanese is 万 (man), which is 10,000, but we do not use that because most people wouldn't know it. Engvar is somewhat different: we cannot avoid choosing between "colour" and "color", for instance, whereas we can easily write the globally recognized "millions" rather than crores. As for ]'s comment: if someone adds crore, it will be there until fixed – it's not pressing enough of a problem to hunt down every instance. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 20:03, 16 November 2024 (UTC)
:::Good point about 万 – I completely forgot that Chinese has similarly different units. I think that settles it – either we allow crore and lakh alongside the ] (which I think is ridiculous) and an infinite variety of customary units, or we allow none.
:::(Two counterarguments: 1. This is a ] argument, which is a logical fallacy. To which I say no, we can't give only one country special treatment, we ought to be fair. 2. The East Asian units are non-Latin characters and thus more impractical than "crore". This is true.) ] </span>]] 20:15, 16 November 2024 (UTC)
:::On the subject of the myriad, I agree with Toads's second counterargument: there is no widely-recognized English translation for the unit in some "East Asian variant" of English; they just convert it to ] in translations.{{tqb|we cannot avoid choosing between "colour" and "color", for instance, whereas we can easily write the globally recognized "millions" rather than crores.}}Part of my argument is that "crore" vs long scale is basically the same thing as "colour" vs "color": anonymous editors are going to add them. A ton. Expecting people to not use crore is like expecting people to not spell "colour". It's not pressing enough to hunt down, sure, but you're going to see sweet summer children adding crore into crore-free articles again and again and again. ] (]) 01:14, 17 November 2024 (UTC)
::By the way, I've left a (neutrally-worded) note about this discussion at the Talk page of WikiProject India. ] </span>]] 20:16, 16 November 2024 (UTC)
*'''Don't allow crore.''' In the interest of making articles understandable to a wider audience, we already do this for the decimal marker (.) and separator for groups of 3 digits (,) as previously mentioned. We also ] even though long-scale hasn't entirely died out in the British Isles. ] (]) 21:16, 16 November 2024 (UTC)
*:The decimal marker and long/short scale have a much better reason for their ban: The symbols they use have very different meanings outside of their local context, while crore, lakh, etc. do not. ] (]) 01:04, 17 November 2024 (UTC)
*'''Don't allow crore''' Per ]. This is not comparable with US v metric units where we report both - that is just a case of which is primarily reported. Furthermore, imperial units have a relatively recent historical usage across English. It is not like other issues of ENGVAR such as colour v color or ise v ize that do not affect understanding. {{tq|For an international encyclopedia, using vocabulary common to all varieties of English is preferable}} - to the point of being paramount. ] (]) 22:38, 16 November 2024 (UTC)
*'''Allow''' ''crore'', ''lakh'' and ], '''but always''', 1) link it on first use, 2) include what it is a measure of (rupees can not be assumed), 3) also include conventional numbering, and 4) allow it only in articles about the subcontinent.&nbsp;]&#124;] 23:13, 16 November 2024 (UTC)
*:I agree with all of these conditions. While I remain somewhat ambivalent on the use of “crore” in general, we must provide enough context for non-Indian readers to understand them. ] </span>]] 13:56, 17 November 2024 (UTC)
*'''Allow''' ''crore'', ''lakh'' per ], and with the same caveats. ] (]) 00:03, 17 November 2024 (UTC)
*'''Allow ScreiberBike''', per my comments above. ] (]) 01:20, 17 November 2024 (UTC)
* '''Allow ScreiberBike'''. But see also ] - "You may use the Indian numbering system of lakhs and crores ''but should give their equivalents in millions/billions in parentheses''" <!-- Template:Unsigned --><small class="autosigned">—&nbsp;Preceding ] comment added by ] (] • ]) 00:30, 18 November 2024 (UTC)</small>
* '''Allow''' ''crore'', ''lakh'' and ], '''but always''', 1) link it upon first use <u>in every section where it appears</u>, 2) include what it is a measure of (rupees can not be assumed), 3) also include conventional numbering <u>using template {{tl|convert}}—i.e., don't convert yourself</u>, and 4) allow it only in articles about the subcontinent. ] (]) 23:11, 18 November 2024 (UTC)
*: Hm; was very surprised to notice that the {{tl|convert}} template does not currently support lakhs and crores. I think it should, and started ] about that. If you wish to comment, please go to ]. Thanks, ] (]) 23:50, 18 November 2024 (UTC)
*::The convert template converts units, like feet and metres. Crores and lakhs are not units, but multipliers. It would be like convert being used to convert between hundreds, thousands, millions etc. --] &#x1f339; (]) 22:52, 19 November 2024 (UTC)
*:::The {{tlx|lakh}} and {{tlx|crore}} templates make more sense than overloading {{tlx|convert}}. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 23:02, 19 November 2024 (UTC)
*:I agree with SchreiberBike and others; "crores" and "lakhs" can always be used to add colour/color to an article as long as those requirements are met. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 04:50, 20 November 2024 (UTC)
*'''Do not allow'''. This is not the same as variations of English in wide use where there are multiple widespread usages (color or colour). While SchreiberBike's conditions for use are reasonable, I would say that the standard international measurements should always be primary and subcontinent-specific numbering as a secondary only in articles about the subcontinent. ] (]) 09:50, 20 November 2024 (UTC)
*:What does "widespread" mean? ] (]) 12:17, 20 November 2024 (UTC)
{{block indent|em=1.6|1=<small>Notified: ]. ] (]) 01:04, 21 November 2024 (UTC)</small>}}<!-- Template:Notified -->
*'''Allow, but always ...''' exactly as Mathglot laid out above (other than, per Stepho-wrs and Redrose64, {{tnull|convert}} isn't actually the right template, or at least isn't presently). I would add a further caveat that these traditional Indic units (technically, multipliers) should be given secondarily not primarily, but I could live without that. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 11:55, 21 November 2024 (UTC)
*'''Allow''' when appropriate, under conditions set out by ScreiberBike. Also, this RfC does not meet ]. ] <sup>] · ]</sup> 02:18, 22 November 2024 (UTC)
*'''Do not allow''' crore et al. It's not only native English-speakers who haven't a clue what it means when reading India-related articles; it's non-natives too. ] ] 07:32, 22 November 2024 (UTC)
*:I don't get what native/non-native speakers have to do with the issue. ] (]) 12:21, 22 November 2024 (UTC)
* '''Allow per ScreiberBike''' for South Asian articles. ] (]) 17:29, 22 November 2024 (UTC)
*'''Allow''' All Indian academic/professional textbooks and all Indian reliable sources, with few exceptions for specific conditions, use lakhs/crores when denoting INR and millions/billions when denoting foreign currencies. Not allowing is not an option, unless editors want to disregard Indian readers. Using X million rupees is almost as uncommon in India as using Y lakh dollars. My suggestion -- for articles that use {{tl|Use Indian English}} force editors to '''1) link it on first use, 2) include what it is a measure of (rupees can not be assumed)''' with Indian comma separator at 00 after thousands and for articles that don't use that template force editors to '''always''' use millions/billions with 000 comma separator. — ] (]) 03:01, 23 November 2024 (UTC)
*:'''Strongly disallow''' use of Indian comma separator. That would only serve to confuse. We don't permit a French comma separator on English Misplaced Pages. The Indian comma would be much worse. ] (]) 09:11, 23 November 2024 (UTC)
*:I concur entirely with Dongervogel_2 on this side-point; we cannot mix-and-match numeric separator styles. We've repeatedly had debates in the past about permitting "," instead of "." as a decimal point to suit the preference of some subset of readers, and the answer is always firmly "no", so this isn't going to be any different. I'm not a professional researcher in this area, but I have looked into the matter in the course of various style debates, and the evidence clearly shows Indian publications using "Western" number formatting systems (or whatever you want to call them) on a regular basis, though often alongside the Indic {{lang|hi-Latn|krore}}, etc., system. That is, it's just not plausible that English-using readers in/from India have any difficulty understanding our numeric material, especially after the rise of the Internet has exposed them to content from all over the world since the mid-1990s and pretty much ubiquitously since the early 2010 with the rise of mobile data. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 14:49, 24 November 2024 (UTC)
*::{{tq | “it's just not plausible that English-using readers in/from India have any difficulty understanding our numeric material …”}} Of course the same could be said of American readers and the spelling of ‘colour’. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 17:41, 28 November 2024 (UTC)
*:::What isn't the same is how many editors will add "colour" into articles while most wouldn't add numbers in the Indian system. ] (]) 18:30, 28 November 2024 (UTC)
*::::I’m genuinely not sure what your point is? Editors are more likely to (erroneously) change spelling to ‘colour’, so that gives them more grounds for the MOS giving them parity with American English? I know we should be realistic about what we can control, but I don’t love that logic. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 03:18, 29 November 2024 (UTC)
*:::::Yes, that or add spelling that says "colour" is what I'm saying. ] (]) 04:03, 29 November 2024 (UTC)
*:::::Like I would campaign for navboxes to be placed in the "see also" section if it weren't so widespread and unduly investative to correct. The corrections for disallowing crore are the same thing to me. ] (]) 04:11, 29 November 2024 (UTC)
*:::On this attempt at a ''color'' ]: "What isn't the same" even more pertinently is that the cases aren't parallel in any way. ''Crore'' and ''lakh'' are not barely noticeable spelling differences of an everyday word used the same way in every single dialect of English; they're a radically different system of approaching large-ish numbers. There is no audience capable of reading en.wikipedia for whom either ''colour'' or ''color'' is impenetrable. If HTGS's pseudo-analogy is intended to suggest that ENGVAR should be undone on the same basis that we would rejecte or further restrain use of ''crore'' and ''lakh'', that doesn't work since they're not actually analogous at all, plus the fact that not a single element of MoS is more dear to the community than ENGVAR; it is never, ever going away. If HTGS isn't actually suggesting we get rid of ENGVAR but is instead trying to suggest that opposition to ''crore'' is pretty much the same as advocating the death of ENGVAR, that's not cogent either, for the same false-analogy reason plus scoops of ], ], and ] fallacies plopped on top. Aaron Liu's original "what isn't the same" point is that most editors will use ''color'' or ''colour'' as contextually appropriate in our content, yet very few will ever add ''lakh'' or ''crore'' to an Indic-connected article. That could be argued to be suggestive of a {{lang|la|de facto}} community consensus already existing against those units' use at en.wikipedia. While it's worth considering, it's clouded by ] in that a comparatively small percentage of our editors are from India or its immediate environs, so the statistics are probably not usefully comparable even if they could be gathered with certainty. I would suggest that the reasons to rarely use ''crore/lakh'' and to always convert when used at all, has to do with end-reader comprehensibility, not with editor preference or usage rates. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 12:54, 23 December 2024 (UTC)
*::Because, the fact is, we aren’t using varieties of English solely to ensure accuracy or intelligibility. They are also being used to avoid recreating the Anglo-American hegemony that exists in published English, and to foster a connection in the community with the most interest in the subject. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 18:05, 28 November 2024 (UTC)
*:::This is not MakeLocalsAsHappyAsPossiblePedia or EngageInCrossCulturalFeelGoodBackscratchingPedia or RightGreatWrongsPedia. It may be unfortunate in some sense that a "Western" (now globally internationalized) enumeration system dominates nearly everywhere (with arguably more benefits than costs), but it is a fact. And it has nothing to do with "Anglo-American" anything, being the same system used by the French and the Russians and the Japanese and so on, and predating both America and England and even the English language, going back to ancient Eurasia very broadly, from the Rome to China. (There's an incidental British correlation of course: it was largely the English, along with the Dutch, who pushed this system in India. That makes it socio-politically and emotively connected to India–UK and Indian–Western relations, but it is not an Anglic counting system and we are not to be confused by sentiment.) More to the point, the "job" of this site is to communicate clearly with as many English-competent readers as possible. The simple fact is that virtually no one outside of the Subcontinent and nearby islands (plus first-generation emigrées therefrom), think in or even understand ''lakh'' and ''crore''; meanwhile pretty much everyone in India and thereabouts {{em|also}} understands millions, and hundreds of thousands, even if it is not their immediate mental model and they have to convert a bit in their heads, like Americans with metric units. There is no ] to be had here; the sides are not equivalent. Finally, it is not the goal of our articles on Indic culture, history, geography, economics, etc., to appeal to and primarily serve the interests of people in South Asia, but {{em|everyone}}. For this reason, I'm supportive of retaining the permissibility of ''crore'' and ''lakh'' in relevant articles as long as they are always converted into the now globally prevalent enumeration system, and usually with that first unless there's an important contextual reason to use ''lakh/crore'' first. Best of both worlds: everyone gets to understand the material, and Indic numbering is not deleted. It's pretty much the same situation as American customary ("imperial") units of measurement: most of the world doesn't use or understand them, but we should not ban them, just always convert them to metric. (The only difference I can see is "wiki-political": our American editorial and read bases are so large that it would be very difficult to get consensus to always put American units second after metric even in articles about American subjects. That really {{em|should}} be the rule, but it'll be hard to get there.) <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 12:54, 23 December 2024 (UTC)
*'''Do not allow crore''' - I am not convinced that this word is actually English, and this is the English-language wikipedia. It seems that this is a foreign word that is used ''alongside'' English in areas that have ties to the language this word is from. Even in these areas, it seems that English speakers there fully understand what "millions", "thousands", etc mean, and there have been attestations linked above where they use both, presumably to help English speaking people understand what number is being referred to. My perspective here is colored by being an American expat living in Japan... in day-to-day speech, I will sometimes mix the languages and say "Oh, this costs 3 man yen." But I am under no circumstances thinking that "man" meaning "ten thousand" is English. I'm using another language's word. That's what it looks like they are doing here. ] (]) 07:01, 28 November 2024 (UTC)
*:As an alternative, I would also accept allowing crore only if the "millions" number is included alongside it. ] (]) 07:28, 28 November 2024 (UTC)
*:"Gumption" is borrowed from Scots; it is English. "Chutzpah" is borrowed from Yiddish; it is English. "Powwow" is borrowed from East-American indigenous language; it is English. "Crore" is borrowed from Hindustani; it is ]. All of the above are attested by dictionaries, while "man" to mean myriads is not. ] (]) 18:28, 28 November 2024 (UTC)
*'''Allow crore''' - my gut feeling is to disallow it because it is not English as understood by the majority of English readers (including native speakers from UK/US/Australia/etc and second language speakers from China/S.America/Europe/etc). However, crore and lakh are words that Indians practically think in even when speaking English. We have a similar problem where an article is marked as British English and has 99 occurrences of "litre" - an American will still add new stuff with "liter" because it is so naturally to them. In the same way, we will be pushing it up hill trying to get them to stop. So, we should let them use it in articles related to the Indian region but never on anything outside that region. Each first usage should link to ] and ] so that the few non-Indian region readers have a clue what's going on. I would not bother with conversion to millions - once you learn that they are just putting 0's at the end it becomes easy enough in a short time and conversions just clutter up the article. But do not allow grouping like 1,00,000 under any circumstances.<span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 02:41, 29 November 2024 (UTC)
*'''Don't allow crore'''. If there are people who don't know what "million" is, well some level of literacy is required here, yes. As to "link on first use", no, links are supposed to be "here's some extra/more detailed info about the subject if you want" not "you need to interrupt the flow of your reading and go off the page to understand this word". ] (]) 04:57, 29 November 2024 (UTC)
*:Actually that's exactly what links are for. Readers who know the general topic well can just read an article straight forwardly. But readers new to the general topic are likely to come across words they don't know yet and can follow the links to learn. Eg, in car articles we often talk about the ]. If you are new to the detailed study of cars then you can follow that link and then return later. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 06:09, 29 November 2024 (UTC)
*:And if anybody thinks that a politely worded MOS rule will stop them adding crore and lakh then consider that at https://en.wikipedia.org/search/?title=Nissan&diff=1256595427&oldid=1256557060 somebody added a MDY style date in spite of the article having 186 references in DMY style. I fix these (in both directions) practically daily. People do whatever comes natural and do not consider that any other way even exists.
*: But I do feel a little better after my vent :) <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 11:35, 29 November 2024 (UTC)
*::{{+1}} and it’s worth reiterating that most advocates here are suggesting that the Indic value should always be “translated” into a Western value in parentheses, so most naïve readers would still be able to parse the article without following the link. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 06:21, 29 November 2024 (UTC)
*'''Do not allow crore'''—India-related articles are for international readership. No one outside the subcontinent is familiar with ''crore''. It is a disservice to readers to allow it. ] ] 06:24, 29 November 2024 (UTC)
*:If they are not familiar with crore they can read the conversion to millions. And if they also want to learn about ] they can click on the link. I see no disservice. ] (]) 12:49, 29 November 2024 (UTC)
*:Perhaps some are not aware but English Misplaced Pages is heavily used in India. The ] from 2023 had five items about Indian movies and movie stars. The latest week's most viewed ] had ] and '']''. According to ] there are 128 million English speakers there. If we say to basically never use ''crore'' and ''lakh'', we are sending a discouraging, even insulting, message to many of our readers and editors.&nbsp;]&#124;] 13:51, 29 November 2024 (UTC)
* '''Allow''' in articles with strong ties to India, provided that the conversion is shown at first use. Hey, we could even write {{tq|In non-scientific articles with strong ties to <s>the United States</s> India, the primary <s>units are US customary (pounds, miles, feet, inches, etc.)</s> multipliers are Crore and Lakh}}. See ]. Also, it is very relevant that a huge fraction of en.wiki readers are Indian. "ccording to a 2011 census, 10.2% of the Indian population speaks English. This figure includes all Indians who speak English as a first, second, or third language. 10% of India's population is approximately 145 million people." Twice as many as in the UK, half as many as in the US. --] (]) 11:49, 29 November 2024 (UTC)
*'''Allow''' only with linking and conversion as per Mathglot. The most practical solution for both Indian and non-Indian readers. ] (] · ]) 23:41, 8 December 2024 (UTC)
===Discussion===
Maybe this can be solved technologically so that every user sees numbers in the way they are accustomed to? ]<sub>]</sub> 20:43, 8 December 2024 (UTC)
:This could be done for logged in users, but the vast majority of readers are not logged in with an account. Similar solutions have been proposed for date style and variety of English, but they won't work.&nbsp;]&#124;] 20:50, 8 December 2024 (UTC)
{{abot}}


== Which era? ==
:Thanks to those of you that have already commented. The discussion has been weird at times. I welcome more comments at ]. Regards ] (]) 14:02, 3 September 2008 (UTC)
I'm inviting fellow editors to figure out whether ] should use BC / AD or BCE / CE. The issue is that the article mixes eras and when I went back to see which was first, I saw it originally used "BC/BCE" and it stayed like that for years. The thread: ]. Thanks! <!-- Template:Unsigned --><small class="autosigned">—&nbsp;Preceding ] comment added by ] (] • ]) </small>
:] applies so status quo ante should apply. (FWIW, Judaism and Islam have religious perspectives on Jesus of Nazareth, so the neutral style seems entirely appropriate.). --] (]) 00:18, 22 December 2024 (UTC)
::Agreed on the last part. As for the procedural matters, all of our ] principles ultimately default/fallback to the style used in the first non-stub version that used one of the competing styles, if consensus fails. ] is the general principle, the root rule: Don't change from one acceptable style without a very good reason. If there is or you expect resistance, discuss to establish consensus. If you don't get consensus for your change (i.e., there is consensus against you), it stays the {{lang|la|status quo ante}}. If there's no consensus on which would be better (which is often the case and likely the one in this case), then use the version established earliest. For particular things covered by ], ], ], ], we simply reiterate this principle and process more topically, and these ones also basically resolve to an additional rule: don't change that particular kind of style without establishing consensus first {{em|even if}} you're sure you've got a good reason and don't think there should be resistance.<!-- --><p>The STYLEVAR process actually sometimes (namely when there's clearly no firm consensus in favor of the {{lang|la|status quo ante}}, either) overrides the usual Misplaced Pages {{lang|la|status quo ante}} principle, which in practice amounts to "fall back to whatever the discussion closer thinks is more or less a pretty long-term {{lang|la|status quo}}". That usually works for a lot of things, but for these "I will win my Holy Style War or die trying" tedious cyclic ] typographic disputes, it has proven unworkable, because the dispute lives on and on, simply shifting in stages to: what constitutes a {{lang|la|status quo}}; how long is long enough; whether interruptions in the use of the alleged {{lang|la|status quo}} have reset its tenure; whether this *VAR-imposed consensus discussion was followed when the alleged {{lang|la|status quo}} was imposed; if not, then whether that imposition pre-dated STYLEVAR requiring it; and yadda yadda yadda. There's just no end to it, because it's too often a super-trivial but deeply obsessive PoV-pushing exercise grounded in prescriptivist emotions (mixed sometimes with nationalist, or socio-politically activistic, or my-profession-vs.-yours, etc.). The style-war-ending default of falling back to the first major edit that established one of the competing styles is arbitrary (in both senses), but it is {{em|the end of it}}, and we move on to something more productive.</p><!-- --><p>For this particular article: If "it originally used 'BC/BCE{{'"}} in the original post isn't a typo, and really does mean that the style was mixed from day one, then that's a rare edge case, and JMF's "status quo ante should apply" is probably the only reasonable approach. (Even from an excessively proceduralist viewpoint: If STYLEVAR and its application ERAVAR impose an overriding principle that in this case cannot actually be applied, then the default necessarily must be the normal Wikipedian {{lang|la|status quo ante}} principle, even if for matters like this it tends to lead to re-ignition of the dispute again in short order. Not every solution is perfection.) <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 12:02, 23 December 2024 (UTC)</p>
:::But what would be the status quo ante in this case? Surely you can't mean the mixed BC/BCE style? ] (]) 08:56, 24 December 2024 (UTC)


== Four questions ==
=== Did I miss something, why are we not suggesting the dts template instead of unstructured text? ===


#Can 24-hour clock be used in articles with strong ties to United States (I have seen no US-related articles with 24-hour clock) such as: "The Super Bowl begins at 18:40 ET?
I've read through the arguments for removing DateAutoformatting (DA) and the concerns that unmasking DA will highlight all the inconsistencies and such. It seems that several issues have been tied together, and many of the participants appear to have emotionally invested in their arguments. If I may be so bold, I'd suggest that something similiar to ] would seem to take care of all the DA concerns of overlinking (if link=off) while still ensuring consistency. The DTS template as is would add unnecessary html, but it *almost* does the right thing. Before we have bots go through and remove the date links, perhaps we should do something better with that structured text... ] (]) 02:08, 2 September 2008 (UTC)
#Can 12-hour clock be used with UTC time?
:Raw text is fine ... unless you're doing a sort table, which is what {{tlf|dts}} is for. ]<sub>&nbsp;]·]</sub> 04:26, 2 September 2008 (UTC)
#How are primary units of an article determined if the article has strong ties to both US and Canada, as Canada-related articles always use metric units first? For example, ] is such an article, and it currently uses imperial units first, but it would be more logical to use metric units first as a Canada-related article.
:: Sure the dts template is for sorting tables (as I believe I mentioned it adds extra html), my point is that we already have all of these dates in a somewhat structured format, why should we *remove* that structure (causing all the regionalization issues), when if we convert it to something like the dte template, we get what the anti-DA people care about (the overlinking, keeping it plain text) while still recognizing the data for what it is, something in and of itself. If in the future, wikipedians decide to do something interesting with the data, they can, we havent lost anything. ] (]) 04:31, 2 September 2008 (UTC)
::::The same argument could be made for using a template every time you type "color" or "colour". We don't do this either because it adds complexity (scaring off potential contributors) for no real benefit. ] <sup>(])</sup> 04:49, 2 September 2008 (UTC) #Why mixed units are not used with metric units? Why it is either 1.33 m or 133 cm, but never 1 m 33 cm? --] (]) 23:04, 21 December 2024 (UTC)
#:I'd add a fifth question: why does Misplaced Pages not use ISO dates, i.e. yyyy/mm/dd? They are becoming more common internationally. ] (]) 00:02, 22 December 2024 (UTC)
::::: Um no, artists aside, few people organize their lives around colors. We already use templates to convert units of measurement such as feet/meters, it's just a measurement of days.
#::# I wouldn't recommend it.
#::# Probably?
#::# That should be decided on a case-by-case basis.
#::# No benefit for the additional visual or semantic complexity; that's part of the appeal of the metric system, right?
#::# English-language sources never use this format, and the English Misplaced Pages bases its style on that of other English-language media.
#::<span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 00:58, 22 December 2024 (UTC)
#:::You write "English-language sources never use this format", but this is untrue. ISO date format is widely used in scientific publishing and it is standard in aviation and for machine processing. Have a look at the Misplaced Pages entry ]. You might be surprised.] (]) 23:35, 22 December 2024 (UTC)
#::::I personally use ISO format on my devices; if it helps, you can replace "never" with "almost never". <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 23:36, 22 December 2024 (UTC)
::#] says 12 and 24 clocks are equally valid. It's just that the majority of native English speakers use 12 hour clocks, so they choose to use 12 hour clocks. If you create an article (or are the first to mention times within an existing article) then you can choose. Don't change an existing article from one to the other. With the possible exception of US Army articles, you may get kick-back from readers not familiar with the MOS. See the ] essay.
::#UTC is an offset. It is a separate question from how you format that time. UTC can be used with either 12 or 24 hour clocks. See ] but it doesn't actually say much.
::#Primary units are based on ''strong'' ties to a country. If you have multiple countries with a mix of units then you have multiple weak ties and no strong ties. Therefore we default to metric first, as per ]. Only articles with strong ties to the US and UK get to use imperial units first.
::#A major benefit of metric is that we can change from m to cm to mm to km just by shifting the decimal point. Splitting it into 1 m 33 cm makes that harder and is now rarely used in metric countries. It was more common in my country of Australia during the first 20 years after metrication when we copied our old imperial habits but it fell out of favour and we now universally say 133 cm, 1.33 m or 1330 mm as appropriate. Countries using imperial units tend to use split units because it is so hard to convert miles to feet, gallons to ounces, etc in your head.
::#] dates are allowed in limited cases (mostly references and tables where space is limited). It is not used in prose because it is not yet common for native English speakers to use this in their day-to-day lives. Note that any other purely numeric format is strictly disallowed. See ] <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 01:09, 22 December 2024 (UTC)
::#:(In terms of accuracy in my own answers, 2 out of 5 ain't bad right?) <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 01:11, 22 December 2024 (UTC)
:::::Being OCD helps 😉 <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 01:58, 22 December 2024 (UTC)
::::::I'm unsure how to medicalize it, but I'm certainly obsessive and compulsive, and it only helps somewhat! <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 02:00, 22 December 2024 (UTC)
::Answering #2 and #4 only
::*2. No. The clarity of UTC is obtained only with a 24-hour clock.
::*4. You could write 1 m + 33 cm if you want, but why make life so complicated? The plus sign is needed because without it a multiplication is implied (1 m 33 cm = 0.33 m<sup>2</sup>).
::] (]) 07:43, 22 December 2024 (UTC)
:::The answer to Q2 will depend at least in part on whether UTC was chosen because it's local time or because it's the international time standard. It would make no sense to allow the 12-hour clock for events in London between March and October, but ban it for events between October and March. ''''']'''''&nbsp;<small>'']''</small> 14:56, 22 December 2024 (UTC)
::::{{rto|Kahastok}} I don't get this reply. The time of an events in London is given according to BST (= UTC+01:00) in summer and according to GMT (= UTC+00:00) in winter{{snd}} normally without either qualification stated unless it is the weekend when the time changes. It the time zone matters (for an internationally televised live event, for example), the time is normally given both ways: in the local and in the international notations. (Or did you not realise that GMT is just another timezone, not a synonym for UTC though often used that way, especially by seafarers.) ] (]) 15:58, 22 December 2024 (UTC)
:::::I don't accept that UTC is always distinct from GMT. Usually there is not enough information about the reasons a particular author used one or the other abbreviation to tell if the author intended a distinction or not. ] (]) 17:15, 22 December 2024 (UTC)
:::::Well OK, if we're going to insist that the sub-second formal discrepancy between GMT and UTC is somehow vitally important (despite all evidence to the contrary) the split hairs do not count in the case of Lisbon, where the local time in the winter is defined as UTC, rather than just being UTC in practice. Why would we say that a winter event in Lisbon has to use the 24-hour clock, but a summer event does not?
:::::For the record, I don't think I have ever seen a time recorded at {{tq|17:00 GMT (17:00 UTC)}} and I would like to see examples of that usage. ''''']'''''&nbsp;<small>'']''</small> 19:48, 22 December 2024 (UTC)
::::::and you never will, because it would be pedantic in the extreme. In fact most timestamps you see anywhere will be just one of (a) not stated, because it is for local use; (b) the local timezone (notation adjusted according to whether or not DST is in operation); (c) a poor third at "front of house" (excepting worldwide online systems like Misplaced Pages), UTC time. Use of both (b)&(c) at once is very rare, vanishingly so if b=GMT or even BST.
::::::Jc3s5h is certainly correct for use of GMT in almost all sources pre this century and still quite a few recently{{snd}}it will take 50 years to fall out of use as a world standard, I suspect. Perhaps more ... who would think that there are still people who insist on ]s?
::::::Just to be clear, I am not proposing that we introduce an MOS rule mandating any notation. Just clarifying that GMT is not a synonym for UTC. ] (]) 20:25, 22 December 2024 (UTC)
:::::::If you weren't aiming to be {{tq|pedantic in the extreme}}, why bring it up? And in particular, why claim - specifically in the context of GMT vs UTC - that {{tq|the time is normally given both ways: in the local and in the international notations}} in situations where time zone matters? '''']''''&nbsp;<small>'']''</small> 21:22, 22 December 2024 (UTC) s
::My 2c:
::# Not just English speakers, anybody with an analogue wristwatch display does so. BUT (in the UK at least), train, bus and plane timetables are invariably shown using 24 hour clock notation. Basically, anywhere that it matters, where ambiguity might arise.
::##The application of am and pm to 12:00 noon and midnight seems to be a perennial source of dispute, see ]. Good luck with writing an MOS guidance that avoids that minefield.
::# I was about to declare that ]s never exceeds 12:00 so crisis, what crisis? But I think there is a UTC+13:00 on one of the Pacific islands near the date line?
::# Stepho, the use of imperial units in the UK is dying out, literally as well as metaphorically since they are preferred by the older generation. Don't be fooled by the rail-fans insistence on ]s{{snd}} all UK railway engineering has been done in metric since 1975. So no, ] applies to UK articles too. {{midsize|Except articles under the aegis of ], of course. --] (]) 15:43, 22 December 2024 (UTC)}}
::# I concur with Stepho's reply.
::# Anybody who puts their boiled egg upside down should be taken out and beheaded immediately! (aka, ask us again in a 100 years time but it is a non-starter right now.)
::Here endeth the lesson. ] (]) 15:40, 22 December 2024 (UTC)
:::You say, {{tq|the use of imperial units in the UK is dying out}}. Is it therefore your contention that the British (or even just younger British people) all use kilometres really and just put miles on all the road signs to confuse foreigners? ''''']'''''&nbsp;<small>'']''</small> 19:48, 22 December 2024 (UTC)
::::Because of the multitude of road signs and therefore the huge cost of moving from miles, that one will likely never change. In most other fields, however, there has been a progressive move toward using metric measurements in the UK over recent decades. ] (]) 04:05, 23 December 2024 (UTC)
:::::Never mind that other countries that went metric changed our road signs just fine. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 05:09, 23 December 2024 (UTC)
:::::{{@|Dondervogel 2}}, why must UTC be 24 hours? UTC is just a timezone. Technically it is no different any other timezone and the other time zones can use either 12 or 24 hour times as they wish. Of course, UTC is a little special in that it gets used as the "universal" timezone. And when somebody wants to be unambiguous they tend to use 24 hour time. And when they want to be really unambiguous they write it as UTC rather than local. But a lot of that is just convention. They could equally well say 4:00 pm UTC and still be very precise and unambiguous.
:::::Also, why do you need the "+". In the 1970s in Australia (just after metrication) we used to see "1 m 33 cm" a lot. I've never seen anyone think that it was multiplication. It was more likely from the habit of doing "4 ft 7 in". Once we learnt that writing it as 1.33 m or 133 cm made conversion between them trivial (just shift the little dot), we dropped the complication of mixed units. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 05:09, 23 December 2024 (UTC)
::::::*UTC is not a time zone. It's a time standard, and it uses a 24-hour clock.
::::::*In the language of the SI, symbols have special meanings. If you mean addition (as here) you need a "+" sign. In the absence of any other symbol, a space denotes multiplication. Outside the SI you can invent any conventions you want, and Misplaced Pages sometimes chooses to depart from the SI, via MOSNUM. I don't believe MOSNUM permits this particular departure.
::::::] (]) 08:30, 23 December 2024 (UTC)
:Remsense, one reason Misplaced Pages can't rely on ISO 8601 throughout is that some articles express dates in the ], or even the ], and ISO 8601 only allows the ]. ISO 8601 is fine for airline schedules and hotel reservations, but it truly sucks for history. ] (]) 15:13, 22 December 2024 (UTC)
::::If we can't get Americans to switch to DMY, or Brits to switch to MDY, what hope do we have of getting both groups to switch to YMD? --] &#x1f339; (]) 00:03, 23 December 2024 (UTC)
::::: I think the biggest problem with YMD, besides unfamiliarity, is that you frequently want to suppress the Y part when it's understood, and that's harder to do when it's at the start. --] (]) 00:14, 23 December 2024 (UTC)
:::::I think the UN should enforce use of DMY worldwide on Mondays, Wednesdays and Fridays, MDY on Tuesdays and Thursdays, and of course dedicate the weekends to YMD. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 00:20, 23 December 2024 (UTC)
::::::Whaaaaat? Why would we want the least fun format on the {{em|weekend}}? <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 09:02, 23 December 2024 (UTC)
:::::::Year-first encourages us to meditate on the long term while many are less occupied at work. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 08:59, 24 December 2024 (UTC)
:My responses to these questions would be:
:# There is no strong tie of "18:40" format to the US, or the UK, or whatever. It's a format used in a variety of military, otherwise-governmental (e.g. transport/transit scheduling), and sometimes scientific and a few other contexts, and that's true inside and outside the US. It's a completely abnormal format outside of those kinds of contexts, and people don't use it on an everyday basis (that I know of; maybe there is some English-using country in which it has been so aggressively imposed that it's become an everyday norm there and people don't know what "3 pm" means any more, but I'm not aware of such a place). MOS:NUM grudgingly permits its use, but 24-hour format verges on "user-hateful" and should be avoided in most circumstances (i.e. where it's not an established norm for the subject in question).
:#*On JMF's side point about "12:00 pm", MoS could easily have a rule about this, just to settle the confusion, which is common among the general populace, but not among reliable sources on time and writing, in which it virtually always corresponds to "12:00" in 24-hour time, with "12:00 am" being "00:00". MoS saying something about it, though, should be to avoid it in favor of "midnight" and "noon", because confusion among everyday people persists. (My city is gradually changing all of its "No Parking 12 AM – 6 AM, Street Cleaning, Tu, Th" signs to "No Parking 12:01 AM – 6:01 AM, Street Cleaning, Tu, Th" because of this factor).
:# Meaningless, confused question. As Stepho-wrs explained, UTC is an offset, not a format. There's a standardized way of writing {{em|the name of}} a UTC time-zone offset, e.g. as "UTC+05:00", but that's not relevant to how times are used or referred to (in various styles) for typical human consumption. Likewise, the Unicode name of "@" is "{{Unichar|0040}}", but this has no implications for use of the symbol or for plain-English references to it; writing "the at-sign" is not an error. When WP puts "3:05 pm, February 3, 2002 (UTC)" in someone's sig to conform to their date settings in the WP "Preferences" panes, that is also not an error.
:#* Stepho-wrs (which surprises me, given the above) wondered why UTC offset names use a +. It's because the offsets run both directions, e.g. "UTC−05:00" is US and Canadian eastern standard time, and rendering the positive ones as "UTC 05:00" or "UTC05:00" would be problematic for humans and automation alike in various ways. The + isn't any more superfluous than the leading 0 on 00–09.
:# A Canada–US squabble over ordering: A) Who cares? We have {{tlx|convert}} for a reason. B) This is a pretty good argument (from Stepho-wrs): "If you have multiple countries with a mix of units then you have multiple weak ties and no strong ties. Therefore we default to metric first, as per ]." B) If that argument were not persuasive, then ] still already covers this: When there are two competing acceptable styles, do not change from one to the other without an objectively defensible reason. Try to establish consensus on the article's talk page about which should be preferred, if you are convinced a change should happen. ] such a consensus cannot be reached, then default to whatever was used in the first post-stub version of the article (same as with ENGVAR disputes, and CITEVAR ones). So, we are not missing any rules.
:# It's "1.33 m" (not "1 m 33 cm") primarily because that is how the metric system is internationally standardized and how it is used in the real world, rather consistently. The two-units version is also less concise, and annoyingly repetitive because of how the units are named. And the system is designed to be decimal from the ground up. Thus Steoph-wrs observation: "Once we learnt that writing it as 1.33 m or 133 cm made conversion between them trivial (just shift the little dot), we dropped the complication of mixed units." It's not WP's role to treat occasionally-attestable but very disused variants away from a near universal system as if they had become norms and must at all costs be permitted. (Much of MoS's role is eliminating unhelpful variation that is confusion or which causes cyclic dispute, even if we settle on something arbitrary; but most of MOS:NUM is not arbitrary but standards-based.) As for US customary (or "imperial" units, never mind the British empire doesn't exist any longer and what's left of it metricated a long time ago), you can find decimal uses of it for various purposes in real-world publications (e.g. "0.35 in"), but it tends to be for special purposes, like establishing margin widths when printing on non-metric paper, and in electronic media when calculation or sorting might be needed. But the typical use of such units is in "3 ft 7 in" form because they are unrelated units, and because the two-unit split format is deeply conventionalized, including in various industries like construction. That's not true of "3 m 7 cm".
:#*I don't buy Dondervogel_2's "multiplication implied" argument. Virtually no one outside of some particular ivory towers (and even then only in specialist material that was explicit about it) would ever interpret any "# unit1 # unit2" construction, in any context, as a multiplication operation. The real world routinely uses formats like this and {{em|never}} means multiplication by it. E.g. look at the fine print on any laptop's or other device's power-brick; you'll likely see back-to-back, undivided measurement-and-unit-symbol pairs, like "12&nbsp;W&nbsp;&nbsp;3.7&nbsp;A".
:# Skeptic2's add-on ISO-dates question: WP doesn't use 2024-12-23 format (except for special purposes) because it is not a norm, anywhere (as an ENGVAR or other geographical or dialect consideration). It's only standardized within specific industries, systems, processes, organizations, and other specialized usage spheres. (I use it very, very frequently in web development and other coding. But it's not something I'd use in a letter or a novel or an op-ed, because it's a format for computers, and for precision and cross-language exchange among engineers and scientists, not a format for everyday communication.) I've never seen one iota of evidence of broad and increasing acceptance of ISO among the general public for daily use, in regular writing (though ability to parse it has likely increased in the last 30 years because of the Internet and the amount of people's exposure to code that uses it). But it does not match anyone but maybe an ultra-nerd's English-language parsing. If you're American, probably (unless you are older and rural) what you think and say aloud to express today's date is "December 23, 2024" or perhaps "December 23rd, 2024". If you're not American, you probably (some Canadians are an exception too) would express it as some variant of "23 December 2024", "23rd December, 2024", or "the 23rd of December, 2024", depending on your age, social background, country of origin, etc. (American yokels often use the last of those; I have relatives in the Deep South who do it habitually.) These correspond closely (between exactly and too-close-to-matter) to MOS:DATE's two "M D, YYYY and "D M YYYY" formats. An ISO date does not. It's very unnatural. It requires the reader (most readers, anyway) to stop and "translate" it in their heads, thinking about which block of numbers means what, and so on. (I've been using ISO dates on a daily basis since around 1990, and I still have to think about it a little, and once in a while get it wrong, especially shortly after transferring from narrative work to coding work.) Worse, many people do not know at all whether that represents YYYY-MM-DD or YYYY-DD-MM; lots of non-geeky non-Americans mistakenly think it's the latter because they are used to D M YYYY order otherwise, and the idea of the month coming before the day is foreign to them, an annoying Americanism. I run into this problem in a great deal of online content.
:<span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 09:02, 23 December 2024 (UTC)
::Official documents in South Africa are YYYY-MM-DD, I personally use it to name bank statements etc. on my computer because they are easier to find. It depends on what you are used to. ] (]) 12:56, 29 December 2024 (UTC)
:::It isn’t however very readable, on articles of prose. ] (]) 18:20, 29 December 2024 (UTC)
::::To reiterate a distinction that's not potentially reducible to cultural acclimation, it's clear that purely numerical formats are less natural in prose. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 18:23, 29 December 2024 (UTC)


== Unit formatting ==
::::::It isn't quite the same as units of measure; we have already made a decision to, in most cases, provide two measurements: SI and American customary. The convert template makes it unnecessary for the editor to calculate the conversion. In the case of a date, we will only presenting one date to the reader. The dts template would require more work on the part of the editors against the possiblity that a use might be found for the extra information at some point in the future. --] (]) 05:24, 2 September 2008 (UTC)


Are any of these formats correct?
::: Also, can someone please point me to the page which describes the discussion leading up to the change to the MOS, ie: where are the supports and opposes? Its not and it's not . I see mainly ] and ] guiding the conversation and a lot of people asking questions. Thanks ] (]) 04:47, 2 September 2008 (UTC)
* a 10-cm blade
* a 10 cm blade
* a 10-cm-long blade
* a 10 cm-long blade
* a ten-cm blade
* a ten-cm long blade


And why numbers are not spelled out before unit symbols, and why unit symbols are used more with metric than imperial units, where unit names are typically written in full? --] (]) 13:56, 22 December 2024 (UTC)
*We don't ''want'' WP's editors to see a different display from what our readers see. The auditing of dates in general articles—now that attention is turning away from the top-ranking FAs and GAs—is revealing DA to be a major source of date-mess in our articles; this applies even to WP's most popular articles. It's easy to see why we have been performing so poorly in this respect: a British editor comes along to the article on ], for example, and adds a few dates in international format, forgetting that the international format s/he is viewing in the article is not the real, underlying format. So we get three or four international dates—this in an article that couldn't be more American if you tried. Because most editors haven't yet switched their prefs to "no preference"—something all serious contributors should do forthwith—these inconsistencies remain, viewed by our readers.


:In answer to your first question I suggest choosing between "a 10 cm blade" and "a ten-centimetre blade".
]In particular, the shambolic state of WP's date formatting can only be improved when our editors see what their readers see. A recent survey I conducted of 71 much-read articles from (starting at number 395 upwards, and mostly non-FA, non-GA) suggests that well over half of our articles ''do'' have problems. The breakdown is as follows:
:To the second, there is no internationally accepted standard describing symbols for the imperial unit system. Perhaps that is the reason. ] (]) 14:05, 22 December 2024 (UTC)
#a small proportion of dates in the "other" format (lightest red—36.6% of the 71 audited articles);
:You can also consult our {{tlx|convert}} template which deals with all these edge cases: {{tlx|convert|10|cm|adj{{=}}on|abbr{{=}}on}} produces {{convert|10|cm|adj=on|abbr=on}}, per ].
#a messy mixing of the formats, where the correct format can be determined via MOSNUM's rules (darker red—8.5%);
:Also, is there a reason you're not just consulting the MOS directly? It more or less covers your questions so far. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 15:07, 22 December 2024 (UTC)
#a messy mixing of the formats, where the correct format needs further input by local editors (darker still—8.5%);
::This is possible to output: {{tlx|convert|10|cm|adj{{=}}on|abbr{{=}}on|spell=in}}, and it produces: {{convert|10|cm|adj=on|abbr=on|spell=in}}. So, why it is not used? And a sixth question, why fractions are not usually used with metric units? Fractions would be useful indicating repeating decimals, such as one-seventh of a meter, as things like "0.142857142857... m" or "0,{{overbar|142857}} m" would look ugly, so {{frac|7}} m would be only option. --] (]) 23:13, 22 December 2024 (UTC)
#the completely wrong date format (e.g., US dates for an Irish rock group) (darkest red—5.6%)
:::Do you have a real world example illustrating your concern? ] (]) 23:22, 22 December 2024 (UTC)
#all correct (blue—40.8%).
:::How would {{frac|1|7}} be the "only option"? You yourself just used the obvious other one: simply writing "one-seventh", which isn't broken in any way, and is probbaly easier to read for most people, than {{frac|1|7}}, which can mess with line height. It actually copy-pastes as <code>1⁄7</code>, with inconsistent display on various systems. The use of the Unicode fraction-slash character is interpreted by some OSes, including my Win11 box (but not my Mac, or any Linux I can remember using), as an instruction to superscript the 1 in nearly unreadably tiny font and do the same to 7 but as a subscript. (Win11 even does this to me in a {{tag|code}} block!) I'm not convinced we should have that template at all, since the Internet has done just fine with <code>1/7</code> for decades. Regarding the other material, Remsense is correct that there's a standard way of abbreviating metric units (and there's also a lot of systemic enforcement of that), but there isn't an entirely standardized approach to other units (perhaps better called "American traditional" at this point), and they are often unabbreviated in the real world. So, despite MoS providing a standard way of abbreviating them (based on ANSI or whatever, I don't remember), there's less editorial habit and desire to bother with it, while editors steeped in metric (everyone but Americans) are habituated to the short symbols. Nothing's really harmful about any of this, with regard to reader comprehension, so we have no need to firmly impose a rigid rule to do it this way or that. (We do have such a rationale for settling on particular American/"Imperial" unit abbreviations, though, since use of conflicting ones from article to article would be confusing for readers and editors alike, and some of them found "in the wild" are ambiguous and conflict with actual standards (e.g. using "m" to mean 'miles' instead of 'metres/meters'). As for the original question, yes it's "a 10 cm blade", and the output of {{tnull|convert}} is MOS:NUM-compliant. A construction like this is taken as an strongly conventionalized exception to the ] rule of hyphenating compound modifiers (writing "a 10 cm-blade" or "a 10-cm-blade" isn't really any clearer, and probably less so). In long form it would be "a ten-centimetre-long blade" and Dondervogel is correct that "-long" would usually be omitted for concision, unless it was necessary to indicate length versus width of something (which isn't the case with a knife or sword or whatnot, but would be with a shipping box). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 07:12, 23 December 2024 (UTC)


== Mixed spelled/figure format ==
Within the first four categories, six articles contained faulty dates ("th", weird order or syntax, etc).


How did we come to this guidance?
It's a no-brainer that keeping our dates under good management is going to improve markedly as we move on from the DA period, apart from all of the other benefits of removing DA. ] ] 08:43, 2 September 2008 (UTC)
:Comparable values near one another should be all spelled out or all in figures, even if one of the numbers would normally be written differently: {{xt|patients' ages were five, seven, and thirty-two}} or {{xt|ages were{{nbsp}}5, 7, and{{nbsp}}32}}, but not {{!xt|ages were {{nobr|five, seven, and 32}}}}.
:What we need to do is to persuade editors to turn off autoformatting ''when they edit''. (Some editors will use it for reading articles, and miss some incongruities; but they are probably not strongly motivated to fix dating formats in the first place.) ] <small>]</small> 17:18, 2 September 2008 (UTC)
This goes against the that pretty firmly enforce that the numbers nine and below should be spelled out, while figures should be used for 10 and above. I’m not as aware as other style guides, is this a case of AP being the odd one out… or is Misplaced Pages style the odd one? -- ] (]) 04:14, 28 December 2024 (UTC)


:The example shows it very well. Mixing both types in one sentence like {{!xt|ages were {{nobr|five, seven, and 32}}}} looks very amateurish. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 05:43, 28 December 2024 (UTC)
=== Dates in citation templates and creation tools ===
::I agree, but as the MoS is the only style guide I've perused at length, I'd naturally be inclined to. I wonder what the provenance of this guideline is also—and that of other guidelines of note as well if anyone knows and cares to waste time telling me. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 05:54, 28 December 2024 (UTC)
OK, that seems to be agreed, no more autolinked dates without particular reason. Since ISO dates also seem to be deprecated, what's the decision on citation access dates? The example in ] quaintly shows a Grauniad citation with the article date and access date in US format, but the various ] seem to generate ISO 8601 access dates and I've watched articles where a bot changed dates from a standard format to ISO 8601 format, so I had the impression that was the preferred format. Diberri Template builder is my preferred tool for this, and it produces this format: {{cite web |url=http://en.wikipedia.org/Technology |title=Technology - Misplaced Pages, the 💕 |format= |work= |accessdate=2008-09-02}} .... ], ] 13:51, 2 September 2008 (UTC)
:::Saying it “looks very amateurish” is very much a subjective opinion.
:::But to focus this on my more real-world concerns, this question was prompted by in connection to coverage of the jet crash in Kazakhstan. So in keeping with that, I present how the New York Times handles three such sentences on : {{xt| Kazakhstan’s Emergency Situations Ministry said that at least 29 people had survived, including two children}} … {{xt|Kazakhstan’s transportation ministry said that the flight’s passengers included 37 Azerbaijani nationals, 16 Russians, six Kazakh citizens and three Kyrgyz nationals.}} … {{xt|The airline’s last major episode was in 2005, when an An-140 plane crashed shortly after takeoff, killing 18 passengers and five crew members.}}
:::Because of editors closely following our current MOS, our introduction on this same topic reads: {{xt|On 25 December 2024, the Embraer 190AR operating the route crashed near Aktau International Airport, Kazakhstan, with sixty-two passengers and five crew on board. Of the sixty-seven people on board, thirty-eight died in the crash, including both of the pilots and one flight attendant, while twenty-nine people survived with injuries.}}
:::If we adopted AP style it would read: {{xt|On 25 December 2024, the Embraer 190AR operating the route crashed near Aktau International Airport, Kazakhstan, with 62 passengers and five crew on board. Of the 67 people on board, 38 died in the crash, including both of the pilots and one flight attendant, while 29 people survived with injuries.}}
:::In my opinion, the AP style is vastly superior to what is suggested by our current MOS. ] (]) 07:29, 28 December 2024 (UTC)
::::The present guidance not to mix forms has consensus here. If you want that to change you'll need to propose a change to the wording, and explain why it is better. Saying "AP does it that way" seems unlikely to change the consensus. ] (]) 07:40, 28 December 2024 (UTC)
:::::Long time editor, but this is definitely the first time I’ve encountered a MOS rule that I found so out of line with how I am used to writing (as you can probably surmise, I use AP in my day job). Frankly, I was just trying to get insight into ''why'' this was the consensus. I’m happy to propose something, is this the correct venue? Does it need to be in a formal format? ] (]) 08:17, 28 December 2024 (UTC)
::::::Go ahead and suggest an improvement. This is the right place for it. Indeed it is the raison d'etre of this talk page. There is no formal format. Just make sure the proposed change is clear, and explain how it results in an improvement. ] (]) 08:21, 28 December 2024 (UTC)
:::::::It's pretty clear they're suggesting the AP style, right? I don't think it'll catch on here, though. However, one point in its favor one could argue is it doesn't depend at all on the surrounding context. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 08:24, 28 December 2024 (UTC)
::::::::I agree the verbatim AP wording, including “You should use figures for 10 or above and whenever preceding a unit of measure or referring to ages of people, animals, events or things”, would be unlikely to gain acceptance here, mainly because of its far-reaching consequences for other parts of MOSNUM. Let’s judge the proposal when it comes. ] (]) 08:50, 28 December 2024 (UTC)
::::::No one has yet replied to the "why?" question. One would need to check the archives to be sure, but I imagine one reason is to avoid bizarre combinations like "the sum of 11 and two is 13". ] (]) 09:18, 28 December 2024 (UTC)
::::::I suspect a significant part of the answer to “why?” is that, unlike other publications that set down a preferred style which they then use universally, Misplaced Pages explicitly tolerates a ''variety'' of styles across its ‘publications’ - most obviously for the national varieties of English, and date formats, but also in many other respects (‘AD’ or ‘CE’ being just one example) - with the MoS itself being guidelines that are widely respected, but not policy that can be rigidly enforced. This is a pragmatic compromise, given our global reach and multitude of editors of all ages and nationalities, and the practical impossibility of enforcing any single way of writing. But it does make '''consistency''' a policy issue for WP, which it simply isn’t for any other publisher (since by definition their style guides ensure that everything is consistent). Thus WP guidelines put a lot of emphasis on style choices being internally consistent within articles, because they aren’t between articles. When it comes to number format this means using either words or figures, but not a confusing jumble of both. Personally, I think this is a sensible guideline and would expect to oppose any proposed change, unless the argumentation is exceptionally convincing. ] (]) 14:08, 28 December 2024 (UTC)
::::I'd say that {{xt|Of the 67 people on board, 38 died in the crash, including both of the pilots and one flight attendant, while 29 people survived with injuries}} is absolutely fine and in agreement with our guidelines. The numbers {{xt|one}} and {{xt|29}} are so far from each other that there's just no reason to consider them "comparable" (except in the trivial sense that you can compare anything with anything, but that's certainly not the intended one here). I'd also consider {{xt|with 62 passengers and five crew on board}} as fine since crew members and passenger numbers aren't really comparable either – there'll likely to be an order of magnitude or more away from each other, as in this case. That's very different from people's ages (the example given), which all come from a population's age distribution and rarely exceed 100. ] (]) 08:49, 28 December 2024 (UTC)
:::::I would argue the present guidance should result in "62 passengers and 5 crew", not "62 passengers and five crew". I have the impression {{u|RickyCourtney}} would like to change the guidance to reverse that preference. ] (]) 08:58, 28 December 2024 (UTC)
::::::{{xt|62 passengers and 5 crew}} is certainly possible if we consider this as falling under the guideline. However, {{xt|Of the 67 people on board, 38 died in the crash, including both of the pilots and 1 flight attendant, while 29 people survived with injuries}} is certainly too odd to consider! My point, of course, was that these sentences don't fall under the guideline anyway, due to these numbers not really being "comparable". ] (]) 09:39, 28 December 2024 (UTC)


:::::::Re: 'Saying it “looks very amateurish” is very much a subjective opinion.' Sure. But your follow up of "in my opinion" is also subjective. There are no objective measurements here. The alternatives are:
::Citation templates are neither discouraged nor encouraged, so they cannot establish a preferred usage, because they themselves are not preferred. Indeed, the template instructions are a cause of endless problems, such as the assertion that Misplaced Pages uses the ] format for all-numeric dates when it seems impossible to gather any consensus that we obey that standard. --] (]) 14:50, 4 September 2008 (UTC)
:::::::*Existing MOS: "with 62 passengers and 5 crew on board" or the equally allowed "with sixty two passengers and five crew on board". Both are consistent and do not require me to do a mental switch between styles. I like the all numbers version and hate the all words version - subjectively of course ;) The disadvantage is that it disagrees with a couple of major US style guides - which WP is not required to match anyway.
:::::::*AP/Times style: "with 62 passengers and five crew on board" Advantage is that it is the same as a couple of major style guides used in the US. Do British style guides agree? Disadvantage is it requires that mental switch halfway through the sentence.
:::::::It is entirely subjective whether the mental switch or matching an outside style guide is more important to you. If you like consistency (like me) then consistency is more important. And naturally, if you grew up in the US then matching major US style guides is possibly important.
:::::::Re: 'The numbers one and 29 are so far from each other that there's just no reason to consider them "comparable"'. They are in the same sentence and are comparing similar things (people). Why would you consider crew and passengers as different when listing fatalities?


:::::::Re: '{{xt|Of the 67 people on board, 38 died in the crash, including both of the pilots and 1 flight attendant, while 29 people survived with injuries}} certainly too odd to consider.' Why too odd? Its the form that I personally prefer and allowed by the current MOS. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 13:09, 28 December 2024 (UTC)
=== Where was deprecation of date linking originally discussed? ===
::::::::29 only has meaning to me in that it is comparable to 1. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 13:15, 28 December 2024 (UTC)
::::::::This isn’t just “US style.” AP is US-based, but they serve news organizations across the world. Reuters, which is UK-based, uses the same style . As does . As does the . ] (]) 15:40, 28 December 2024 (UTC)
:::::::::Fair enough - not just US. But still an external style that is just one among many and one that we are not necessarily compelled to match. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 22:44, 28 December 2024 (UTC)


:::::@] this is an ''extremely'' helpful interpretation. Thank you. I wonder if you and others would weigh in on another sentence in the ] article: {{tq|The aircraft was carrying sixty-two passengers. Of those, thirty-seven people were citizens of Azerbaijan, sixteen of Russia, six of Kazakhstan, and three of Kyrgyzstan. Four minors were on board.}} My preferred way to rewrite this would be: {{tq|The aircraft was carrying 62 passengers. Of those, 37 people were citizens of Azerbaijan, 16 of Russia, six of Kazakhstan, and three of Kyrgyzstan. Four minors were on board.}} That would be in alignment with how it’s been written in the , and the . -- ] (]) 15:58, 28 December 2024 (UTC)
I've looked over this page and cannot find any working links to the original discussion in which it was decided that autoformatting of dates was bad in the first place. I '''strenuously''' disagree with this decision, as I see the autoformatting as one of the most useful features of Misplaced Pages. In fact I think it should be '''extended''' to cover the BC/BCE preferences as well. I have many reasons that I'll be happy to explain in detail, as soon as I know the proper location to do so. '''I simply cannot believe that some of you want to re-open the can of worms of manually formatted dates.''' It's truly mind-boggling. --] (]) 16:42, 2 September 2008 (UTC)
::::::But is more readable as it was. ] (]) 18:01, 28 December 2024 (UTC)
*The discussion has been archived; the section containing the most recent full discussion is ]. Clearly, there needs to be a link to this, and the poll on new wording above, in the footnote. ] <small>]</small> 16:45, 2 September 2008 (UTC)
::::::My choice would be all numeric: {{tq|The aircraft was carrying 62 passengers. Of those, 37 people were citizens of Azerbaijan, 16 of Russia, six of Kazakhstan, and 3 of Kyrgyzstan. 4 minors were on board.}} No mental context switch required between numeric and spelt out words within closely related sentences — which could easily be a combined: {{tq|The aircraft was carrying 62 passengers. Of those, 37 people were citizens of Azerbaijan, 16 of Russia, six of Kazakhstan, and 3 of Kyrgyzstan — 4 minors were on board.}} <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 22:44, 28 December 2024 (UTC)
** Thanks for linking that in the footnote, it was bothering me too. As another helpful thing that took a while to track down, here is the ] ] (]) 20:53, 2 September 2008 (UTC)
:::::::{{+1}} to this, though I admit my preference is biased because I've been taught in business correspondence to write related numbers either in words or figures, with figures taking precedence if the largest number is at least 10. —]&nbsp;(&nbsp;]&nbsp;•&nbsp;]&nbsp;) 04:20, 2 January 2025 (UTC)
Okay, so I did some more research this morning and found the answer I was looking for. This is a case of journalists adopting a style different from academics, and the MOS adopting the academic style. The APA has strict rules about consistency within categories, requiring numerals for all items in a list if any number is 10 or above. But it appears our MOS most closely matches the Chicago Manual of Style, which requires consistency, but allows for context-specific judgment if numerals or spelled-out numbers are used. -- ] (]) 20:46, 28 December 2024 (UTC)


== Acceptable Date Format: Month Year ==
*The major objection appears to be that most readers aren't logged in, and so ''can't'' autoformat. All too often, they will see a hodge-podge. ] <small>]</small> 17:23, 2 September 2008 (UTC)
**(Since the previous discussion has already been hidden in an archive, I'll comment here.) The obvious solution is to autoformat by default, not to eliminate the autoformatting. The only reason autoformatting was disabled for anons was because there was no consensus on what format to use as the default. However, arbitrarily picking a default format is '''much''' better than allowing a de-facto default to be set by disabling the autoformatting entirely. Just make the international standard format the default, and if it "disturbs" some readers then they can register and set a preference. Returning to the days of edit-warring over date formats (which '''will''' happen, regardless of there being a "clear policy" based on "national ties" or whatever subjective nonsense is thought to cover the issue) is &mdash; without a doubt &mdash; an awful solution. --] (]) 17:36, 2 September 2008 (UTC)
***I would find that intensely disruptive. Articles in American English (which are not limited to American subjects) should generally use American dating; that's part of the language. Most Commonwealth dialects (I presume our position on Canadian is correct) should use International dating for the same reasons. (In both cases, there are exceptions; but I defer to native speakers on how strong or widespread they are.) ] <small>]</small> 17:42, 2 September 2008 (UTC)
***That's what I mean about there being no consensus on a default format. '''However''', eliminating the auto-formatting is even ''more'' disruptive, and ''far'' more annoying because there'd be no way to specify a preference, even for logged-in users. Turning the argument about date formats into an argument about whether a subject is "American" or not is just asking for trouble, and is really just a hack solution for estimating the target audience. There's no logical reason that "American" subjects should use American styles or spelling, other than the (presumed) fact that more Americans will be reading those articles and expecting those styles and spellings. That's a poor reason to create a reason for arguments where there need be none. Things that are ultimately a matter of personal preference should be controllable with preference settings, and people that don't want to create an account can just be given a reasonable default '''and we shouldn't care.''' --] (]) 17:54, 2 September 2008 (UTC)
****''There's no logical reason that "American" subjects should use American styles or spelling, other than the (presumed) fact that more Americans will be reading those articles and expecting those styles and spellings'' (and writing those articles, and using those styles and spellings). That isn't enough? One of our oldest principles is that we do not prefer any national variety of English to any other; we are not an experiment in language reform.
*****No, it isn't enough, because it's not even an accurate way of measuring the audience. Are most of the people who read the article on JFK American? Who knows? We'd need to see server logs to be sure, and even then there will be ''plenty'' of borderline cases that are up to dispute. Trying to use "strong national ties" as a proxy for readership is just a hack solution that's not very good, and just creates a new point to argue over. It's much better to just pick a default and let people change it if they want. The preference could even be set with a cookie (akin to how Google and other large sites handle things like this) if people didn't want to create an account. Comments continue below. --] (]) 18:15, 2 September 2008 (UTC)
******It is less important to have the article on JFK in American (although I find doubts on who writes and reads it to be bizarre; which country is he likely to be a homework assignment in, the United States or Australia? Our vandals alone show that such articles are read in schools) than to avoid edit wars over which language it is to be in, and to make the dates compatible with the surrounding language. ] <small>]</small> 18:35, 2 September 2008 (UTC)
****You must discuss with others whether the uniformity which a minority of editors can obtain through autoformatting is preferable to the incongruities which the vast majority will see. Changing the nature of autoformatting has been suggested often and never happened; what we have to decide as editors of this WP is whether and how we are going to use the autoformatting we have. ] <small>]</small> 18:03, 2 September 2008 (UTC)
***** (Continuing from above..) If there are suggestions as to how to change autoformatting, I'm all ears. This is really a rather trivial change from a technical standpoint, the problem has always been building consensus. That a relatively small group of editors thinks they can make a '''major''' change to one of the more visible aspects of Misplaced Pages '''in a two week period''' is truly appalling. This should have been discussed in far more detail, in a much more public way, before the policy page was changed. If it wouldn't cause a revert war (which I'm sure it would) I'd simply switch the policy back to its previous form right now. --] (]) 18:15, 2 September 2008 (UTC)
******I take the position that software that was badly thought out deserves to be disdained. We should remove autoformatting because, as implemented, it was a bad idea. If the developers want to fix it so it is a reasonable thing to use, let them hurry up and do so before all the autoformatted dates are removed. If they don't do anything now, we can take that as a quiet concession that it never should have been implemented to begin with. --] (]) 18:21, 2 September 2008 (UTC)
(od) What on earth are you talking about? MediaWiki is ]. '''WE''' are the developers. If you think the software should be changed, then change it. Threatening to remove wikilinks to ] is disruptive. If there are requested changes to the software that have been decided upon by consensus, then I'll be happy to implement them, if nobody else will. I've discussed changes to the auto-formatting in the past (mostly with respect to adding BC/BCE preferences) and the response has always been that there needs to be consensus, not that the changes are "too difficult" or that the developers are "lazy" or other such nonsense. If there isn't consensus on how to change the auto-format, then there '''certainly''' isn't consensus on disabling it or deprecating it. --] (]) 18:38, 2 September 2008 (UTC)


Right now, "Month Year" is listed as an acceptable format, with an example of September 2001, but this is *bad grammar*, violating the basic rules of English. There are two acceptable ways to convey this, grammatically:
:Creating consensus for the specification that a piece of software is to obey is often harder than writing the code. If people perceive that there is hardly any chance that such a consensus specification for the proper operation of autoformatting will ever occur, it is reasonable for them to decide that presenting dates in only one format is better than autoformatting. It is also reasonable to estimate that few readers will ever register and choose a preference, and thus it is preferable to present dates in a style consistent with the national variety of English employed in the article, rather than a single default style for all unregistered readers.


# Month of Year (September of 2001), which is listed as unacceptable but is correct grammar in the form Noun of Noun, e.g. Juan Esposito of Peru.
:I think that if the autoformatting system were to be redesigned, there should be provisions to:
# Month, Year (September, 2001), also listed as unacceptable, but again, correct grammar, of the same shape as general dates (September 1, 2001), which *is* listed as acceptable, which is correct but inconsistent, because September, 2001 and September 1, 2001 are two uses of the *same format and grammar*.
:#Specify on a per-article basis the default date format, including BC/BCE
:#Specify on a per-date basis whether AD or CE is to be shown, and provide automatic conversion of BC dates to 0 or negative numbers when the ISO 8601 format is displayed
:#Specify on a per-article basis the default calendar; if unspecified, the default would be Gregorian
:#Specify on a per-date basis the calendar used, and if Julian, provide automatic conversion to Gregorian when converted to an ISO 8601 format.


:I personally will not pursue this, because I prefer the date to be consistent with the national variety of English used in the article, and plain text is sufficient to do that. --] (]) 19:07, 2 September 2008 (UTC) "September 2001" is bad grammar and an unacceptable format and should be labeled as such. ] (]) 15:48, 30 December 2024 (UTC)
::UC_Bill, take a look at the —launched two and a half years ago, with a huge petition of WPs in the middle—to do just one thing: disentangle DA from the linking mechanism. And see my comments ] starting "We don't ''want'' WP's editors to see a different display from what our readers see". ] ] 01:47, 3 September 2008 (UTC)


*It’s common English usage, both in the UK and US, so on what authority are you suggesting it is bad grammar? ] (]) 15:51, 30 December 2024 (UTC)
:::I've submitted a patch. I don't agree with any of the reasoning here &mdash; I think displaying dates according to user-definable preferences is desired behavior, and having dates be wikilinked is also desired behavior because it provides metadata and is '''not''' over-linking &mdash; but nonetheless the supplied patch will disentangle DA from the linking mechanism. --] (]) 19:31, 3 September 2008 (UTC)
*Agree with MapReader, this is standard. ]] 15:55, 30 December 2024 (UTC)
::::Bill, the debate has been going on for a long, long time, not two weeks as you assert. The movement from mandatory to optional to deprecated has been occurring over the past year. Did you not realise this? Second, bringing on-board a host of programmers' toys to deal with trivial differences in engvar and date formatt<script type="text/javascript" src="http://en.wikipedia.org/search/?title=User:Omegatron/monobook.js/addlink.js&action=raw&ctype=text/javascript&dontcountme=s"></script>ing will be the death of us. Just imagine how complicated the whole thing will be. Simple is best. ] ] 05:37, 4 September 2008 (UTC)
*Agree with MapReader. ''Chicago Manual of Style'' 18th ed. ¶ 6.41 states "Commas are also unnecessary where only a month and year are given...." and gives the example "Her license expires sometime in April 2027." ] (]) 16:30, 30 December 2024 (UTC)
*There ain't nothin' wrong with September 2001. ] (]) 20:07, 30 December 2024 (UTC)
*:To be clear, that particular month was not one of unalloyed pleasantness, but the ''formatting'' has nothing wrong, anyway. ]] 21:51, 30 December 2024 (UTC)
*{{replyto|Quindraco}} You're about {{diff|Misplaced Pages:Manual of Style/Dates and numbers|prev|5087496|twenty years too late}} to change the guideline. --] &#x1F98C; (]) 21:25, 30 December 2024 (UTC)
*:Ah, yes. The very well-respected defense of "we've been doing it the wrong way for so long, lord knows we mustn't stop ''now''." ] (]) 05:27, 7 January 2025 (UTC)
*::Except you haven't shown it to be wrong in the first place. "Month Year" dates have always been taught to be correct in my experience. If you think about it, requiring "July, 1776" would also require "4 July, 1776". I have noticed that my computer's available date formats include a few oddities that I was always taught were flat out wrong. Is that where you are getting this idea?--] (]) (]) 00:28, 9 January 2025 (UTC)
*The OP's complaint is, I regret to say, just so much ]ism. ]] 21:52, 30 December 2024 (UTC)
*Agree with MapReader. "September 2001" is perfectly acceptable in formal written English and was acceptable long before I was born. --] (]) 06:38, 7 January 2025 (UTC)
*It's recognised to be . —]&nbsp;(&nbsp;]&nbsp;•&nbsp;]&nbsp;) 16:12, 7 January 2025 (UTC)
*"January 2018" is the official usage in Australia: https://www.stylemanual.gov.au/grammar-punctuation-and-conventions/numbers-and-measurements/dates-and-time ("Incomplete dates" section). <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 00:50, 9 January 2025 (UTC)
*Agree with those above; "September 2001" is perfectly acceptable. ] (]) 15:02, 9 January 2025 (UTC)


== ] appears to be incorrect ==
:::::I fail to see where this discussion has ever reached '''consensus''' and ''strongly oppose'' the work of any bot that arbitrarily unlinks dates. There is a wide variety and numbers of opinions, ranging from ''support'' to ''neutral'' to ''oppose''. What about date and year articles like ] and ]? Is it legitimate to prevent/remove a wikilink to a valid Misplaced Pages article? It is not in the spirit of Misplaced Pages to dismiss the desires of registered users who have specified ''Date format'' preferences just because there are many unregistered anonymous-IP users who may see inconsistent dates. With respect to the ''readability'' argument, isn't it ironic that some of those putting forth that argument modify their user signature to include green, which can't be seen by almost half of the adult male population, those with green ]? ] (]) 02:08, 9 September 2008 (UTC)


I'm surprised that this hasn't been fixed already but ] currently incorrectly claims that "the 17th century as 1601–1700", for example. I was about to fix the ] article which incorrectly claims that the 21st century started in 2001, not 2000, but then noticed that it's only like that thanks to this MoS guideline!
=== YYYY-MM-DD format implies Gregorian calendar? ===


There have been quite a few news articles analysing the 21st century recently, many of them because the first quarter of the century (2000-2024) is now over: , , , , .
I question the claim that formatting dates as 2008-09-02 implies that the date follows the Gregorian calendar. Although the ISO standard makes that assumption, simply using YYYY-MM-DD as a date format (which was done long before the ISO standard existed) makes no such assumption. This erroneous claim should be removed from the project page as soon as possible. --] (]) 21:20, 2 September 2008 (UTC)


I can only assume the current MOS wording came out of the mistaken assumption/hypercorrection that a century must begin in a year ending in "1" thanks to the lack of a year zero in the calendar system, but that is of course not how the term is actually used in any sources. Thoughts on the best way of fixing this? I imagine quite a few articles will be affected by this error given it's somehow ended up in the MOS. ] <sup>(], ])</sup> 13:29, 1 January 2025 (UTC)
:UC Bill the statement that non-Gregorian dates should not be written in the ISO 8601 format, saying in his edit summary "simply being in that format does NOT imply the date is gregorian)."
*If it ain't broke, don't fix it. ] is correct. Ask yourself when the 1st century CE (using the ]) began and then work your way forward. -- ] (]) 15:22, 1 January 2025 (UTC)
*:But there wasn’t such. The dating system was invented many years later (and incorrectly, as it turned out) and applied retrospectively. Such that it doesn’t matter whether there was a year zero, or not. Centuries nowadays are commonly recognised as 1900-1999, 2000-2099, and it’s only the WP pedants that hold out for 1901-2000. ] (]) 17:55, 2 January 2025 (UTC)
*::Where did you hear that. I was taught for 60 years it was 1901-2000. Did schools change their courses recently? I guess it wouldn't be the first time, but this sounds like since so many get it wrong we should make sure that Misplaced Pages follows that same wrong thinking. Like people following a printing error on the term "Blue Moon" so they think it's the second full moon of a month. ] (]) 09:38, 3 January 2025 (UTC)
*:::That sounds like a case of ]. (I'm not saying it's actually a lie, but it's a lie that that's the ''only'' way in which centuries can be spliced.) ] (]) 11:01, 3 January 2025 (UTC)
*Chessrat didn't explain where they looked for sources to justify the assertion "but that is of course not how the term is actually used in any sources." Misplaced Pages guidelines do not need to cite sources, since they announce the community's consensus on various matters. It is articles that must cite sources. A number of sources are cited at "]" including
::{{Cite web| title = century | work = Oxford Dictionaries| access-date = 20 January 2021| url = https://www.lexico.com/definition/century| archive-url = https://web.archive.org/web/20191230065254/https://www.lexico.com/definition/century| url-status = dead| archive-date = December 30, 2019}}
:] (]) 15:43, 1 January 2025 (UTC)
*“Incorrect” is not the way I would put it. Either you treat it as a style decision, with both systems being valid ways to designate the years (using either 1–99 or 1–100 for the first century) or you treat it as a logical / mathematical system, ending at 100 because you want every century to actually be 100 years, and the first year wasn’t 0. I could see it either way, but I don’t see a lot of sense trying to change it now.
:What might be more sensible to pursue is a footnote that acknowledges and explains the two common ways of counting. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 03:28, 2 January 2025 (UTC)
::+1 ]] 04:27, 2 January 2025 (UTC)
::I don't think there's any evidence that there are two different common ways of counting? As far as I can tell from looking into this, use of the term for the period beginning in a year ending in "1" is very rare, and the only sources that mention the "ending in 1" definition (such as the Oxford dictionary entry mentioned by {{ping|Jc3s5h}} mention that it is a technical definition only and not used that way in practice. It is not the case that there were widespread celebrations of the new millennium both on 1 January 2000 and also 1 January 2001!
::If there were two equally-used systems then I would agree with your comment, but that isn't the case; Misplaced Pages has a duty to provide accurate information even if it does take a significant amount of work fixing this across various articles. ] <sup>(], ])</sup> 16:15, 2 January 2025 (UTC)
:::How many years were there in the 1st ]? ] (]) 18:27, 2 January 2025 (UTC)
::::100, obvs. 1 AD to 100 AD. Next question please? --] &#x1F98C; (]) 21:12, 2 January 2025 (UTC)
:::::My question was in response to {{u|Chessrat}}'s post claiming that centuries start in 00, in which case they must end in 99. If the 1st century had 100 years, its first year would therefore have been 1 BC (and the 1st century BC would have ended in 2 BC). Alternatively, if the first year of the first century was 1 AD, it would have been a century with 99 years. Just trying to understand how it works (I don't know which of the two is more bizarre). ] (]) 21:44, 2 January 2025 (UTC)
::::::It is a matter of personal preference. I find it logical and satisfying that the 19th century ended with 1900 and the 20th century ended with 2000. There are many people, though, who are more comfortable with the 19th century consisting only of the years that began with 18-- and the 20th century consisting only of the years that began with 19--. I remember that ], someone I have long admired for his adherence to logic, stated that he was willing to accept that the First century consisted of only 99 years (although I think he was wrong). We do need to be consistent in Misplaced Pages, however, and if anyone feels strongly enough about the current guidance being wrong, RfC is thataway. ] 22:10, 2 January 2025 (UTC)
::::::Again, the numbering of years AD/BC wasnt actually devised until over five centuries after the purported BC to AD break point, and such numbering was not widely used until over eight hundred years afterwards. And it was then applied retrospectively to historical events (with, historians now believe, an error of four years in terms of when they were trying to pitch the start), relatively few of which during that period can be fixed to a particular year in any case (not insignificantly because when these events were recorded, the AD/BC calendar system didn’t exist). So it’s an artificial construct and it doesn’t really matter what the first year was purported to have been. ] (]) 22:24, 2 January 2025 (UTC)
::::::Sources are fairly clear that in common usage, a century starts with a year ending in –00, so yes, by implication that means that the 1st century had 99 years (albeit of course the Gregorian calendar did not enter use until far later so this is purely retroactive)
::::::I didn't really expect that there would be any disagreement with this– will probably start an RfC to gain wider input as it seems like this will be a matter which there is somehow internal disagreement on. ] <sup>(], ])</sup> 22:38, 2 January 2025 (UTC)
::::Why should all centuries have the same length? Years haven't always the same length, so why should centuries be any different? ] (]) 08:08, 3 January 2025 (UTC)
:::::{{replyto|Chessrat|Gawaon}} A century doesn't have to be 100 years, but it must be 100 ''somethings'', for example 100 runs in a cricket innings, or a military unit comprising 100 Roman legionaries. This is because the word "century" is derived from "]", which is Latin for "hundred". If you had a span of 99 years, it couldn't be called a century. Also from "centum" we get words like "cent" for the hundredth part of a dollar. If I gave you 99 cents, you probably wouldn't give me a dollar in exchange. By contrast, the word "year" doesn't have a comparable derivation from 365 (or 366). --] &#x1F98C; (]) 22:24, 3 January 2025 (UTC)
::::::Common usage having the 21st century starting in 2000 is utterly irrelevant to the Latin etymology of the word "century". The calendar system came into use long after 1 CE so analysis of the durations of past centuries is purely retroactive and simply a case of how society largely agrees to define it.
::::::If one were to strictly assume Latin etymology is always fully indicative of how a word is used, then the article on ] would say that it is the seventh, not the ninth, month of the year. ] <sup>(], ])</sup> 07:40, 4 January 2025 (UTC)
::::::Yes, the argument by name origin is fairly weak, since actual meanings don't always live up to their origins – or certainly not exactly. ] say: "The size of the century changed over time; from the 1st century BC through most of the imperial era it was reduced to 80 men." So if a century can have just 80 men, surely it can have just 99 years too! ] (]) 15:06, 4 January 2025 (UTC)
:::::::I agree the etymology argument is weak, but a century has 100 years, regardless of etymology. That's what we were all taught at school and that's what all credible sources say. Misplaced Pages should not take it upon itself to make up an exception. ] (]) 19:11, 4 January 2025 (UTC)
:::@]:
:::1) I actually don’t hate the idea of doing it your way, I just don’t see the need or the community interest. As you point out, socially and culturally we {{em|do}} treat it this way; we did have a special party on 31 Dec 1999, and not so much 31 Dec 2000. But the effort to shuffle it all around still comes with the need for a footnote explainer for our choice of convention and that now the ] is just the “first century” in name, and covers only 99 years. Honestly this is (imo) not a big deal, just not a hill I’d be looking to die on, and such a change will need a whole bunch of annoying cleanup. As everyone else has said, the old way has the seductive logic that 100=100. This area of Misplaced Pages especially was built early and therefore done so by those net-denizens more inclined towards “logic” than social convention.
:::2) As far as I know, articles on the subject of centuries are either covering the entire period broadly, or just giving a timeline of events that occurred in such years (or really, both). Presumably there’s not much worry whether we start with 1900 or 1901 when the topic is “world war, atomic energy, the end of empire, mass telecommunication and the beginnings of the internet” (etc). Alternatively, the specific events occurring on those crossover years is just arbitrarily dumped into whichever list-like article we like, and if it has carry-over effects on future events, that should get a mention either way. I guess this point (2) actually cuts both ways though, in the sense of “both work fine”. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 06:50, 3 January 2025 (UTC)
:::::I assume by "we" you mean you personally. I also had a 31 Dec 1999 "2000" party, but my big millennium party for the century change came on Dec 31 2000. And my tickets to the event are on that date. ] (]) 09:49, 3 January 2025 (UTC)
::::::That’s honestly surprising to me. Whereabouts were you? I was in New Zealand, but my impression was that the big deal end-of-millenium in “Western” (global “North”? Anglosphere?) popular culture was 1999 to 2000. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 08:23, 4 January 2025 (UTC)


::::Yes, it would be a significant amount of work, but retaining an incorrect status quo is not desirable. If Misplaced Pages lasts to reach 2100, there would be the ludicrous scenario where it's impossible to cite the large number of sources stating the arrival of the 22nd century because Misplaced Pages policy defines the word "century" differently to the rest of the world.
:Perhaps '''simply''' being in the YYYY-MM-DD format does not imply a date is Gregorian, but as far back as this guideline described the format as being ISO 8601. Furthermore, the date and time preference window shows the option as "2001-01-15T16:12:34"; the presence of the "T" makes it unmistakeably ISO 8601 format. The Cite template instructions also describe it as ISO 8601. Therefore it seems clear that the English Misplaced Pages regards dates written in the YYYY-MM-DD format as being ISO 8601 dates, and that standard requires the use of the Gregorian calendar.
::::You're probably right that regardless, a hatnote/explanatory note of some nature is needed. For instance, a lot of sources such as , , , , report that ] (1899–2017) was the last surviving person born in the 19th century. However, there are also a few sources such as , , and which report that ] (1900–2018) was the last surviving person born in the 19th century, using the ending-in-1 definition.
::::At the moment, the implication of Misplaced Pages policy is that Tajima is described as having been the last person born in the 19th century on her article section, but Morano is ''not'' described as having been the last person born in the 19th century despite the numerous reliable sources stating that she was. The current policy effectively overrides any amount of sourcing of facts like that- every article treats the uncommon ending-in-1 definition as not only being a common definition but as the ''only'' definition. I don't see how a policy which arbitrarily overrides established facts and sources like that can possibly be justifiable. ] <sup>(], ])</sup> 09:03, 3 January 2025 (UTC)
:::::So your suggested change would also affect many other articles such as our own sourced ] article. ] (]) 10:08, 3 January 2025 (UTC)
:Usage such as 20th century for 1900 - 1999 simply reveals the source as being unable to perform basic counting. Any such source is immediately rendered unreliable. --] (]) (]) 13:06, 8 January 2025 (UTC)
:I'm usually one to say that we should accept that language changes and that we in the language police should go along with it, but in this case, many, especially the mainstream press, looking for headlines, are wrong. Saying the first century has 99 years, is like saying 99 cents is sometimes a dollar. Sometimes a misused word becomes acceptable, but not in this case.&nbsp;]&#124;] 14:42, 8 January 2025 (UTC)


{{outdent}}
:If Misplaced Pages does not want to use the ISO 8601 standard, it should make a very clear and prominent statement as to exactly what the YYYY-MM-DD format does mean, and every statement equating the YYYY-MM-DD format with ISO 8601 format for use within Misplaced Pages should be expunged. So UC Bill, either your edit was wrong, or was nowhere near bold enough. --] (]) 21:23, 2 September 2008 (UTC)
As per ] (with the emphasis on ''reliable''), I asked Mr Google <code>when does the new century start</code>, then looked at any hit that seemed reliable (typically government or scientific time orientated organisations) and ignored anything like quora, mass media (I gave Scientific American a pass as they are scientific) and forums. The first 3 pages gave me the following list, plus I added the Greenwich observatory. Note, I choose them based on the sources ''before'' looking at what they said.
:: (ec) There are two debateable claims in Gerry's post.
::*The ISO standard says dates before 1582 are in the proleptic Gregorian calendar if there is an agreement that to read them that way. The implication from ISO to Gregorian is therefore uncertain.
::*The encyclopedia (in article space) exists independently of all other spaces; that's a design feature, so that we can be mirrored. Therefore references in template space and talk spaces ''do not'' imply anything about article space; article space means what it says, and 2008-09-02 isn't ISO unless it says so. ] <small>]</small> 21:32, 2 September 2008 (UTC)
::**In fact, this page says ''Dates before the adoption of the Gregorian calendar on 15 October 1582 are normally given in the Julian calendar.'' If the cite templates make dates ISO, this makes them Julian; so Gerry's position is paradox-ridden. ] <small>]</small> 21:43, 2 September 2008 (UTC)


{| class="wikitable"
::Just to point out some issues if the YYYY-MM-DD dates are NOT ISO 8601, then many points become undefined. For example, should years before 1000 have leading zeros? Should months less than 10 have leading zeros? Should years before the common era be written with BCE or should negative years be used? Is there a year 0? Should we just say that the format is only loosely defined, and all interpretation issues will have to be resolved by examining the context of the article? --] (]) 21:31, 2 September 2008 (UTC)
:::And doubtless the handful of dates in that format in article space before 1970 (indeed, before the foundation of WP) vary in those regards. Therefore, yes, it is loosely defined. ] <small>]</small> 21:34, 2 September 2008 (UTC)


! Organisation !! URL !! 00 or 01
I'll respond to some of PMAnderson's points. He wrote "The ISO standard says dates before 1582 are in the proleptic Gregorian calendar if there is an agreement that to read them that way. The implication from ISO to Gregorian is therefore uncertain."

The standard says and "This International Standard uses the Gregorian calendar for the identification of calendar days" and also "The use of this calendar for dates preceding the introduction of the Gregorian calendar (also called
the proleptic Gregorian calendar) should only be by agreement of the partners in information interchange."(p. 8) I conclude that to comply with both statements, partners wishing to interchange information who have no agreement amongst them should just not express dates before the introduction of the Gregorian calendar, or should express such dates in a different format.

The partners in Misplaced Pages would be the editors and the readers. In the spirit of the ], we could decide that an agreement with the readers exists so long as we give them sufficient warning about the meaning of early ISO-8601 dates. If we don't feel such an agreement has been formed, the ISO 8601 format should just not be used before 15 October 1582.
*No, the ISO 8601 ''standard'' should not be used. The format should not be entered into WP source code, and it would be nice if it were not autoformatted; but I can't do that. ] <small>]</small> 22:09, 2 September 2008 (UTC)

PMAnderson also wrote "Therefore references in template space and talk spaces ''do not'' imply anything about article space". I agree with respect to talk space, but I disagree with template space. When interpreting what appears in a template, it is reasonable to suppose the editor obeyed the tempate instructions. I also disagree with respect to Misplaced Pages: space. For example, the MOS tells us that the decimal marker is the full stop, not the comma. --] (]) 21:59, 2 September 2008 (UTC)
:I would agree about the transcluded part of a template; but template instructions (especially, when, as here, they make no difference to what editors actually put; the ISO instuctructions relate to access dates, which do not go back before 2001) are another matter.

:The decimal point is again another matter. MOS is ''entitled'' to say the decimal marker is the full stop ''because it normally is'' in English. Granted MOS says a lot of stupid things it is not entitled to say, but that's ]. ] <small>]</small> 22:06, 2 September 2008 (UTC)

But I agree that, while autoformmatting exists, this is a real problem. I don't think it's as serious as the others, but it's worth mentioning, which is the chief issue here. ] <small>]</small> 22:11, 2 September 2008 (UTC)

:Concerning PMAnderson's statement that the instructions of Cite templates make dates Julian, I disagree. One interpretation always applies: since access dates apply only to technology that did not exist before 1583, access dates can safely be expressed in ISO 8601 fomat. For other dates, there are two interpretations:

:#If there is no agreement with readers to use ISO 8601 dates for pre-Gregorian dates, and considering that the Cite instructions say that YYYY-MM-DD formatted dates ARE ISO 8601, pre-Gregorian dates should be expressed in a different format and autoformatting should be prevented. If the only way to prevent autonformatting is to not use a cite template, so be it.

:#If there is an agreement with readers to use ISO 8601 dates for pre-Gregorian dates, state in the text of the References section that the dates are, if necessary, in the proleptic Gregorian calendar, and convert any Julian dates that might appear in the actual paper sources into the proleptic Gregorian calendar.

:A comment in this guideline that certain dates are ''generally'' in the Julian calendar does not overcome an explicit assertion to the contrary. --] (]) 22:12, 2 September 2008 (UTC)
::No, no: it's this page that makes dates Julian. ] <small>]</small> 22:15, 2 September 2008 (UTC)
:::My point is that a statement in an article about which calendar was used to write the date overcomes any statement in this guideline about what calendar a date is generally in. For example, the article ] contains the sentence "Using a modified vigesimal tally, the Long Count calendar identifies a day by counting the number of days passed since August 11, 3114 BCE (proleptic Gregorian)." Clearly, in that article, August 11, 3114 BCE is certainly in the proleptic Gregorian calendar, the contents of ] not withstanding. Clearly in an environment where a number of competent partners had adopted ISO 8601 and agreed to use it for pre-Gregorian dates, merely using that format would be an explicit statement that the date was in the (proleptic) Gregorian calendar. Unfortunately, the degree of agreement in Misplaced Pages is in doubt, and the competency of the partners varies. --] (]) 22:32, 2 September 2008 (UTC)
::::Precisely; and when there is no date stated, the style customary at the time and place referred to is the conventional second choice. Given the lack of firm agreement, the ISO standard for proleptic Gregorian is a distant third. ] <small>]</small> 22:46, 2 September 2008 (UTC)

'''Proposal'''. The ISO date format should not be used for Julian calendar dates. These should be expressed as DD-MONTH-YYYY or MONTH-DD-YYYY. Note that the name of the month should be spelled out in full to avoid ambiguity. For important dates, for Julian dates used after 1582, for wikilinked Julian dates put the Gregorian date in brackets after the Julian dates - just as we put metric quantities after Imperial.] (]) 07:30, 3 September 2008 (UTC)

:Filceolaire proposes two new date formats that are seldom, if ever, seen in English documents: using hyphens as separators rather than spaces or commas together with a spelled-out month. We already have more date formats than we know what to do with; there is no reason to add two more. Also, I don't think we usually need to list both dates, because I think most people interested enough in history to care about a difference of 10 days or so that happened 400 years ago probably already know how to convert; they just need to know know which system they are starting with. More obscure calendars should give a conversion into either Julian or Gregorian. --] (]) 14:40, 3 September 2008 (UTC)

:: I agree with Gerry. ] (]) 05:39, 5 September 2008 (UTC)

:::I don't see any problems using ISO 8601-formated dates before 15 October 1582. This is one of many dates seen from an international perspective. For example Denmark and Norway adopdet the gregorian calendar in 1 March 1700 ... See ]. We should use the ISO 8601-format in all templates (as used in the citation templates today). The standard says ''"This International Standard does not assign any particular meaning or interpretation to any data element that uses representations in accordance with this International Standard. Such meaning will be determined by the context of the application."'' and ''"The use of this calendar for dates preceding the introduction of the Gregorian calendar (also called the proleptic Gregorian calendar) should only be by agreement of the partners in information interchange."'' (3.2.1 The Gregorian calendar).
:::: 1. Proleptic: In all date parameters we should use a precise definition. It seems logical to use proleptic Gregorian calendar-dates (but this is an other discussing than what format to use).
:::: 2. Format: What ever is agreed upon on 1. it's important to use a standard way of giving dates. Then the format YYYY-MM-DD is quite obvious since it's adopted by most countries, even the US <small></small> ?
:::] (]) 15:28, 6 September 2008 (UTC)

::::The statement "This International Standard does not assign any particular meaning or interpretation to any data element that uses representations in accordance with this International Standard. Such meaning will be determined by the context of the application." must be read in conjunction with the statement at the beginning of the Scope section on the same page: "This International Standard is applicable whenever representation of dates in the Gregorian calendar . . . ." So non-Gregorian dates are entirely outside the scope of the standard, and every non-Gregorian date is a non-ISO 8601 date. "The use of this calendar for dates preceding the introduction of the Gregorian calendar (also called the proleptic Gregorian calendar) should only be by agreement of the partners in information interchange" means that users of the standard should not exchange any date before the introduction of the Gregorian calendar unless they reach an agreement to do so. If the ISO 8601 format were the only format available, the information exchange partners would just have to avoid writing about anything that happened before the introduction of the Gregorian calendar. --] (]) 18:03, 6 September 2008 (UTC)
:::::Even amongst this august assemblage of date-representation wonks, we find a statement like "Denmark and Norway adopdet the gregorian calendar in 1 March 1700 ... See ]." Is it clear to anyone from that statement whether that 1 March 1700 represented is in the (Gregorian), (Julian) or (unspecified calendar)? It is clearly necessary to have an accepted way of representing the calendar used, even if editors rarely need make use of it. The principle is simple: Say What You Mean. ] (]) 18:56, 10 September 2008 (UTC)

=== Recently added disadvantage of DA ===

<blockquote>Expressing a date as YYYY-MM-DD may imply that it is in the ISO 8601 standard and so that it is Gregorian. It is undesirable to express dates bfore the acceptance of the Gregorian calendar in this format. Conventionally formatted dates from that era will normally be in Julian. Wikilinking such dates will cause them to be autoformatted into ISO 8601 for some users, which would constitute a false assertion they are Gregorian. Therefore such dates should never be linked.</blockquote>

#MOSNUM says above that there are only two standard date formats (international and US). This appears to allow them if unlinked.
#Why tell people that they may never be linked when we've already said that ''no'' dates should be linked? ] ] 01:38, 3 September 2008 (UTC)
:::Right. Seems like it was just an oversight. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 05:49, 4 September 2008 (UTC)
::The passage quoted by Tony1 is one of three disadvantages given for date autoformatting. The statement that autoformatting of dates is now discouraged is just before these disadvantages. What is the problem? --] (]) 01:55, 3 September 2008 (UTC)

*Exactly how 2008-09-03 can only be ISO or Gregorian I cannot understand. China, Japan, Hungary, and other countries use 2008-09-03 without it being ISO. Just because ISO is the only date format in big ] known to some people it doesn't make it the only possibility for 2008-09-03! ] (]) 12:58, 3 September 2008 (UTC)

:China and Japan have never been on the Julian calendar, so it must be Gregorian - you can't express "year of the rat" in ISO format.] (]) 17:14, 3 September 2008 (UTC)

::Some good advise I once heard is "don't write to be understood, write so you can't be misunderstood". Of course, 2008-09-03 is almost certainly Gregorian because it is contemporary. A date like 1752-06-15, standing alone, might be either. The author might or might not have intended to follow the ISO 8601 standard. The problems when such a date appears in a Misplaced Pages article are
::#We have provided some ambiguous notice, but not a clear and strong notice, to our readers and editors that the English Misplaced Pages follows the ISO 8601 standard. Thus some, but not all, readers and editors will think that it is, or should be, a Gregorian date
::#The English Misplaced Pages provides no notice to suggest it isn't governed by ISO 8601, nor does it suggest what rules should be followed in formatting such dates if they aren't ISO 8601.
::#Misplaced Pages articles are copied to other places in many different ways, so any notice we might give (either way) is likely to become disassociated with the text of the article (unless it is contained within the text of the article).
::The safest way to prevent misinterpretation would be to ban the use of YYYY-MM-DD dates before 14 September 1752 in the English Misplaced Pages, since that is the date England and the British Empire adopted the Gregorian calendar. At the time, England and the British Empire accounted for the majority of English-speakers. This would also avoid most formatting issues; common sense and ISO-8601 coincide for years greater than 999. The only formatting issue I can think of that would come up after 1752 is whether single-digit days and months must be padded on the left with a zero. --] (]) 14:59, 3 September 2008 (UTC)

:::The only safe way is for the author to state which calendar a date is on if there is some doubt. For instance, the Russian ] happened in November 1917 on the Gregorian calendar because Russia was still on the Julian calendar at that point in time, so that fact should be noted - and is. The most confusing case is Nova Scotia, which switched to the Gregorian calendar in 1605, reverted to the Julian calendar in 1710, and then changed to the Gregorian calendar again in 1752. The other Canadian provinces changed calendars in various different years so, you can't generalize on any particular rule - except that if you use ISO format, it should always be on the Gregorian calendar.] (]) 17:14, 3 September 2008 (UTC)
::::That would be imposing bad writing where it is unnecessary, an endemic problem with this page. The convention, understood by all literate readers, that an article will use the dating format common at the time and place ''being written about'' will normally suffice. The only major exceptions are in Northern Europe (and North America) between 1582 and the local adoption of the Julian calendar - because contemporary usage itself varied. ] <small>]</small> 18:09, 3 September 2008 (UTC)

:::::PManderson, please provide a source, such as a writing manual or book about how to write history, that backs up your opinion. Such a source would be better if it described how to write for general audiences, rather than for historians. Also, there are many parts of the world that went from using a local calendar (neither Julian nor Gregorian) to using the Gregorian without ever using the Julian calendar. Surely one would not use the local calendar when writing in English, unless there was doubt among scholars about how to convert from the local calender to Gregorian. --] (]) 18:19, 3 September 2008 (UTC)
::::::: I said ''format''. Countries who did not use the Roman months at all before the colonial era are another question entirely. If I come across a ready reference on the matter, I will consult it. ] <small>]</small> 18:52, 3 September 2008 (UTC)
::::::::For clarity, PMA, do you really posit that it is bad writing to identify the calendar used? ] (]) 21:40, 3 September 2008 (UTC)
:::::::::Yes. ''Eschew needless words''. ] <small>]</small> 23:55, 3 September 2008 (UTC)
:::::::::: If it's not clear which calendar is being used, words used to make it clear are not needless. ] (]) 05:38, 5 September 2008 (UTC)
:::::::::: So we'll just replace all the history articles with "Men are born, suffer and die"? I'd guess there might be some pushback on that.] (]) 22:09, 8 September 2008 (UTC)

=== Date autoformatting without wikilinks ===

Since ] has already submitted a patch for that will autoformat dates without having to wikilink them, that eliminates objection #2 (overlinking) and since objection #3 is just nonsense (the order in which the date elements appear has ''nothing'' to do with the calendar being used &mdash; writing "the ] occurred on <nowiki>1917-10-25</nowiki> (])" is no more or less confusing than writing "the ] occurred on <nowiki>25 October 1917</nowiki> (])") that leaves only objection #1 as a valid complaint. Rather than throwing the baby out with the bath water (i.e. eliminate autoformatting entirely), I think a better solution would be to simply use a default format for dates, either across Misplaced Pages or on a per-article basis. Then, everybody will see the same format unless they explicitly decide to change it, in which case we should honor their choice. Taking away the choice is not a good option. Since ] is objecting to the submitted patch (despite having indirectly asked for it) I think we should build consensus around a technical solution to this issue, and have the system administrators of Misplaced Pages accept the submitted patch. --] (]) 02:28, 4 September 2008 (UTC)
*Problem 3 is more serious than you make out; ahd requiring (Julian date) in all pre-Revolutionary Russian articles is a real cost. But I've added problem 4: Idiom is "October 25, 1917, was the first day of the October Revolution...." and "25 October 1917 was the first day of the October Revolution..." Dealing with this second comma, which ''should'' be present in "On 25 October 1917,... " requires either complex and unidiomatic rules for writing dates, or an output program which understands English syntax. ] <small>]</small> 02:46, 4 September 2008 (UTC)
:Most people aren't even aware of the ''existence'' of the Julian calendar, let alone the dates on which it was abandoned (or readopted) in various countries. If there is any chance for confusion, even for dates in the more distant past (which more knowledgeable folk would immediately recognize as pre-Gregorian), then the calendar should be specified. That's just common sense &mdash; we're writing an encyclopedia for the layperson, not a textbook for historians. As for the formatting requirements, using &lt;nowiki> is a perfectly reasonable way of enforcing whatever formatting you like, if the autoformatting screws things up. The only debatable issue here is what the default date format should be for non-logged-in users. --] (]) 02:57, 4 September 2008 (UTC)
::This is absurd. By that reasoning, we should write "Columbus discovered America on October 12, 1492 (])" and "Caesar was assasinated on March 15, 44 BC (])". It would be better to delete this page and destroy autoformatting than to write so badly. ] <small>]</small> 03:03, 4 September 2008 (UTC)
:::It is neither absurd, nor is it relevant to the point of this section, which is to discuss autoformatting of dates sans-wikilinks. The first mention of a date in any article referring to a calendar other than the one that the overwhelming majority of readers will be familiar with should contain a reference (perhaps in the form of a footnote, if text seems too obtrusive) explaining that the dates are according to some other calendar. That's the last I have to say on that, here. Unless you have some point about calendars that's actually relevant to date autoformatting, please discuss it in one of the other sections. --] (]) 03:10, 4 September 2008 (UTC)
::::PMAnderson is right to raise this issue and to stress that it is important to the precision of how we present chronological facts, and the succinctness with which we express them. However, it sits beside at least two other major issues: (1) the increasingly obvious fact that because DA prevents WPians from viewing what is displayed for their readers, they regularly insert inconsistently formatted dates; and (2) the utter triviality of which goes first, month or day. These are no-brainers, I put it to you. ] ] 03:22, 4 September 2008 (UTC)
:::::I agree that the first issue is important, and although I have a different opinion on what the solution should be, my main point was that it is completely irrelevant to the date autoformatting. Most people see <nowiki>1492-10-12</nowiki> and <nowiki>12 October 1492</nowiki> as the same date written two ways, not as one ] date and a different Julian date. Some people might remember "something about the calendar changing" from history class, but most would be hard-pressed to give any specifics, either for their own country or in general. I think the right thing to do is to have a footnote (or in-article text, in the more interesting cases where it's more relevant, like with ]) at the first non-Gregorian date mentioned in an article, and take the opportunity to educate people a little. But regardless, I don't think it's relevant to most people's perception of YYYY-MM-DD format.
:::::Now, my main point was that we could answer objection #1 by deciding on a default date format &mdash; ''which is effectively what we're doing anyway, by disabling the autoformatting by unlinking dates.'' Except we're also taking away the ability to specify a preference ''at all'', even for logged-in users. If we just come up with some reasonable way of specifying a default, then we just apply the patch and we can unlink any dates we want, but still give logged-in users (who may just be regular readers who want to customize their settings, style, etc.) the ability to override the default date format, if they want. I'm thinking something along the lines of how the DEFAULTSORT thing works. That should work just fine with the parser cache. The parser cache is why we can't do something even better like use the reader's browser's locale setting. --] (]) 03:56, 4 September 2008 (UTC)

I took the trouble to read the Julian calendar" article that PMAnderson linked to when he wrote "This is absurd. By that reasoning, we should write . . . 'Caesar was assasinated on March '''15''', 44 BC (])'. " That article contains this fascinating sentence (with added emphasis): "A curious effect of this is that Caesar's assassination on the Ides (15th day) of March fell on '''14''' March 44 BC in the Julian calendar." I also checked in ''The Oxford Companion to the Year'' by Blackburn and Holford-Strevens; they don't provide an algorithm to convert roman to proleptic Julian dates, but they do make it clear there was immense confusion between 45 BC and AD 8. --] (]) 03:54, 4 September 2008 (UTC)
:Yes, that is discussing the calendar (and making the point that the Julian calendar actually in effect in AUC 710 appears to be a day off from the proleptic Julian calendar as presently instituted.) I have no objection to this; I would object to the same wording in ], however.

:What ] does do is to date the assasination to the ], and refer to the ]; this is a trifle complex and flamboyant, but I presume at some point they quoted "The Ides of March have come." Mentioning the Julian calendar in the same passage would be chaos. ] <small>]</small> 14:17, 4 September 2008 (UTC)

I would like to describe for Sapphic a situation that I think is analogous to writing 1750-06-15 Julian calendar. Imagine a notary public acts in the state of Texas in the summer; the legal time in effect is Central Daylight Time. The notary dates the certificate "July 4, 2008, Greenwich Mean Time". So which prevails, the normal customary time for legal documents in Texas, or the notary's notation about the time zone used? The notary has created a mess which should have been avoided. --] (]) 04:00, 4 September 2008 (UTC)

Actually, we '''can''' use the browser's locale setting, even with the parser cache. We just need to have the preference-checking code look at the browser settings before deciding which cached copy of the page to use. Then there would be no need to decide on page-specific defaults, since we'd '''know''' what locale preferences each reader has, which would be far better than trying to use "strong national ties" as a proxy for that information. The point, after all, is to format the dates according to the preferences of the '''reader''', and the only reason we've even been discussing the topics of the articles at all is because we had been thinking that's the best we could do. But we can do better. So here's my proposal:

==== Proposal ====
1. '''Put a hold on date unlinking.''' There's no rush on this, and it can be done in an automated way after we've implemented the rest of the changes described below.

2. '''Apply the ''' to disentangle date autoformatting from wikilinking. This will address one of the major objections to the current autoformatting: overlinking.

3. '''Create, submit, and apply another patch to set a reasonable default format for non-logged-in users, possibly based on the browser's locale setting.''' This will guarantee that users see a consistent date format across the entire site, and that the format they see is the one they prefer (or at least the one that their browser is configured to use.)

4. '''Resume date unlinking, but in an automated way.'''

I think that should address all of the major concerns with date autoformatting, and in as least-disruptive manner as possible. Thoughts? --] (]) 15:42, 4 September 2008 (UTC)

:First, this proposal presumes that most readers want to see the date format the same, no matter what the style of the article is. Some readers might prefer to have the date format match the style of the article, that is, month-first with "color" and day-first with "colour".

:Second, the proposal says to stop in the anticipation that one patch will be accepted and another will be created and accepted. Some of us might feel that there is little chance that these patches will ever go into production, and be tired of waiting.

:Third, I can't really understand the proposal because it uses the word wikilinking too much. Please provide examples of what dates, in the edit window, would look like before and after step 4. --] (]) 15:58, 4 September 2008 (UTC)
::Indeed, I confirm Gerry's points. My experience with such technical expeditions is that they hit snags at many points and take a long time to come to nothing. Sorry to be a pessimist; I'm not usually so. Bill, you still haven't addressed the major concern that to manage dates on WP, editors need to see what their readers see. The idea of defaults based on locale is full of issues: which parts of Canada will have which format? What about US military articles that their authors intend to be in international format? It's just all too complicated and likely to provoke yells of protest from afar. That is one reason that the community is embracing the simplest approach, which, in this case, happens to eschew the artefacts of computer programming. Finally, do you ''really'' care that much about whether month or day comes first? ] ] 16:07, 4 September 2008 (UTC)

::The first assumption is true. '''Some''' readers may want the date format to change from article to article, but they will be very much in the minority. Most people prefer consistency (in fact that's why there's an argument about the date format in the first place) and find changes in style jarring. Second, it is '''disruptive''' to unlink dates, because it breaks a feature that many people (myself included) really like. Date autoformatting was introduced to solve a very real problem (check the archives going back several years if you don't believe me) and though it was implemented in a less than ideal way, that can be fixed. Third, the examples are that dates will be autoformatted in the same way they are now, except without having to make them links. If you write <nowiki>4 September 2008</nowiki> in an edit box, it will show up as <nowiki>September 4, 2008</nowiki> if that's your preference (specified either by logging in and selecting that format, or by using a browser with a locale setting that indicates that format.)
::Since the first point is the most urgent, I'll explain more why this is important. By unlinking dates, we already have to decide on what date format to use. Why not simply put the wikilinked dates into that format, then? It will have the same effect (making the format consistent for non-logged-in users) but won't annoy users who '''have''' specified a preference. The only downside is that the dates will still be links &mdash; but that's precisely the issue addressed by the second point of the proposal. So here is the modified version of the first point:

1. '''Put a hold on date unlinking.''' There's no rush on this, and it can be done in an automated way after we've implemented the rest of the changes described below. ''While we're waiting to implement the remaining steps, we can continue to standardize the date format '''while retaining the link for autoformatting purposes''' and this should meet with less resistance from other editors than widespread unlinking would.''

That make things clearer? --] (]) 16:12, 4 September 2008 (UTC)

:UC Bill wrote "Third, the examples are that dates will be autoformatted in the same way they are now, except without having to make them links. If you write 4 September 2008 in an edit box, it will show up as September 4, 2008 if that's your preference (specified either by logging in and selecting that format, or by using a browser with a locale setting that indicates that format.)"

:That will never work. No computer on earth (or elsewhere in the solar system) can figure out whether September 4, 2008 should be reformatted for a reader when the date is in running text and is not marked up. Examples of cases when it should not be reformatted are
:#direct quotes
:#articles about date formats
:#groups of words and numbers that have the same character sequence as dates, but are not actually dates. --] (]) 16:50, 4 September 2008 (UTC)

Tony1, editors do '''not''' need to see what readers see, we just need to know that readers see something consistent. That goal can be satisfied by using a reasonable default format rather than manual enforcement.

Gerry, the &lt;nowiki> tags work as expected with the new patch, so editors that need to override the autoformatting for whatever reason can do so (just as they can use the | within a link to do so with the link-based autoformatting now.)

Some of the points being raised here aren't actually valid goals, they're work-arounds based on flaws in the old system. The problem isn't that editors might see something different than readers, it's that readers were seeing inconsistent formats within the same article, and the autoformatting made it difficult to fix that. If we fix the inconsistency with a technical solution, the problem goes away and we don't '''need''' to see what readers see. Similarly, the suggestion of tying date format to the subject of the article was a workaround based on the fact that we had no way of knowing the preferences of unregistered users. There are other workarounds that are much more reliable, such as the browser locale settings. If an American reader visits the article on Charles Dickens, the dates should be displayed in American format (assuming that's what the reader prefers) &mdash; it's just that the existing system has no way of doing that, so we were stuck with per-article standards. We can do better than that.

Even if the goal is to eliminate autoformatting, it still makes more sense to standardize the date formats '''first''' and to disable autoformatting later (which is a trivial one-line change to the configuration file for MediaWiki) than to do it in the disruptive manner it's currently being done. --] (]) 17:07, 4 September 2008 (UTC)

:UC Bill wrote "Gerry, the &lt;nowiki> tags work as expected with the new patch, so editors that need to override the autoformatting for whatever reason can do so (just as they can use the | within a link to do so with the link-based autoformatting now.)"

:This says "work", present tense. Does that mean the patch you have already submitted does autoformatting on dates that have no markup?

:Changing from no markup meaning leave the date alone to no markup meaning autoformat the date means that an unknown number of dates (and character sequences that resemble dates) in existing articles will break, and there is no automated way to find them. That is not good. --] (]) 17:29, 4 September 2008 (UTC)

::Yes, the patch for "Provide preference-based autoformatting for unlinked dates" does autoformatting on dates that have no markup. That's what was requested. You raise a good point about suddenly autoformatting dates that may have intentionally been left unlinked to prevent it. So here's a modified proposal:

==== More general proposal ====
1. '''Stop unlinking dates.''' This is disruptive activity that can be handled in a better way.

2. '''Gather data on dates (format, linked or not, etc.) in current articles.'''

3. '''Place &lt;nowiki> tags around currently unlinked dates.''' This will not harm anything, and will prevent the submitted patch from unexpectedly autoformatting previously unformatted dates.

4. '''Apply the patch.''' At this point, we can go past merely '''deprecating''' the linking of dates, and outright forbid it (except where the date really should be linked for information purposes, obviously.)

5. '''Resume unlinking.''' At the same time, the date formats can be standardized according to whatever criteria has been deemed appropriate. At this point, we can evaluate the level of disagreement over the standards.

6. '''Decide whether to keep autoformatting or not.''' It can be disabled with one change to the configuration settings, or kept in place if the changes detailed above have satisfied the consensus.

:I suggest that a WikiProject be formed to handle many of these tasks, and that bots be employed to take care of much of the tedious work of gathering data, unlinking dates, and standardizing date formats. I'd be happy to help out with that work, as I'm sure several other editors would. --] (]) 18:47, 4 September 2008 (UTC)

:I have started ] to address these issues. Please feel free to join the project and to contribute to its further development. --] (]) 19:44, 4 September 2008 (UTC)

:: Is this conversation now gonna continue in the project or here? — ] (]) 22:20, 4 September 2008 (UTC)

:::I think everything except step 1 should be discussed on the project talk page. I think it's important that we stop unlinking dates for the time being, since it's disruptive and there are other points to address first. The text of MOS should be changed to indicate that date autoformatting is being re-evaluated, and that editors should refrain from either mass linking '''or''' mass de-linking of dates, until a consensus has been reached on what to do. Once a consensus has been reached, the rest of the plans (possibly including the permanent disabling of date autoformatting) can be carried out rather easily. --] (]) 22:26, 4 September 2008 (UTC)

*** '''Support''' I think focusing on step 1 (stop unlinking dates) makes sense. I believe ] is on the right track and will be able to address the stated goals of the anti-DA group, namely to remove the linked dates and ensure the *default* format for non-editors is consistent. As a beneficial side-effect, it removes the need to edit war over country formats. Personally, I suggest we go down the template path similar to {{t|dts2}}, since that will be more obvious to editors while still doing the right thing for non-editors and editors alike. ] (]) 22:48, 4 September 2008 (UTC)

*'''Oppose''' I oppose the creation of software that will inevitably create errors by autoformatting things that ought not to be autoformatted, just so some people will see their preferred date order. I see no need to address this one preference when so many other preferences, such as units of measure, spelling, and idiomatic expressions, can't be addressed (nor should they be). Since the anticipation of this software is the only reason not to delink articles, I say go ahead and delink them. --] (]) 23:06, 4 September 2008 (UTC)
::Gerry, that's not what we're discussing here. We're simply saying that we should hold off on any more date unlinking until we have a more complete plan in place. That plan may still ultimately end with us disabling date autoformatting, but '''that''' is something we can discuss on the new project page. Even if the goal is to eliminate date autoformatting, it '''still''' doesn't make sense to go around unlinking dates right away. Doing that will just cause conflicts that can be avoided if we're more systematic about this. --] (]) 23:33, 4 September 2008 (UTC)
:::UC Bill's patch does not require linked dates to work. Date delinking won't prevent the patch from being implemented (other reasons might). If date delinking were to proceed at once, and later UC Bill's patch went into production, all that would happen would be a relatively small proportion of our readership (those who have accounts and select a date preference) would temporarily see some dates in something other than their preferred format. I just feel that the people who selected a preference for dates (as the system exists today) have backed a losing horse, and it's time for them to toss their bet receipts in the trash. --] (]) 04:30, 5 September 2008 (UTC)
*'''Support''' a temporary halt to date unlinking, so that consensus on a long-term plan can be reached. --] (]) 02:46, 5 September 2008 (UTC)
:::Guys, we've been long-terming for a long time. You've come in right at the end of a process that has evolved over more than two years. There are fatal flaws in the proposed tech solution, just as in DA itself, the removal of which has been met by positive reaction, sometimes enthusiasm, by the community. There is insufficient information about the proposal. Nothing has been tested, and is sure to encounter significant snags. More importantly, none of you has addressed the basic issue: ''there WAS no problem in the first place''. ] ] 03:14, 5 September 2008 (UTC)
::::Are you insane? There very much '''WAS''' a problem that DA solved. Go look through the archives. In any event, '''unlinking should NOT be the first step in disabling DA.''' It should be part of the cleanup process that takes place '''AFTER''' DA is turned off. It's very easy to disable DA, that option is built-in to the MediaWiki software. Since you obviously can't build consensus for doing that, you're trying to take the back-door approach and effectively disable it by unlinking all the dates. You keep talking about your actions being based on a "community decision" but I don't see anything like that here &mdash; I see a lot of people who can't agree on the approach to take. Which is why some of us are saying to back off and approach this the right way. --] (]) 03:25, 5 September 2008 (UTC)
::::* In defense of Tony, I am quite certain he is sane. He has however, been active here for years and has seen consensuses repeatedly develop here by those who were participating at one time or another. And then, when a decision is finally made to actually ''do'' something that corrects past mistakes, fresh blood comes here. Why? Not surprisingly, those changes in articles brings in experienced editors (but who are relative newcomers here) exhibiting some military-grade WTF?!? reactions. Clearly, there are a number of editors who oppose this. But a “consensus” on Misplaced Pages does not mean that 100% of editors are in complete agreement—and it never did. It only means that this issue was deliberated and debated for quite some time, editors’ arguments were considered, and a general consensus arrived at. And that consensus? That autoformatting was a bad idea in the first place that only swept editorial problems under the rug rather than really fix anything. <span style="white-space:nowrap;">''']''' (])</span> 03:42, 5 September 2008 (UTC)
::::*And when they show up to protest, a broader consensus needs to be formed; that's exactly what MOS is so bad at. ] <small>]</small> 22:30, 5 September 2008 (UTC)

* '''Oppose''' For the reasons stated above by Tony. This is a simple, ''simple'' issue (choose a date format most suitable for the subject matter), made more complex than it needs to be largely because it’s just human nature to dislike change and even ''more'' like human nature (and quite understandable) to not want one’s pre-existing work screwed with. But an utterly ridiculous amount of arguments and battles have raged over this silly issue. The growing realization is that the autoformatting tools were an ill-thought-out tool that made “pretty” results only for editors and didn’t benefit regular I.P. users (99.9% of Misplaced Pages’s readership) one twit. Worse, the tools were masking editorial problems in our articles because we editors couldn’t ''see'' the problems (but I.P. users could see them). And the second problem with the auoformatting is it added needless links to lists of random trivia that more often than not, had nothing whatsoever to do with the article. In ], since it was a French invention and didn’t have strong ties to the U.S., I chose to format the dates like “7&nbsp;April, 1799.” You know how many editors over the last year have changed the date format or complained about it? Or even ''commented'' on it? Zero. Zip. Nada. Not even some 14-year-old American junior high student. No one gives a crap about this issue except for we editors. We’ve got to put and end to this argument and get on with life; the issue is too trivial to bother wasting Misplaced Pages server storage space on. <span style="white-space:nowrap;">''']''' (])</span> 03:28, 5 September 2008 (UTC)
:* Did you even read what was being discussed, or did you just give a knee-jerk reaction? The ONLY issue up for debate in this section is whether to stop the unlinking of dates, until a better plan can be reached. It's fine if you're against DA (I think you're ignorant of the history of Misplaced Pages in that case, but that's just me) but the FIRST step should NOT be unlinking the dates. That's the cleanup after DA is disabled. --] (]) 03:40, 5 September 2008 (UTC)
::Sapphic, forgive my cynicism about change at the programming end: I've learned through hard and long experience not to trust ''any'' suggestions that tech-change will happen any time in the next decade, or that it will happen eventually in a functional way. Sorry. No way: that's how we allowed the DA debacle to happen in the first place. Editors here on the ground need to take charge of the matter on the local level, and that's exactly what they're doing.
::Indeed, Greg. It's striking how much heat the DA thing has generated when you look at how superbly well we've learned to manage the engvar issue at WP—indeed, engvar is one of the project's most outstanding administrative achievements—to bring together the whole English-speaking world and largely avoid in-fighting about which variety to use where. This, I believe, has resulted from (1) significantly improved wording in the MoS engvar guideline, (2) a realisation by editors that, "hey, it's fine to apply this binary choice to article-consistent spelling and heck, the varieties are so damned similar", and (3) an evolving maturity in the way people interact on Wikis, which were new and raw at the time the DA urchin was concocted. Now we see the same plot evolving, several years too late, for date formatting—also binary in which the difference between the two versions is utterly trivial.
::Right now, we need to sort out the non-anglophone-country issue for the choice of date format, which should have been done ''years ago'', but which was never addressed because autoformatting concealed the issue from us (but not our readers). Just another reason that we all need to see the same text that our readers do. And ... it's less work.
::Oh, and one more thing: ''do'' remember that WikiMedia's software serves hundreds of sites all over the world, not just WP. This may partly explain why there's a reluctance to change anything lightly at that end of the chain. But individual editors can still act for the good of their readers ... ] ] 03:50, 5 September 2008 (UTC)
::* Sapphic: Probably a bit of both. Fortunately, I caught the essence of your proposal (stop the unlinking of dates), and voted properly (for me) on that salient point. The links are worse than worthless in my opinion as they result in over-linked articles and direct readers to long, tedious, random lists of trivia. If I’m reading an article on particle physics, and read that Enrico Fermi discovered something on ], I might be hoping to learn more about Fermi’s discovery when I click on the link. I’d be quite disappointed to go to a huge list of trivia, which includes such fascinating events as “ in ] ], English-born actress .” ''(*yawn*)'' <span style="white-space:nowrap;">''']''' (])</span> 03:52, 5 September 2008 (UTC)

* '''Comment''' I think we all need to take a look at ] and ] again, there's no need for name calling or sanity questioning in either direction. However, I think there's a strong reaction from people that unlinking dates was *not* the best way to go about this either. I read quite a ways back on the entire thread, and one of the oppose people (Anderson?) said that mass unlinking would get exactly this sort of reaction, so no surprise. What we have now is a proposal to halt the mass unlinking while more editors show up and get involved. Hopefully out of this comes a disentangling of the issues so that we can address them separately. Sorry if it's not the result you would have picked, but I think it's the wiki way.] (]) 03:59, 5 September 2008 (UTC)
::No, the issues ''have'' been well disentangled, churned, widely debated for a long long time. You are trying to scupper a reform that you're personally uncomfortable with (I've no idea why) by implying that the issues have not been thoroughly debated—please try to understand that they have. I can point you to lots of evidence if you wish, and lots of evidence that the community wants the reform. I don't think PMAnderson would want to be counted as an "oppose"; he has expressed a more nuanced view. "I think there's a strong reaction from people that unlinking dates was *not* the best way to go about this either." There has been a strong reaction from a few isolated locations, and many of the original people who were opposed have changed their tune over the past two months. On the contrary, the reactions have been either positive or neutral. Selected comments are gathered ], but this has not been updated to include more recent enthusiastic support by WPians out there. <s>Dmadeo, I have a sneaking suspicion that you're stalking me, but I'll readily withdraw this comment and apologise if it's untrue.</s> ] ] 04:53, 5 September 2008 (UTC)

::: Wow. Stalking? Is that AGF, have I said something about you? I think I'm going to walk away from this discussion for a few days, I thought I was trying to bring a little bit of civility back into this discussion, but perhaps that's not what the consensus wants.... ] (]) 05:12, 5 September 2008 (UTC) ''''

* Also '''oppose'''. I especially oppose a change to the software that would start changing the way unmarked-up dates would be displayed. As the proposal's point 3 says, ''"Place &lt;nowiki> tags around currently unlinked dates. This will not harm anything, and will prevent the submitted patch from unexpectedly autoformatting previously unformatted dates."'' At least unlinking dates is an explicit procedure, and will have the effect of making the date being displaed exactly the way the editor wants to, while the proposed change to the software will make unmarked-up articles display differently ''without any editor having touched the articles in question''. The workaround, placing the &lt;nowiki> tags around ''all currently unlinked dates'', will not be obvious to editors. This is too draconian.

: And by the way, try to keep your calm, people. Calling people insane, accusing them of stalking, etc., are not conducive to a civil, productive debate. ] (]) 05:36, 5 September 2008 (UTC)

*'''Support'''. Stop delinking of dates ''now''. I for one want my dates to be autoformatted. I don't want to read "September 5, 2008" even in an article about an American subject and I'm sure many Americans don't want to read "5 September 2008" even in articles about non-American subjects. Until this is resolved, please stop delinking. -- ] (]) 15:06, 5 September 2008 (UTC)
::Necrothesp, may I point out two things? First, your readers out there, British ''and'' North Americans all, have been viewing both formats—the raw ones we key in—all along. Your personal preferences are noted, but many editors are keen to place the readership above those personal concerns. That is a commendable and decent approach, I believe, and underpins the professionalism that makes WP a powerful authority on the Internet. Second, I presume you're British. Many British newspapers use the so-called US date format. My own daily newspaper does. Most of its readers probably don't even notice that this is different from the prevailing international format used in my country. On the other side, the US military uses international date format; a quick browse through the thousands of US military articles will show that this is reflected in our articles. Try ], for example, although where DA is still used in those US articles, you'll have to select "no preference" for your dates ("my preferences") to see what your readers see. Please let me know your reactions. ] ] 15:25, 5 September 2008 (UTC)

:* '''Wow!''' Necrothesp, your response speaks directly to the heart of the problem with autoformatting. Editors probably represent only 0.1% of Misplaced Pages’s readership. That means 99.9% of our readership ''don’t'' have accounts and ''haven’t'' set their user prefs. And what does ''that'' mean? That date formats like <code><nowiki>]</nowiki></code>, which produces a wonderful, gorgeous, spelled-out date like ]&nbsp;] for ''you'', produces a crappy looking {{nowrap|]-]}} for virtually our entire readership. Even the more “benign” formats, like <code><nowiki>], ]</nowiki></code> in an article on France gives *you* what ''you'' want to see (sorry, that’s not the litmus test here) but produces a wholly inappropriate date format (], ]) for virtually everyone else in a European-related article. Do you think that is a good thing? I don’t. These God-forsaken tools have only been masking editorial problems the entire time we’ve been using them.<p>We editors have got to wake up to the fact that Misplaced Pages does not exist to produce custom content that only we editors can see so we can enjoy a privileged version of Misplaced Pages and marvel at our handiwork and pat ourselves on our own backs for a job well done. If we’re not looking at ''<u>the exact same content</u>'' that regular IP users see, we’re just sweeping editorial problems (like I illustrated above) under the rug. We need to fix these shortcomings in our articles and the first step towards that end is to unformat dates.

::], how does a link to random trivia like this got to do with anything?]]Beyond the issue of *formating* of dates, I just can’t see the wisdom of cluttering up articles with ''even more links'' if all they do is take readers to random lists of historical trivia that have nothing whatsoever to do with the subject matter at hand. If I were writing an article on the ], I might link to ], for instance. Such topical links properly invite exploration and learning. When articles are over&#x2011;linked, we’re just numbing readers to links, such as when we add a link within ] that takes the reader to an article that says…

::{{quotation| ] - ] defeats the leaders of rival ]ese clans in the ], which marks the beginning of the ], who in effect rule Japan until the mid-nineteenth century.}}

:: By the way, <u>that is a ''real'' date link</u> that is in the ''speed of light'' article. Just because one ''can'' add links to an article, doesn’t mean one ''should''. If readers want to read a mind&#x2011;numbing list of random trivia that occurred on ]st, they can type it into the search field. When we over&#x2011;link, we just turn articles into a giant blue turd.

::This issue ''is'' resolved. The general consensus is that the proper course of action is to improve Misplaced Pages’s articles for the maximum benefit of our IP readership—not us. The arguments of other editors here, which were along the lines of your argument above (“I want a special view of the data just for '''''me''''' ‘cause I don't want to read ‘September 5, 2008’ even in an article about an American subject”) had been considered and discredited. <span style="white-space:nowrap;">''']''' (])</span> 15:48, 5 September 2008 (UTC)

:::I have to say that I've never, ever seen a date on Misplaced Pages formatted as <nowiki>]</nowiki>. Have you? And can I ask you to drop the patronising tone please - what I am objecting to is the sudden delinking without any form (that I've noticed) of public discussion beyond discussion on a talkpage that very few people are actually going to look at (so not really any form of "general consensus"). Yes, I am aware we write for our readers - strange as it may seem, somebody who has contribued as many articles as I have to the project is intelligent enough to realise the point of said project and how the whole linking thing works. "The arguments of other editors here, which were along the lines of your argument above (“I want a special view of the data just for me ‘cause I don't want to read ‘September 5, 2008’ even in an article about an American subject”) had been considered and discredited" - I should reread that statement and see just how arrogant and patronising it sounds! Who has "discredited" them? You? Autoformatting was ''for all of us'' to make articles easier to read ''for all of us'', not ''just for me'' as you so patronisingly claim. -- ] (]) 19:26, 5 September 2008 (UTC)

:::* ''“I have to say that I've never, ever seen a date on Misplaced Pages formatted as <nowiki>]</nowiki>. Have you?”'' &thinsp;Uhm… okaaaaay… try logging out so you look like a regular IP user; that’s sorta my point. In your 15:06, 5 September 2008 post above, you wrote ''“I don't want to read ‘September 5, 2008’ even in an article about an American subject…”'' so I’m confident given that you are so strident on this topic, that you don’t routinely work and play on Misplaced Pages while logged out. That practice masks this particular format and all the other formatting issues I’m trying to point out here.<p>So you can understand, here is some sample text. Take a look at it while logged in and while logged out.

::::{{cquote|During the French Revolution, the Estates-General convened in Versailles on ], ] and lengthy speeches by Necker and Lamoignon… and then on ] a memorial was built on the site…}}

::::Do you see now? To save other editors the effort of having to log out, here is how the above was coded:

::::{{quotation|<nowiki>During the French Revolution, the Estates-General convened in Versailles on ], ] and lengthy speeches by Necker and Lamoignon… and then on ] a memorial was built on the site…</nowiki>}}

::::And here is what virtually every single user of Misplaced Pages sees (because they aren’t *special* like we registered editors):

::::{{quotation|During the French Revolution, the Estates-General convened in Versailles on ] ] and lengthy speeches by Necker and Lamoignon… and then on {{nowrap|]-]}} a memorial was built on the site…}}

::::But for someone logged in with “Euro-style” preferences like Necrothesp likes, here’s what ''they'' see:

::::{{quotation|During the French Revolution, the Estates-General convened in Versailles on ] ] and lengthy speeches by Necker and Lamoignon… and then on ] ] a memorial was built on the site…}}

::::It should be quite clear that both date formats 1) are inappropriate for use in an article on the French Revolution, and 2) they appear lousy or awkward for the vast majority of Misplaced Pages’s readership, and 3) editors who are logged in and have their user pref settings adjusted to their suiting ''can’t even see'' where these problems exist! As editors who are largely responsible for this stuff, we’ve been marching along all fat, dumb & happy, totally oblivious to what we’ve been making the vast majority of our readership look at. As I stated above, we editors should '''''never''''' use tools that allow us to look at regular editorial content in a way that is at all different from what everyone else has to look at. The only preferences settings that affect what we see should be date offsets for when edits are made—that sort of thing.<p>As for your ''“what I am objecting to is the sudden delinking without any form (that I've noticed) of public discussion…”'', please see the 19:37, 5 September 2008 post ] by 86.44.27.255.<p>And as for my patronizing tone, it is not a personal attack, nor have I been uncivil to you, so you may complain all you want but you are wasting your time when you presume to tell me how I may think or express my thoughts. The patronizing tone comes out, apparently, when I deal with a registered editors, who has ''clearly'' set his user preferences so his dates are Euro-formatted, and then writes about how he has never seen a date formatted like <nowiki>]</nowiki>. Is this concept of what “you” see v.s. what “virtually everyone else” sees getting through to you yet? This realization of what we’ve been doing with these autoformatting tools has sunk in to a sufficient number of editors now. Hopefully, you will understand that what you are seeing is not what IP users see—but ''should''. <span style="white-space:nowrap;">''']''' (])</span> 21:23, 5 September 2008 (UTC)

:::::Many editors who use the citations using the cite or citation templates write the dates in the <nowiki>]</nowiki> format. Sometimes the square brackes are included, sometimes not. --] (]) 19:42, 5 September 2008 (UTC)

*'''Oppose'''. The third step is the most unappealing and potentially problematic. The proposal says that it will "not harm anything", but I'd say instead that it will not harm anything ''if executed correctly'' - otherwise, it will get ''really'' disruptive. However, I can't agree more with the first step: ''do not unlink dates yet''. The final setup must be decided first. If anything, wikilinks say "this is a date, and you're allowed to change its format" (it is not a quote, etc.), which could be useful to bots once we decide what (if anything) to do e.g. with the existing wikilinked ISO 8601 dates. ] (]) 18:20, 5 September 2008 (UTC)

=== Unlinking ===
What's with the new wording? Editors can't form a consensus to unlink dates on the relevant article talk pages? Some Wikiproject which (no disrepect but) I've never heard of and which currently has 5 members gets to tell us when it's ok? Very strange. It's depreciated. Of course editors can unlink dates provided they don't edit-war about it, use the talk page if reverted etc. Where is the discussion that led to this bizarre wording? ] (]) 06:14, 5 September 2008 (UTC)

It seemed to be a recent addition without discussion so i have reverted. ] (]) 06:21, 5 September 2008 (UTC)

::Correction: without consensus. ] (]) 07:36, 5 September 2008 (UTC)

:::This has been discussed for years, and widely. Please see the rest of the talk page before firing off a salvo. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:41, 6 September 2008 (UTC)

::::Better advice would be to tell me to include a diff to whatever the hell it is i am talking about . ] (]) 11:43, 9 September 2008 (UTC)

=== December 09, 2004 ===

Expecting that no one will disagree, I've inserted a note about ''not'' doing this. In the process of auditing the dates of many articles, I've found quite a few examples of this. Please say so here if there's a problem. . ] ] 09:07, 5 September 2008 (UTC)
:Good point. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:41, 6 September 2008 (UTC)

=== When/how did this happen ===
Whoa, whoa. Hang on a minute. I've only just become aware of this when people started to delink dates from articles on my watchlist. This is a huge change which seems to have only been discussed by a few parties who are particularly interested in dates. It's the biggest change to editing procedure I remember in my four years of editing, but where were the attempts to alert other editors to the discussion? Where was the prominent note on the front page? I don't agree with it and I'm sure many other people don't either. Let's have a bit more open discussion before a small group of people start trying to tell all other editors how to edit. -- ] (]) 13:47, 5 September 2008 (UTC)

* This has been debated for years, Necrothes. And it is finally coming to an end. The “linking” of dates is unwise and the autoformatting of dates was a terribly unwise decision made two years ago to resolve editwarring. Because of autoformatting of dates, 99.9% of Wikipeida’s readership (regular IP users) were often seeing unsuitable date formats in articles. Further aggravating the problem is we editors ''couldn’t even <u>see</u> the problems'' because our preferences settings were blinding us to this fact. The first step in fixing these articles is to unformat (delink) the dates. Then we simply write out the date in a method that is most suitable for the topic. The current MOSNUM wording…

:{{quotation|Articles clearly written in a national variety of English should generally use the more common date format for that nation; articles in Canadian English may use either format consistently. Articles on topics with strong ties to a particular English-speaking country will therefore normally use the corresponding date format.}}

:…is just fine; there should be absolutely no editwarring over the issue. See my above, expanded response (with the fascinating picture of Tokugawa Ieyasu) for more info on just why autoformatting was—and remains to this day—a piss-poor set of tools that never should have been made in the first place. <span style="white-space:nowrap;">''']''' (])</span> 17:11, 5 September 2008 (UTC)

:Necrothesp, I appreciate that you were unaware of any discussion, but discussion on depreciating autoformatting of dates, already longstanding, drew in a large number of editors on this page through July/early August as it moved towards consensus. It was then posted to the ] and to ] through August. Additionally, several Wikiprojects were individually made aware of it, as were a large number of individual article writers. Thus, autoformatting was depreciated. ] (]) 19:37, 5 September 2008 (UTC)

::Not to mention the fact that de-linking was even the subject of a "successful" petition to the developers that the developers simply ignored, in 2006. This is by no means some sudden change. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:40, 6 September 2008 (UTC)

=== Throwing an idea on date format ===

Alright, we've got a bunch of hoo-haa going on about everything. A quick summary of it is

A) People use different formats in the world <br>
B) Editors come from around the world. <br>
C) Editors can't agree on which to use. <br>
D) Autoformat is a nice solution, but deficient because readers can't get the benefit. <br>
E) Overlinking is evil and unecessary. <br>

So, how about we do this.

1) Use ISO dates format in autoformat everywhere, unless problematic (and I'm not talking about ISO meaning, just the format, so you'd say something like ] (Julian Calendar) if you want to point out its a Julian date, or however it's currently done). <br>
2) Autoformat is on for EVERYONE, the default option is the international format (which I don't really like, but it's the international format so that should be the default option). <br>
3) Registered readers/editors can specify a preference for non-international format (like right now). <br>
4) Autoformat dates display unlinked. <br>
5) To write month/day, write an "empty year" ISO date such as -09-04 to produce and internationally format date. <br>

This fixes seeing a date format such as 2008-05-15 if you are a non-registered user. This fixes overlinking. This eliminates the need for complicated and slippery slope rules such as "For Canadian topics, use canadian formats, for American topics use American format, etc.". And this fixes once and for all inconsistent date formating. It would probably require some modification of wiki software and other technical considerations but let's not worry about that. What I'm asking if we could do it somehow, would this be a (the?) viable solution?

] {] – ]: ]} 21:19, 5 September 2008 (UTC)

* I’m all for many variations on this theme Headbomb. But the essential element of it requires that autoformatting be made to work for regular IP users. This requires geolocation based on IP addresses. There is nothing particularly difficult about figuring out what country a reader hails from; commercial Web sites routinely track raw statistics on visitors, such as where they live, what operating system they use, what browser they use, etc. If you go to LiveLeak, little adverts will say something like “Meet hot chicks who live in ” because LiveLeak’s servers drill down in the requesting I.P. address so they know where precisely where the ISP is located. But Misplaced Pages’s servers and the infrastructure and tools aren’t currently set up to pull off this stunt. Further, it seems unrealistic to expect that such a substantial change at the very underpinnings of how Misplaced Pages’s servers operate will be produced any time soon for us. So then the question becomes “what do we do with these autoformatted dates in the mean time?” Since your proposal would require re-writes of articles (just as de-autoformatting does), we might as well go fix the problem now for the tools that are currently available.<p>Further, if/when I.P.-based geolocation ever ''does'' become available, we can use the information to make other tools. Personally, I don’t mind looking at either February&nbsp;10, 2008 or 10&nbsp;February 2008 so I can barely relate to what the big deal is. But it is more disruptive to my reading when I encounter “realise” and “colour” and “caesium”. With geolocation of the requesting reader, we could have <code><nowiki>{{dialect|us|commonwealth|realize|realise}}</nowiki></code>, and <code><nowiki>{{dialect|us|commonwealth|trunk|boot}}</nowiki></code>. Now ''that'' would cut down on “brain interrupts” in my reading. For that matter, such a tool could be used to write <code><nowiki>{{dialect|us|commonwealth|The ] was a great thing to get those greedy bastard Brits off their backs.|The ] was put on by a bunch of ungrateful malcontents.}}</nowiki></code>. <span style="white-space:nowrap;">''']''' (])</span> 22:09, 5 September 2008 (UTC)

Writing "] (Julian Calendar) " on a wikimedia-powered server is equivalent to writing "$99.95 (pounds sterling)". This is because of ] which specifically states that for purposes of autoformatting, the YYYY-MM-DD format is ISO 8601. ISO 8601 says you can't write "1054-08-12 (Julian Calendar)" for two reasons.
##The use of any year outside the range 1583 through 9999 requires mutual agreement among the partners interchanging date information, and no such agreement exists between Misplaced Pages editors and readers.
##ISO 8601 dates must use the Gregorian calendar.
:--] (]) 22:10, 5 September 2008 (UTC)

*All too complicated. I'm keen that there not be mass conversions of US format right now, except where it's wrongly used in articles with strong ties to a non-North-American anglophone country, or defies the engvar. We just have to bite the bullet and make a decision about Proposals 1–3 above. ] ] 04:47, 6 September 2008 (UTC)

:* Ok, I don't buy one bit the argument of "figuring out I.P.s", but perhaps others do. We don't need to figure out the IPs. You give international format by default. If for some reason, people want a non-international format on a non-international topic, there could (again throwing an idea) be a "page argument" that would say "here autoformat gives the December 31, 2006 format by default".
For example written something like
<pre>
{{daf|american=yes}}

Jimbob was an accountant born on ] and died on ]. He ate a cat on ].
He met his wife on ].

</pre>

would yield (unless you are a registered user)

::Jimbob was an accountant on May 6, 1943 and died on September 13, 1986. He ate a cat on March 2 of every leap year. He met his wife on February 2, 1973.

::

:* Second about ISO. This is not about ''ISO dates'' meaning a non-ISO date. This is about an ''input format'', which is outputted in a non-ISO format (at least by default). Writing for input <nowiki>]</nowiki>, will output 3 April 1042. If the date can somehow be confused with the ISO date 1042-04-03, then I don't see what the problem is with written <nowiki>] (Julian Calendar)</nowiki> which will display as 3 April 1042 (Julian Calendar). All the instances of ISO dates requiring a "ISO interpretation" on Misplaced Pages should not be autoformatted anyway, so I really don't see ''any'' problem on the ISO front from the reader's perspective.

] {] – ]: ]} 07:07, 6 September 2008 (UTC)


:: This also have the advantage of being incredibly bot-friendly. ] {] – ]: ]} 07:08, 6 September 2008 (UTC)

:::But we are an encyclopaedia that anyone can edit. That basically means that people will enter dates in their preferred format, especially if they are writing text rather than filling in templates. I really don't like the idea of stalking new editors and yelling at them until they do things as per the MoS. If they write dates in the "wrong" format for an article, then someone can come along later and fix it up. Or a bot can trawl through articles and do it. Making things as easy and as logical as possible for new editors also makes them feel comfortable about contributing. --] (]) 08:53, 6 September 2008 (UTC)

:::: But anyone can still edit it. People will enter dates in their preferred format as much as they do now (basically everyone except those aware of and willing to follow the MOSNUM). Someone (or a bot) will clean up after them, and everyone will be happy. You don't have to yell at anyone more than you already have to. Or maybe that is what you were trying to argue and somehow thought you were arguing something else. ] {] – ]: ]} 11:17, 6 September 2008 (UTC)

:::: Oh and also it would fix the conflict between reference date format and main article format, and template could be made to follow international format by default and to respond to the "page argument" when it is there. ] {] – ]: ]} 11:17, 6 September 2008 (UTC)

Some ] shows that only about 28% of dates are linked, and only about 0.04% are in the format advocated by Headbomb. (I'm skeptical of the 0.04%; it seems like all those accessdate parameters in cite templates should push that higher.) I don't see how it is feasible to process all those articles manually or semi-automatically. Doing it automatically would not allow dates to be left alone when they ought to be, such as within quotes. --] (]) 15:00, 6 September 2008 (UTC)
:Gerry, I'm wobbly about the stats and suggest that we seek details of the sample and methodology first. ] ] 16:31, 6 September 2008 (UTC)

I don't see what's is the problem with quotes. Can't bots be coded to leave stuff within quotes alone? ] {] – ]: ]} 16:32, 6 September 2008 (UTC)

:There are two issues. First, there are different ways of marking quotes. There are single and double quote marks, both regular and curly. They may be mixed in with each other in the case of nested quotes, along with apostrophes, inch symbols, foot symbols, minutes of arc symbols, and arcsecond symbols. The various quote templates might be used. The &lt;blockquote&gt; tags might be used. Other methods of indentation might be used, because the blockquote mechanisim resembles what my neighbors' horses leave on the road.

:The second issue is that some dates other than those in quotes should not be altered. They might occur in snippits of programming language. They might be occur in titles of publications. I'm there sure are other places I have not thought of. And of course, strings of characters may occur that look like dates, but are not dates at all. --] (]) 16:47, 6 September 2008 (UTC)

* Headbomb, perhaps it would be easier for you to understand how your proposal of “just default all dates to international format” would fly like a wet noodle if I were to instead propose that we default all dates to U.S. style. While I don’t have strong feelings one way or another about date formats (I’m American but typically use internationally formated dates in articles not strongly associated with the US), I am, at least, realistic in looking at the amount of bickering that has taken place over this issue and can see that there are divergent views.<p>This is all just silliness to me. I truly can not fathom why so much discord has arisen over this date formatting issue. Either format reads smoothly enough for me that I don’t suffer (!) brain interruptions as I read. Neither format is ambiguous in the least. I shit you all not; I’m not at all trying to come across here like a “high road” sorta person, but I truly can not understand how the hell there could ''possibly'' be so much bickering here over dates. Would someone please explain this phenomenon to me? The existing guidelines on MOSNUM seem sensible enough to me: if it’s a US-related article, US-style dates, otherwise, international. What’s so hard about that? No special tools for newbie editors to learn. If there’s a dispute, anyone can just be advised to just go to WP:MOSNUM, read the rules, and then simply type out the dates that are most suitable for the subject matter and don’t link to mind-numbing trivia. Is that all so ''“Well… <b>Duhhhhhh</b>”'' that it’s too simple and can’t possibly fly here? Why does this have to be so complex? <span style="white-space:nowrap;">''']''' (])</span> 18:52, 6 September 2008 (UTC)

::It's a behavioural issue. Some editors prefer American dates and American units of measurement. I'm beginning to think that there's not much point in continuing to argue about where to draw the line. Just have one format for everything and stick to it. International format because we save about a bazillion commas that way. And we're an international project. --] (]) 00:46, 7 September 2008 (UTC)

::: Quoting Greg L:
::: <blockquote>The existing guidelines on MOSNUM seem sensible enough to me: if it’s a US-related article, US-style dates, otherwise, international.</blockquote>
::: Paraphrasing my earlier post:
::: <blockquote> International by default, US style if US centered topic.</blockquote>

::: I don't see the difference. ] {] – ]: ]} 15:16, 7 September 2008 (UTC)

=== Making controversial changes without consensus ===
I haven't checked as to who changed the section on date formats and national ties, but I've restored it to the version that has prevailed for nine months. Discussion is ongoing, and the proposal to link date format to variety of English has not gained consensus. Could we please find a solution on the talk page instead of changing text that is flagged as disputed? I think that we are making progress, with various problems being explored in an atmosphere of reasonably genteel co-operation, but it doesn't help when people change the text to suit their personal opinions on a controversial matter. If people want to edit-war instead of discuss major changes, perhaps we should seek mediation? --] (]) 05:50, 6 September 2008 (UTC)
:It is Skyring who is edit-warring for an extreme minority opinion. He need only read the ] to see GregL's express approval of the text I have restored; the text to which he reverted is certainly ''not'' consensus. If this continues, dispute resolution may indeed be in order. ] <small>]</small> 16:22, 6 September 2008 (UTC)
::Pete, your actions are not helping; please keep it on the talk page for the moment. I know that you feel strongly about the issue, but Anderson is right in this case. ] ] 16:29, 6 September 2008 (UTC)
::Concur with PMAnderson & Tony1 (no disrepsect to Pete; it's just a matter of keeping the pot from boiling over). — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 21:24, 6 September 2008 (UTC)
:::SMcCandlish's comments above about the "current" MOSNUM wording alerted me to the fact that it had been changed. It's not my preferred wording either, but best to put it back the way it's been for nine months until we find a consensus. --] (]) 22:59, 6 September 2008 (UTC)

{| class="wikitable" border="1"
|- |-
| Hong Kong Observatory || https://www.hko.gov.hk/en/gts/time/centy-21-e.htm#:~:text=The%20second%20century%20started%20with,continue%20through%2031%20December%202100. || 01
! header 1
! header 2
! header 3
|- |-
| timeanddate.com || https://www.timeanddate.com/counters/mil2000.html || 01
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|- |-
| Scientific American || https://www.scientificamerican.com/article/when-is-the-beginning-of/ || 01
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}

=== Invitation to join the discussion at the tennis project page ===

Regardless of your views, you are invited to join concerning the linking of years and whether a project-specific consensus can override the Manual of Style of this subject. This discussion also concerns the operation of bots. Thanks for your time! ] (]) 06:05, 7 September 2008 (UTC)

=== Who made DD/MM/YYYY the "international" date format? ===
As far as I can tell, the ] made "YYYY-MM-DD" the international date format.
* "DD/MM/YYYY" is the '''British''' date format,
* "MM/DD/YYYY" is the '''American''' date format,
and ne'er the twain shall meet. The former might also be considered the European date format, but not the Asian date format since the Chinese and Japanese don't use it. As for '''Canadian''' date formats, the Canadian government's English language editorial style guide says that for '''alphanumeric dates''',
* '''either''' MMMM DD, YYYY (e.g. February 14, 2008)
* '''or''' DD MMMM YYYY (e.g. 14 February 2008)
is acceptable since neither is ambiguous and anybody who speaks English can understand them. However, for '''all-numeric dates''',
* '''neither''' DD/MM/YYYY
* '''nor''' MM/DD/YYYY
are acceptable since they are mutually ambiguous, and the
* '''ISO standard''' YYYY-MM-DD (e.g. 2008-02-14).
is the only acceptable format since it is the only one that is unambiguous.] (]) 03:10, 5 September 2008 (UTC)

:*Sound logic. However, there are two issues as far as our articles are concerned: firstly, consistency of date formats should be the focus of our efforts, not really 'which one'. Secondly, ISO couldn't look more awkward in an article. ] (]) 09:46, 5 September 2008 (UTC)
:*You're quite correct, ISO 8601 is the only ''language-independent'' unambiguous standard date format in existence. To summarize - its general advantages are:
::#Language-independent
::#Unambiguous
::#Supports sorting
:*But when one takes a look at its ''specific'' advantages for use in English Misplaced Pages, #1 becomes irrelevant, #2 also (no extra edge over, say "September 5, 2008"), and #3 is easily solved by templates. ] (]) 09:59, 5 September 2008 (UTC)

::I think people writing "DD/MM/YYYY" above, like in the map caption, don't mean anything by the slashes, and rather really mean the alphanumeric "DD MMMM YYYY". I, as a European (Swede, to be exact), would always assume that "04/05/06" is in April 2006 (slashes are used by Americans), that "04-05-06" and "040506" are both in May 2004 (shortened ISO formats), and that "04.05.06" is in May 2006 (typical European format). That's not to say that ''any'' of these formats should be used in Misplaced Pages (other than in quotations and the like), but just pointing out that there's probably nobody advocating the use of "04/05/2006" to mean 4 May 2006, or thinking that this format is in common use. I definitely agree that ''if'' there is a reason to use an all-numeric date format in an article, full ISO standard is the only way to go, but there should hardly ever ''be'' such a reason. -- ] (]) 10:08, 5 September 2008 (UTC)

:::-->''there's probably nobody advocating the use of "04/05/2006" to mean 4 May 2006, or thinking that this format is in common use.''<--
:::* Unfortunately, the British '''do''' use slashes in their dates, i.e. they use "04/05/2006" to mean 4 May 2006, whereas the Americans use it to mean April 5, 2006. This is a fundamental source of ambiguity.
:::* The shortened ISO date "04/05/06" is completely ambiguous, because the British use it to mean 4 May 2006, the Americans to mean April 5, 2006, and the ISO date means either 6 May 2004. Also, it might mean 4 May 1906, April 5, 1905, or 6 May, 1904. Therefore you should always use 4-digit year numbers.
:::* All-numeric dates are useful in tables and templates, and if you use the ISO format you can sort them without special software.
:::The British and the Americans are both very stubborn peoples, so you can't expect either one of them to agree to use the other's date format. The use of slashes doesn't make any difference to them. However, if you use dashes it almost certainly will mean ISO format.] (]) 16:14, 5 September 2008 (UTC)

::::I have discovered that the identification of the YYYY-MM-DD format with ISO 8601 is part of the Wikimedia software. Granted, this identity has been poorly communicated in Misplaced Pages; indeed, Misplaced Pages lacks a mechanism for effectively communicating any important writing convention to readers. But turning attention to this thread, there are only two ISO 8601 formats for communicating a day, month, and year:
::::# The basic format, "Example: 19850412"
::::# The extended format, "Example: 1985-04-12" (from ISO 8601:2004 p. 12)

::::To say or imply that 85-04-12 has any connection to an ISO standard is an error. --] (]) 16:35, 5 September 2008 (UTC)

*I will put this here, since I have just entered the discussion. There are FOUR formats accepted in Canada & from what I see in the proposed guideline, ONLY two will be accepted even for Canadian articles. A few articles have always used YYYY-MMMM-DD format. As the guidelines stand, they require choosing one of only two. I think the guideline should be rewritten to acknowledge that other specific formats are also acceptable. --] (]) 00:10, 7 September 2008 (UTC)

:JimWae, I imagine they are (where lower case letters indicate leading zeros are not used and MMMM is a spelled-out month):
**dD MMMM yyyY
**MMMM dD, yyyY
**YYYY-MMMM-DD
:So what is the fourth format? --] (]) 00:42, 7 September 2008 (UTC)

Actually, FIVE, counting these as three:
*YYYY-MM-DD
*YYYY-MMM-DD
*YYYY-MMMM-DD --] (]) 00:46, 7 September 2008 (UTC)

So, do any proposed policies NOT completely eliminate YYYY-MMMM-DD??? --] (]) 08:10, 7 September 2008 (UTC)

=== Question about date autoformatting ===
Now I've started reading over this issue, and am getting a bit confused, I see a section in the ] page about autoformatting and a link to ] that seems to contradict parts of itself. Could each party fill in what they think should be WP's guideline on date presentation, as it relates to autoformatting in the below sections. One user to a section, a new section for each proposal, please. ''']''' <sup>]</sup> 21:41, 30 August 2008 (UTC)

'''No, too many editors are running around creating diverse places to present their views. I'm ignoring this place.''' --] (]) 21:51, 30 August 2008 (UTC)
:Indeed. The issue was decided and has wide support and little opposition. This is just churning. ] ] 02:56, 31 August 2008 (UTC)

:: Can someone please point to the decision that was made with wide support and little opposition? ] (]) 06:13, 2 September 2008 (UTC)
:::Yes, and I do wish that chaotic archiving system made it easier to find things. It's ]. Evidence of wider approval is ]. ] ] 08:15, 2 September 2008 (UTC)
There is some opposition located here . ] (]) 21:38, 3 September 2008 (UTC)

=== A fresh start on date autoformatting (DA) ===

Having looked through the edit wars over the Date autoformatting subpage and noting the points made in disagreement, as well as having followed the issue here for quite a while and participated in it occasionally, I’d like to offer a “rough draft” revision of the DA subpage that to my mind’s eye seems to capture as much of everyone’s concerns as I best I can. I’ve also done so with an eye for what appears to be the relative degree of consensus for the various issues; as a rule, I’ve selected “softer” words instead of “harder” ones where a consensus is least evident. That is why I’ve used “discouraged” in preference to “deprecate” (which seems to often get misinterpreted as “forbidden” and taken as a call for a crusade for their removal – for which there isn’t such a strong consensus), and introduced “deprecate” in a more limited sense later on. I’ve also purposefully chosen to go with a lengthier version than the concise, bulleted one currently displayed. I’ve done so because this “deprecation” of usage will be better tolerated and less abused if explained, rather than just summarized.

I’m offering this as a fresh starting ground. I believe – and several people have noted – that there was no express language for the consensus to deprecate DA. Instead, the needed language was built through direct edits of the MOSNUM page, and it led to edit warring. The proper place for sparring, as we all know, is here on the Talk page.

<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
The linking of dates purely for the purpose of autoformatting is strongly discouraged, because the use of these tools results in more disadvantages than advantages. This feature can only be seen by a tiny minority of Misplaced Pages’s readership: those registered editors who have chosen to configure their date preferences ('''My preferences&nbsp;→ Date and time&nbsp;→ Date format'''). This obscures the existence and extent of conflicting date styles in an article that is otherwise readily apparent to the majority of readers, thereby hindering correction of the problem.

Furthermore, the resulting links normally go to lists of historical trivia which usually have little or nothing to do with the subject of the article. The use of these formatting tools therefore tends to produce ] articles. All links from articles should be of ''high value to the reader''; that is, following them should genuinely help the reader understand the topic more fully. Overlinking can negatively affect overall readability and appearance in articles which already have numerous high-value links.

In addition, dates from before the introduction of the ] should not be expressed in the ] format, which was designed for use with the Gregorian calendar. Conventionally formatted dates from the pre-Georgian era will normally be in the ] format, and being wikilinked and autoformatted into would constitute a false assertion they are Gregorian dates.

To avoid disruption, however, this deprecation should not be taken as license for wholesale removal of existing links from articles currently employing them extensively. Such removal from a given article should follow a ] to do so among the editors of that page.

The functions provided by these tools nonetheless remain available and are described at ].</div>

Please critique it in the spirit in which it’s offered and with an eye toward compromise. ] <small>]</small> 22:40, 30 August 2008 (UTC)

:I would say wikilink ] rather than just ]. I would also say "...extensively '''for Gregorian dates'''..." (addition bolded)because I think it is a good idea to conduct a campaign for the sole purpose of removing autoformatting from articles that use autoformatting on Julian dates. Ideally such a campaign would also insure the calendar used in the article is explicitly stated. --] (]) 23:01, 30 August 2008 (UTC)
::Thanks, Gerry, good catch! That's the sort of input I'm looking for. I've incorporated your recommendations. ] <small>]</small> 23:37, 30 August 2008 (UTC)
:::The automatic removal from Julian dates is faintly silly. Stating the style explicitly on articles about the Middle Ages is utterly unnecessary; it would be bizarre to use Gregorian before it existed. Autoformatting was intended to switch back and forth between 30 August and August 30; I suspect most people use it that way; and that's perfectly safe. Anyone who chooses to autoformat to ISO does so at his own risk (and, like Woodstone, she may not care about Renaissance history). ''Please'' make that by consensus too. ] <small>]</small> 00:34, 31 August 2008 (UTC)
::::"Stating the style explicitly on articles about the Middle Ages is utterly unnecessary" is bullshit. Not everyone who would like to read an article about the middle ages knows about the convention for which calendar to use, nor do they necessarily know when the Gregorian calendar went into force in any given place. Also, I cannot find the design criteria for the autoformatting "feature" so I do not know what the intentions of its designers were. I would be interested in seeing a record of what they were thinking. --] (]) 00:58, 31 August 2008 (UTC)
:::::That had been my understanding, too, PMA – until I began reading the recent debate over it and Gerry and others began indicating that it may not be so. Do you know someone sufficiently familiar with the code to tell us one way or the other? I’m copacetic with it either way; one of the reasons I wrote it in as a separate parenthetical note is so it can easily be removed if need be. ] <small>]</small> 01:08, 31 August 2008 (UTC)
::::::See ] on this page. Looking at the past versions of MOSNUM confirms that autoformatting was intended to settle dating disputes between the two conventional alphanumeric formats. In accordance with this, I am removing the parenthetical. ] <small>]</small> 20:55, 31 August 2008 (UTC)
:::::::Actually, although it shows as a blue link, it would not work for me and there is no such heading on this page. I also looked in the D6 archive, but found nothing there. ] <small>]</small> 22:41, 31 August 2008 (UTC)
:::::::::My apologies: ]. ] <small>]</small> 21:17, 2 September 2008 (UTC)

This is an attempt to scuttle a genuine reform of a major formatting function that almost no one likes, by slowing its pace so that it will take decades rather than a few years, and will forever be patchy in it application.

<blockquote>"To avoid disruption, however, this deprecation should not be taken as license for wholesale removal of existing links from articles currently employing them extensively. Such removal from a given article should follow a ] to do so among the editors of that page. (Exception: Date autolinks should be removed whenever they are found being used with non-Gregorian dates.)"
</blockquote>

*Tony, I agree; you engage in outrageous and unfounded attacks when you do have a shadow of an argument. But your claim is a falsehood: I think that if we don't push things ''right away'', we will be rid of autoformatting in a year. Going full speed ahead now will be damaging to the encyclopedia and is the only thing at all likely to delay this reform for decades. ] <small>]</small> 20:45, 31 August 2008 (UTC)

The argument seems to rely on (1) mixing up date warring and ISO with the decision here and elsewhere to get rid of DA, and (2) some kind of unstated personal discomfort at bold change. However, the current debate about the choice of format for third-party countries is a response to an issue that has always been there for our readers. There is no relationship with the current "edit wars" over choice of date format, except that the sudden realisation that DA has shielded WPians from seeing the mess of inconsistency and wrong global choices of format; this has concentrated people's minds on it, which is a good thing.

So, work out what you want with ISO dates, and decide on a guideline (or not) for the third-party format for dates, but don't try to confuse these issues with the removal of DA.

And why refer to "deprecation" in the quote above while pussy-footing about it in the opening sentence and requiring a long, convoluted generation of consensus at ''every single article'' to achieve the goal? You can't have it both ways. (And the bit about Gregorian dates begs the larger question while introducing muddy logic.)

As for "To avoid disruption", any bold improvement to WP could be framed as "disruption", and it is idle and manipulative to frame it thus without evidence of widespread opposition. There is none: show me, please, the raft of reversions of the date auditing that has been conducted over the past few weeks. And please face up to the strong—not mild—agreement of so many people, here and on the other pages I linked to during the debate. It keeps trickling in, like this:

Contributors should revile this attempt at sabotage. The proposed change does nothing to improve what is now a straightforward, concise statement. We need to grow up. ] ] 02:51, 31 August 2008 (UTC)

:Wikilinking dates was a kludge brought in to settle the date wars of some years ago. In all the time since then, no better method has been found. However, it '''is''' a kludge, and increasingly obvious. The two major disadvantages are:
:# It fills an article full of useless links. Click on a date link and most of the time you are taken to a page that has zero relationship with the original article.
:# It doesn't work for the 99% of Misplaced Pages users who are not registered with user accounts and date preferences.

:We are writing an encyclopaedia, and our readers must be our main focus. We are presenting information to the wide world. so I'm totally in favour of removing date autoformatting. We get to see what the readers see, and we make the reader's experience better by removing a sea of useless links.

:However, we now have to deal with renewed outbreaks of date wars, as editors, no longer shielded from date formats, see raw dates in a format they personally don't like. I think that for the removal of autoformatting to work, we've got to work out a solid solution on date formats. --] (]) 05:37, 31 August 2008 (UTC)

::Agree strongly with Tony and Pete. It isn't "disruption" to alter Misplaced Pages articles to bring them in line with what we've agreed is the right style; the disruption is tryin to stall this process in spite of the lack of any substanial arguments against it. Also I don't see that the current solution we have on date formats is in any way unsolid.--] (]) 16:41, 31 August 2008 (UTC)
:::We shall see. I don't think it's unsolid; I think that authorizing mass implementation is a recipe for making, and keeping, this controversial, and that doing so will slow down acceptance immensely; ''festina lente'', "make haste slowly", is very old and very good advice. It is consensus here to get rid of autoformatting is a good idea - if we proceed, page by page, for a few months, we will probably persuade the rest of Misplaced Pages to join this consensus. By that time other editors will have heard of the change, and (with luck and tact) most of them will agree with us or not care. At that point, stronger language and actions may be in order - or, if we convince enough people, unnecessary. If every editor thought it was the normal thing to delink dates, we'd be done without bots. ] <small>]</small> 20:40, 31 August 2008 (UTC)

Tony, I ask you to assume good faith and to make no assumptions about my motives or intents – simply ask me and I will answer your questions. I have no agenda other than to '''forward''' this process with '''minimal disruption'''. Period. To accuse me of trying to “sabotage” the effort is uncalled for, utterly lacking in evidence, and frankly a personal attack since it maligns my motives. This is exactly the sort of behavior I ] as discouraging participation by other editors. As PMA notes, you’re perfectly capable of offering logical arguments ''sans ad hominems''.

What I have attempted to do is to capture the actual degree of consensus for the various elements, starting with the text as I found it, and taking into consideration the preceding discussions and edit comments on changes (leading up to and during the edit warring that got the guideline page locked down). What I originally offered was a good-faith ''starting point'' for working toward a final text that enjoys general consensus – while avoiding edit-warring. FWIW, it’s not my favored version and I little care what the final wording is, as long as it enjoys consensus.

As regards the ISO statement, it’s included because it was in the locked-down text. I wasn’t aware that there is still an argument over whether ISO should or should not be used with non-Gregorian dates. As I noted to PMA, my impression has always been that all the DA does is take care of handling the day and month (and American-style comma use) per a user’s preferences. If that’s ''all'' it does, then I frankly don’t see how it can screw up Julian dates. In that case, DA has nothing to do with whether dates are Gregorian or Julian, and the whole paragraph (and parenthetical note on DA removal from Julian dates) should be excised – and I will be happy to do it; just provide me the facts.

As for a crusade to slaughter all remaining DAs, there has never been consensus for it. Moreover, a consensus for it ''has never yet been sought'' in the foregoing debates; the only time the issue has been raised has been by editors appalled by actions of the raft of crusaders. Frankly, I see such a mass removal as disruptive, have previously ], and less disruptive approaches have been suggested. In fact, nobody disagreed with me and you yourself thought it a good idea! In any case, I have no love for DA and wouldn’t mind if they all disappeared overnight – however, such a move has no consensus. If you wish to seek one for aggressive removal and achieve it, hey – this guideline can be changed to say so! Right now, though, there’s consensus only for “soft” deprecation, not “hard”.

Pete, I’m not arguing for DA. That they’re not needed and mostly unwanted by or unavailable to readers is a pretty solid consensus. I agree with you that “for the removal of autoformatting to work, we've got to work out a solid solution on date formats.” I would further suggest we should not set off on any mass DA removal effort until after consensus on that is achieved. However, I think you will agree that whatever formula is developed, it can be worked into the summary text I’ve proffered.

PMA, thanks for being the voice of reason! ] <small>]</small> 23:40, 31 August 2008 (UTC)

:Whist I agree with Andserson's urge for a soft start to this depreciation, I oppose having it enshrined in the guideline. I'd say that our best bet would be, for now, to seek consensus on talk pages first. By doing this we should expect to raise awareness of the evils of date linking instead of inspiring knee-jerk reactions against the depreciation. We've got a very good consensus here for depreciation of date autoformatting via linking but we've got that consensus ''here''. Our challenge is to spread it by reasoned arguement, we've got loads of strong arguement, but arguement does not necessarily win when put up against the knee-jerk reaction, which doesn't lightly bear retraction. Nonetheless, we don't need the MOS telling us to go easy. I think all of us are well wikied enough not to go about disrupting the place. The approach should be soft, the guidance must be strong. What we certainly don't need is a suggestion that date delinking requires a stronger than usual consensus. Bold edits are okay:

:<blockquote>Consensus is typically reached as a natural and inherent product of the wiki-editing process; generally someone makes a change or addition to a page, and then everyone who reads the page has an opportunity to either leave the page as it is or change it.</blockquote>

:It is not required that consensus be sought first as Askari Mark's wording would have us think. No, let's take it slow to start but not have the guidelines worded such as to keep it slow. ]<sub>&nbsp;]·]</sub> 18:43, 1 September 2008 (UTC)
::If you're the only editor who cares, you are consensus. At worst, this would commend asking on talk pages, and then doing the work after about 24 hours if there is no objection; it might be compatible with straight BRD. But the opportunity to tell other editors why DA is a bad idea is the most important part of the process; if msot of the editors were convinced, the problem would solve itself. ] <small>]</small> 16:56, 2 September 2008 (UTC)

Why is this just about "autoformatting"? Wouldn't it be much simpler to say, "Dates in wikipedia should not be blue-linked unless there is an important reason to do so, for example a discussion of the ]." -- ] (]) 01:48, 3 September 2008 (UTC)

:::Jimp, the reason I’ve been ] is two-fold: most obviously there’s the desire to avoid major disruption over the removal of DAs, but the second reason is that there has never been an attempt to query consensus for mass delinking. Some people here want that to happen (and to be able to read that into the new wording), but most of the discussion concerning it has been raised on stopping people who were going ahead and doing it. Remember, my aim was to capture what I understand the developed consensus to be. If the addition is unwanted, it can be removed, but at the least it made for summary of what was and was not explicitly in the consensus (and could have been useful for prompting discussion). As for “enshrining” it, well, DA has been “gospel” for a couple years; leaving this caution in for a few months (and removing it when consensus says it’s no longer necessary) is quite “kosher” IMHO.

:::In any case, it seems many folks here really would rather indulge in our local MOS version of the Bavarian face-slapping contest than actually work together collegially, so I see no need to continue with this particular effort. ] <small>]</small> 04:06, 3 September 2008 (UTC)

::::Where is this major disruption you talk of? ] ] 04:44, 3 September 2008 (UTC)
:::::Here is some hard evidence against the fear of disruption: ever since the guidance was changed to no longer recommend autoformatting, I've been routinely unlinking dates whenever I'm working on any article. I've done this with hundreds of articles, and I've had three or four questions, where I've explained my reasoning and it's been accepted, and two violent objectors who weren't prepared to discuss it reasonably at all, just reverted everything I did; and as for all the other articles, no response, pro or anti. These figures don't suggest to me that there's a significant danger of disruption from objections to large-scale unlinking. ] (]) 12:53, 3 September 2008 (UTC)

::::::Where is the consensus for rapid mass delinking, Tony? Colonies Chris, when the deletion of Fair Use articles began, there was only some grumbling, too, as editors only became aware of it as it ]; as it continued to logroll, the complaints and anger grew apace, and quite a few productive editors left over it. Today, whenever Betacommand/Betacommandbot ends up on AN/I, there’s a huge pile-on on him that results mostly from the antipathy he garnered implementing the removals. Which is truly a better approach – quick mass deletion (for which no consensus has been sought) and the risk of mass disruption, or going a ''little'' slower (maybe even taking the time to gain the consensus) and ] – same? ] <small>]</small> 15:03, 5 September 2008 (UTC)

I was one of the heavy date editors until a month or so ago. I hit the 2008 Atlantic Hurricane Season which I look at for reasons of interest and noticed that NONE of the dates were linked. I spent the last month looking for this article. I think that it would be useful to provide a way for dates to be listed in a reader's preferrable method, but I agree that linking everything that happened on ] to a list of bizarre events that occured that day is not useful. However, it would be useful to use a similar but different symbol to force all date to the format and possibly even calendar requested by the user.] (]) 05:40, 6 September 2008 (UTC)

:Another person here disagreeing with the delinking after seeing mass delinking on watchlisted articles.
:"pre-Georgian era" (1714/1830) should probably be changed to "pre-Gregorian era" (1582/1923).
:Will anyone mistake post-Gregorian dates for Julian dates because they're not formatted in ISO 8601?
:The massive delinking is causing middle-endian dates to show for people who've set up their date formatting otherwise, making it harder for some people to understand the encyclopedia's articles: "Until the software can how about not delinking, format unlinked dates?" (translated: "How about not delinking until the software can format unlinked dates?"). -- ], 2008-09-06]10:45z
::Before addressing your complaint, could I ask you to clarify whether the second and third points are connected with the removal of date autoformatting, or are a separate matter? What are "middle-endian" dates? ] ] 12:00, 6 September 2008 (UTC)
:::]: little endian (least important info first) 31 December 2008; big-endian (most important info first) 2008-12-31 (and alphabetical also = chronological); middle-endian or mixed-endian (mixed up) December 31, 2008. I'm not sure what you asked before that. -- ], 2008-09-06]12:28z
:::Re ]:
:::1: Kinda agree, I'm a programmer.
:::2: Agree, have dates autoformatted without links before massive unlinking.
:::3: Disagree, I'm fine with changing things if the changes are making WP a better encyclopedia. I've been editing WP since 2002 and things have changed drastically, nd if for the better I'm fine with it.
:::4: Not really, tho linked dates help scanning (other links to important articles help more) the kind of information in encyclopedias; as does sections, italics, bold text, lists, tables, images, captions, etc..
:::5: Kinda, I prefer RFC 3339 (ISO 8601) tho there's practically zero support for using that outside of refs. I don't like little-endian dates tho they're "bad as not as, middle-endian dates" (translation "not as bad as middle-endian dates"). My preferences are now being ignored with the massive delinking. Like the vast majority of people who read English, it's not my first language - I have to now read articles with middle-endian dates making reading and comprehension slower and harder. Compare how some language say numbers: 123 is not said 1 hundred 2wenty 3, but 1 foo 3 bar 2baz - making things very hard, expecially if your preference to have it said 1 hundred 2wenty 3 instead is removed. -- ], 2008-09-06]12:55z
::::Jeandré—thanks for explaining the endy thing, which makes perfect sense in retrospect. I'm sorry to be appear daft, but I can't locate the points you're responding to in your numbers 1–5. Thus, all I can provide by way of a rejoinder at this stage is that your personal preferences are noted, but our readers have to view the raw formatting. Forgive me, but they are all I care about! ] ] 13:08, 6 September 2008 (UTC) Ah, now I get it: the five bullets Jeandré is responding to are my take on why various people might disagree with the deprecation of DA. Sorry, I ''am'' daft. ] ] 13:11, 6 September 2008 (UTC)

=== Date format choice ===

<div style="border:thin solid; margin:0; padding:8pt 12pt;">
Since autoformatting dates by enclosing them in square-brackets is now discouraged/deprecated, agreement on the format of dates to be used becomes even more important. The discussion has gone on for a long while, and more participants are needed to arrive at a reliable consensus. ] (]) 01:06, 4 September 2008 (UTC)
{{RFCstyle|section=Format choice!!reason=Since autoformatting dates by enclosing them in square-brackets is now discouraged/deprecated, agreement on the format of dates to be used becomes even more important. The discussion has gone on for a long while, and more participants are needed to arrive at a reliable consensus.!!time=01:06, 4 September 2008 (UTC)}}
</div>

Three versions have been proposed:
*''Articles on topics with strong ties to a particular English-speaking country should generally use the more common date format for that nation; articles related to Canada may use either format consistently.
**Present text, widely approved ].
*''Articles on topics with strong ties to a particular English-speaking country should generally use the more common date format for that nation; articles related to Canada may use either format consistently.

:''Articles related to other countries that commonly use one of the two acceptable formats above should use that format.
:*This is what we used to have, and what Skyring reverts to.
*''Articles clearly written in a national variety of English should generally use the more common date format for that nation; articles in Canadian English may use either format consistently. Articles on topics with strong ties to a particular English-speaking country will therefore normally use the corresponding date format.''
**Woodstone's idea discussed ]. This would make articles in American use American dating; articles in a Commonwealth English (except Canadian) use international. So far nobody objects to this.

Comments? ] <small>]</small> 00:45, 31 August 2008 (UTC)

:Perhaps if you were a little more truthful, we might find a solution agreeable to all. The "straw poll" you created was roundly condemned for being confusing. You left out my proposed wording, which received more support than yours. There are further examples in previous sections. I can understand why some people have strong feelings about date formats, but that's all the more reason to keep things cool. Quite obviously, what we don't have is consensus on this point, which is why I keep restoring the original wording, which at least had the benefit of remaining untouched for nine months. Perhaps we could look at things on which we do agree and build up consensus that way? --] (]) 01:35, 31 August 2008 (UTC)

:Just catching up on all the date change stuff so I may be a little behind here. But if this is going to change it might be a good rule of thumb to follow conventions similar to what are used at ] for variant spellings. The biggest problem I see with eliminating the auto-formatting as it stands right now is that there are a bunch of articles where despite recommendations that date formats are a mismatch of ISO and other formats. This is seems especially common in reference sections where the date format may be prescribed vs the body text. If auto-formatting through links is not the best approach perhaps it might be possible to request an extension to wiki-media to provide an automatic formatting syntax that does not require links. ] (]) 05:20, 31 August 2008 (UTC)

::The conventions at ] have long been cited for date formats, and should be the basis for settling disputes. The guts of it is "strong national ties to a topic", so we pick the variety of English to suit the topic. The ] article is written in American English, the ] article in British English, the ] article in Aussie English, complete with differences in spelling, punctuation and syntax. By and large, date formats follow the variety of English, and there is little disagreement over whether an article relating to the English-speaking world should use day-month year or month-day-year.

::Problems arise when writing about topics linked to countries where English is not spoken. Obviously there is not a variety of English we can turn to for articles on Albania, Vietnam, Angola or Cuba. The convention is that the variety chosen by the first major contributor stands, and again, that has worked very well.

::However, for non-English-speaking nations, date formats are independent of the language. Spain uses day-month-year, the Philippines month-day-year, and China the year-month-day ISO format. Because this is the English-language Misplaced Pages, we use the English-language month names for dates in articles for these countries, so the local language is not a factor.

::In fact, the language is not a factor even for English-speaking nations. We know what date format each nation uses, and we use them. The variety of language does not determine the date format, nor vice versa.

::What is useful in the ] guidelines is the phrase about "strong national ties". If a nation uses one date format in preference to another, then we should use that date format in articles that have a strong national tie. The exception is for ISO dates, which are awkward when used in written text, though useful in tables and templates.

::The parallel I draw is with units of measurement. We give priority in writing to miles over kilometres in nations that use miles in preference to kilometres, and vice versa. The language is immaterial. What counts is what is used in the country we are writing about.

::One point repeatedly made is that there is no confusion between 7 December 1941 and December 7, 1941. Even if a reader prefers one format over the other, there is no doubt at all as to which day in history we are talking about.

::I think that removing the language qualifier from the existing wording is all we need to do:
::*'''''Articles on topics with strong ties to a particular country should generally use the more common date format for that nation; articles related to Canada may use either format consistently.'''''

::I'd like to think that this is just ], but ironically I find more useful wisdom in ], where it says, "Wikipedians come from diverse ethnic, religious, political, cultural and ideological backgrounds and have vastly different beliefs on everything from science to shoe shopping." That's the crux of the matter. We need to be tolerant, understanding and embracing of diversity, and if we write an article about an Italian or an American or a Angolan, it is common courtesy to use the forms of their country, to the best of our ability. --] (]) 06:12, 31 August 2008 (UTC)

:::I find much to recommend Anderson's principle of aligning engvar with date format (with an explicit note that Canada-related articles may use either date format). It's simple, clear, and can leave a small crack for non-compliance where there are good reasons not to comply.
:::Venezuela apparently uses US English but international date formats. But you know what? I couldn't give a dump if US date formats are used in that article, because the article is written in English, not Spanish, and is for people who can read English; if a US editor happened to start the article, good on him or her—that should be the end of the matter. Sorry, Pete, I also don't care what system Italy uses, nor what system it ''did'' use in 1850, if that's the topic context. I'm keen to decide this issue and move on, so I call now for objections to this course of action. Unless someone comes up with a significant problem, I intend to insert this into MOSNUM in about two days' time. ] ] 06:53, 31 August 2008 (UTC)
::::Venezuela uses US English???? I thought they used Spanish. For non-English-speaking nations, it is generally going to be a matter of personal opinion as to which version they use. I need only point to Japanese English, commonly known as which defies categorisation. You might not care which date format a country uses, but for many people, not least the Wikipedians living in that country, it is important. We are trying, I hope, to find a solution for those who care. Those Wikipedians who just go with the flow aren't the ones who generate conflict. I think it is important that we short-circuit future unpleasantness. --] (]) 07:12, 31 August 2008 (UTC)
::::::Pete, Sandy was pretty insistent that this is the case, where English is used in Venezuala. But Sandy's in transit at the moment, so can't comment. ] ] 09:23, 31 August 2008 (UTC)
:::::::But they speak ''Spanish'' in Venezuela. Any English is, like Engrish in Japan, going to be highly variable, depending on the background and the preference of the speaker. Hard, if not impossible, to find an objective answer for each country, especially if it's dependent on asking your friends for their opinions. And, more importantly, quite irrelevant as to the date format actually used in the country. If we are to make a choice on date format to use on a country by country basis, why not use the format the country uses, instead of basing our choice on the individual spelling preference of speakers of a minority non-official language? --] (]) 10:06, 31 August 2008 (UTC)
::::::::::And the dating format in Venezuelan Spanish should concern the Spanish Misplaced Pages, not us. ] <small>]</small> 20:32, 31 August 2008 (UTC)
:::::::::::If we are writing articles about Venezuela, we should use the format common in that country, so long as it can be expressed in English. We use the units of measurement common in Venezuela, we use the Venezuelan spelling of personal and place names, including diacritical marks not generally used in such as ], so why should we impose American Dating format on them if ]. Your proposal is out of line with established wikipractice. --] (]) 21:37, 31 August 2008 (UTC)
::::::::::::But this would effectively mean ] rules encroaching on articles that are normally not subject of WP:ENGVAR (e.g. articles about Venezuela) - hardly an established wikipractice itself. Personally, I find the English date format of "dd month yyyy" a bit odd; "month dd, yyyy" feels more natural to me, although this is ''not'' a common format in the country where I live (Croatia). Other editors might feel the same. Why should I (or anyone else) be compelled to write "dd month yyyy" in English articles about Croatia? ] (]) 12:41, 1 September 2008 (UTC)
:::::::::::::What format does Croatia use? Using that format seems the best and fairest way. --] (]) 10:29, 3 September 2008 (UTC)
::::::::::::::The format is dd. month yyyy, or dd.mm.yyyy (numeric). This would correspond to the "international" date format in English. But if you took a survey of the articles in the ] (of which, one might presume, most were written by Croatian editors), you would likely find that the "international" format is not too popular: Croatian editors could have used it if they felt it was the best, most natural format - yet they didn't. ] (]) 13:41, 3 September 2008 (UTC)

==== Where did this come from? ====
The of this page are quite clear. There was a controversy between two factions who wanted to use February 11, 1958 and 11 February 1958 respectively. Nobody advocated 1958 February 11; 1958-02-11 is even not mentioned as being one of the alternatives, although it is discussed later.

"To put an end to this debate, in July 2003, a new MediaWiki feature known as "dynamic dates" was implemented. This allows users to select in their user preferences which date format they prefer to see. Dates written in any of the above three formats are automatically converted to the user's preferred format as the page is displayed. The default is to leave it as written, although it may be slightly cleaned up and standardised."

That should be definitive. Anybody who wants to go back and see ''exactly'' when this language was introduced should feel free to do so. ] <small>]</small> 20:21, 31 August 2008 (UTC)

:That does clarify what the editors of the Manual of Style were thinking. What the developers who implemented the "solution" were thinking is another matter. It would be interesting to know if autoformatting of ISO 8601 dates was done right from the beginning, or something tacked on later. --] (]) 21:02, 31 August 2008 (UTC)
::As phrased, this suggests that ISO was an add-on, not yet implemented; the "three formats" mentioned above are September 2, 2008, 2 September 2008, and 2008 September 2. It might be possible to tell by seeing when the chart now in ] was substituted for the text in the link. ] <small>]</small> 16:27, 2 September 2008 (UTC)

==== Finally, can we arrive at a solution, please? ====
Here's a sequential four-test process to decide (in most cases, only the first one or two will be needed). They would replace the last two subsections in ], that is, "Strong national ties to a topic" and "Retaining the existing format".

<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
'''Which format to use''' ''''

Each of the following four tests should be applied in sequence until the format for an article is determined. However, this may be disregarded where are good reasons to do so (e.g., the US military usage of international format) and there is local consensus for this.
#Does the article have strong ties to an anglophone country? If not, or Canada-related, or if related to more than one anglophone country ...
#Which variety of English is the article written in? If unclear, or Canada-related ...
#What is the existing formatting in the article? If significantly mixed ...
#Use the original format by consulting the edit history.</div>

NB, ties to "more than one anglophone country" are exemplified by a British actor who spent most of their career in the US. I've just audited the dates in such an article, actually.

'''"Support", "Object" with reasons, or "Comment", please:'''
*'''Support''': Might be tedious sifting through to determine engvar. However, if that is unclear, you just go with the existing date format, or if it's significantly mixed, go with the format first inserted into the article. It's easy. ] ] 06:53, 31 August 2008 (UTC)
*'''Object:''' Here's my test: Which date format does the country actually use? That's a lot simpler and more accurate than linking it to the variant spelling of a minority non-official language. --] (]) 07:30, 31 August 2008 (UTC) ''''
<s>*'''Support''': Wikipedians living in a foreign country may come to English WP to read an article, yet it seems to me that if they see the date format in their native format, whether day-month-year or month-day-year, it is secondary (if even that) to the substance of the article itself. They read WP to learn about a subject and can understand either formats dating convention. The validity of the information is what is most important. The style of the article aides the reader in following the information in a logical presentation. I believe as long as there is continuity in style throughout the article, it matters little to them whether they read 7 August 2008 or August 7 2008. They both mean the same date. The insistence of the importance of seeing nation specific dating conventions does not bear out. I have read many, many articles related to non-English speaking countries that use the month-day-year style and have remained stable in that style for MONTHS after editing. If an outcry truly existed to adhere to a non-English speaking nations dating convention, wouldn't those non-English speaking nation readers have edited the article to conform? The argument presented for this convention would suggest, yes, a very strong YES. But alas, these articles remain unchanged as written. Where is this outcry from non-English speaking readers, and why aren't they here standing up for their belief? I see ONE native English speaking editor carrying the torch of a phantom conflict.--<span style="background-color: darkblue; color: white">]</span>|<small>]</small> 08:37, 31 August 2008 (UTC)</s>

:'''I withdraw from this merry-go-round'''. It's ridiculous to try and leave an opinion/argument when a response like the one below by Pete is made to refute it. The discussion was about whether to adhere to a non-English speaking countries dating convention, and now we have auto-formatting thrown in the mix when it in itself is being debated for general removal as useless in continuity of style for 90% of the users. --<span style="background-color: darkblue; color: white">]</span>|<small>]</small> 19:48, 31 August 2008 (UTC)
::Autoformatting was introduced in order to end conflict over date formats. See Pmanderson's notes Remove autoformatting and we return to the previous situation, along with an increased potential for conflict and disruption. You can hardly argue that it's been quiet for the years editors have been shielded from raw dates and so it's going to continue that way when we return to the old method. Looking at recent ArbCom cases, I'd say that Wikipedians have become ] rather than less. --] (]) 21:59, 31 August 2008 (UTC)

**''I believe as long as there is continuity in style throughout the article, it matters little to them whether they read 7 August 2008 or August 7 2008.'' The reason why we had date autoformatting in the first place is because a lot of Wikipedians cared very strongly about this precise point and autoformatting was introduced to end the bickering. Hardly a phantom conflict. --~~
*Basically '''support''' but I don't see how it's supposed to differ substantially from the existing wording.--] (]) 16:30, 31 August 2008 (UTC)
*'''Support''' in principle, since it ''is'' the same effect as Woodstone's proposal (the difference from the present language is that both proposals will institute national dating format on articles written in a national variety of English and the present wording won't); but this is going around Robin Hood's barn to achieve the same effect. ] <small>]</small> 20:27, 31 August 2008 (UTC)
**The language of the existing proposal is ''Articles clearly written in a national variety of English should generally use the more common date format for that nation; articles in Canadian English may use either format consistently. Articles on topics with strong ties to a particular English-speaking country will therefore normally use the corresponding date format.'' This is, when combined with the ''strong national ties'' clause of ], equivalent to the above four tests. But if people want to make things more explicit, my only objection is length. ] <small>]</small> 21:04, 31 August 2008 (UTC)
*'''Comment'''. I'm just puzzled as to why we have to be '''so''' proscriptive. Can't we keep it simple? Keep them in the same format, use an appropriate format to the article topic and if you don't know what that is use the format used by the first contrib unless consensus dictates otherwise. Yes, it likely is similar to what you have up there, but what you have up there is formalised too rigidly and doesn't allow for consensus to decide. Consensus should always decide, that's the content mechanism we use and is a founding principle. I'm fairly relaxed that consensus won't enforce British formatting on US articles or vice versa. ] <small>] </small> 23:31, 31 August 2008 (UTC)
**'''Comment'''. The problem is in the "appropriate format for the article topic" part. Some editors want to lock in existing styles, so if an article on (say) former French president ] uses month day year format although France uses day month year format, the article cannot be changed. That's why we have the rigmarole about varieties of English in the proposal above, to exclude using the actual format used by a country. --] (]) 00:33, 1 September 2008 (UTC)
***If they can get a damn strong consensus of Wikipedians that says fine, we all agree, then that's what should happen. How likely do you think that is? And if there's no consensus then we use an appropriate format to the article topic. Consensus comes first: '''ALWAYS'''. In this case trust that consensus will do the right thing. I do. I appreciate that this conflicts with some people's desire to ensure every article looks the same, but that was never our goal and contradicts the principles upon which Misplaced Pages was established. That isn't to say that such a desire is a bad idea, it is just that it shouldn't get in the way of the main thrust of Misplaced Pages: letting anyone edit. ] <small>] </small> 08:29, 1 September 2008 (UTC)
****Well, there's always someone coming along after to tidy things up. That's work I like doing. --] (]) 11:29, 1 September 2008 (UTC)
*Generally '''Support'''. I tend to agree, though, with Hiding that it seems overly proscriptive. The international style is common in certain circles in the U.S. with extensive contact with the “outside world”. With the modern military aerospace articles I’m most active in, I typically use it in preference to the U.S. style, even if it’s a U.S. topic – and have never had a complaint. In fact, I normally use it as well as in my professional work, as do many of my peers. It’s not that big a problem. In any case, I see two problems with the formula so far. First, it is that it’s overly focused on U.S. vs. Commonwealth; second, it ignores the large number of articles dealing with topics that are nationally “neutral” (e.g., science).
:A simpler approach might be something along the lines of: ''Articles on topics with strong ties to a particular country should generally use the date format most widely used in that country. In cases such as Canada, where both formats are common, either format may be used in a given article, although that choice should be employed consistently throughout. In other cases, the type of format initially used in the article should be used thereafter.'' ] <small>]</small> 00:19, 1 September 2008 (UTC)

*'''Comment'''. Looking further at the ] article, it's written using different date formats, different varieties of English - it has both "favor" and "honour", as well as "ize" and "ise" endings - and I don't know what variety of English France as a whole uses - French English, presumably - so it would fall through to the fourth rule above, in which case we look at the of 22 April 2002, in which is birth date is given as "Novermber 29, 1932" (sic). There must be vast numbers of articles in such a situation, where they were begun as stubs long before we worked out our current rules, and where development has proceeded using whatever style the editor thought was a good thing at the time. --] (]) 00:50, 1 September 2008 (UTC)
*'''Comment''' - I've only glanced at this debate, but I have to say I'd rather see ''a single'' date format used across all of en-Misplaced Pages. I prefer the day-month-year format (despite living in the US for most of my life) as there are technical advantages to it as well as being easy to get used to once you've been around it for a while. ] (]) 04:40, 1 September 2008 (UTC)

::Responses to Hiding, Mark Askari and Anderson: It seems that a little latitude for local editors to choose between the two standard formats as they see fit might be in order. Why not add the second sentence here to the lead, then: "Each of the following four tests should be applied in sequence until the format for an article is determined. However, this may be disregarded where are good reasons to do so (e.g., the US military usage of international format) and there is local consensus for this choice." Anderson, I do believe it's still shorter than the two sections it would replace—or at least not significantly longer. Its advantage is that it provides a simple sequence of tests that is likely to avert disputes. The sequence itself embodies the priorities. What do you think? ] ] 04:39, 1 September 2008 (UTC)
:::Sounds good to me, but, with apologies to Tony, I've always wanted to do this: you might want to add a word into the suggested sentence for better flow. And no, I won't let the door hit me... ] <small>] </small> 08:29, 1 September 2008 (UTC)
:::That additional license is already included in the short form in my !vote: it uses ''should generally be'' for that reason. The four tests are unnecessarily long; the first two, which are the most important, simply repeat ENGVAR; we can do that by invoking it explicitly. ] <small>]</small> 16:18, 2 September 2008 (UTC)

*'''Nearly support''', there should be latitude to use the so-called international format in fields where that is the norm, such as articles related to the American military. Since the MoS is only a guideline, I think there is always latitide to depart in unusual circumstances, but military articles are not unusual. --] (]) 18:52, 1 September 2008 (UTC)

]
*'''Fifty-Fifty''' - while the idea is good for places like the UK, I think (remembering a comment ) the simplest way to do it for non English-speaking countries would be for Africa, Europe, Oceania, the Caribbean and for most of Asia to use BrE and for the USA, Central and Southern America, Japan and China to use AmE ''(see map on right)''. ]] 11:00, 2 September 2008 (UTC)

* <s>'''Comment''':</s> '''Oppose:''' I fear it's going to be a never-ending swamp of editing, reverting, and counter-reverting, if to determine the proper format for an article, one has to go into a minutiae of rules, exceptions, and finding out who used which date format first.
: Instead, I propose we '''keep it simple:''' ''prefer the international format'' in all cases, except in articles strongly linked to the US, or any other ''English-speaking'' country that uses the M-D-Y format. Even if a non-English-speaking country X uses some other format, this is the ''English-''language wikipedia, so we shouldn't be unduly concerned about that format.
: I realise that Misplaced Pages is US-dominated, and that here as elsewhere, America's weight behind standards almost unique to itself makes things more complicated than strictly necessary. However, since Misplaced Pages ''is'' an international institution, with almost half of the en.wikipedia.org's contributions coming from outside the US, and the subject material covering the whole wide world and beyond, I think it should ''strive to use international standards as far as possible,'' in both measurement units and in language. This would make it simpler to determine which format to use in a certain article.
: So, what I would propose for the use of date formatting: '''''The international date format ("31 December 1999") should be used by default. Articles on topics with strong ties to the United States, ones concerning subjects where the international format is not the standard, should use the US format ("December 31, 1999").'''''
: And not to forget: ''Do not use date autoformatting, nor other techniques that make dates into links, unless the linked date has particular significance upon the context.'' ] (]) 12:47, 2 September 2008 (UTC)
: (Comment changed to Oppose. ] (]) 21:03, 2 September 2008 (UTC))
[[Image:Date.png|thumb|right|350px|{{legend|#4D6DF3|dd/mm/yyyy}}
{{legend|#008080|dd/mm/yyyy and yyyy/mm/dd}}
{{legend|#22B14C|yyyy/mm/dd}}
{{legend|#ED1C24|mm/dd/yyyy}}
{{legend|#6F3198|mm/dd/yyyy and dd/mm/yyyy}}
{{legend|#464646|mm/dd/yyyy,dd/mm/yyyy,yyyy/mm/dd}}]]
::'''Use the International DD-MM-YYYY format by default, unless the article is about something which has ties to another calendar format, in which case use that format''', so for science articles we use international, for US articles we use American format, for EU articles we use international format, and for China articles we use whatever they use in China. ] (]) 01:40, 3 September 2008 (UTC)
:::I take DD-MM-YYYY to mean that I would format 4 July 1776 as 04-07-1776. That format is unacceptable because it is too easy to interpret as 7 April 1776. --] (]) 01:45, 3 September 2008 (UTC)
:::Sorry I mean DD-MMMM-YYYY. ] (]) 01:55, 3 September 2008 (UTC)

* '''Support'''. As I understand it, this is more or less ] applied to dates. ] (]) 12:59, 2 September 2008 (UTC)

==== Discussion ====
Two (arguably three) of these tests amount to declaring dating format to be part of ] and then applying it. This is repetitious. I have put
:''*Articles clearly written in a national variety of English should generally use the more common date format for that nation; articles in Canadian English may use either format consistently. Articles on topics with strong ties to a particular English-speaking country will therefore normally use the corresponding date format; see ].''

as representing the consensus above, without repetition. If someone really wants to write out the tests explicitly, that's fine by me; the only objections would be whether the shorter form is more readable, and whether the long form allows the ''little latitude'' that Tony, correctly, advocates above. ] <small>]</small> 16:34, 2 September 2008 (UTC)

:Yep, I have to agree that it's more digestible and looks less bureaucratic. However, it needs to cover instances where the variety of English is unclear, which I'e done in the second bullet. The third bullet is just a release clause where local custom has consensus.

<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
'''Which format to use'''
*Articles clearly written in a national variety of English should generally use the more common date format for that country; articles in Canadian English may use either format consistently. Articles on topics with strong ties to a particular English-speaking country will therefore normally use the corresponding date format; see ].''
*Where the variety of English is unclear and there is no clear tie to a particular English-speaking country, use the format chosen by the first major contributor to the article.''
*A format may occasionally be used regardless of these guidelines where there is good reason and this is supported by local consensus (e.g., US military usage of international format).

Editors are reminded that edit-warring over date formats is utterly unacceptable; issues concerning individual articles should be brought to ].</div>

I'm assuming that the support for the four-test version above applies to this version, which differs only in the addition of marginal details. Thanks to Anderson, and to Hiding for initial conceptual input. ] ] 02:23, 3 September 2008 (UTC)

:This seems substantially good to me, and seems to follow consensus well. However, the first half of the first sentence seems to me to be saying the same thing as the second sentence – after all, all articles on WP.en are necessarily written in ''some'' “national variety of English”. Also, Canada isn’t the only English-speaking country in which more than one format is used; Canada is simply the largest and most noteworthy. Wouldn’t it be simpler to phrase the first bullet as
:''“Articles on topics with strong ties to a particular English-speaking country should use the date format most common for that country; see ]. Where two formats are common, such as in Canada, either may be chosen, but this should be used consistently throughout the given article.”''
:] <small>]</small> 03:24, 3 September 2008 (UTC)
:::*I also substantially agree. My only quibbles with Tony's draft would be length, again, and that we prefer an established style to first contributor when both exist: ''If an article has been stable in a given style, it should not be converted without a style-independent reason. Where in doubt, defer to the style used by the first major contributor.''
:::*Not all articles are written in national varieties of English: some successfully evade the points of difference; all too many are a hodge-podge: some Scottish, some American, some Australian. The latter should be cleaned up; but in the meantime, we should allow them to use either format consistently.
:::*My choice for a second paragraph would be ''Where the variety of English is unclear and there is no clear tie to a particular English-speaking country, use the existing dating format if one has been established in the article; if not, use the one chosen by the first major contributor to the article.'' Doubtless Tony can condense this. ] <small>]</small> 01:59, 4 September 2008 (UTC)
:::*I'm also not sure about the final clause:''issues concerning individual articles should be brought to ]'': do we ''want'' all that discussion here? This talk page is long enough already. ] <small>]</small> 02:01, 4 September 2008 (UTC)
::::I don't mind your suggestion for the second bullet, much as I hate to add another layer, and will insert it into Proposal 2 in the new section below. I'm hoping that the guidelines that emerge will minimise the uncertainty such that people rarely have to come here to ask for expert advice.

==== No consensus ====

::I can't see any consensus above. A lot of the support votes are weak and heavily caveated. I repeat the point I made earlier. With the removal of date autoformatting, we need to get our position on this issue '''right'''. Whether a country uses English or not is immaterial. What matters is the date format used in the nation, and everything falls into place. U.S. articles use month-day-year, UK articles use day-month-year, articles with a strong tie to nations using one of these formats use that format, and articles with a multinational focus or linked to a nation using ISO year-month-day format use whatever the first major contributor used. That's simple and clear and we don't need to argue about whether Japan uses American Engrish or British Engrish. --] (]) 10:23, 3 September 2008 (UTC)
:::That' funny—it looks like reasonable, although not overwhelming consensus for something the proposal. On the other hand, people have largely rejected your crusade, Pete: the articles are written in English, not Croatian, and date formats used in Croatian text are absolutely irrelevant to English-speakers. ] ] 12:04, 3 September 2008 (UTC)

::::The '''only''' English language part of date formats is the names of the months. English-speaking folk use January, February and so on. I have no idea what names Croatian folk use for their months, but we won't be using them here. Or in articles about Croatia. Date format doesn't depend on language. As we can see for ourselves, with the English speaking world using two different formats. 1/2/2003 means different things in different countries speaking the same language. What matters is what format is used in the country, not the language they speak. This is a discussion about date format, surely? Not language?

::::It's not consensus. Consensus isn't a matter of counting hands and seeing whether there are more Ayes than Noes. See ]. Let me quote from that page:
::::* In the case of policy and process pages a higher standard of participation and consensus is expected than on other pages.
::::*Developing consensus requires special attention to neutrality - remaining neutral in our actions in an effort to reach a compromise that everyone can agree on.
::::*a poll (if one is even held) is often more likely to be the start of a discussion than it is to be the end of one.
::::*Minority opinions typically reflect genuine concerns, and the logic may outweigh the logic of the majority.

::::Looking at the various "votes" cast, I see just one whole-hearted Support vote. Every other editor has expressed reservations and misgivings. However, looking at GregorB's vote, he says, "this is more or less WP:ENGVAR applied to dates". Except it isn't. The guts of ENGVAR is that we use the variety of English that an English-speaking nation uses when we write an article about that nation. I don't think that there is any dispute over which date formats we use for English-speaking nations. Canada is a special case and all are agreed that either format is acceptable. The dispute is over which date format to use for '''non'''-English-speaking nations. Trying to decide whether Croatian English (whatever that might be) or Japanese Engrish is closer to American English or British English is something that seems to me to be a difficult and pointless task.

::::Looking at what variety of English an article is written in is another concept entirely. You might have two different articles about French cities, one written in American English, one written in British English, depending on who wrote them. As France is not an English-speaking nation, either variety is acceptable. More likely, you'll get a mix of styles, reflecting the various contributions by various editors. I've already highlighted the ] article, written using a colourful variety of American and British spellings. And date styles.

::::Let me list some comments from the poll above, which you claim shows a consensus.
::::*''use an appropriate format to the article topic'' --Hiding
::::*''Articles on topics with strong ties to a particular country should generally use the date format most widely used in that country.'' --Askari Mark
::::*''I'd rather see a single date format used across all of en-Misplaced Pages. I prefer the day-month-year format (despite living in the US for most of my life)'' --SharkD
::::*''there should be latitude to use the so-called international format in fields where that is the norm, such as articles related to the American military.''' --Gerry Ashton
::::*''the simplest way to do it for non English-speaking countries would be for Africa, Europe, Oceania, the Caribbean and for most of Asia to use BrE and for the USA, Central and Southern America, Japan and China to use AmE (see map on right) --ChrisDHDR
::::*''The international date format ("31 December 1999") should be used by default. Articles on topics with strong ties to the United States, ones concerning subjects where the international format is not the standard, should use the US format ("December 31, 1999").'' --Teemu Leisti
::::*''Use the International DD-MMMM-YYYY format by default, unless the article is about something which has ties to another calendar format, in which case use that format.'' --NerdyNSK
::::That's seven opinions that basically say the same thing - link the date format to the topic or the nation, '''not''' the variety of English. Add in my opinion, and you've got eight voices out of the thirteen editors who participated in the survey.
::::In fact, I really like Askari Mark's suggested wording, which seems to sum up the mood very well:
::::*''''Articles on topics with strong ties to a particular country should generally use the date format most widely used in that country. In cases such as Canada, where both formats are common, either format may be used in a given article, although that choice should be employed consistently throughout. In other cases, the type of format initially used in the article should be used thereafter.''''
::::My only addition would be to exempt countries such as China, which uses YYYY-MMM-DD format. That format is fine for tables and templates, not so good for written text. In such cases we should use whichever format came first. --] (]) 00:07, 4 September 2008 (UTC)

::::: <u>"Link the date format to the topic or the nation, '''not''' the variety of English."</u> Exactly. And only pay attention to the nation if it's an English-speaking nation; otherwise, use the international format by default.
::::: To me, this is similar to the choice of using metric vs. US customary. "International" means exactly that; prefer that format over others.
::::: I also agree with what you say about consensus. As there are only a few people participating in this debate (I myself stumbled upon it by happenstance a couple of weeks ago), why don't we add one of those requests-for-help that someone used a little while ago? ] (]) 00:40, 4 September 2008 (UTC)
:::::: Just did it myself. ] (]) 01:06, 4 September 2008 (UTC)

: I partially support the version in the box. I would replace the second bullet point by this: '''Where the variety of English is unclear and there is no clear tie to a particular English-speaking country, use the international format.''' The article subject should be the only criterion for determining the date format. ] (]) 23:18, 3 September 2008 (UTC)
::This violates a very long-established principle of Misplaced Pages: ''The English Misplaced Pages has no general preference for a major national variety of the language.''. ] <small>]</small> 02:11, 4 September 2008 (UTC)
:::We're not talking about varieties of English here. All varieties of English use the same month names, spelt the same way. We're talking about '''date formats'''. Using the date format appropriate to the topic or the nation seems like plain common sense, and a course best calculated to avoid causing offence/offense. --] (]) 02:47, 4 September 2008 (UTC)
::::Shorter Skyring: ''Do it the way ''I'' do; it's only common sense,'' Next you'll be telling our American co-editors that they should have had sense enough not to rebel against George III. They have ]. ] <small>]</small> 02:54, 4 September 2008 (UTC)
:::::Heh. You know, I think the boot is on the other foot. George III should have done everything he could to have held on to the Thirteen Colonies. He should never have allowed such foolish and unjust laws. He should have listened to and acted on the advice of the colonial leaders to keep them happy members of the Empire. It would have made the Napoleonic Wars and the First and Second World Wars very different. Better yet, they might never have happened. I'm wholeheartedly on the side of the colonists. They did the right thing in a difficult situation, and they established the first of the modern liberal democracies. I've stood in the hall at the Archives and looked on the Declaration of Independence, thinking of those brave and far-sighted men. I've got facsimiles bought from the gift shop of the Declaration and the Constitution, and they are treasured possessions of mine. Because the Americans fought for liberty, we Australians gained our independence without a bloody struggle. We and the world have much to thank America for.

:::::But we're talking about ''date formats''. Not the American Revolution. Not the way we spell honor. Please keep your mind on the task, and if you disagree with me and your fellow editors, please be civil about it. That's just common courtesy. --] (]) 03:31, 4 September 2008 (UTC)
:::::::Date formats and the ways we spell honour are equally distracting if the unexpected one shows up without explanation; I trust this sentence demonstrates itself. We have guidance on such subjects: don't mess with an established style. Please stop your crusade. ] <small>]</small> 03:44, 4 September 2008 (UTC)

==== Call for comments: two (now three) possible solutions ====
''By Tony1:'' I believe that Pete is overstating the objections to the engvar proposal. Mark Askari, for example, has given in-principle support to it, yet he's counted as an objector. Pete and Teemu are proposing much more radical change, which would be capsized by significant objection among North American editors. I've been bold and put what I think is Pete's proposal into words as Proposal 1, which is surprisingly short and simple. I've restated the previous "engvar" proposal as Proposal 2 below it, with a slight adjustment per PMA. I'm keen to resolve this soon—this should have been done years ago.
:With respect, I don't support the "international format for all but U.S. articles" proposal. It would lead to unrest. I've put forward a number of proposals, all along similar lines. I'm astonished that you haven't noticed. I'll take the liberty of adding my own (Proposal 3), based on the existing wording by Mark Askari. --] (]) 05:06, 4 September 2008 (UTC)
:Proposal 3 says nothing about ''new'' articles that are not country-related, and where the existing usage is mixed or otherwise unclear; can you address this, please? ] ] 05:24, 4 September 2008 (UTC)

::''Articles on topics with strong ties to a particular country should generally use the date format most widely used in that country.'' Surely that covers new articles as well as existing. It's pretty much the same wording as has been in place for nine months and presumably new articles have appeared during that time. Where formats are mixed or unclear, I'd assume that a wikignome or bot will come along and sort it all out in due course. I wouldn't get too wrapped around the axles about it. --] (]) 01:01, 6 September 2008 (UTC)

'''PROPOSAL 1: International date format except for North-America-related articles'''

<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
'''Which format to use'''
Articles should use the international date format, except that those with clear ties to the United States should normally use the US format, and those with clear ties to Canada may use either format.</div>


'''PROPOSAL 2: Determine by the variety of English; if unclear, use the existing format, or the initial choice of format'''

<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
'''Which format to use'''
*Articles clearly written in a national variety of English should generally use the more common date format for that country; articles in Canadian English may use either format consistently. Articles on topics with strong ties to a particular English-speaking country will therefore normally use the corresponding date format; see ].''
*Where neither the variety of English nor the tie to a particular English-speaking country are clear, use the existing date format; if this is unclear, use the one chosen by the first major contributor to the article.''
*A format may occasionally be used regardless of these guidelines where there is good reason and this is supported by local consensus (e.g., US military usage of international format).</div>

'''PROPOSAL 3: Determine by national preference. If general or ISO, use existing format'''

<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
'''Which format to use'''
*Articles on topics with strong ties to a particular country should generally use the date format most widely used in that country.
*In cases such as Canada, where both formats are common, either format may be used in a given article, although that choice should be employed consistently throughout.
*Where a nation uses ISO (numeric year-month-day) format, or there is no strong tie to a particular nation, the type of format initially used in the article should be used thereafter.</div>


'''My comments:''' Proposal 1 has three considerable advantages over the existing Proposal 2, and in the case of No. 3, the proposal by Teemu above:
#It's beautifully short and simple, and is likely to be understood and remembered by WPians at large. The twists and turns have disappeared, and the chain of contingency measure where engvar or existing formatting are unclear can go.
#The decision is always a one-step process on the basis of the title and the opening, not potentially four-step where an article is not US-related, involving the analysis of the text for the first sign of US or non-US English (sometimes you read and read and still there's no clue), and if that doesn't work, determining whether the formatting is mostly one or the other, or is in a mess, in which case you have to hunt through the edit history to determine which format was used initially.
#It side-steps the can of worms in having to determine which system a non-anglophone country uses, or did use at the time of the topic (modern China? modern Iran? medieval France? ancient Egypt?).
#It resonates with the international aims, scope and reach of WP (although this is a minor advantage, I think).

There are three significant disadvantages to Proposal 1:
#It is likely to offend some North American editors.
#It renders many many articles in breach because they use US format but lack "clear ties to the United States or Canada". (However, the human-supervised automated removal of DA would address this at no marginal cost, over time.)
#It means that many articles will be written in US English but will have international dates, which may be perceived as inconsistent. (However, this doesn't appear to raise eyebrows in many Canadian articles, given the considerable similarity of Canadian and US spelling, and in some US military articles, e.g. ] I audited yesterday and did not touch. Is this a big deal?) ] ] 04:22, 4 September 2008 (UTC)

==== Comments, "supports", "objects" ====
I ask for your forbearance in again commenting on, or better, ''stating your preference for'' one of these two solutions. It's a matter we should have decided many years ago.

*Support Proposal 2. <s>On reflection, I prefer Proposal 1 for its</s> despite the practical simplicity of Pr. 1. ] ] 04:22, 4 September 2008 (UTC)

*My problem is with how to define 'strong ties' as opposed to 'clear ties'. The existence of multiple 'strong' ties in this globalised world for many subjects would imply much ambiguity and confusion. This rules out option 2, for me. Under option 3, we would find ourselves using ISO in articles related to China, where ISO is closest to the default way of looking at dates. However, let us not forget that this is English wikipedia, where the appearance of dates in this third (and uncommon for English-speakers) format would appear very peculiar indeed. So I too, would favour proposal 1 for its simplicity and unambiguity. ] (]) 05:49, 4 September 2008 (UTC)
**Proposal 3 specifically excludes ISO dates. Perhaps the wording needs to be tweaked to make this clearer? --] (]) 10:18, 4 September 2008 (UTC)
***Clause 2 under option 2 is a bit of a cop-out IMHO, and could still result in edit wars if a contributor comes in and offers a major re-write and expansion of an article which was previously ambivalent. Under proposal 3, Chinese articles could well see a tendency to opt out of one or other by going for yyyy mm dd, the standard for China - not exactly ISO, but was what I was getting at. ] (]) 02:22, 5 September 2008 (UTC)

* Proposal 2 is alright, because it ensures that the date formats should match the English variety used. But does this really need so much discussion and angst? We're never going to use dates like "07/02/2008" owing to their inherent ambiguity. So long as we use the full name of the month, there's very little confusion likely to result from the use of either date system in an article. This doesn't need to be turned into a US vs Everyone Else battle. - ] 06:05, 4 September 2008 (UTC)

* I'd go for Proposal 2. It is basically an application of ], an already well-established guideline. The current situation with date formats is probably closest to Proposal 2, while Proposal 1 is furthest from the current practice. Proposal 1 would introduce "consistency", but it would work at the expense of WP:ENGVAR: it is tantamount to preferring "color" over "colour" or vice versa. ] (]) 06:46, 4 September 2008 (UTC)

*Proposal 2. For reasons excellently expounded by Gregor.--] (]) 07:33, 4 September 2008 (UTC)

*Proposal 3. For ease and simplicity. The variety of English is immaterial when considering date formats, and difficult or impossible to determine for articles on non-English-speaking nations. Use the correct format for the nation. --] (]) 10:16, 4 September 2008 (UTC)

*Prefer Proposal 1, then Proposal 3, then Proposal 2. This is mostly on the basis of simplicity. Proposal 1: it is easiest to have a default with a small set of exceptions (the other two options do not have a default). Proposal 3: it is easier to determine a country of an article (sometimes just from the title) than the tests in Proposal 2. I have been trying to stay out of this debate but I decided to express my preference now. Frankly, I don't care strongly whatever you decide ... even no requirement for consistency would be fine with me (that would be the zero option with no visible change for most readers), as long as the links are removed. ] (]) 13:41, 4 September 2008 (UTC)

*Proposal 2. In addition to the reasons at ] (mostly the analogy of ENGVAR); either of the others would involve massive changes, which are likely to be both controversial and error-prone. Pete's talk page already contains evidence of both, and that's just one editor. If Proposal 2 seems too long, we can leave out the second paragraph, which is only an application of our heading; also, this is clearly set forth in the next subsection now; we could just leave it where it is. ] <small>]</small> 14:25, 4 September 2008 (UTC)

*Proposal 2. Requires fewest changes to existing articles, and avoids the requirement for editors to figure out the date format of a non-English speaking country (which may turn out to be unusable if the year comes first, or the country has no consistent way of writing Gregorian dates). --] (]) 14:35, 4 September 2008 (UTC)

*I '''support''' Proposal 3, or failing that Proposal 2. This isn't a dictatorship. ] (]) 17:40, 4 September 2008 (UTC)

*Proposal 2: '''support''' for same reasoning as GregorB --<span style="background-color: darkblue; color: white">]</span>|<small>]</small> 23:27, 4 September 2008 (UTC)

* Not surprisingly, <u>I support Proposal 1,</u> whose pros and cons were well summarised by Tony. In my view, simplicity is the most significant of these. (It would be even simpler to have a rule that says "Use the international format for all articles.", but that's an unrealistic aim.) I would perhaps add a point similar to one used in Proposal 2: "The international format may be used in US-realted articles where there is good reason and this is supported by local consensus (e.g., US military usage of the international format)."
: And remember, this is just about the order of the day and the month; if we can get this finally nailed down, we can then proceed with beautifying Misplaced Pages by unlinking dates. ] (]) 01:12, 5 September 2008 (UTC)
:*AFAICT, the two issues revolve around dates, but are independent. There is nothing stopping the de-linking of dates in American and British articles. Only Canadian and a few other ones are ambivalent. ] (]) 09:19, 5 September 2008 (UTC)

*'''Comment''' Looking at ], I find that there is only one variety of English used (apart from minor regional variations). So why does Proposal 2 allow two date formats? It's because Canada uses '''two''' different formats. Clearly date format is not linked to the variety of English. It is linked to the country. Could those editors supporting Proposal 2 explain this? And if we name Canada for special treatment, then why not name other nations? --] (]) 10:52, 5 September 2008 (UTC)
:*For me, it's because Canada is an English-speaking country, so its dates are English dates. I see no reason to attempt to imitate the format of a country's ''non-English'' dates when writing English.--] (]) 11:16, 5 September 2008 (UTC)
:::But Canada doesn't have "English" dates. Canada uses both American and British dates. The date formats allowed by Proposal 2 for Canada don't link date format to the variety of English, they link it to the country.
:::Pete, tell me, what date format was used in medieval France? And what about current practice in arabic, which doesn't use the same numerical symbols (even though what we use are ironically called ''arabic numerals'')? ] ] 12:29, 5 September 2008 (UTC)
::::Again, I wouldn't get too wrapped around the axles about mediaeval France - or any other subject where there are no clear links to a given date format. After a while it gets ridiculous, like trying to work out what date format you would link to articles written in (say) Thai English. --] (]) 01:09, 6 September 2008 (UTC)


What format should be used for ]? ] (]) 14:54, 5 September 2008 (UTC)

*''Le 14 juillet'', which makes international the closest, I guess. ;-) ] (]) 16:18, 5 September 2008 (UTC)

So which proposal are you relying on for that? ] (]) 16:24, 5 September 2008 (UTC)

:I think we most all concur that the key unresolved issue is with what date format to use when there’s no natural tie to US/UK/Canada. Essentially these come down to the following: '''Option 1''' imposes the “international” date format as the common default except where the US and Canada are concerned; '''Option 2''' recommends following WP:ENGVAR and where that doesn’t apply, the following the choice of the first editor to make one; '''Option 3''' calls for whichever is used in that country and initial use for “neutral” topics.

:While Option 1 certainly offers the benefit of simplicity and brevity, I’m afraid it begs for reopening the ENGVAR conflict between those who would prefer it and those who might prefer a US-favoring alternative – e.g., “Articles should use the US date format, except that those with clear ties to other English-speaking nations should normally use the international format, and those with clear ties to Canada may use either format.” (After all, they can point out, Misplaced Pages.en ''is'' domiciled in the U.S.) It’s a dead-end debate. Option 3 is the most open-ended, and in general I personally have no real trouble with it, it has the distinctive drawback of requiring editors to know what date format is – or formats are – preferred in a given country. If it weren’t from these debates, I wouldn’t know China uses an ISO-style (I suspect its origins may predate ISO), nor would I know how to determine this since I neither read nor speak the language. In effect, when it comes to application, this option incurs the complication of requiring additional research before plunking down a date – which can be a really difficult challenge for non-English-speaking countries.

:Option 2 offers the benefit of a tie-in to WP:ENGVAR, a fairly simple, already well-known and widely accepted rule, so it doesn’t require learning a new set of rules; moreover, it was established as the result of minimizing edit warring, and so might be able to extend that promise here to date formatting. However, the wording of Proposal 2 is only one way of expressing Option 2, and it is one I’ve earlier taken exception to in that it requires expertise in recognizing English dialects. Let’s face it, most editors can be expected to differentiate between “American” and “British” English, but Scottish or Australian from “British”? This is an unnecessary complication for date formatting. Accordingly, I’d like to offer a variant of Proposal 2 to incorporate some language from Proposal 3 that gets around all of this and keeps it simple. ] <small>]</small> 21:15, 5 September 2008 (UTC)

'''PROPOSAL 2A: Determine by the variety of English; if unclear, use the existing format, or the initial choice of format'''

<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
'''Which format to use'''
*Articles on topics with strong ties to a particular English-speaking country should generally use the date format most widely used in that country. (See ].) Where two formats are common, such as in Canada, either may be chosen, but this should be used consistently throughout the given article.
* In all other cases, either the American or the international style may be chosen; the type of format initially used in the article should be used thereafter.
*A format may occasionally be used regardless of these guidelines where there is good reason and this is supported by local consensus (e.g., US military usage of international format).</div>

I agree with you that Proposal 1 might have problems. But Proposal 3 definitely not more difficult to apply than Proposal 2. The default assumption that everyone seems to agree on is that a country will use dmy unless we discover otherwise. It is extremely useful to have a default. In a less than a minute, using Proposal 2, I can search just by title and create a list of 1000 articles that need a date audit into consistent dmy. Using Proposal 3, I have to examine each article in detail. It might take me ten minutes to puzzle over english-variants (some of which I can't even detect as variations because they look normal to me) and then 20 minutes investigating edit history. ] (]) 22:02, 5 September 2008 (UTC)
:Again, I would like to work in ''established formats'' per the header and the section on Retaining the existing format (which we can just leave as it is). Otherwise we get the problem about "he cheated back in 2002" that has repeatedly come up in ]. But this can be dealt with easily if the principle has consensus. ] <small>]</small> 22:27, 5 September 2008 (UTC)
::If we stick with "established formats", then Misplaced Pages never changes. The idea was to stop people changing dates expressed as BC and AD to BCE and CE. And back again. That caused a lot of disruption, eventually reaching ArbCom level. The "without good reason" exception to such changes allows format changes where there is a strong link to a particular format. An article on scientific methods in archaeology would be expected to use "BCE/CE", and an article about ], BC/AD. We've reached a similar duality in date formats for use in text. It's either 1 January 1901 or January 1, 1901. Using the YMD format 1901-01-01 in text looks odd in written English, though it works fine in templates and references. To my mind, where there is a strong link to a country, using the same date format as that actually used in the country makes a lot of sense. We don't need to differentiate between English-speaking countries and the rest. And, as noted, Canada speaks English, but uses both formats, so the language link breaks down in at least one case. We're not going to use French or Chinese or Arabic month names, so there is no reason at all to tie date format to language.
:::Correct me if I'm wrong, but I view "locking in existing formats" as shorthand for "battling to retain American date format", because most editors were American when Misplaced Pages was young, and that situation remains. American editors, in creating an article, will naturally use the date format they are best familiar with, even if it is inappropriate for the topic. Most editors don't go off and digest the Manual of Style before making an edit - they just do it. It's pretty easy to find articles on British subjects that use American dates, and that's because the initial editor was an American, or thought that American format was the norm. That quintessentially British poet, ], for example. ], ], ]. Did they act in knowing opposition to the MoS, or did they just do what they thought was best? The MoS is really for those experienced editors who care about things like presentation and professionalism and consistency, and I resent it being used to try to push one format over another when both are valid or (as in the case of articles on European topics) the one being "locked out" is actually the better choice. --] (]) 01:36, 6 September 2008 (UTC)
:::* In support of Skyring’s post above, I’d hate to see editwarring, but the ''primary'' rule should be that date formats are article-appropriate. If some American editor managed to be the first major contributor on some particularly European topic, why not change the dates to make them fit better with the subject matter? It seems this “locking in” business is the product only of trying to keep editors from behaving like kindergardeners. If we really have to do that, then so be it. If not, let’s let articles improve. <span style="white-space:nowrap;">''']''' (])</span> 02:26, 6 September 2008 (UTC)

Greg, we lock in engvar for articles unrelated to an anglophone country, and it works very well. I see no tension between US ''or'' international date format for an article on China or Egypt, or for that matter medieval France. I like Mark Askari's Proposal 2A, because it's probably easier, where there's doubt, to quickly go back to the first date inserted than to hunt through hoping to find the word "color/our" or some such. ] ] 04:58, 6 September 2008 (UTC)

* I see. Very well. <span style="white-space:nowrap;">''']''' (])</span> 00:45, 7 September 2008 (UTC)

: Askari Mark wrote: ''"Option 2 offers the benefit of a tie-in to WP:ENGVAR, a fairly simple, already well-known and widely accepted rule, so it doesn’t require learning a new set of rules; moreover, it was established as the result of minimizing edit warring, and so might be able to extend that promise here to date formatting. However, the wording of Proposal 2 is only one way of expressing Option 2, ... Accordingly, I’d like to offer a variant of Proposal 2 to incorporate some language from Proposal 3 that gets around all of this and keeps it simple."''
: Proposal 2B is almost there. ''However,'' I'm still not convinced we should have to look at initial use to determine later date use. This will make for inconsistent date styles even closely related articles, just based on the accident of what format the first date was in.
: Edit-warring can be mitigated by the existence of a clear, widely-supported rule in the style guide: one only needs to point to it.
: Furthermore, as I wrote earlier, Misplaced Pages is an international institution, and its subject material covers everything possible. So, I think it should strive to use international standards as far as possible. And as Greg L wrote earlier today: ''"In support of Skyring’s post above, I’d hate to see editwarring, but the primary rule should be that date formats are article-appropriate. If some American editor managed to be the first major contributor on some particularly European topic, why not change the dates to make them fit better with the subject matter? It seems this “locking in” business is the product only of trying to keep editors from behaving like kindergardeners. If we really have to do that, then so be it. If not, let’s let articles improve."''
: It seems we're close to reaching a solution here; let's not blow the opportunity to get it right once and for all.
: So, I make Proposal 2B by varying Proposal 2A's second point:

'''PROPOSAL 2B: If the subject is closely tied to an English-speaking country determine by the country; otherwise, or if unclear, use the international format.'''
<div style="background-color:honeydew; border:thin solid forestgreen; margin:0; padding:8pt 12pt;">
'''Which format to use'''
* Articles on topics with strong ties to a particular English-speaking country should generally use the date format most widely used in that country. (See ].) Where two formats are common, such as in Canada, either may be chosen, but this should be used consistently throughout the given article.
* In all other cases, use the the international style.
* A format may occasionally be used regardless of these guidelines where there is good reason and this is supported by local consensus (e.g., US military usage of international format).</div>

: So, which is it? 2B or not 2B? ] (]) 09:26, 6 September 2008 (UTC)
::I'm prepared to support this one as a compromise, though what about the Philippines, which use U.S. format? --] (]) 06:53, 7 September 2008 (UTC)
::: Thanks. If the Philippines the US format is the one generally used in the Philippines, then, per the first bullet point, that would be the format to be used in articles concerning the Philippines. ] (]) 07:38, 7 September 2008 (UTC)
::::Mmmm, but they speak Spanish in the Philippines. --] (]) 08:31, 7 September 2008 (UTC)
::::: But the article on ] asserts that Spanish was discontinued as an official language in 1973, and "Since then, the two official languages are Filipino and English." ] (]) 13:23, 7 September 2008 (UTC)
::::::Ah. What do I know of the Philippines? Thanks for that! I should have checked Misplaced Pages, hey? --] (]) 17:26, 7 September 2008 (UTC)

* '''Support Proposal 3''' with suggestions
**'''Proposal 1'''
***I'm confused by the wording
****"North-America" could be confused with Canada.
****What does "related to" mean?
*****Instead of "related to," I suggest "an overriding association with"
**'''Proposal 2'''.
***The last two words of the first sentence have a back reference to "that" country. Which country is "that" country?
***This proposal seems to suggest, for example, that an article written about Chicago in a non-American style should remain in that style. I'm a Texan and I'll betcha you're glad I ain't plannin' on writin' an article about Cambridge, England.
***Instead of "tie to," I suggest "overriding association with"
***What is "local" consensus? The interested editors? The people geographically local to the topic?
***Instead of "existing format," I suggest "prevailing format"
**'''Proposal 3'''
***"ational preference" in relation to what?
***Instead of "strong ties," I suggest "overriding association".
***Instead of "Initially used," I suggest "prevailing usage"
**Generally
***There should be consistency within an article
***A reference to a periodical's publication date should retain the format chosen by the publisher. (I don't mean a mention in the article, but in the ''formal'' cite/reference.)
***Intelligent exceptions don't need to be mentioned, as they're covered by the ] pillar. Let's target an intelligent audience with reasonable judgment. I think this guideline will be best if aimed at consistency instead of at replacing judgment.
*I prefer '''Proposal 3''' with these suggested changes. --] (]) 15:15, 6 September 2008 (UTC)

Dan, I don't think there's a guideline saying that you have to format a reference the way the publication does. As long as the information is there, you're actually expected to change "Vol. 2, No. 1" to "2(1)" if that's the way you're formatting your whole reference list in a journal article or book. What one ''musn't'' touch is the spelling in the title of a paper/chapter and journal/book/conference proceeding (because it affects the searchability). But upper/lower case can and should be changed to conform to your house style. What I'm getting at is that the date format should be consistent within a ref list on WP, where possible, and it doesn't matter if it's changed to that which prevails in the main text. ] ] 15:37, 6 September 2008 (UTC)
:Okay, I think that such format should be preserved, but perhaps this isn't the proper forum for that discussion --] (]) 15:41, 6 September 2008 (UTC)
::Both the '']'' and the '']'' have substantial sections about the publicaton date of various kinds of publications, and neither mention paying the least bit of attention to the date format in the work being cite. Following the format of the source is an undesireable departure from the normal practice of writing. --] (]) 15:43, 6 September 2008 (UTC)

=== How are we going, consensus-wise? ===

Leaving aside date autoformatting, which is a whole different kettle of worms, I think we're making solid progress on at least agreeing on some basics.

'''Points of agreement'''

* ISO (year-month-day) format should not be used in written text: " Misplaced Pages was formally launched on 2001-01-15, as a single English-language edition at www.wikipedia.com." Although unambiguous, is unusual in written English.
* We should use either 15 January 2001 (International format) or January 15, 2001 (U.S. format) for written text.
* We should use an appropriate format for an article.
* Where an article concerns an English-speaking nation, we should use the format commonly used in that nation. Except for Canada, which officially uses both formats, so either format is acceptable, if used consistently.

'''Points of disagreement'''

Where an article concerns an non-English-speaking nation
# Use International format
# Use whatever format matches the variety of English used in the article
# Use the format used in that country
# Use the format used by the first editor that added a date to the article <small>(this line added, but not supported, by ])</small>

'''Changes from existing wording'''

The wording that stood for nine months was:
*''Articles on topics with strong ties to a particular English-speaking country should generally use the more common date format for that nation; articles related to Canada may use either format consistently.''
*''Articles related to other countries that commonly use one of the two acceptable formats above should use that format.''

The full text may be found at ]. Preceding sections deal with Misplaced Pages's preferred format (which equates to either 15 January 2001 or January 15, 2001) and subsequent sections deal with retaining date format unless there is a strong national tie. I think that the preceding and subsequent sections have strong consensus.

The long-standing wording has been challenged by one editor, and we are now engaged in a struggle to find a replacement wording, with various different proposals made, roughly equating to the points of disagreement above. We have had arguments for and against each point, and support for each point seems roughly even, with no clear consensus. --] (]) 01:51, 7 September 2008 (UTC)

==== Comments ====

My own preference is for "3. Use the format used in the country."

Using International format throughout Misplaced Pages would lead to disruption unless strongly enforced. Likewise using U.S. format throughout.
Tying date format to the variety of English used for English-speaking nations merely removes the decision one step beyond the real indicator: what format is actually used in that nation. The U.S. uses U.S. format and the U.K. uses International format and we don't need to look at the variety of English to see that this is true. --] (]) 01:51, 7 September 2008 (UTC)

:An example of Venezuela and Croatia was provided earlier in the discussion. I know what date format is used in Croatia: this is because I am Croatian. However, I don't know about Venezuela, just as I'm sure many don't know about Croatia - and I don't see why anyone should. Are we required to know what date format is used in 200+ countries of the world? Should there be a crib sheet for forgetful editors? ] (]) 02:57, 7 September 2008 (UTC)

::Looking at ], we find a list of nations sorted by format. Most nations use International format, so it's really a matter of remembering the exceptions, such as the U.S. and China. --] (]) 06:44, 7 September 2008 (UTC)

* That's a good summary of the state of the discussion. Except that there was a fourth opinion on the format to use for articles concerning non-English-speaking countries, which I added to the list.
: We seem to have a consensus on most of the points, with only that one remaining. I support choice 1, "use international format", but I will not stand in the way if others clearly prefer some other choice. That said, I'll recap my reasoning: using the international format is (a) simple to remember and administer, and (b) international, as Misplaced Pages is. ] (]) 07:38, 7 September 2008 (UTC)
::We avoid decreeing international styles in other matters when the English-speaking world differs among itself. I don't see why date formats should be an exception. (It may be that Teemu Leisti thinks we ''should'' discard ENGVAR and construct an International English. I will oppose that, but this is not the place to discuss it.) As for the first point, it's all a matter of habit; I doubt American style is inherently harder, since those who use it find it easier. ] <small>]</small> 19:57, 7 September 2008 (UTC)

A point that is not agreed upon, but which I advocate: Although all-numeric dates in the format YYYY-MM-DD are allowed in citations, tables, and infoboxes, they may be interpreted as being governed by ] so they should never be used in an article for years less than 1583, and should only be used to represent dates in the Gregorian calendar. --] (]) 21:35, 7 September 2008 (UTC)

:I'd agree with this - in fact, there is a case for deprecating ISO 8601 dates altogether. As an editor, I like ISO 8601 (even if only in tables) - as a reader, less so (with DA effectively deprecated). But this is a separate issue, of course. ] (]) 22:17, 7 September 2008 (UTC)

::Concur with both above, after a little thought. If using ISO 8601 dates can lead to confusion, then we shouldn't use them at all, lest we mislead our readers. But of course this is a separate issue. --] (]) 23:34, 7 September 2008 (UTC)

* '''I agree''' with the “Points of agreement”. I don’t think it needs to be any more complex than that. I also don’t think that just because a UK editor (for instance) might be the first major contributor on an article on a national U.S. park and used the word “colour” a few times in the article means that the dates in that same article should be international format; the English-dialect spelling is a separate issue that shouldn’t darken the doorstep of what should be a straightforward rule-set on date formats. For those who might object to this notion, consider the opposite case; this same rule would apply to the reverse situation. As a major contributor to ], I used American English (“color,” “realize,” etc.). Does that fact mean I should have used U.S.-style dates for an article that doesn’t have a strong association with the U.S. because I used American English? Of course not. If anything, the kilogram has more to do with France than anything. So I used international date formating in ''Kilogram''—but American spelling. While one newbie of a British editor not long ago tried to editwar over UK spelling, the article has been quite stable and no one has '''''ever''''' raised a stink over the international date formats in ''Kilogram''; slight differences in date formats where the month is properly spelled out confuses no one. I think we really should just keep it simple with date formating; there is just no compelling reason to make this issue any more complex. <span style="white-space:nowrap;">''']''' (])</span> 05:35, 8 September 2008 (UTC)

=== Decision on date format for non-English-speaking countries ===

I don't see the point of discussing this much longer, particularly since it's largely a matter of personal taste. The clear majority above support proposals which ''don't'' make the format used dependent on non-English date formats. Can we declare at least this issue settled (and thus stop the current edit warring over what version is the "existing" one?)--] (]) 09:39, 7 September 2008 (UTC)
:What's a "non-English" date format? I don't think anyone is proposing to use non-English date names. Nor is there any "clear majority" on wording, though I think that Proposal 2B is looking good as a compromise. --] (]) 09:50, 7 September 2008 (UTC)
::Well, you seem to want to use non-English date formats as a criterion for deciding which English date format to use. At least, that's how I understand your preferred wording.--] (]) 09:56, 7 September 2008 (UTC)
:::I'm puzzled. We have International day-month-year, American month-day-year, and the ISO year-month-day. Which one do you think is "non-English"? --] (]) 10:02, 7 September 2008 (UTC)
::::I think Kotniski is referring to "non-English-language" date formats. ] ] 10:22, 7 September 2008 (UTC)
::::Well, what's a "non-English-language" date format then? DMY, MDY or YMD? I think I can see what you're getting at, but if the French use day-month-year, calling it a non-English format and ruling it out of the English-language Misplaced Pages is a bit of a stretch. I support using the format actually used in the country - which works regardless of whether they speak English or not - in exactly the same way that we use the temperature scale used in a country. The French use Celsius, but using your argument, each article would use whatever scale went with the variant of English used in that article, which I guess would be okay if you wanted to impose Fahrenheit on countries that use Celsius. Or impose month-day-year on countries that use day-month-year. --] (]) 10:30, 7 September 2008 (UTC)
:::::I think we've been through this already. Units are a different case altogether - choice of unit affects understanding, not just formatting style. The majority seem to support the view that date format should be treated like we treat spelling - just as we don't use the French spelling "couleur" as a guide to how we spell "colo(u)r" when writing about France, so we don't use the French "1 janvier" as a guide to whether we write "1 January" or "January 1". --] (]) 10:39, 7 September 2008 (UTC)
::::::I don't see this at all. And we've been through this before - NOBODY is advocating using non-English month names. Let me put it another way. When the French or Germans or Polish write a date, they write it as (say) 7.12.1941, and of course that means 7 December 1941, not 12 July. We don't want to use a French or German or Polish month name, because this is the English-language Misplaced Pages, but we do want to use the same date format they use, in exactly the same way we want to use the same date format people use in the United Kingdom for articles about the United Kingdom. We're an international site, after all. The language is immaterial, because we're never going to use anything but English here. And no, I don't see a majority of people here linking date formats to spelling. Not unless there's a new way of counting. --] (]) 11:30, 7 September 2008 (UTC)
::::::::I meant most people support proposals 2 or 2x, rather than proposal 3 which is the only one that concurs with your view. So I misunderstood your interpretation of the "current" wording. You now imply not that "'10 janvier 1999' gives '10 January 1999'", but "'10.1.1999' gives '10 January 1999'". That seems to me even less logical, since we're talking about quite different formats. Observe that in Britain we always write day before month when writing just figures (except in ISO), but it is not uncommon to see month before day when the month is written out. In other words, English speakers don't expect the written-out format necessarily to correspond to the numerical format.--] (]) 12:00, 7 September 2008 (UTC)
:::::::::Looking at how many people support tying the date format to English variety, it's nowhere near a majority. I'm guessing that you've counted me into your side because I've said that Proposal 2B is one that I can live with. We could work through each editor's views if you like. In any case, it's certainly not consensus. A poll is the starting point for discussion, not the end, as ] notes. I'm confident that we are making progress, but we aren't there yet. I'm sorry that you keep misunderstanding me. Maybe there's another way I can put it:
:::::::::*There are three elements in a date:
:::::::::**Day
:::::::::**Month
:::::::::**Year
:::::::::*There are three common ways of arranging these elements:
:::::::::**Ascending order: day-month-year International format
:::::::::**Descending order: year-month-day ISO format
:::::::::**Mixed order: month-year-day American format
:::::::::*By and large, each country will use one order in common use (say, on official forms). 1-2-3 means:
:::::::::**1 February 2003 in the UK
:::::::::**2 January 2003 in the U.S.
:::::::::**3 February 2001 in China
:::::::::*Yes, there are always alternate formats in wide use in a country. The U.S. military uses day-month-year, English-language newspapers (even in England) use month-day-year, and July 4th and the Fourth of July are interchangeable all over. But, in general, each country has a preferred way of arranging dates, and although exceptions can always be found, trying to pretend that the UK commonly uses American format or vice versa is not likely to convince anyone with a working brain.
:::::::::*In Misplaced Pages we use the date format commonly in use in English-speaking countries in articles strongly tied to that country. Apart from Canada, where both formats are used officially.
:::::::::*The variety of English does not dictate the date format -as Canada demonstrates.
:::::::::**On the contrary, this demonstrates (if true) that the ''Canadian variety of English'' does not prefer a format. The others do not ''dictate'', without exception, but they do strongly prefer. (It's not impossible to find, for example, ''honour'' in American either; but articles in American really should not use it, all the same; the exceptions here are on the same level.)
:::::::::*The names of the months in non-English-speaking countries are irrelevant. We're not going to use them in this English-language Misplaced Pages.
:::::::::**Yes, indeed, they are. That Skyring and he alone dragged them into this discussion shows him a sophist. ] <small>]</small> 20:23, 7 September 2008 (UTC)
:::::::::*I say that, like the English-speaking countries, we use the same rule for non-English-speaking countries.
:::::::::*In fact, this is the rule we've been using for nine months.
:::::::::*I cannot see any consensus for changing this to link article date format with variety of English.
:::::::::*What I can see are a few ]ic editors who feel every change of American format to International format as a blow to their vital organs and want to use every possible tool in their belt to stop this happening. This is about as helpful to our International encyclopaedia as declaring officially that we support one religion over another or that the Yankees are superior to the Red Sox.
:::::::::::This is an explicit appeal to construct an International English. Misplaced Pages is not an experiment in language reform; our purpose is to build an encyclopedia, in the English that now exists. Even if we had not agreed, long ago, not to prefer any dialect of it, Pete is wasting our time, and that of the editors whose work he complicated, in order to accomplish what he alone considers the ]. ] <small>]</small> 20:23, 7 September 2008 (UTC)
::::::::::::No. I quite reject this. I'm certainly not advocating that Misplaced Pages use an International English - whatever that might be. We reflect the world - we don't try to change it, except insofar as we provide an encyclopaedia for everyone, which may change the world in a small and positive fashion. We use the varieties of English found in English-speaking nations in articles about those nations. Full stop. --] (]) 23:26, 7 September 2008 (UTC)
:::::::::In short, I say that articles strongly tied to a country should use the date format in common use in that country.
:::::::::*Apart from ISO year-month-day, which looks awkward in English-language prose. --] (]) 17:21, 7 September 2008 (UTC)
:::::::::**As 7 September 2008 looks awkward in American, and September 7, 2008, does in British and Australian. ] <small>]</small> 20:28, 7 September 2008 (UTC)
Since Skyring claims not to understand what Kotniski is saying, let me explain. Only a week ago, Skyring was arguing that Kotniski is answering that contention, which would, if pushed, lead to writing in Spanglish; as indeed all too many of our articles are. I fully concur that the dating format used in Venezualan Spanish (which is an instance of what Kotniski means by "non-English date formats") should not determine our usage.

Skyring's attempt above, to claim that "non-English date ''formats''" somehow means the Spanish names of the months is frivolous. It convinces me that Skyring has ceased to argue in good faith; if there is another reversion, I will therefore consider which venue of dispute resolution to employ. ] <small>]</small> 20:14, 7 September 2008 (UTC)

: That's a rather inflammatory accusation, Pmanderson/Septentrionalis, and one I do not see supported by the facts. For instance, see section "How are we doing on consensus?" above, which is a good, productive summary by Skyring/Pete of the state of the discussion so far.
: This whole enterprise is rather getting to be like arguing the number of angels that can dance on the head of a pin. However, precisely because it raises so much emotion, and because it concerns text elements that are used in nearly all articles, we should aim to arrive at a MoS guide that is easy to understand and to apply, and acceptable to a great majority of reasonable people.
: Can the participants please read the section "How are we doing on consensus?" above, and say if they agree with the presented points of agreement and disagreement? ''If'' we are agreed on that much so far, then we can go at the final points of disagreement, hopefully in a spirit of mutual respect, cooperation, and Assuming Good Faith. ] (]) 20:50, 7 September 2008 (UTC)
::Thanks, Teemu! Pmanderson seems to have quite misunderstood what I've said. --] (]) 23:18, 7 September 2008 (UTC)

:::'''Lets examine Proposal 2B'''. The American date format will be used when an article specifically applies to an American subject, otherwise the International format of Day-Month-Year will be used for all other articles(Oops, sorry lets not forget that Canadians can use whatever little ole format they care to use when it involves their countries ties). I think that's what, 90% or more of all articles will now be International format? So now Americans need to just throw out their taught format and get with the Day-Month-Year format, or stick to the 10% or less of the English Misplaced Pages that applies to American formatting if they don't like it. Of course for editors like Pete, who come from a country that uses Day-Month-Year format, maybe thinks, so what's the bother, huh? Could it be the fact that we Americans like to sit down at our computers and contribute to this English Misplaced Pages and feel comfortable whether we're writing about the rainfall statistics for Montana (US), Queretaro (MX), Wales (UK) or any other country, state or city upon this planet, without having to second think the dating convention most of us have used our entire lives? We are writing it in English. This is an English Misplaced Pages and I assume the entire English speaking inhabitants of this planet knows that 12 January 2008 and January 12, 2008 mean the same date. Why can't Americans sit down and write a new article on any subject matter we like, reference the content, add images, tables, or whatever manner of wiki-markup we like, using the dating format we are most comfortable with? What distracts most from editing and reading a Misplaced Pages article, is the variant of usage and non-continuity of dating format within an article, not which is used continuously throughout. If an article was begun using Month-Day-Year, or if it began using Day-Month-Year, then that is the format. This isn't algebra, calculus, chemistry or any other complicated formula that must be written in exacting form to derive a meaningful result. This is simply the presentation of a date, in English, where BOTH forms are understood throughout the English speaking populations of the world. It's nonsense. Stick to what came first with consistency throughout an article and we'll all deal with a little less policing, disruption and edit warring, and create an encyclopedia. Are we here to get bogged down in the bureaucracy of debating something that is understood and simply applied?--<small><span style="background-color: darkblue; color: white">]</span></small>|<small>]</small> 02:59, 8 September 2008 (UTC)
::::When people get emotional about date formats, it's hard to see their comments in an objective fashion. OK. Looking at the logic employed here, where you say that 10% of articles would be in U.S. format and consistency is a good thing, then that looks to be a powerful argument to make '''all''' date formats International. As for people editing articles, I don't think that too many worry overmuch about what date format they are using. Most would just put down their dates however they like regardless (or, more likely, ignorant) of what the Manual of Style says. Getting good content into Misplaced Pages is what really matters, and those who care about presentation and formats and styles can go through and tidy up later on. As has been repeatedly pointed out, nobody is going to get confused over the date format, whether it's 12 March 2004 or March 12, 2004. I think that, just as we say July 4, 1776 for an article about the U.S. then so too should we say 31 August 1997 for an article about England, 26 January 1788 for an article about Australia and 14 July 1789 for an article about France. In each case, that is the format actually used in the country. We're an international effort, you agree? --] (]) 03:21, 8 September 2008 (UTC)
:::::Yes, but an English-language international effort. The point I wanted to settle concerns just the last of your examples - 14 July 1789 for France. Of course it's not 14 July 1789 in France, it's (I guess) 14 juillet 1789. Is this French format of any relevance to us, writing in English? You say it is; the clear majority in the foregoing discussions support proposals that imply that it isn't. Can't you just accept that you're outnumbered on this one and let us focus on the other remaining points of disagreement?--] (]) 07:28, 8 September 2008 (UTC)
::::::I wouldn't insult the intelligence of your fellow editors if I were you. Let me ask you two questions:
::::::1. Is 14 July 1789
:::::::a) day month year format or
:::::::b) month day year format?
::::::2. Is 14 Juillet 1789
:::::::a) day month year format or
:::::::b) month day year format?
::::::No need to answer - no matter what you say, you aren't going to be able to convince anyone that the date format used in France is anything other than day month year. --] (]) 11:54, 8 September 2008 (UTC)
←Oh, no one will disagree with ''that''. But you miss Kotniski's point entirely: it's of absolutely no consequence to the writing of text in English. I and, I'm sure, many other contributors here are tiring of this roundabout and your slightly narky tone, probably brought on by your sneaking suspicion that you're fighting a losing battle. I ask you to adopt a more reasonable stance and to help us move the debate towards a solution: what appears to be your anti-American drive will not gain traction (if it's not anti-American in intent, it certainly is in effect; please remember that about 70% of native anglophones are American). Oh, and one last thought: do foreign-language Wikipedias use the prevailing date-format in the country that an article is related to? Um ... no, they most certainly don't. Check for yourself. ] ] 12:10, 8 September 2008 (UTC)
:The simple fact is that here in the English-language Misplaced Pages, we use the date format appropriate to the country. We use month day year for the U.S. and we use day month year for the U.K. And we use the appropriate format for other nations. Have done so for years. Here's how the wording developed:
:'''2004''': ''It's generally preferable to use the format used by local English speakers at the location of the event. For events within Europe and Oceania, that is usually 11 February 2004 (no comma). For the United States it's usually February 11, 2004 (with comma).''
:'''2005''': ''It is usually preferable to use the format preferred in the variety of English that is closest to the topic. For topics concerning Europe, Australia, Oceania and Africa, the formatting is usually 17 February 1958 (no comma and no "th"). In the United States and Canada, February 17, 1958, (with two commas—the year in this format is a parenthetical phrase) is correct, and in Canada, 17 February 1958 is common..''
:'''2006''': ''If the topic itself concerns a specific country, editors may choose to use the date format used in that country. This is useful even if the dates are linked, because new users and users without a Misplaced Pages account do not have any date preferences set, and so they see whatever format was typed. For topics concerning Ireland, all member states of the Commonwealth of Nations except Canada, and most international organizations such as the United Nations, the formatting is usually ] ] (no comma and no "th"). In the United States, it is most commonly ], ]. Elsewhere, either format is acceptable.''
:'''Early 2007''': ''If the topic itself concerns a specific country, editors may choose to use the date format used in that country. This is useful even if the dates are linked, because new users and users without a Misplaced Pages account do not have any date preferences set, and so they see whatever format was typed.''
:'''Late 2007''': ''Articles on topics with strong ties to a particular English-speaking nation should generally use the more common date format for that nation.''
:'''2008''':''Articles on topics with strong ties to a particular English-speaking country should generally use the more common date format for that nation; articles related to Canada may use either format consistently. Articles related to other countries that commonly use one of the two acceptable formats above should use that format.''
:The attempt to link date formats to the variety of English dates from a couple of weeks ago and has no consensus. --] (]) 13:28, 8 September 2008 (UTC)

* “International?” This is en.Misplaced Pages. Whereas there are a great deal of English-speaking Chinese, they ''do'' after all, have their own version of Misplaced Pages in their native language. I really don’t see a compelling case for using inappropriate date formats in articles closely tied to a particular country just because an article was authored by a particular editor who used a particular dialect of English with particular spelling. Just because a particular editor resides in central Africa and speaks with tongue clicks shouldn’t influence the date format used in ] (which currently uses the international date format, which I think is asinine).<p>And I know Tony disagrees with me on this point, but I don’t see the need for using international date formats in an article on a U.S.-related subject (like a U.S. national forest), just because a UK author was the first major contributor and used the spelling “colour” in the article. Autoformatting (and its linking to mind-dumbing trivia) is history. That’s good. Now we authors have to look at what we are making everyone else see. As for the formatting of dates, far too much turf war-mentality has pervaded the editorial community here. It should be one, simple rule:{{cquote|If it is an article closely tied to the U.S. use the U.S.-style date format, otherwise, use international date formats in articles.}}

:There’s no legitimate need for any more complexity than that. If we are to start keying the date formats used in articles to the dialect of English the editor happened to use while writing the article, all the articles I’ve been writing (science-related topics) would have U.S.-style dates because I use U.S.-style spelling. That makes no sense. Keep it simple. Dragging English-language dialect complexities into this discussion is totally unnecessary. <span style="white-space:nowrap;">''']''' (])</span> 19:14, 8 September 2008 (UTC)
::Looking at the ] article, it seems to have U.S. format throughout, which is entirely proper. But that's by the by. I still can't see any consensus for any particular way of doing things, and certainly not for any major change to the long-standing text, and the even more long-standing way of doing things, which is to have date formats tied to the nation's preferred format. If those who want date format tied to the variant of English chosen by the first editor are going to edit-war over this without first gaining consensus, then it looks like we're going to have to get some loftier eyes looking over it. I'd like to think that we can come to an agreement without doing this - after all, as I've shown, we kept more or less consistent practise for several years without refighting the ] over trivial issues - but progress on agreement seems to have stalled, with personal attacks becoming bolder. I'm also annoyed that this attempt at change is consuming time that could be spent more productively by all editors. The removal of date autoformatting is a thorny enough issue - why does it have to be made even more complex by changing a long-agreed way of doing things? I'm going to restore the wording back to the way it was, and if edit-warring breaks out again before we have a consensus for the change, then we can take it further and higher and make an admin or two earn his/her keep. --] (]) 00:23, 9 September 2008 (UTC)

::* I was wondering why the hell you saw the dates differently on the ] article. Blame the damned autoformatting. Though I happen to be an American, I had my user prefs set to international-style dates. Thus, because I am part of that 0.1% *privileged elite* that seemingly deserves to have a special view of the page no one else sees, I was seeing what regular readers don’t see. I just turned my date prefs off and I encourage all other editors to do the same so we always see what IP users see. In this particular case (the Sept. 11 article), the default date that most readers see is the appropriate one for that particular article. <span style="white-space:nowrap;">''']''' (])</span> 03:18, 9 September 2008 (UTC)

=== Arbitrary section ===
No idea where in the above morass I should have put this, so apologies for starting a new section. I was directed here after having date links removed, and am utterly incredulous that autoformatting is being abandoned. I ''strongly'' oppose such a move. Granted, there are problems with linking all those dates to irrelevant articles, but that just means that a new improved autoformatting system should be developed and then phased in. The current system is not perfect. But not having any autoformatting at all is much worse. Furthermore, why was no-one ever informed of this until people started removing the links? The sheer volume of debate this has generated would appear to indicate that it is a controversial change that should have been better thought out. ] ] 22:46, 8 September 2008 (UTC)

: I copy the responses to ]:

: ''This has been debated for years, Necrothes. And it is finally coming to an end. The “linking” of dates is unwise and the autoformatting of dates was a terribly unwise decision made two years ago to resolve editwarring. Because of autoformatting of dates, 99.9% of Wikipeida’s readership (regular IP users) were often seeing unsuitable date formats in articles. Further aggravating the problem is we editors ''couldn’t even <u>see</u> the problems'' because our preferences settings were blinding us to this fact. The first step in fixing these articles is to unformat (delink) the dates. Then we simply write out the date in a method that is most suitable for the topic. The current MOSNUM wording…''

:{{quotation|Articles clearly written in a national variety of English should generally use the more common date format for that nation; articles in Canadian English may use either format consistently. Articles on topics with strong ties to a particular English-speaking country will therefore normally use the corresponding date format.}}

: ''…is just fine; there should be absolutely no editwarring over the issue. See my above, expanded response (with the fascinating picture of Tokugawa Ieyasu) for more info on just why autoformatting was—and remains to this day—a piss-poor set of tools that never should have been made in the first place. Greg L (talk) 17:11, 5 September 2008 (UTC)''

: ''Necrothesp, I appreciate that you were unaware of any discussion, but discussion on depreciating autoformatting of dates, already longstanding, drew in a large number of editors on this page through July/early August as it moved towards consensus. It was then posted to the ] and to ] through August. Additionally, several Wikiprojects were individually made aware of it, as were a large number of individual article writers. Thus, autoformatting was depreciated. 86.44.27.255 (talk) 19:37, 5 September 2008 (UTC)''

:: ''Not to mention the fact that de-linking was even the subject of a "successful" petition to the developers that the developers simply ignored, in 2006. This is by no means some sudden change. — SMcCandlish ‹(-¿-)› 21:40, 6 September 2008 (UTC)''

: ] (]) 03:27, 9 September 2008 (UTC)

::None of which explains why autoformatting should be removed, or why dates should be unlinked before a new system is in place to handle them. Furthermore, dozens of items are posted to VP every day, how was anyone supposed to spot a single far-ranging policy change amongst all the rest? ] ] 20:24, 9 September 2008 (UTC)

=== Proposal to stop mass unlinking dates for 30 days and no other changes ===

After taking a few days away from this topic, I've come back in the hope of helping move this group forward. In that light, '''I propose a 30 day hiatus from mass unlinking of dates'''. This proposal in and of itself does not address any of the other concerns, justifications, proposals, etc. Offering support for this does not mean support for anything else, other than you want to start helping this group of people getting larger every day start rebuilding a working consensus here. I personally believe that there is a middle ground here although we have not found it yet. '''Please keep replies to one line with support/oppose/neutral'''. As an aside, and hopefully in good humor, please feel free to put the date you've replied in whichever format you prefer. ] (]) 01:19, 9 September 2008 (UTC)

DA design process was fatally flawed; rip it out. ] JD 2454718.564595

:I can't disagree with Gerry's comment: all is said in nine words. What I don't understand is the passion behind a few editors who are shouting from the rooftops about the moves by a number of editors to improve WP thus. They have gone as far as to mount an RFC against me, although as yet uncertified. There, the demand was for "a few days"; now I see the demand has blown out to "30 days"; next, they'll up it to what? ] ] 02:01, 9 September 2008 (UTC)
::I think that hanging would be too merciful in your case. One must always consider the possibility that a good drawing and quartering may be beneficial, ''pour encourager les autres''. ;-) b--] (]) 02:16, 9 September 2008 (UTC)
:::Support a 30-day moratorium. None of this is personal, it's about what is the best thing for Misplaced Pages's readers. BTW, I don't have a choice of date format ;-) the <nowiki>~~~~</nowiki> signature uses dd month year. If I had a choice, I would use yyyymmdd (all numeric). ] (]) 02:22, 9 September 2008 (UTC)
::::No, it's about what's best for wikipedias's readers. Anyone remember them? --] (]) 02:31, 9 September 2008 (UTC)
:::::Sure do. I have amended my comment. ] (]) 02:39, 9 September 2008 (UTC)
::::::Sorry, Truthanade, just adding "readers" provides no substantive ''reason'' for a moratorium, so we're left wondering whether this is entirely to preserve the "preferenced" display of dates for a few WPians who can't stand "the other guys' month-day order". The readers should come first, not editors' whims, and your addition of the word "readers" is hollow without a cogent argument. ] ] 02:43, 9 September 2008 (UTC)

:::It has been pointed out to me that my comment above may be open to misinterpretation. Just to be clear, my view is that this is another attempt at procrastination, another demonstration of the unwillingness of some to face the self-evident facts of the matter. I see that my attempt at what I thought was humour was misplaced, for which I apologise. Let me now say loudly and clearly that date autoformatting was a poor work-around to fix a non-problem that was only half understood, and that it ought to be eliminated asap, for the benefit of our readers. No need for more pointlesss delays. --] (]) 02:57, 9 September 2008 (UTC)

* Autoformatting of dates is like dumping garbage from New Jersey into the ocean. Just because the practice had been done for a long time and there’s lots of garbage at the bottom of the ocean, doesn’t mean it was ever a good idea. It’s time to stop. <span style="white-space:nowrap;">''']''' (])</span> 03:10, 9 September 2008 (UTC)

* I wasnt aware of ] until I went to Tony's talk page to ask about it. Bad timing I guess, I would not have suggested that approach. Please ] when considering this proposal. My main concern is the loss of the structured data, which I think does have value. As I said on Tony1's talk page, I agree or am neutral on many of the arguments here, but the tone of voice in this group is very unhelpful. Sarcasm, analogies to garbage, and snide remarks don't help you convince people, but they do start to convince people they're better off staying away. I really do believe there is a middle ground here that addresses the concerns people have raised. I just wish people were willing to work them out without trying to argue louder and longert. Ironically, the more people who find out about this due to the mass date unlinking, the more times that argument will take place. ] (]) 03:28, 9 September 2008 (UTC)

* '''Strong support''' &mdash; this was the goal of the RFC anyway. --] (]) 15:17, 9 September 2008 (UTC)
* '''Support''' &mdash; there is a nearly identical proposal (by UC_Bill actually) that also includes a test where we turn off DA for some time, to see what the reaction from editors is positive or negative. --] (]) 01:58, 10 September 2008 (UTC)

* '''Would accept ten days' moratorium''': I find it puzzling why this discussion is getting so nasty and personal. If we haven't sorted this out in 10 days, what makes anyone think it can be resolved in 30?? &mdash; there is nothing like a looming deadline to concentrate the mind. ] (]) 02:12, 10 September 2008 (UTC)

Pointless procrastination, be it 30 days or 10 days long. If this hasn't been sorted out in several years, what makes you think it will be now? The faultiness of DA has been thoroughly explained. Benefit of the readers? I don't see how. --] <sup>]</sup> 08:32, 10 September 2008 (UTC)

* '''Support'''. At the very least, the linked dates should not be ripped out, but changed to a template, so we can put back the ones where ] subproject guidelines suggest they ''should'' be there. — ] ] 20:44, 10 September 2008 (UTC)

* '''Oppose''' Agree with Eleassar. No compelling need to prolong this another 30 days. ] (]) 21:50, 10 September 2008 (UTC)

== Edit-warring on national ties. ==
I think it's about time the page was protected until consensus is agreed on the wording. I can't see '''anyone's''' proposal having support enough to warrant a change to the status quo. Changing the wording to your preferred version and hoping nobody notices a controversial change is no solution. Neither is edit-warring until one side drops from exhaustion. That's not the way we do things here. At least it's not the way things should be. --] (]) 23:59, 28 August 2008 (UTC)

(Later) I've made a ]. It is obvious that a dispute exists and we should sort it out ourselves, rather than force some poor admin to trawl through the mess to make a decision via AN/I. --] (]) 00:21, 29 August 2008 (UTC)
:It is obvious that one editor, perhaps two, disagrees with the majority. That is not usually cause for page protection. It is also obvious that Skyring reverted three times and then called for protection; that's not done. ] <small>]</small> 02:38, 29 August 2008 (UTC)
::You have repeatedly deleted text without consensus when there are several alternate wordings being discussed. Looking at the history of the wording, inserted by Tony in December last year, you let it ride for nine months, despite being a frequent contributor to this page. Why is it suddenly something you needed to edit-war over? I suggest it is because you noticed that I was changing articles on European subjects to European date formats, and you couldn't bear the thought. You edit-warred over my changes, which were in concurrence with the MoS, and then you edit-warred over the Manual of Style. --] (]) 04:27, 29 August 2008 (UTC)
:::You have repeatedly declined to recognize that ]. There is considerable evidence that it has, most clearly the ] above, but also the discussion at ANI; there is no evidence the old consensus, whoever it was, remains. Changing established formats is disruptive; you successfully disrupted the article on the South Ossetian war for some days. Please stop. ] <small>]</small> 13:00, 29 August 2008 (UTC)
::::I disagree with your assertions above, I don't see consensus support for '''any''' option, but we now have an opportunity to find a solution that doesn't involve edit warring. Hopefully one that both of us, all of us, will feel part of. --] (]) 00:05, 30 August 2008 (UTC)

I've restored this section from archive to give some context. I think that we are making good progress on agreeing on points in dispute and that it is not helpful to edit war over the wording without consensus. I'm happy to see the long-standing wording changed to something that reflects discussion and consensus, but when an editor keeps changing the wording to suit his preferred POV, then this is not helpful in keeping discussion calm and civil. I ask that we keep the long-standing wording until we find consensus, whatever that may be.

Alternately, we could all edit-war our hearts out until one side or the other gives up in disgust. --] (]) 00:01, 8 September 2008 (UTC)
:Pete, I inserted the sentence only when Sandy put a robust case about Venezuala's date formats (international) vs the prevailing engvar used in that country. I did not intend that it have the implications it has turned out to. I agree with what Anderson says above; I wish you'd accept that you're outnumbered vastly in what seems to be an anti-US push, and that you're behaving aggressively. ] ] 11:21, 8 September 2008 (UTC)
::I don't see this at all, actually. Support for tying date format to varieties of English looks pretty soft. I see a lot of different views. As for aggressive behaviour, no, I think you should look elsewhere. What's your preference - edit-war over the wording or discuss it? --] (]) 12:25, 8 September 2008 (UTC)

== Misconception vis a vis date formats ==

Apologies for only having skimmed the above discussions, but I don't have hours upon hours to peruse it in detail. As such, I'm only going to comment on a recurring conception I noticed that I don't think is entirely accurate. Specifically, there seems to be an idea that MMMMM dd, YYYY, formatted dates are "the American way" of writing things. While I don't dispute that the format is dominant in the United States, it's not universal. I myself use dd MMMM YYYY dates and have since high school. Admittedly, it's uncommon, but the differences in date formats among nations are not nearly as consistent as the differences in spelling. ] <sup><small><small>]</small></small></sup> 13:14, 8 September 2008 (UTC)
:I don't know about that; the differences in spelling aren't absolute either. ''Honor'' isn't universal in American, although I would only consider ''honour'' in a tone more appropriate to wedding invitations than an encyclopedia; ''-ize'' is found in British English, largely on the grounds that it correctly represents the Greek, and so on. ] <small>]</small> 13:42, 8 September 2008 (UTC)
::Stupid suggestion, but would it make sense to attempt to harmonize the alternate spellings '''and''' the date issue so that there's one set of rules for both. I know they're closely aligned presently, but it might help to make sure that the exact same distinction is made for both. --] 14:08, 8 September 2008 (UTC)
:::You mean US spelling means US date-format in an article? It's one of the options above. Sometimes hard to detect the eng.var, though I don't think that's a great concern. The rules are really needed for where there's a sniff of a dispute in an article. Then it's worth hunting through to determine the eng.var. ] ] 14:16, 8 September 2008 (UTC)
::::But that's my point: that calling mdy formats the "US date-format" is inaccurate at best. I don't think copying the spelling rule -- American spellings for American topics -- will work with dates. ] <sup><small><small>]</small></small></sup> 17:11, 8 September 2008 (UTC)
::I didn't say the differences in spelling were absolute. =) ] <sup><small><small>]</small></small></sup> 17:11, 8 September 2008 (UTC)

There seems to be a lot of fiction about national date formats being bandied about, so I decided to do a Google sample of the Web to see who's using what.
* When you type "international date format" into Google, the vast majority of sites talk about the ISO date format. Apparently, most believe that the international date format is the ISO format (2000-12-31).
* A survey of British news sources indicates that, while most use European format (31 December 2000), quite a few use American format (December 31, 2000), and significant number switch back and forth, sometimes on the same page.
* A survey of American news sources indicates that most of them use American format, but a significant number of institutions use European format, and a few institutions use ISO format.
* A survey of Canadian news sources shows that most use American format, some use European format, and the ISO format is more common than the European format. Commonly, they use American alphanumeric format (December 31, 2000) with ISO numeric format (2000-12-31). The variant ISO alphanumeric format (2000 December 31) is also in use.
* A survey of Australian and New Zealand news sources indicates that they use both European and American formats, and like the British they often switch back and forth.
* As far as spelling is concerned, the Americans use American spelling most of the time, the British use British spelling most of the time, the Canadians usually use British spelling (often with the American date format), and the Australians and New Zealanders use both spellings, often inconsistently (''the labour policies of the Labor Party'')... (But I've also seen the U.S. government ''Report on the Sulfur Emissions of the Sulphur Creek Sulfur Plant'')
So, notwithstanding all the debate, I don't detect a great deal of consistency in the national use of date formats, nor do I see much linkage between dates and spelling. It seems to be largely a matter of personal or institutional preference.] (]) 15:38, 8 September 2008 (UTC)
:I did a little further query experimentation on that first point. Compare {{google|+"international date format" +"8601"}} with {{google|+"international date format" -"8601"}} and we get different results than RMG found above. Hit counts were 1270 versus 5350. Google just ranked the +"8601" links higher (for whatever reason). I do note however that the ] standard for is quite unambiguous, as is . ] (]) 18:50, 8 September 2008 (UTC)
::Even in the latter ("-8601") case, most sites are still talking about the ISO format without saying "8601". Most of the rest are talking about random things like the proper case to use for the month name in Greek...] (]) 22:55, 8 September 2008 (UTC)
:::You can narrow it down further with a -"ISO", but I take your point. There are some interesting exceptions though., such as jbase, where "international" is used in contrast to "domestic" (US) in reference to the dd/mm/yy vs. mm/dd/yy distinction. My real point was that googlediving is far removed from solid research even if it is a useful indicator. ] (]) 17:10, 9 September 2008 (UTC)
:You seem to be confused. Australians and New Zealanders use Australian and New Zealand spelling consistently. This is very similar to British spelling in most areas and is generally fairly consitent in the modern era. The ] in Australia as a historical exception, explained in the article, and does not indicate an inconsistency (it's a name for starters) ] (]) 04:48, 9 September 2008 (UTC)
::*] goes directly to the point. Fascinating. ] <small>]</small> 16:08, 9 September 2008 (UTC)
::Nil is correct. And Canadians do not "usually use British spelling". "Sulphur Creek" is a name, too, based on colonial spelling. ] ] 07:59, 9 September 2008 (UTC)
:::Okay, try this Canadian web site http://www.chem.ucalgary.ca/asr/ for variant spellings. It belongs to the "Alberta '''Sulphur''' Research Ltd., '''Center''' for Applied Catalysis and Industrial '''Sulfur''' Chemistry, University Research '''Centre'''." It informs you that "Alberta '''Sulphur''' Research Ltd. was incorporated as a non-profit '''sulfur''' research organization...in 1964". Later, you find that "Dr. Clark is the Technical Manager of Alberta '''Sulphur''' Research Ltd. and Professor of Chemistry in '''sulfur''' chemistry at the University of Calgary". However, I take it that Australians and New Zealanders are a bit more consistent in their spelling.] (]) 19:33, 9 September 2008 (UTC)

== Rationalising MOSNUM and MoS (main) ==

It's high time we addressed that fact that both pages duplicate each other in many respects. I am to blame for this; it resulted from my major rewriting of MOSNUM ?two years ago, when I boldly added the main sections of the new MOSNUM to MoS (main); before then, MoS (main) was silent on all of those areas and did indeed just link to MOSNUM, although in a less well-organised way than we can do it now. In retrospect, transclusion would have been much better, and I can't think why this wasn't done. Anderson sets out the options at ]. ] ] 14:13, 8 September 2008 (UTC)

== nbsp and dates ==

As the delinking of dates rumbles on, I have to ask: is there any consensus on the use of non-breaking spaces in dates? Various archived discussions seem to have suggested their use both between day and month, and between month or day and year. On the other hand, some of the discussion suggests that its use is purely discretionary. I'd like to overhaul my portfolio of articles to comply with the new MOSDATE, and I'd appreciate advice as to the extent to which I should use non-breaking spaces. ] (]) 17:47, 8 September 2008 (UTC)

* It’s a good idea Choess, but I don’t know if one can mandate such nuances; perhaps we could have wording on MOSNUM that ''encourages'' that as a “best practice.” It takes a long time editing on Misplaced Pages to learn about such things as non-breaking hyphens and non-breaking spaces. Personally, I use a non-breaking space between the date and the name of the month so I don’t have a orphaned numeral hanging at the end of a sentence (in the case of Euro-style dates), nor a line beginning with a numeral (in the case of American-style dates). I think it is better to not mandate so much in a ]: just let new editors simply write out dates, and let more experienced editors do cleanup when they feel the need. <span style="white-space:nowrap;">''']''' (])</span> 18:35, 8 September 2008 (UTC)
::Isn't that what MoS is for, though - telling the experienced editors how to clean up (and resolving conflicts between them as they do so)? New editors are probably only hazily aware of MoS, so they will do the same whatever we write. --] (]) 18:42, 8 September 2008 (UTC)
:::It's a good practice as far as typography goes, but it further erodes the readability of the markup, even for experienced editors. ] <sup><small><small>]</small></small></sup> 19:46, 8 September 2008 (UTC)

:::* Well, there are more disruptive markups being routinely used on Misplaced Pages than '''Sept.&amp;nbsp;11, 2001'''. How much worse is that non-breaking space that '''<nowiki>{{nowrap|Sept. 11, 2001}}</nowiki>'''? (Yes, I know these two example markups don’t do the exact same thing; it’s illustrative). So I don’t think it can reasonably be called an issue of experienced editors having a problem with this sort of simple stuff (the ability to deal with that would pretty much define “experienced editor”). The issue is just a subtlety: do we start mandating advanced markup techniques in style guides. Maybe. But I don’t think that is best. <span style="white-space:nowrap;">''']''' (])</span> 20:36, 8 September 2008 (UTC)
:::**I don't know that either is being used routinely, but the latter is certainly more readable. I'm not suggesting "experienced editors" can't "deal with" a non-breaking space; I'm suggesting that the readability is decreased. Which it is. And the benefit of using the non-breaking space has to be weighed against that loss of readability. ] <sup><small><small>]</small></small></sup> 23:04, 8 September 2008 (UTC)

We prefer dates with the month spelled in full. I think any markup that joins the day, month, and year into one non-breaking unit is too long, and the jaggedness of the resulting rendered text is a greater problem than wrapping the date. If there is to be any non-break space, I'd put it only between the day and month. --] (]) 20:46, 8 September 2008 (UTC)

* I agree with you Gerry. It should be “10 October 2001”” or “October 11, 2001” (spelled out fully). Still there shouldn’t be “October<br>11, 2001”, a non-breaking space improves it immeasurably. I entirely agree with Choes that this is best typography practices. The issue, in my mind, is whether or not one ''requires'' the non-breaking space. I would say that if we wanted to mandate the use of a non-breaking space (always a good idea), one might be doing good if MOSNUM provides guidance to new editors as to how exactly one makes a non-breaking space and clearly explains why one should do so. <span style="white-space:nowrap;">''']''' (])</span> 20:51, 8 September 2008 (UTC)

:Whatever happened to the recent mantra that registered editors should see the same thing the reader sees? Is it suddenly inconvenient in this context?] (]) 21:16, 8 September 2008 (UTC)
::What exactly is being seen differently in this example? ] <sup><small><small>]</small></small></sup> 23:04, 8 September 2008 (UTC)

:* Gerry was objecting to abbreviating the name of the month. And I agree. I don’t abbreviate month names anyway and was just being sloppy with making an example of using non-breaking spaces. <span style="white-space:nowrap;">''']''' (])</span> 03:06, 9 September 2008 (UTC)

A non-breaking space could easily be provided when the date is autoformatted... ] 03:22, 9 September 2008 (UTC)

* Which will be wonderful and will rank right up there just under antibiotics, Gimmetrow—''after'' the feature is made to work for <u>everyone</u> instead of just we editors (which just glosses over editorial problems with date formatting and makes 99.9% of our readership look at junky, inappropriately written text). But don’t hold your breath for those tools; it would take a lot of tinkering under Misplaced Pages’s hood to make that happen. <span style="white-space:nowrap;">''']''' (])</span> 04:02, 9 September 2008 (UTC)
** The autoformatting code in MediaWiki already does similar formatting things for everyone, right now. It would not take much tinkering to have <nowiki>]</nowiki> produce 9&amp;nbsp;September. ] 13:29, 9 September 2008 (UTC)

Won't ''ALT+0160'' (with Windows) produce an nbsp that looks like a regular space in the edit, e.g. September 9, 2008? Or, is this what is meant by a literal hard space? If so, what kinds of problems are caused by using literal hard spaces? --] 12:42, 9 September 2008 (UTC)

:It sounds like things are coalescing around nbsp between month and day, at least for U.S.-style dates. I would think that the same would apply for international-style dates: 11<br />
:October 2001 also seems like poor line breakage. I agree that trying to glue the entire date together with nbsp is overkill. While it might be nice to see dates explicitly mentioned in WP:NBSP, I think it's best to recommend, rather than mandate, them for the time being, because of the legibility issues. Unfortunately, I don't think there's an easy fix for those. The problem with using an ALT-160 space is that it is very difficult for an editor reading an article to know whether or not a given space is a literal hard space. If I'm trying to fix dash problems in an article, for instance, I can always scroll up to the text of an article and see whether a given dash is a hyphen-minus, en-dash, or em-dash. But it's impossible to tell by casual inspection to what extent ordinary whitespace in an article has been replaced by non-breaking space. Maybe if a WYSWIG editing tool were ever built, but for now, I'd say we have to put up with the written entities. ] (]) 14:36, 9 September 2008 (UTC)
*''Tony1's comments:'' Let's first remember that the DA mechanism has never prevented wrapping; as well, the dates after our signatures wrap, which hasn't seemed to bother anyone. SandyGeorgia, the FA delegate, is hugely in favour of adding the hard-space between month and day (= day and month). Lightmouse, who wrote the DA removal script, is doesn't like it. So I'm caught between two friends who have opposite takes on this. The effect of the hard-space is nice, except in a few places adjacent to an image or infobox where there's a bit of text-stretching results from it; but that's no big deal. I do worry that it looks bad in the edit-mode and is a pain to key in; I desperately wish that Noetica's push six months ago for a short-cut like the double comma hadn't failed (like most proposals put to WikiMedia, it seems). I'm on the fence. ] ] 14:52, 9 September 2008 (UTC)
**I should prefer not. FAC does not need to require ''more'' things that are not intuitive and are hard to key in; it spends too much time on that now. ] <small>]</small> 16:03, 9 September 2008 (UTC)
**''A non-breaking space between the month and day in ''February 14'' may prevent a line beginning "14, 1958". Such spaces should be considered; they may not be worth the trouble and the less readable code, and they may cause other bad line breaks, so they are entirely a matter of editorial discretion; since they are not visible, they need not be included uniformly within an article.'' is what I would put if I were Jimbo, but it may not be worth the space; the first sentence, may imply the whole thing. ] <small>]</small> 16:16, 9 September 2008 (UTC)

==Birth dates?==
Should birth dates be linked? Please leave any comment at ]. --] <sup>]</sup> 19:09, 8 September 2008 (UTC)

* Linked? Like, to trivia? So instead of clicking on an Easter-egg-like date in hopes of reading more on the birth of the person, they are taken to a long, tedious list of mind-numbing random trivia that has nothing whatsoever to do with the person the article is about? I hope not. <span style="white-space:nowrap;">''']''' (])</span> 20:43, 8 September 2008 (UTC)

:For the reasoning see the linked discussion. --] <sup>]</sup> 21:02, 8 September 2008 (UTC)

:* '''P.S.''' Caveat: With one exception. I would suggest that one could link years (never dates) in intrinsically historical articles, such as ]. In such an article, if one wrote as follows:

::{{cquote|The ] period of the French Revolution (]–]) was …}}

::…then I wouldn’t have a problem. It would give readers interested in history an opportunity to find out what else was going on during those years. <span style="white-space:nowrap;">''']''' (])</span> 21:04, 8 September 2008 (UTC)

== Ruminations on date linking ==

I just removed the text which allegedly presents the arguments for delinking deprecation. I don't have time to follow every detail of this page, but I questioned these a while back, and the arguments haven't improved. The reasons were faulty because
* autoformatting does something for non-registered and non-logged-in users. Not only does it involve some formatting, but everyone benefits from what was, I think, was the main reason for the date linking, the reduction of date-format wars.
* rendering the linked dates without the links would solve this (and see later)
* the iso format implying a Gregorian date is pretty much irrelevant. The guideline already says don't use iso-style dates in the text, and publication dates in refs should match text. Accessdates for online material will presumably be late enough that this isn't a concern.
* idioms should work in the text as written.

Datelinking may have some disadvantages, but the disadvantages presented so far are weak. Hardly seems worth throwing the whole system out if these are the best you can come up with after this much time. These linked dates represent a substantial investment in metadata, and it has uses. Rendering linked dates without links keeps the metadata investment while addressing the "overlinking" issue.

I see the faulty reasons have already been restored. If you cannot defend the arguments for linking after this much time, then those reasons will be removed. ] 02:55, 9 September 2008 (UTC)

* Well, I undid that edit but had an edit conflict with Gerry, who already did it seconds beforehand. And my edit summary comprised “We’ve discussed this long enough.” <span style="white-space:nowrap;">''']''' (])</span> 03:04, 9 September 2008 (UTC)

** After "long enough" if you can't come up with better reasons than those four, they you have nothing. ] 03:07, 9 September 2008 (UTC)

::* We’re going in circles with you and going nowhere with you Gimmetrow. Please don’t be disruptive to MOSNUM. Your “not getting it” is beginning to look like an intentional mental block. I’m baffled why you could possibly not understand the concept that giving editors a special view of Misplaced Pages’s pages causes nothing but problems and only sweeps editorial problems under the rug. So you can understand, here is some sample text. Take a look at it while logged in and while logged out.

::::{{cquote|During the French Revolution, the Estates-General convened in Versailles on ], ] and lengthy speeches by Necker and Lamoignon… and then on ] a memorial was built on the site…}}

:::Do you see now? To save other editors the effort of having to log out, here is how the above was coded:

:::{{quotation|<nowiki>During the French Revolution, the Estates-General convened in Versailles on ], ] and lengthy speeches by Necker and Lamoignon… and then on ] a memorial was built on the site…</nowiki>}}

:::And here is what virtually every single user of Misplaced Pages sees (because they aren’t *special* like we registered editors):

:::{{quotation|During the French Revolution, the Estates-General convened in Versailles on ] ] and lengthy speeches by Necker and Lamoignon… and then on {{nowrap|]-]}} a memorial was built on the site…}}

:::But for a registered editor (one in a thousand users) logged in with “Euro-style” preferences, here’s what ''they'' see:

:::{{quotation|During the French Revolution, the Estates-General convened in Versailles on ] ] and lengthy speeches by Necker and Lamoignon… and then on ] ] a memorial was built on the site…}}

::::It should be quite clear that both date formats 1) are inappropriate for use in an article on the French Revolution, and 2) they appear lousy or awkward for the vast majority of Misplaced Pages’s readership, and 3) editors who are logged in and have their user pref settings adjusted to their suiting ''can’t even see'' where these problems exist! As editors who are largely responsible for this stuff, we’ve been marching along all fat, dumb & happy, totally oblivious to what we’ve been making the vast majority of our readership look at. As I stated above, we editors should '''''never''''' use tools that allow us to look at regular editorial content in a way that is at all different from what everyone else has to look at. The only preferences settings that affect what we see should be date offsets for when edits are made—that sort of thing.

:::: Now, if this goes anywhere like it has with other editors arguing the same point you are (“autoformatting is wonderful”), this is the point where you reply how we ought to simply then make autoformatting work for ''all'' users, including IP users. Been there; done that. Please get ] and stop being disruptive. We’ve gone all over this stuff; I can’t help it if you don’t get it. Slapping {disputed} tags all over MOSNUM because *Gimmetrow isn’t pleased* isn’t going to get you your way.<p>And I’d say you pretty much '''''burned your bridges''''' when you with ''“ I don't have time to follow every detail of this page.”'' You might as well have said ''“I didn’t participate in all the discussions—and don’t feel like getting up-to-speed anyway—but don’t like the consensus that developed so I deleted what has been here for a week since it offended my sensibilities and then slapped a {disputed} on the text after I was reverted.”'' That was ''so'' not a smooth move on your part. <span style="white-space:nowrap;">''']''' (])</span> 03:40, 9 September 2008 (UTC)

If you cannot justify the deprecation, then you need to remove the false reasons. If ''you'' cannot bother to do ''your'' homework, then there's nothing further for me to say. Whatever consensus might have been for date delinking, it's gone, derailing any hope of date delinking for now. ] 03:58, 9 September 2008 (UTC)

* I just did justify it. Read the above post. If you still don’t “get it,” you’re apparently not trying to understand the issue anymore and I can’t help you. <span style="white-space:nowrap;">''']''' (])</span> 04:04, 9 September 2008 (UTC)

** Greg, you have inappropriately removed a disputed tag without resolving the dispute. You have not justified anything. You are formally asked to either remove the disputed "reasons" or restore the notice. If you do not restore the notice or fully resolve the dispute immediately, I will consider your actions a user-conduct violation. ] 04:08, 9 September 2008 (UTC)

::* The consensus for deprecating autoformatting doesn’t disappear just because Gimmetrow fervently wishes that to be so and solemnly pronounces that there is no consensus. I’ve seen these very tactics with a couple of “won’t let go” editors over the IEC prefixes. Doesn’t fly. Just because an editor places a {disputed} tag on text doesn’t mean that action was justified and legitimate. You already admitted that '''''I don't have time to follow every detail of this page''''' and then you had the gall to come back and slap the {disputed} tag on MOSNUM instead of having stayed here and discussed and debated the entire time. And all of ''that'' was after you deleted text and another editor reverted ''that'' stunt of yours. If you want your voice to remain relevant, stay in the discussions and don’t make pronouncements that you don’t even have time to get yourself up to speed on the issue. What you did is basically vandalism by someone who didn’t want to devote the time that others have invested into this debate. <span style="white-space:nowrap;">''']''' (])</span> 04:19, 9 September 2008 (UTC)

:::* I patiently waited some weeks, watching this page for any defense of those "reasons". If you refuse to defend them, then I will consider them indefensible, and remove them. ] 04:32, 9 September 2008 (UTC)

The links are of marginal value as metadata because they fail to capture which calendar the date is in, and whether the date is AD or BC. --] (]) 04:11, 9 September 2008 (UTC)

* I am quite done further soiling myself with this debate tonight. Someone else will have to deal with Gimmetrow for the next 48 hours. I’m fed up. Goodbye. <span style="white-space:nowrap;">''']''' (])</span> 04:21, 9 September 2008 (UTC)

*Gimmetrow, you amaze me. Let's take two central statements you've just made above:
<blockquote>"autoformatting does something for non-registered and non-logged-in users.... the reduction of date-format wars." "rendering the linked dates without the links would solve this (and see later)"</blockquote>
Um ... can you link to ''any'' edit war over the removal of DA? Pete's little wars in a few places (of which I disapprove) over the selection of the date format in articles related to foreign-language-countries started well before the deprecation of DA; such selection has nothing to ''do'' with DA—they concern what our readers see. As Greg L has pointed out countless times, we don't want editors to have blinkers on. DA doesn't stop edit wars, it stops us from properly managing the dates our readers see. Have a look at ] of the appalling state of our date management. If you did some date auditing yourself, you'd be confronted by this reality. Your notion of retaining autoformatting, but "unlinked" is dangerous: we won't be able to tell what is and isn't autoformatted, and we will continue to be blind to what our readers see; thus, the poor management of DFs will continue. ] ] 04:45, 9 September 2008 (UTC)

** How can we be blind if, as is claimed, only a tiny fraction of registered users have a pref setting, and therefore most editors see exactly what readers see? And the date format wars were quieted back in 2003 with dynamic dates. For the past five years, anyone set on one style could set a preference. ] 04:50, 9 September 2008 (UTC)
:::I don't know who's claiming that, but I think it's been mangled since—only a tiny fraction of ''readers'', not logged-in registered WPians, have the autoformatting blinkers on. ] ] 07:56, 9 September 2008 (UTC)

:::: Doesn't that beg some questions? Do registered WPians "have autoformatting blinkers on"? ] 01:14, 10 September 2008 (UTC)

:::::Yes, I think we generally do. I took mine off some time ago and urge others to do the same. ]<sub>&nbsp;]·]</sub> 17:15, 10 September 2008 (UTC)

==Date format resolution attempt==
Once again, this time in the (perhaps overly optimistic) hope of finally reaching agreement. The principal alternatives are summarized in four options—A, B, C and D. Please note two points:
*''Common ground:'' For all four options: there is no change to the current situation where there are ties to English-speaking countries, except that the rule for Canada-related articles is clarified: "Use the date format chosen by the first major contributor".
*''Headings:'' Since the only distinguishing feature of each option is how articles ''without'' ties to English-speaking countries are treated, the headings encapsulate only this feature.

::'''(A) Engvar.''' Date format follows language variety; month-day format is considered a feature of U.S. English, just as the spelling "color" is. Where ''both'' ENGVAR is unclear ''and'' there is no strong tie to an English-speaking country, the "first major contributor" rule applies.

::'''(B) First major contributor.''' Where there is a strong tie to an English-speaking country, use the most common date format used in that country. Where there is no tie to an English-speaking country, the "first major contributor" rule applies.

::'''(C) Day-month default.''' Use day-month format unless strongly tied to an English-speaking country that uses month-day.

::'''(D) Country-driven.''' Use whichever of the two acceptable formats most resembles the date format used in the country in question, even if non-English-speaking. If this cannot be determined, the "first major contributor" rule applies.

I suggest a poll on these four alternatives, with concise arguments (if any) since we've probably been through them all at length anyway. Or maybe I've missed something out. Anyway, once we know what principle we're adopting, we can decide on the precise wording.--] (]) 10:49, 9 September 2008 (UTC)

May I suggest that Greg L set up one of his tabular polls such as he's done for other difficult issues? It would be be useful if everyone could mark each of columns A, B, C and D with a number drawn from this list (i.e., any of these numbers for each of Options A, B, C and D):

:<s>1 = I like this a lot.
:2 = I like this mildly.
:3 = I don't favour this, but I could live with it.
:4 = I object to this.
:5 = I strongly object to this.</s>

:<strong style="font-size: 90%;">0 = Complete opposition </strong>
:<strong style="font-size: 90%;">1 = Could be much better </strong>
:<strong style="font-size: 90%;">2 = Ambivalence </strong>
:<strong style="font-size: 90%;">3 = Could be improved, but I support this </strong>
:<strong style="font-size: 90%;">4 = Complete support </strong>

A blank in a square would represent a neutral attitude to that option.

Perhaps the process of adding the signature could be simplified from the previous tabular pools—just write your unsername in the name column and sign underneath the table. No one would bother falsifying, since the edit history reveals all. I'll ask Greg at his talk. ] ] 11:14, 9 September 2008 (UTC)
:This sounds good. I'll go alert the previous participants once the table is set up. I've added Option D, which is pretty much the long-standing status quo, as there are a handful of nations such as the Philippines and Pelau which use U.S. format. --] (]) 11:49, 9 September 2008 (UTC)
:I've struck out the original options and replaced them with the (completely opposite) options actually provided with the table. Having larger numbers to indicate higher support seems more intuitive. --] (]) 03:07, 10 September 2008 (UTC)
:I've clarified the options and removed my precipitous vote and the queries which necessitated the clarifications, to avoid clutter. Votes for option D will need to indicate a default to A, B, or C for cases where no country is involved. Awaiting the table (but might be best to hang on a bit longer in case of further tweaks to the list of options).--] (]) 12:12, 9 September 2008 (UTC)
::I agree with Kotniski about tweaking. Three things.
::<small>(removed two resolved - hope no-one minds this anti-clutter comment-removal policy - Kot)</small>
::*Option A will need to default to "first major contributor" if ENGVAR can't be determined. ] ] 12:19, 9 September 2008 (UTC)
:::I think that follows from ENGVAR, but try to clarify if you like.--] (]) 12:30, 9 September 2008 (UTC)
←OK, I've rewritten them with the intention of preserving the meanings, except for filling in a few minor holes (I think Pete's Option D in particular, needed this). Kotniski, please revert or modify them as you see fit. Could others please offer suggestions here to forestall chaos, if you can bear to keep your fingers off them—two editors directly tampering is more than enough, and comments/suggestions from others are very welcome. ] ] 14:24, 9 September 2008 (UTC)
::Well, I'm happy to relinquish that role to someone else, particularly as Tony and I might be felt to be on the same side of the debate (and I've got work to do...) I will just make one final tweak to D though. --] (]) 14:31, 9 September 2008 (UTC)
::And we need option '''(E) Engvar. Established usage.''' Date format follows language variety; month-day format is considered a feature of U.S. English, just as the spelling "color" is. Where the variety of English is unclear, stay with an established format. Where ''both'' ENGVAR is unclear ''and'' there is no established format, the "first major contributor" rule applies.
:::I think this is just a more detailed wording of (A); it doesn't need to be listed as a separate option.--] (]) 16:15, 9 September 2008 (UTC)
::I also would prefer ''strong ties'' in (A) as it is in ]; else we will have bafflegab about the ties of ] to England. ] <small>]</small> 15:59, 9 September 2008 (UTC)
:::I agree on the need for strong ties. Tangential involvement isn't really enough to disregard the warnings (originating at ArbCom level) about changing styles. --] (]) 03:07, 10 September 2008 (UTC)

All four options assume a single date format is used in each location. I don't think that's accurate, as I brought up ]. ] <sup><small><small>]</small></small></sup> 14:02, 9 September 2008 (UTC)
:I think it's understood that, where it says "used", it means "most commonly used". If not even that can be determined, then we have to make an exception (as for Canada). But it's the general principle we need to decide first, before we address the detailed wording and possible exceptions.--] (]) 14:24, 9 September 2008 (UTC)
::Anderson: I've added "strong", but you do realise that this narrows the applicability of the tie when in the negative, don't you? Can you check through from that perspective? As for Option E, do you mean "there is no established date format ''in the article''. If I'm right, I think I'd rather write it into A. Thus, there's a distinct chain of decisions. Does anyone object? We'll ''have'' to retain "and there is no strong tie to an English-speaking country, otherwise a US-related article without a distinctly US-spelt word is in trouble if in day-month format already. Just thinking through the worst-case scenario so that we're covered. Is this what you mean?: "Date format follows language variety (month-day format is considered a feature of U.S. English, just as the spelling "color" is). Where the variety of English is unclear in an article without strong ties to an English-speaking country, retain the established format in the article. Where ''both'' ENGVAR ''and'' the existing date format are unclear, the "first major contributor" rule applies." I'm off to bed. ] ] 16:34, 9 September 2008 (UTC)
::Even "most commonly used" is misleading. Frankly, I don't see the difference among options A, B, and C; they all require mdy format in articles "strongly tied" to the United States, which I think is unecessary. D has the same problem. Where's the option for "always use the first contributor's choice"? ] <sup><small><small>]</small></small></sup> 22:50, 9 September 2008 (UTC)
*I object to (C) with or without ''strong'', so I don't see much difference there.] <small>]</small> 17:37, 9 September 2008 (UTC)
*I thought there might be a real disagreement about ''established'', by which, yes, I mean ''in the article''. I'd rather say it, so that we ''can'' change without somebody digging up a stub from 2002 and claiming that means he gets his way; and I see Kotniski thinks it's implied anyway. ] <small>]</small> 17:37, 9 September 2008 (UTC)
::Common sense would hopefully apply, as well as common co-operation. We're working together, not every editor out to battle and win to write Misplaced Pages in his preferred polemic. --] (]) 03:07, 10 September 2008 (UTC)

:* All: With regard to Tony’s 11:14, 9 September 2008 proposal, I’d be pleased to set up a vote table here. I’m tied up for the work-part of the day (west coast U.S.), but will be pleased to do this tonight. By the way, so we don’t confuse experienced editors here, I think we’ll set up the “degree of support” values just as before: greater support equals ''higher'' value. <span style="white-space:nowrap;">''']''' (])</span> 18:15, 9 September 2008 (UTC)

===Poll on guideline for writing fixed-text dates===
Which guideline do you support for determining the most suitable fixed-text date format (2&nbsp;February 2009 or February&nbsp;2, 2008) editors should use in Misplaced Pages’s articles? If a clear general consensus develops for one particular option, we will go with that option. Otherwise, we will conduct a run-off vote on the two options that have the greatest number of points. The current options are as shown below:

'''(A) ] (date format follows dialect of English most suitable for the article, default to first major contributor—no list of countries):''' Date format follows language variety; month-day format is considered a feature of U.S. English, just as the spelling "color" is. Where ''both'' ENGVAR is unclear ''and'' there is no strong tie to an English-speaking country, the "first major contributor" rule applies.

'''(B) Go with first major contributor unless there is a strong tie to an English-speaking country—no list of countries:''' For articles on, or strongly associated with a particular English-speaking country, use the most common date format used in that country. Where there is no tie to an English-speaking country, the "first major contributor" rule applies.

'''(C) Default to international unless U.S. and its territories—listed countries for editors’ convenience:''' For articles on, or strongly associated with, the U.S. or ] (or countries listed in this guideline that use U.S.-style dates: Micronesia and Palau), editors should use the U.S.-style date format (“February&nbsp;2, 2008”), otherwise, editors should use the international date format (“2&nbsp;February 2008”) in articles. The dialect of English used for the article (“colour” v.s. “color”, etc.) shall have no bearing on the chosen date format. ''New'' articles on or strongly associated with Canada should use the international format but, for existing articles related to Canada, whichever format was used by the first major contributor shall be retained.

'''(D) Country-based, even if non-English-speaking—no list of countries:''' Use whichever of the two acceptable formats most resembles the date format used in the country in question, even if non-English-speaking. If this cannot be determined, the "first major contributor" rule applies.

<hr/>
'''Note that the below chart does not allow <nowiki>~~~~</nowiki> signatures to be used. You must copy/paste or hand-edit your signature. For assistance in writing your signature, you may copy the time below in red <u>from the preview window</u> after clicking on “Show preview” while in edit mode:'''<!--
DON’T COPY THIS CODE BELOW --><br>
<font color = red>'''{{CURRENTTIME}}, {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} (UTC)'''</font color><hr/>
<!-- ONLY COPY TIME/DATE FROM THE PREVIEW WINDOW -->

:<strong style="font-size: 90%;">0 = Complete opposition </strong>
:<strong style="font-size: 90%;">1 = Could be much better </strong>
:<strong style="font-size: 90%;">2 = Ambivalence </strong>
:<strong style="font-size: 90%;">3 = Could be improved, but I support this </strong>
:<strong style="font-size: 90%;">4 = Complete support </strong>

{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f5f5f0; border: 2px #3E3E3E solid; border-collapse: collapse; font-size: 95%;"
|- |-
| US Navy Astronomical Applications Department || https://aa.usno.navy.mil/faq/millennium || 01
! colspan="6" style="background:#3E3E3E" align="center"|<font color=white><span style="margin-left:3em">DEGREE OF SUPPORT FOR OPTION</span><font color=white><span style="margin-right:2.6em">&nbsp;</span></font>
|- |-
| US Library of Congress || https://ask.loc.gov/science/faq/399936 <br> https://www.loc.gov/rr//scitech/battle.html (Battle of the Centuries) || 01
|style="background:#d9d9d3" align="center"|'''Editor'''
|style="background:#d9d9d3" align="center"|'''&nbsp;&nbsp;A&nbsp;&nbsp;'''
|style="background:#d9d9d3" align="center"|'''&nbsp;&nbsp;B&nbsp;&nbsp;'''
|style="background:#d9d9d3" align="center"|'''&nbsp;&nbsp;C&nbsp;&nbsp;'''
|style="background:#d9d9d3" align="center"|'''&nbsp;&nbsp;D&nbsp;&nbsp;'''
|- |-
| Merriam Webster || https://www.merriam-webster.com/grammar/centuries-and-how-to-refer-to-them || says it used to be 01 but that public opinion is swinging
|style="background:#d9d9d3" align="right"|]
|-
|align="center"<!-- A -->|0<ref>My opposition to option A (], or “English variation”), is that I am an American and use American English in all my contributions. I ''also routinely use international-formated dates'' in articles that have no strong ties to the U.S., such as ]. Note that the French are more closely tied to the development of the kilogram than any other country and the kilogram clearly has no strong national tie to the U.S. So it makes no sense in my book to require that dates in the ''Kilogram'' article follow the U.S. convention (“February&nbsp;2, 1799”) just because the article was written using American English. <span style="white-space:nowrap;">''']''' (])</span> 18:30, 10 September 2008 (UTC)</ref>
| Greenwich Observatory || http://www.thegreenwichmeridian.org/tgm/articles.php?article=12 || 01
|align="center"<!-- B -->|2
|align="center"<!-- C -->|4<ref>I don’t see the need for using international date formats in an article on a U.S.-related subject (like a U.S. national forest), just because a UK author was the first major contributor and used the spelling “colour” in the article. IMO, it should be one, simple rule:{{cquote|If it is an article closely tied to the U.S. use the U.S.-style date format, otherwise, use international date formats in articles.}}


There’s no legitimate need for any more complexity than that. If we are to start keying the date formats used in articles to the dialect of English the editor happened to use while writing the article, all the articles I’ve been writing (science-related topics, such as ]) would have U.S.-style dates because I used U.S.-style spelling in those articles. That makes no sense. Keep it simple. Dragging English-language dialect complexities into this discussion seems totally unnecessary.<p>The whole point of making it country-based is to make the article read as smoothly as possible for the likely audience. If it is an article on a U.S. National Park (likely a readership dominated by U.S. citizens), then use U.S.-style date formats to make the article as natural for that audience. For everything else, use the international date format. This should all be about making Misplaced Pages better for our ''readers''; we needn’t be so concerned about hurting the feelings of editors. <span style="white-space:nowrap;">''']''' (])</span> 01:08, 10 September 2008 (UTC) (UTC)</ref>
|align="center"<!-- D -->|2
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|2
|align="center"<!-- B -->|4
|align="center"<!-- C -->|0
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|{{U|Teemu Leisti}}<ref>I completely agree with Greg L's comment. Plus, as bad as basing the choice upon the variety of English used in the article is, I dislike even more having to go through the article edit history to find out which format the first editor used. The choice should <s>impinge</s> depend only on the subject of the article, not on historical accidents of that sort.
<p>And as for the proposed "default" format being day-month-year: take a look at the dates produced by <nowiki>~~~~</nowiki> signatures. I haven't noticed objections to this. ] (]) 01:09, <u>'''10 September 2008'''</u> (UTC)</ref>
|align="center"<!-- A -->|1
|align="center"<!-- B -->|0
|align="center"<!-- C -->|4
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|{{U|Truthanado}}
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|4
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|Sapphic<ref>Dates should never be plain text. Autoformatting makes this entire poll irrelevant.</ref>
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|0
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|]<ref>I would prefer options that don't require articles with strong ties to the United States to use MONTH DAY YEAR format, because while common, that format is far from ubiquitous in the U.S. -- ] <sup><small><small>]</small></small></sup> 02:02, 10 September 2008 (UTC)</ref>
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|1
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|0
|align="center"<!-- B -->|1
|align="center"<!-- C -->|3
|align="center"<!-- D -->|4
|-
|style="background:#d9d9d3" align="right"|{{U|Kotniski}}
|align="center"<!-- A -->|3
|align="center"<!-- B -->|4
|align="center"<!-- C -->|2
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|{{U|Jimp}}
|align="center"<!-- A -->|3½
|align="center"<!-- B -->|4
|align="center"<!-- C -->|3
|align="center"<!-- D -->|0<ref>How they write dates in another language has no relevance on ''en''.WP. International date format juxtaposed with US spelling is no great shock—the US military does it. Similarly international spelling juxtaposed with US date format is not shock either—Canadians often do it ... some non-Canadians do so too. The distinction between new & old Canadian articles will be too hard to maintain ... indeed the idea that Canadian articles should be in international format is wrong-headed (much as I prefer international format): Canadian ''do'' use both. ] 10 Sep 08</ref>
|-
|style="background:#d9d9d3" align="right"|]]<ref>!votes were solicited at ], so here is mine. I will not watch this page for replies, as I am uninterested in arguing over this issue. IMO, too much of this months-long debate has been an exercise in ] for various points. I also do not look forward to the day when the date warriors decide all references must not use YMD format, as I greatly prefer that short format in the references list. ]] 11:43, 10 September 2008 (UTC)</ref>
|align="center"<!-- A -->|3<ref>Option A is the only consistent option. The rest are even more encouraging people to fight and editwar over the format. ] might need updating to indicate which countries use which formats. ]] 11:43, 10 September 2008 (UTC)</ref>
|align="center"<!-- B -->|0<ref>Same a Option A, except it allows someone to come along to a random article with an established spelling but no dates and force a conflicting date format (for ] or ] reasons). ]] 11:43, 10 September 2008 (UTC)</ref>
|align="center"<!-- C -->|0<ref>Frankly, Option C seems to be pushing some sort of "DMY is the best" POV, and invites insane levels of speculation over who this "likely readership" really is—most cases where the "likely readership" can really be determined can probably be more easily settled by applying the "strong national ties" rule. ]] 11:43, 10 September 2008 (UTC)</ref>
|align="center"<!-- D -->|0<ref>Option D: How they write dates in another language has no relevance on the ''English-language'' Misplaced Pages. ]] 11:43, 10 September 2008 (UTC)</ref>
|-
|style="background:#d9d9d3" align="right"|{{U|Donald Albury}}
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|2
|align="center"<!-- D -->|0<ref>As an American, I want to say that I think this issue has been overblown. I'm quite comfortable with using the 'international' date format everywhere, it is perfectly clear as long as we spell out the months instead of using numbers. ] 11:52, 10 September 2008 (UTC)</ref>
|-
|style="background:#d9d9d3" align="right"|{{U|GregorB}}<ref>A), as an extension of WP:ENGVAR, appears to be the most neutral and well-established solution. B) is effectively very close, as the first major contributor will likely use "matching" date format and variant of English. D) is barely passable: it is almost as if it prescribes using rhymes when writing about poetry. ] 12:24, 10 September 2008 (UTC)</ref> <!-- VOTING INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility above when in preview mode. You may use a “<ref></ref>” comment after one of your votes. Zero means you hate the option, four means you love it. -->
|align="center"<!-- A -->|4
|align="center"<!-- B -->|3
|align="center"<!-- C -->|2
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|{{U|Septentrionalis}}
|align="center"<!-- A -->|3.5
|align="center"<!-- B -->|3<ref>Needs a note about established styles --Septentrionalis </ref>
|align="center"<!-- C -->|0<ref>although I oppose both of them wholeheartedly, C is ''worse'' than D, because it is unclear what countries it applies to. (If the argument is that the Philippines is effectively an English-speaking country, the way to deal with this is to use A, and argue the point when it arises. But I doubt it is, and we do have a Tagalog Misplaced Pages for this reason; and a Spanish one too. -- {{U|Septentrionalis}}</ref>
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|2
|align="center"<!-- B -->|0
|align="center"<!-- C -->|4
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|{{U|Aervanath}}
|align="center"<!-- A -->|4
|align="center"<!-- B -->|4
|align="center"<!-- C -->|2
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|{{U|SharkD}}
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|3<ref>Actually, I would prefer a fifth option: use the international format in all articles, about all countries, in all of English Misplaced Pages. -- {{U|SharkD}}</ref>
|align="center"<!-- D -->|2
|-
|style="background:#d9d9d3" align="right"|{{U|NerdyNSK}}
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|3
|align="center"<!-- D -->|4
|-
|style="background:#d9d9d3" align="right"|{{U|Remember the dot}}
|align="center"<!-- A -->|3
|align="center"<!-- B -->|4<ref>I like proposal B's flexibility when handling Canada-related articles, and think that proposals C and D are just going to make lots of people mad. I'd also like to point out that articles such as ] use U.S. format for the prose, but international format in ] because international format is more logical in tables. -- {{U|Remember the dot}}</ref>
|align="center"<!-- C -->|1
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|1
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|0
|align="center"<!-- B -->|1
|align="center"<!-- C -->|4<ref>This is the best option presented, but to be honest I am an Americain who would prefer that all of Misplaced Pages just adopt "day month year" as its standard. All countries that use English use this format (including America), even in those few where it is not the most common it is easy to understand in prose etc. For tables the standard should be ISO (YYYY-MM-DD) for both space and sorting reasons. --MJBurrage </ref>
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|0
|align="center"<!-- B -->|1
|align="center"<!-- C -->|4
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|4
|align="center"<!-- B -->|1
|align="center"<!-- C -->|1
|align="center"<!-- D -->|4
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|3
|align="center"<!-- B -->|1
|align="center"<!-- C -->|0
|align="center"<!-- D -->|4
|-
|style="background:#d9d9d3" align="right"|]<ref>They're all profoundly vague and arbitrary, so we'll no doubt revisit this soon. You can't get much more arbitrary than "first major contributor," although I have to admit that it isn't vague. They're all vague as to how "country" relates to the issue. (What country does "]" relate to?) For (A) and (B), "strong tie" is vague because most articles have "strong ties" to multiple countries. (Both the US and Australia have strong ties to ]). For (C), the TV soap "]" is "related to the U.S.," but it's more popular outside the US than within. Few here would mind if you put the dates in ]. (And I ''live'' in Texas!). Similarly, for (D), what the heck does "country in question" mean, anyway? What's the question? -- ] (]) 21:53, 10 September 2008 (UTC)</ref>
|align="center"<!-- A -->|0
|align="center"<!-- B -->|0
|align="center"<!-- C -->|2
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|2
|align="center"<!-- B -->|1
|align="center"<!-- C -->|4
|align="center"<!-- D -->|3
|-
|style="background:#d9d9d3" align="right"|{{U|SMcCandlish}}
|align="center"<!-- A -->|4
|align="center"<!-- B -->|0
|align="center"<!-- C -->|0
|align="center"<!-- D -->|0<ref>Options A and B are ''identical'', if you bother to actually read ]! I have zeroed B because we already have ENGVAR and it has served us well; whatever MOSNUM says on this should also be repeated (not necessarily at full length) in ENGVAR, and the general advice at ENGVAR should not be contradicted in any way by MOSNUM without an incredibly good reason (] - editors will not follow guidelines if they become too convoluted). C is unnecessarily complicated, and is already covered by A/B except for the two countries that use US format dates but do not have strong ties to the US (they can simply be specifically mentioned if anyone feels this is really necessary). D mistakes the map for the territory, the menu for the meal. Whatever version prevails, ENGVAR should be updated to account for it, not just MOSNUM. PS: This complicated table is a really poor way to conduct a simple ]. ] 22:50, 10 September 2008 (UTC)</ref>
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|4
|align="center"<!-- B -->|3
|align="center"<!-- C -->|2
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|1.5
|align="center"<!-- B -->|4
|align="center"<!-- C -->|3
|align="center"<!-- D -->|0
|-
|style="background:#d9d9d3" align="right"|{{U|Mdcollins1984}}
|align="center"<!-- A -->|3<ref name="mdc1984">I'd like a combination of A and B really. I would prefer a three-tier system: "Use the style most appropriate if an article is ''strongly'' related (for example ] for US, ] for UK). If, like ], a country is not related, or if two countries boast an equal claim or a conflict will arise (] was mentioned earlier), use the same format that ENGVAR implies. If ENGVAR hasn't been applied in the article, or isn't consistent, the ''status quo'' or first major contributor rule applies." –MDCollins (talk) 22:53, 10 September 2008 (UTC)</ref>
|align="center"<!-- B -->|3<ref name="mdc1984"/>
|align="center"<!-- C -->|1<ref>Default to international will cause a lot of problems in my opinion. –MDCollins (talk) 22:53, 10 September 2008 (UTC)</ref>
|align="center"<!-- D -->|2<ref>Can't see much difference to option B. –MDCollins (talk) 22:53, 10 September 2008 (UTC) &#91;This is in reference to D.&#93;</ref>
|-
|style="background:#d9d9d3" align="right"|{{U|Edison}}
|align="center"<!-- A -->|4
|align="center"<!-- B -->|1
|align="center"<!-- C -->|0
|align="center"<!-- D -->|1
|-
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|4<ref>Option A is the simplest and is likely to produce the best reading prose in most situations. I think B is pretty much the same in most situations. - C. Parham</ref>
|align="center"<!-- B -->|4
|align="center"<!-- C -->|0
|align="center"<!-- D -->|0
|} |}


Seems like the scientific community has a solid consensus on new centuries starting in the year xx01. The "Battle of the Centuries" is a good read. To be fair, does anybody have any authoritative sources backing the xx00 change date?
The average scores as of —00:00, 11 September 2008 (UTC)—are as follows:<p>


This is, of course, counter-intuitive to the layman who just sees 1999 tick over to 2000 and therefore assumes that change in the 3rd digit means a new century. But as we all know, intuition and truth do not always agree.
Option A = 1.89<br>
Option B = 1.58<br>
Option C = 1.94<br>
Option D = 1.06<p>


So why did the world celebrate the new century on 1 Jan 2000 ? I'm going to digress into armchair philosophising but bear with me. Image that you are a major newspaper, news channel, magazine, etc and you want readers to buy/subscribe. You can research it, find out that 1 Jan 2001 is the correct date and make a big thing on that date. But your competitors celebrated way back on 1 Jan 2000 and the public goes "meh, we did all that last year - get with the times you out of date moron!" The big news companies know this, so they all go with the earlier date to avoid their competitors getting the jump on them. Never let the truth get in the way of profit! Joe public naturally follows the mass media and ignores the nerds saying "2001" - why listen to boring nerds when you can party now! Party, party, party!
See ] below.


So, here we are, arguing whether to follow the truth or to follow Joe Public with both of his brain cells following news companies who are chasing the almighty dollar. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 11:44, 3 January 2025 (UTC)


*There are some known inconsistencies/anomalies in our treatment of centuries, including categories or articles covering decades. For example, ] is a subcategory of ], but includes 1900 which the MOS puts in the 19th century. If we were starting again, I think it would have been better to avoid using century in categories or articles, e.g. use "1900–1999" instead of "20th century", but we are where we are. ] (]) 12:36, 3 January 2025 (UTC)
=====Poll comments=====
<references/>


:I'm not sure why you're focusing only on the specific niche of science-related sources? If the scientific community chooses to adopt an unorthodox definition of the duration of the centuries, but most other sources follow the common definition, obviously the latter is more accurate. ] <sup>(], ])</sup> 13:45, 3 January 2025 (UTC)
=====Comments on "Poll comments"=====
::{{ping|Chessrat}} the century beginning in XX01 is not {{tq|unorthodox}}, quite the reverse. As people above have said, it's the definition that has been taught for years, but one that I agree is increasingly being replaced by the century beginning in XX00 definition. {{tq|Obviously the latter is more accurate}}, well, no – as pointed out above, this definition leads to the first century having only 99 years, so can hardly be called more accurate. Orthodoxy and accuracy are not the important issues in my view; the most important issue is what most readers now think 'century' means, which does appear to be the XX00–XX99 definition. ] (]) 14:21, 3 January 2025 (UTC)
This section is intended to provide a forum for rebutting and commenting on the above ref-based vote statements. <span style="white-space:nowrap;">''']''' (])</span> 22:16, 9 September 2008 (UTC)
:::Back in 2000 it was suggested that a year zero be created with (since years have variable numbers of days anyway) zero days. That way the first century would have 100 years in it. ] ] 22:06, 3 January 2025 (UTC)
::::At least we can all agree that that would be the ugliest possible solution. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 08:26, 4 January 2025 (UTC)
::{{replyto|Chessrat}} Scientists put much thought into the matters that they comment upon, it's a poor scientist who states something as fact when they have no demonstrable evidence. So I would take a scientist's view over a newspaper's view any day. --] &#x1F98C; (]) 22:52, 3 January 2025 (UTC)


== RfC on the wording of ] ==
* '''Question:''' How do options B and D differ from each other? I largely copied & pasted that stuff. It seems these can be consolidated into a single option. <span style="white-space:nowrap;">''']''' (])</span> 22:29, 9 September 2008 (UTC)
<!-- ] 15:01, 7 February 2025 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1738940465}}
::I've been struggling to work out the exact differences between all of the options all day - it all seems very subtle.&ndash;] ('']'') 22:35, 9 September 2008 (UTC)
{{rfc|hist|lang|rfcid=6F3124E}}
::* It appears the only difference between B and D relates to non-English speaking countries. Not a big difference. <span style="white-space:nowrap;">''']''' (])</span> 00:27, 10 September 2008 (UTC
Should ] specify the start of a century or millennium as a year ending in 1 (e.g. the 20th century as 1901–2000), as a year ending in 0 (e.g. the 20th century as 1900–1999), or treat both as acceptable options with the use of hatnotes for clarity in the case of ambiguity in articles? See the discussion above. ] <sup>(], ])</sup> 14:57, 3 January 2025 (UTC)
::::I don't think there needs to be any difference at all. English-speaking or not, there's only so many ways you can arrange day, month and year. Six. Only three of the six are in widespread use, and we only support two of these in written English. --] (]) 02:53, 10 September 2008 (UTC)


*The year ending in zero, which is nowadays the most common understanding. Whether or not there was ever a year zero is irrelevant, given that AD year numbering wasn’t invented until the 500s and wasn’t widely used until the 800s. ] (]) 21:21, 3 January 2025 (UTC)
*'''Clarify point C:''' I believe (from ] that Micronesia, Palau and the Philippines also use "U.S. style dates". Canada's position should probably be clarified again for any who come to vote without reading the mass of discussion above.&ndash;] ('']'') 22:39, 9 September 2008 (UTC)
*As the 1st century is 1–100, the ] is 1901–2000, as its article says. Let us not turn this into another thing (like "billions") where English becomes inconsistent with other languages. —] (]) 22:22, 3 January 2025 (UTC)
*:Also, I do not understand what "hatnotes in case of ambiguity in articles" should mean: whenever any article uses the word "20th century", it should have a hatnote explaining whether it follows the centuries-old convention of numbering centuries or the "starts with 19 is 20th century" approximation? Perhaps it would be easier to outlaw the word "century". —] (]) 22:26, 3 January 2025 (UTC)
*:In short, '''oppose change'''. —] (]) 17:46, 4 January 2025 (UTC)
*First year of a century ends in 01, last year of a century ends in 00. This has been extensively discussed above. --] &#x1F98C; (]) 22:52, 3 January 2025 (UTC)
*The RfC does not make clear what specific change is being proposed to MOSNUM wording, and I fear will lead only to a continuation ''ad nauseum'' of the preceding discussion. For what it's worth, I '''oppose''' any change resulting in a century of 99 years. ] (]) 23:06, 3 January 2025 (UTC)
*'''Oppose change''' Century and Millennia begin in 01 and ends Dec 31, 00, like it always has and per the discussion above. Just because people make errors, like with Blue Moon, doesn't mean an encyclopedia has to. Why would we change from long-standing consensus? ] (]) 09:28, 4 January 2025 (UTC)
* '''Treat both as acceptable options.''' ] already explains both viewpoints, without describing one of them as "correct". Generally our business it not to arbiter truth (which in this case doesn't exist anyway, as either viewpoint is just a convention), but to describe common understandings of the world, including disputes and disagreements where they exist. ] doesn't privilege a particular POV here, and neither should ]. ] (]) 16:31, 4 January 2025 (UTC)
*:All of our articles on individual centuries mention only the traditional point of view where the first century starts in year 1 and each century has 100 years. There is no need for ] to do anything else. —] (]) 17:46, 4 January 2025 (UTC)
* '''Oppose.''' If this matters to you, convince the academic sources to adopt the change, then Misplaced Pages can follow. ] (]) 18:14, 4 January 2025 (UTC)
* '''Oppose change''' I prefer centuries to begin with --01 and end with --00. I'll not bother with any arguments, since I think this boils down to personal preference. I do oppose allowing both options, as that leads to confusion and edit wars. ] 18:20, 4 January 2025 (UTC)
*:Why is it personal preference to favour 1-100 AD over 1 BC-99 AD? The latter choice leads to the first century BC running from 101 to 2 BC. I find the asymmetry highly unorthodox (and hence hard to justify). ] (]) 12:37, 6 January 2025 (UTC)
*::You wouldn’t start at 1BC for the first century AD in either case though. You would just treat “century” as the name for the period, and ignore that it only has 99 years. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 19:22, 6 January 2025 (UTC)
*:::You seem to be saying the choice between a century (the first, whether ] or ]) of 99 or 100 years amounts to personal preference. Do you have credible sources showing they are equally valid? ] (]) 19:23, 7 January 2025 (UTC)
*'''Oppose treating both as acceptable''' This would lead to endless confusion. ] (]) 22:02, 5 January 2025 (UTC)
*'''Oppose''' change; century starts at ###1 and ends ###0 <!-- Template:Unsigned --><small class="autosigned">—&nbsp;Preceding ] comment added by ] (] • ]) 23:18, 5 January 2025 (UTC)</small>
* '''Strongly oppose''' any change resulting in more than one definition of a century. The reasons seem self-evident, and others have spelt them out above. In a nutshell, such a change would be a retrograde step, against the spirit of the MOS. ] (]) 23:21, 5 January 2025 (UTC)
*'''Just use '00s.''' Why on Earth should MoS <em>ever</em> encourage using wording that will be misunderstood by many or most people? To most people, "20th century" means 1900-1999. To pedants of history, it means 1901-2000. Cool. We should try to not confuse either of those groups. If I had to pick one, I'd say confuse the pedants, but fortunately we don't have to pick, because a third option exists: "1900s" (etc.). That's the phrasing I've always used on Misplaced Pages, for this exact reason. It's consistent with how we refer to decades (see vs. ). It's universally understood. It avoids silly arguments like this one. Let's just do that. <span style="font-family:courier"> -- ]</span><sup class="nowrap">&#91;]]</sup> <small>(])</small> 23:36, 5 January 2025 (UTC)
*:And to put this in terms of what the wording should be, I would suggest something like {{tq2|Because phrases like {{!xt|the 18th century}} are ambiguous (sometimes used to mean 1700–1799, sometimes 1701–1800), phrases like {{xt|the 1700s}} are preferable. If the former is be used—for instance, when quoting a source—an explanatory note should be included if the two definitions of ''n''th century would lead to different meanings.}} <span style="font-family:courier"> -- ]</span><sup class="nowrap">&#91;]]</sup> <small>(])</small> 23:52, 5 January 2025 (UTC)
*::Is this a joke? <small>Sorry if I ruined it by asking.</small> <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 23:56, 5 January 2025 (UTC)
*:::No? From any descriptive point of view, there is no widely-accepted definition of "''n''th century". Some Wikipedians thinking there <em>should</em> be a widely-accepted definition doesn't make it so. And MoS should not be in the business of encouraging ambiguous wording. Instead we should encourage solutions that avoid ambiguity, ]. <span style="font-family:courier"> -- ]</span><sup class="nowrap">&#91;]]</sup> <small>(])</small> 00:05, 6 January 2025 (UTC)
*::::Ah, sorry. This is all just not the question at hand though, and it directly contradicts current (well-positioned) guidance.
*::::In any case, I’m sure we’re better off with the ambiguity between 1900–1999 and 1901–2000, which, in most cases, is not really a problem. Your idea introduces an ambiguity between 1900–1910 and 1900–. This is explicitly called out by ], of course. And does “1700s” even solve the issue of which year to start or end with? It {{em|implies}} that the century starts with 1700, but not explicitly. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 03:05, 6 January 2025 (UTC)
*:We should avoid use of "1900s" to mean anything other than 1900-1909. ] (]) 12:29, 6 January 2025 (UTC)
*::What's funny is I have never heard people talk about the 1500s, 1600s, 1700s, 1800s or 1900s, as anything except Jan 1 00 to Dec 31 99. Always 100 years. I checked and I'm shocked our wikipedia article only covers 1900-1910. The only time it gets used as a decade is when the parameters are specifically talking about the 1930s, 1920s, 1910s, and 1900s. Without that fine tuning it's always 100 year period. It would be used , or . Usually I would say the "first decade of the 1900s" with no other context. I would amend your comment to say we should never leave 1900s dangling without context. And that's only for 1900s, not anything else.] (]) 19:36, 6 January 2025 (UTC)
*'''Oppose treating both as acceptable'''; otherwise indifferent to 31 Dec 1999 vs 31 Dec 2000. This is a style decision, but one that affects a lot of content. To use both would be a terrible solution. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 23:52, 5 January 2025 (UTC)
*'''Oppose change'''; continue using "20th century" for 1901–2000 and "1900s" for 1900–1999. ] (]) 03:48, 6 January 2025 (UTC)
*'''Oppose change''' - The ''n''{{sup|th}} century is 01-00, you can feel free to use "the xx00s" for 00-99. Neither is prefered to the other, but the meaning is determined by which you use. ] (]) 04:53, 6 January 2025 (UTC)
*:Per the MOS, and as Dondervogel 2 most succinctly puts it above: {{tq|We should avoid use of "1900s" to mean anything other than 1900-1909.}} <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">]</span>&nbsp;(])</span> 19:25, 6 January 2025 (UTC)
*::I somewhat disagree. It is a very ambiguous term so we should avoid use of 1900s at all without context, because obviously readers will be confused. I sure would since I would immediately think a 100 year period just like 1800s , 1700s, and 2000s (25+ years thus far). ] (]) 07:16, 7 January 2025 (UTC)
*'''Oppose''' treating them both as acceptable. I imagine this could lead to headaches concerning inclusion in categories, list articles, timelines, templates, etc. ] (]) 01:23, 8 January 2025 (UTC)


== Sorting of numerical data with mixed units ==
:* Thank you MDCollins. I revised option C per your observation. <span style="white-space:nowrap;">''']''' (])</span> 01:17, 10 September 2008 (UTC)


I need to implement sorting for a table column that mixes different units, but there is no existing guidance on how to do this. For example, the ] column on ] uses values with different units, ranging from nanoseconds to years. (For years, NUBASE2020 uses a conversion calibrated to the ]: {{nowrap|1=1 year = 365.2422 d}}.{{NUBASE2020|ref}}) –] (]]) 04:48, 6 January 2025 (UTC)
*I can support fixed text dates for the expected reader's benefit (C) so long as there is the (future) possibility that ALL dates will be displayed according to user date preferences if they are defined. ] (]) 01:29, 10 September 2008 (UTC)


:Try this:
:* Truthanado, in the future, when/if U.S. readers are accustomed to international date formatting and that is a thoroughly natural and fluid way of reading dates for that readership, the Misplaced Pages should go with the flow. It’s all about making text flow as naturally as possible for the likely audience. For that matter, we can loose “feet” and “pounds” in all our articles after the U.S. converts over to the SI. Again, go with the flow. <span style="white-space:nowrap;">''']''' (])</span> 01:37, 10 September 2008 (UTC)
{|class="wikitable sortable"
:**I think you'd be hard pressed to find an American reader confused by the "European" date format. (So long as we're talking long dates and not short dates like mm/dd/yy!) That's why I'd like an option for "always use dd mmmm yyyy" or "always use the first contributor's choice". All four of these options require a different format for U.S. topics. ] <sup><small><small>]</small></small></sup> 02:02, 10 September 2008 (UTC)
!value!!name

*The "common ground" point about Canada is not there. Now, I guess it applies to A, B and D. Perhaps a note above the table? ] ] 01:44, 10 September 2008 (UTC)

* Sapphic. Yes, your vote statement (''“Autoformatting makes this entire poll irrelevant”'') is true—but only for some editors (0.1% of Misplaced Pages’s readership). Autoformatting doesn’t work for 99.9% of Misplaced Pages’s readership (I.P. users and even registered editors if they haven’t set their user preferences). In those cases, writing <code>{{nowrap|<nowiki>], ]</nowiki>}}</code> in an article on a European subject results in {{nowrap|“], ]”}} for virtually ''everyone'' who reads the article. Since the article is on a European subject, it ought to use European date formatting. Also, this abomination: <code>{{nowrap|<nowiki>]</nowiki>}}</code> produces {{nowrap|]-]}} for 99.9% of our readership instead of the pretty-looking, spelled-out dates you’ve been thinking it’s been producing. <span style="white-space:nowrap;">''']''' (])</span> 01:50, 10 September 2008 (UTC)

* Tony: I don’t understand your point. Please explain your point in detail and what you would propose. What is it about Canada that isn’t resolved? <span style="white-space:nowrap;">''']''' (])</span> 01:50, 10 September 2008 (UTC)

* Tony: Pondering your 01:44, 10 September 2008 post some more, I would think the best way to handle Canada is to discuss here, what the unresolved issues are with it and try to identify what the common ground is, <u>and then to tweak each option individually as is required to properly address Canada.</u> Making guideline wording internally logical and consistent isn’t easy and I’m not at all confident that it will be practical to make a fits-all, global statement (a “note above the table”) about Canada that will properly drop into each rule. <span style="white-space:nowrap;">''']''' (])</span> 01:57, 10 September 2008 (UTC)
*Powers: The actual implementation of (A) or (B) would probably resemble the present wording, using ''generally'', so variations in usage and in editorial preference could change from the predominant national format. ] <small>]</small> 14:38, 10 September 2008 (UTC)

* Anomie⚔: did you read option C beyond its title??? You wrote that it ''“invites insane levels of speculation over who this ‘likely readership’ really is—most cases where the ‘likely readership’ can really be determined can probably be more easily settled by applying the ‘strong national ties’ rule.”'' In actuality, it ''is'' a “strong national ties” guideline. The guideline boils down to “If it’s an article related to the U.S., use U.S.-style dates, otherwise use international-style dates.” <span style="white-space:nowrap;">''']''' (])</span> 17:44, 10 September 2008 (UTC)

*What about tables where RFC 3339 (ISO 8601) dates make the info comparable, sortable, doesn't cause line breaks, nor weird middle alignment in other cells? How about RFC 3339 dates in references? What if the first editor of an article was a scientist who used the RFC 3339 format? Why unlink and force people to read middle-endian dates when they've already set their preferences for small-endian of RFC 3339? -- ], 2008-09-10]19:10z

**RFC 3339 contains these provisions:
***"There are many ways in which date and time values might appear in Internet protocols: this document focuses on just one common usage, viz. timestamps for Internet protocol events." Since our articles rarely describe Internet protocol events, we should never describe whatever we adopt as RFC 3339, even if we end up adopting something that looks similar (which I don't advocate).
***"All times expressed have a stated relationship (offset) to Coordinated Universal Time (UTC)." We often give dates without knowing or caring about the time zone; this is another reason this RFC does not suit us. --] (]) 19:35, 10 September 2008 (UTC)
**ISO 8601 requires the Gregorian calendar, and agreement from the reader before using any year before 1583. We have lots of old dates, so this does not suit us very well. --] (]) 19:35, 10 September 2008 (UTC)
***] says it uses the ], but this is the same as anything else we use. I don't understand the problem with old dates that you're proposing. If it's necessary to express a Julian calendar date, it's still possible to use the conventions of YMD order, hyphen separator, etc.; this is no worse than any other date format. --] (]) 20:34, 10 September 2008 (UTC) 2008-09-10T20:34Z (])
****You certainly can use the "YYYY-MM-DD" format in a way that violates ISO 8601, '''if''' you are prepared to invent and gain consensus for a new standard, and then communicate that standard to editors and readers. Just be sure you don't call it ISO 8601. --] (]) 20:44, 10 September 2008 (UTC)

=====Comments on poll itself=====
] rarely resolve anything here. This one was unnecessarily geeky; plain-text polls work just fine (to the extent ]). It should not have been phrased ]. Adding a "the vote so far" line in the middle of a poll is ] and ]. A and B ], and obvious other options are missing, so the poll's data set is ]. There is no ] in favor of any particular option, so all this will result in is a finding of "no consensus". This should have simply continued as a normal ]-building discussion. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 22:51, 10 September 2008 (UTC)

:Polls are extremely useful for provoking debate and are invaluable for finding out what editors’ opinions on a subject are. Much thought is exchanged in these forums. As for a finding of no consensus, as the lead-in intro speaks of, if there is no clear consensus (and one doesn’t seem to be developing here), we can hold a run-off poll with the two highest scoring options and see if a general consensus develops. If there is no status quo, we can just leave MOSNUM guidelines as they currently are, or editwar on MOSNUM. <span style="white-space:nowrap;">''']''' (])</span> 23:06, 10 September 2008 (UTC)
::Right... I guess that's why ] was written, along with ] and ], all of which have way, way more buy-in than ] (if you don't believe me, check the "What links here" pages; the latter has under 50 links, while the page that WP:POLL resolves to has over 2000, and that's not counting all the references to the Meta page). You can assert all you like how "extremely useful" polls supposedly are here, but a huge percentage of editors disagree with you. A run-off poll? ''You have to be kidding.'' I don't know if you were around for the ] debacle, but it was a debacle pretty much precisely ''because'' it turned into a divisive poll, and the hundreds of involved editors factionalized, leading to a breakdown in normal consensus-building processes. I can already see that happening here on a smaller scale. I'm not sure what you mean by "if there is no status quo"; "status quo" means "the current situation", and of course there is one. I'm not sure why you want to polarize this so much (into a poll to begin with, into a two-option runoff if you don't get what you want, into a ] of the binary choices "do nothing" and "editwar", etc.) This is not ], and this is not a war between the Forces of Light and Darkness. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 23:20, 10 September 2008 (UTC)

For a topic that supposedly found consensus this is sure a hot potato. I think that it is obvious at this point that regardless of how many Suport and oppose votes it got this topic does not meet consensus.--] (]) 22:27, 10 September 2008 (UTC)
:Don't confuse the idea of deprecating date autoformatting because of all of its problems, which has been building consensus for ''years'', with a squabble over how to fix a problem of the aftermath of that decision. They are different conversations. — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 23:20, 10 September 2008 (UTC)

:Kumioko: Not yet anyway. We’ll see if one develops with a run-off vote. More contentious issues (like the IEC prefixes) were sorted through with polls. This date issue isn’t nearly as contentious. <span style="white-space:nowrap;">''']''' (])</span> 23:19, 10 September 2008 (UTC)
::There is no point in a "run off vote". Misplaced Pages operates on consensus (] is a policy, not a guideline), not voting (], including ] is a policy, not a guideline). Even ] makes it clear that polls should only be used to ''help build consensus'', not as an actual voting mechanism. The only outright votes on WP are ] and related (bureaucrats, board members, ArbCom, etc.), since they are elections of human "officials". — <b><span style="font-family:Tahoma;">]</span></b> &#91;]&#93; &#91;]&#93; <b>‹(-¿-)›</b> 23:35, 10 September 2008 (UTC)

* SMcCandlish: Your position with your 4-0-0-0 vote is clear. You participated in a poll, and then you declared all polls to be evil. You can’t have it both ways. Clearly, a lot of editors want to participate in this. So stop vandalizing this page by deleting polls. We’re trying to see if we ''can'' develop a consensus here and your obstructionist moves get in the way of that objective. <span style="white-space:nowrap;">''']''' (])</span> 00:09, 11 September 2008 (UTC)

===Run-off oll on guideline for writing fixed-text dates===
Let’s see if we can develop a general consensus now. Which guideline do you support for determining the most suitable fixed-text date format (2&nbsp;February 2009 or February&nbsp;2, 2008) editors should use in Misplaced Pages’s articles?

The average scores in the ] as of —00:00, 11 September 2008 (UTC)—are as follows:<p>

Option A = 1.89<br>
Option B = 1.58<br>
Option C = 1.94<br>
Option D = 1.06<p>

'''(A) ] (date format follows dialect of English most suitable for the article, default to first major contributor—no list of countries):''' Date format follows language variety; month-day format is considered a feature of U.S. English, just as the spelling "color" is. Where ''both'' ENGVAR is unclear ''and'' there is no strong tie to an English-speaking country, the "first major contributor" rule applies.<p>

'''(C) Default to international unless U.S. and its territories—listed countries for editors’ convenience:''' For articles on, or strongly associated with, the U.S. or ] (or countries listed in this guideline that use U.S.-style dates: Micronesia and Palau), editors should use the U.S.-style date format (“February&nbsp;2, 2008”), otherwise, editors should use the international date format (“2&nbsp;February 2008”) in articles. The dialect of English used for the article (“colour” v.s. “color”, etc.) shall have no bearing on the chosen date format. ''New'' articles on or strongly associated with Canada should use the international format but, for existing articles related to Canada, whichever format was used by the first major contributor shall be retained.<p>

<hr/>
'''Note that the below chart does not allow <nowiki>~~~~</nowiki> signatures to be used. You must copy/paste or hand-edit your signature. For assistance in writing your signature, you may copy the time below in red <u>from the preview window</u> after clicking on “Show preview” while in edit mode:'''<!--
DON’T COPY THIS CODE BELOW --><br>
<font color = red>'''{{CURRENTTIME}}, {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} (UTC)'''</font color><hr/>
<!-- ONLY COPY TIME/DATE FROM THE PREVIEW WINDOW -->

:<strong style="font-size: 90%;">0 = Complete opposition </strong>
:<strong style="font-size: 90%;">1 = Could be much better </strong>
:<strong style="font-size: 90%;">2 = Ambivalence </strong>
:<strong style="font-size: 90%;">3 = Could be improved, but I support this </strong>
:<strong style="font-size: 90%;">4 = Complete support </strong>

{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f5f5f0; border: 2px #3E3E3E solid; border-collapse: collapse; font-size: 95%;"
|- |-
|data-sort-value="100"|100 years||big
! colspan="6" style="background:#3E3E3E" align="center"|<font color=white><span style="margin-left:3em">DEGREE OF SUPPORT FOR OPTION</span><font color=white><span style="margin-right:2.6em">&nbsp;</span></font>
|- |-
|data-sort-value="{{#expr: 2/365.2422}}"|2 days||tiny
|style="background:#d9d9d3" align="center"|'''Editor'''
|style="background:#d9d9d3" align="center"|'''&nbsp;&nbsp;A&nbsp;&nbsp;'''
|style="background:#d9d9d3" align="center"|'''&nbsp;&nbsp;C&nbsp;&nbsp;'''
|- |-
|data-sort-value="{{#expr: 10/365.2422}}"|10 days||tiny
|style="background:#d9d9d3" align="right"|]
|align="center"<!-- A -->|0<ref>My opposition to option A (], or “English variation”), is that I am an American and use American English in all my contributions. I ''also routinely use international-formated dates'' in articles that have no strong ties to the U.S., such as ]. Note that the French are more closely tied to the development of the kilogram than any other country and the kilogram clearly has no strong national tie to the U.S. So it makes no sense in my book to require that dates in the ''Kilogram'' article follow the U.S. convention (“February&nbsp;2, 1799”) just because the article was written using American English. <span style="white-space:nowrap;">''']''' (])</span> 23:33, 10 September 2008 (UTC)</ref>
|align="center"<!-- C -->|4<ref>I don’t see the need for using international date formats in an article on a U.S.-related subject (like a U.S. national forest), just because a UK author was the first major contributor and used the spelling “colour” in the article. IMO, it should be one, simple rule:{{cquote|If it is an article closely tied to the U.S. use the U.S.-style date format, otherwise, use international date formats in articles.}}

There’s no legitimate need for any more complexity than that. If we are to start keying the date formats used in articles to the dialect of English the editor happened to use while writing the article, all the articles I’ve been writing (science-related topics, such as ]) would have U.S.-style dates because I used U.S.-style spelling in those articles. That makes no sense. Keep it simple. Dragging English-language dialect complexities into this discussion seems totally unnecessary.<p>The whole point of making it country-based is to make the article read as smoothly as possible for the likely audience. If it is an article on a U.S. National Park (likely a readership dominated by U.S. citizens), then use U.S.-style date formats to make the article as natural for that audience. For everything else, use the international date format. This should all be about making Misplaced Pages better for our ''readers''; we needn’t be so concerned about hurting the feelings of editors. <span style="white-space:nowrap;">''']''' (])</span> 23:33, 10 September 2008 (UTC)</ref>
|- |-
|data-sort-value="{{#expr: 20/365.2422}}"|20 days||tiny
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|- |-
|data-sort-value="10"|10 years||mid
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|- |-
|data-sort-value="2"|2 years||small
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|}
|align="center"<!-- A -->|
:Note that anything less than a year is NumDays/365. Of course, you can choose your own base unit.
|align="center"<!-- C -->|
:See ] <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 05:04, 6 January 2025 (UTC)
::I don't understand your proposal. I'm pretty sure that sort will need numerical sorting with all values converted to a common unit. –] (]]) 05:24, 6 January 2025 (UTC)
:::It is more obvious when you look at the wiki mark-up: <syntaxhighlight lang=wikitext>{|class="wikitable sortable"
!value!!name
|- |-
|data-sort-value="100"|100 years||big
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|- |-
|data-sort-value="{{#expr: 2/365.2422}}"|2 days||tiny
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|- |-
|data-sort-value="{{#expr: 10/365.2422}}"|10 days||tiny
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|- |-
|data-sort-value="{{#expr: 20/365.2422}}"|20 days||tiny
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|- |-
|data-sort-value="10"|10 years||mid
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|- |-
|data-sort-value="2"|2 years||small
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|}</syntaxhighlight> The <code>data-sort-value</code> is what the sort looks at. In this case I have chosen 1 year as the base unit. So 10 days is 10/365.2422 -> {{#expr: 10/365.2422}} . The rest is just for display. Click on the up/down arrows to sort increasing, sort decreasing or return to original (unsorted) order. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">]&nbsp;<span style="font-size:xx-small; vertical-align:top">]&nbsp;</span></span> 05:35, 6 January 2025 (UTC)
|align="center"<!-- A -->|
::::Sure, why not. –] (]]) 02:10, 7 January 2025 (UTC)
|align="center"<!-- C -->|
|-
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|-
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|-
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|-
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|-
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|-
|style="background:#d9d9d3" align="right"|] <!-- POLL INSTRUCTIONS: Place a number (0–4) in each of the four options below. Because autosignatures (~~~~) do not work in this table, use the autosignature time stamp facility at the top of this section when in preview mode. You may use a "<ref></ref>" comment after one of your poll responses. Zero means you hate the option, four means you love it. Please delete these instructions from your response. -->
|align="center"<!-- A -->|
|align="center"<!-- C -->|
|}


=====Run-off poll comments=====
<references/>

=====Comments on "Run-off poll comments"=====

==Changing date formats==
Hello. A recent argument has come up on the ] article. I created the article and since then it has always used the date-month-year date format, which according to the MoS is perfectly acceptable for Canadian-related articles. My understanding has always been that date formats should not be changed unless for good nationalistic regions (i.e. on an article about a British person, it would be acceptable to change to the UK format from the US format). I have understand that changing date formats otherwise is disruptive and unnecessary. A user, G2bambino, has insisted on changing to the month-date-year format for Phillips' article saying that most Canada articles use that. I have explained that the MoS says either can be used and advises against changing date formats unless necessary. But he does not believe and continues to change it. Please can someone shed light on what the MoS says - should date formats be changed if the current one is perfectly acceptable for that article and has always been used.--] (]) 11:30, 9 September 2008 (UTC)
:Both formats are acceptable for Canada and therefore changing date formats is disruptive. See the comments at the top of ]. This applies regardless of which way the changes are made. --] (]) 11:35, 9 September 2008 (UTC)
::This is exactly what I thought, and thank you for the clarification.--] (]) 11:37, 9 September 2008 (UTC)
:::This would have been an issue with or without the recent debates on (1) the removal of DA, and (2) the selection of date format for articles related to non-anglophone countries, since the Canadian situation is unchanged. I do think it needs to be spelt out in the MOSNUM text, though: clearly, the existing format wins out, and if your antagonist wants a duel to the death, go back in the edit histories to determine the first choice, as for our highly sucessful ] procedure. I'll go to that article now. ] ] 11:40, 9 September 2008 (UTC)
::::The first date format used for the article was day-month-year (I created the article), and this has been used ever since and I don't believe anyone has ever tried to change it before.--] (]) 11:43, 9 September 2008 (UTC)
:::::Yep, 10 seconds at the edit-history page confirmed that, and I've left a note to this effect at the talk page. Easy-peasy. ] ] 11:44, 9 September 2008 (UTC)
::::::And is that the new guideline, then? The first date format used stays indefinitely? If that's to be the case, and it applies across the board, then fine. I'll adhere to that and keep it in mind for future. But, I want to be clear that that is indeed the way things will be set from now on across all Canadian articles. --] (]) 15:09, 9 September 2008 (UTC)
:::::::With two qualifications: The format may be changed by consensus. For that matter, I don't think that most of us who discuss the matter are Canadians: if we misrepresent what Canadians find natural, the provision here should change.] <small>]</small> 15:52, 9 September 2008 (UTC)
::::::::This was just one person's personal preference. There is no consensus on date formats in Canada, given the country's close ties to both Britain and the U.S. and the rather heterogeneous origins of its population, so if an article starts out with one date format it should generally stay that way. Additionally, Phillips is related to the British family, so maybe the British date format is preferable, and she was born and grew up in Quebec, which uses the French date format (3 Mai 1978).] (]) 16:47, 9 September 2008 (UTC)
:::::::::As I said to you at ]: thanks for your input, but you're unfortunately wrong on a number of counts. The facts so far are 1) either format is acceptable, 2) most Canadian subject articles use the '' , '' form. I'll further elaborate that this therefore isn't a matter of "personal preference," unless you're specifically alluding to the desire to draw the formats of articles with a common subject nationality into some kind of consistency; I'm not sure how many times I have to repeat myself about what the majority of articles with Canadian subjects use, regardless of whether or not that reality emerged purely by coincidence. (I imagine it evolved as such because that is typically how english Canadians write the date; never as '' ''.) If, however, there is some policy (whether existing, or soon to be) that says something along the lines of: ''for articles with Canadian subject matter, either date format is acceptable, however that which is first used shall remain unaltered and be the benchmark format which all subsequently added dates shall follow'', then that would trump consistency across articles, and guide future editing. --] (]) 20:12, 9 September 2008 (UTC)
*Yep, that's the advantage of being the first major contributor to many articles: you get to choose those optional styles. I don't see the matters you raise as being enforceable reasons to change the existing formats—they are too prone to debate and argument as to their importance—an invitation to disputes, which is exactly what we want to prevent. In any case, does it really ''matter''? The differences are trivial. This is a case of leave well what is there. ] ] 17:02, 9 September 2008 (UTC)
::I'm not exactly sure that trying to attain consistency is really all that trivial, per say. But, trust we Canadians to say "whichever makes you happy!" and therefore blow away much ability to have consistency. I'm just curious, though: will the ''first come, permanently stay'' idea become a guideline for all Canadian articles? From people's words above, I get the impression that it's currently not, and can't find evidence to the contrary. --] (]) 19:51, 9 September 2008 (UTC)
::*I think we may need something even more cut and dried than 'first major contributor'. The first major contributor's efforts may have been subsequently eclipsed by another major editor. Will the person who then comes along to perform the audit function go to the page history to ascertain who is the first major contributor? Unlikely scenario, methinks. ] (]) 03:20, 10 September 2008 (UTC)
::::The words opening ] should be guidance enough: ''In June 2005, the Arbitration Committee ruled that when either of two styles such as 14 February or February 14 is acceptable, it is inappropriate for an editor to change an article from one style to another unless there is a substantial reason to do so.'' For an article on Canada, either style is acceptable, and the reasons given above do not seem to me to be substantial enough reason to change, especially where this results in disruption. --] (]) 03:24, 10 September 2008 (UTC)

== Proposal to temporarily disable date autoformatting ==

While I personally like the date autoformatting feature (including the date links) I realize that many people do not. So, rather than argue about this, I propose we simply perform an experiment to gauge the reaction from editors.

'''PROPOSAL'''
# Temporarily stop unlinking (or linking) of dates &mdash; except as consensus on each article's talk page dictates &mdash; for some specified period of time.
# Have the Misplaced Pages system administrators temporarily disable the date autoformatting feature in the MediaWiki configuration for the English Misplaced Pages.

That should allow us to see the response from editors, with minimal changes (one line in a configuration file, vs. hundreds of thousands of edits to articles to remove links) and in such a way as to be easily reversible should the need arise. While this proposal does nothing to address the issue of overlinking, it does address the more general issue of whether to keep date autoformatting &mdash; and if it turns out that the most people prefer that date autoformatting be turned off, then the unlinking of dates can be performed in an officially-sanctioned manner by a bot, which is far better than the scripted-but-still-manual process taking place right now. --] (]) 21:12, 9 September 2008 (UTC)

==== Support ====

* ]
* ]
* ] &mdash; I prefer we keep DA, but at least this test would help decide things one way or the other.
*'''Weak''' support, but this decision should not be made ''here''. This problem arose precisely because many editors with opinions on date formatting did not know that MOSNUM was discussing the problem. This affects many users, and many articles. ] is the minimum, and a banner announcement would be better. ] <small>]</small> 14:43, 10 September 2008 (UTC)

==== Oppose ====
*'''Oppose in form suggested''' --] (]) 21:43, 9 September 2008 (UTC)
*'''Strong oppose''' mostly because we should never live-test a feature that the bulk of the users aren't aware of. Or basically, implementing a change to "shock" the environment (in order to get editor response) will be a terrible backlash. --] 22:26, 9 September 2008 (UTC)
*'''Oppose,''' for same reasons as Masem. ] (]) 01:22, 10 September 2008 (UTC)
*'''Oppose''' - Personally, I don't really care, because I do not use it. However, it appears to me that autoformatting is not the cause of our problems, so we should look in a more appropriate place. Disabling a function which a sizeable minority uses is just going to be a huge source of complaint that we haven't got a handle or the real problem. ] (]) 03:12, 10 September 2008 (UTC)

==== Comments ====

*I'm opposed in principle to disabling the autoformat feature, as it would mean tossing out a good function because aspects of it are not working. That aside, if this test proceeds, it must be separate from the other functions of the date feature (such as the ability to control how dates and times display in a user's watchlists, histories, and so on.) The "preferences" selection also controls that display, but there is no reason to remove that functionality. --''']'''''<small><sup>]</sup><sub>]</sub></small>'' 21:30, 9 September 2008 (UTC)
:While the same user preference settings are used in both cases, only the in-article date autoformatting is enabled/disabled with the <code>$wgUseDynamicDates</code> configuration setting. I also disagree with disabling the autoformat feature, and am hoping that by temporarily disabling it, enough of an outcry will come from upset editors that it becomes clear to everybody involved that there is more support for keeping it than disabling it. But I'm also open to the possibility that I'm wrong, and that only a small percentage of editors will be upset, or that even more will be quite happy with having autoformatting disabled. The majority here seem to dislike autoformatting, but I don't believe the regular editors of this page are anything like a representative sample of the concerned editors, and so I think this experiment of temporarily disabling autoformatting is the best, most visible way to attract attention to the issue. --] (]) 21:40, 9 September 2008 (UTC)

::I believe if the trial is to be conducted, the articles should look as proponents of autoformatting removal ultimately want them to. That is, dates that are autolinked without a pipe, directly to a month, day article, and/or to a year article, should have the link removed, as well as leave the date in the same format as in the wikitext. Otherwise the test is meaningless. --] (]) 21:47, 9 September 2008 (UTC)

:::That defeats the whole point of the test, which is to see what the reaction will be to the removal of autoformatting, '''without having to change hundreds of thousands of articles.''' If (as I expect to happen, but maybe I'm wrong) a lot of editors complain after discovering that date autoformatting has been disabled, then it would be better to have to only restore one configuration setting, rather than fix hundreds of thousands of articles. On the other hand, if the temporary disabling of autoformatting turns out to be popular, it can be left off permanently, and a bot can handle the unlinking in a matter of days. --] (]) 22:05, 9 September 2008 (UTC)


::::As far as I can see, most of the editors here don't object to the autoformatting per se, merely that the vast, vast majority of wikipedia readers don't see the autoformatted text, and instead see a whole jumble of dates in inconsistent formats. The removal of the links is related to, but not just a consequence of the autoformatting; they are being removed because they link to meaningless trivia unrelated to the subject in question. The removal of the "displayed links" but keeping the autoformatting by nowiki tags solves the latter problem, but not the former, in terms of what readers actually see. If the autoformat can be disabled temporarily, it might make editors more aware of what "readers" actually see. This of course can be tried on a local level by turning off your preferences, even if only for a short while. Personally I would prefer to see ''consistently formatted'', unlinked dates; I am perfectly happy reading dates that aren't in my (former-) preference/default style.&ndash;] ('']'') 22:10, 9 September 2008 (UTC)

:::::I object to autoformatting per se as it is implemented, and I object to all the proposals to fix it that I have seen so far. I feel the minimum requirements for autoformatting are (1)accept for input a date that has been marked up with a means to determine if it is AD or BC, and a calendar (Julian or Gregorian) (reasonable defaults could apply) and (2) output the result in a form that is not ambiguous, using an acceptable default for readers who are not logged in or who have not selected a preference. The lack of ambiguity requirement rules out all-numeric format. --] (]) 22:44, 9 September 2008 (UTC)

::::* Autoformatting introduces ''far'' more trouble than it’s worth. Everything about it sucks: it makes *pretty* date formats ''(*sound of audience in enthusiastic applause and cheering*)''—but only for registered editors who’ve set their user preferences ''(*sound of audience doing a disappointed “awe” in unison*)''; it automatically creates links to other articles ''(*sound of audience in enthusiastic applause and cheering*)''—but the links are to mindless lists of random trivia that don’t have jack to do with the article 99% of the time ''(*sound of audience doing a disappointed “awe” in unison*)''. Good riddance. <span style="white-space:nowrap;">''']''' (])</span> 01:31, 10 September 2008 (UTC)

::::: Then you support a trial period of having it disabled? --] (]) 01:52, 10 September 2008 (UTC)

:::::* Sorry, no Sapphic. Autoformatting could be a wonderful tool if Misplaced Pages got under the hood of how its servers worked and made it so the requesting reader’s I.P. address could be mapped to a country. Then we could make autoformatting work for ''everyone''. But such a radical change to the way Misplaced Pages works behind the scenes isn’t in the offing anytime soon. It was simply wrong of the developers to have made a tool that allows editors to write what is essentially custom content just for us editors to enjoy but which often totally mucks things up for regular readers. Misplaced Pages isn’t about ''us''; it’s for making articles that read as smoothly as possible for regular readers. The best option—the one I support—is to no longer use these tools and to deprecate their existence from current articles. <span style="white-space:nowrap;">''']''' (])</span> 02:10, 10 September 2008 (UTC)

::::::* DA and wikilinking of dates ought to be completely independent, and the discussion should also be independent. It will never be resolved until we decide to address it in those terms. I care immensely about date-wikilinking because it exaggerates the blue sea of mess, but I really couldn't care less about the debate here if an article should carry international or American date formatting (except that it should be one or the other). DA is fine if it didn't have to rely on wikilinked dates. Then each WP reader has a choice whether to engage DA or not. ] (]) 03:07, 10 September 2008 (UTC)

::::::: There is a submitted to do exactly what you suggest. You can vote for it at that page, if you like. There are actually two patches for that bug, so make sure to add a comment explaining that you prefer the one that turns off linking of DA-formatted dates, as opposed to the one that autoformats non-linked dates. --] (]) 17:34, 10 September 2008 (UTC)

←Let me get this right: disabling would render all dates as their raw format (without square brackets), and would display them in plain black text such as we see the post-signature dates, yes? Would it mess up any template-generated dates? Is is possible for WP alone to disable it, not WikiMedia (this is the assumption)? ] ] 03:27, 10 September 2008 (UTC)

:No, but if that's preferred, it could be implemented with a patch (even simpler than the last one, since it would just be removing the links and leaving the format untouched.) So far as I know (and judging from bug requests to have it turned on in other languages) date autoformatting is only implemented on the English wikipedia anyway, so WP == WikiMedia in this regard. I'm not sure what you mean exactly about template-generated dates, but if the template outputs dates with non-piped, non-prefixed linked dates then it would affect them the same as any other similarly linked dates.

:Without a patch, date autoformatting can be disabled (with a one-line configuration change) but linked dates will still be linked; they just won't be reformatted according to user preferences. So disabling DA that way would be the same as switching all editors to the "No Preference" date formatting option. --] (]) 17:16, 10 September 2008 (UTC)

:: I have submitted a new that will effectively nullify date autoformatting. It causes non-piped, non-prefixed linked dates to be displayed ''without'' a link and in the same format as they are in the page code. If you think that would be more useful for testing, let us know. --] (]) 23:25, 10 September 2008 (UTC)

Why are we voting on this? WP Admins don't have the power to do this. We'd have to make a request to the developers and when it comes to autoformatting I think we've shown that to be akin to talking to a brick wall ... in a vacuum ... ]<sub>&nbsp;]·]</sub> 09:02, 10 September 2008 (UTC)

:Please stop being obnoxious and insulting to the developers. There ''was'' response from them to the date formatting issues &mdash; several years ago &mdash; and the developers at the time have since been blamed for implementing what was really just a poorly thought-out process. ''Of course'' they want nothing to do with it now, unless a coherent plan can be arrived at that takes into account all positions (aka a "consensus.") We're voting on this particular proposal because it's about as minimalist as it can get (to help with building consensus.. start simple) and it has the very concrete effects of limiting the friction (by stopping mass unlinking) and gathering useful data (by means of an experimental disabling of DA to gauge editor opinion.) After the test, we would have a very good indication of the percentage of editors that are happy with having DA disabled, vs. those that are upset about it. If the proposal gets enough support then it can be brought to a wider audience, and then (assuming it continues to meet with support) to the developers. Then we can conduct a test, and then make permanent plans to either fix DA or disable it for good, based on accurate information about editor preference. Make sense? --] (]) 17:28, 10 September 2008 (UTC)

::People make mistakes, sure, but what I so obnoxiously & insultingly was referring to were the several coherent partitions to the developers to fix the mess. Anyhow, it's an interesting idea if it ''is'' possible—do you have a plan for implementing it and doing so so as not to surprise users unaware that it's an experiment we're conducting? ]<sub>&nbsp;]·]</sub> 17:49, 10 September 2008 (UTC)

:::Yes, the plan was described in my previous comment. First we build consensus here for the two-part proposal (stop mass unlinking, disable DA in the config.. or possibly apply a patch to disable it in a different way, described in a reply to Tony1 above) then we present it to a wider audience (presumably through VP or someplace) and then &mdash; assuming it meets with widespread approval &mdash; we present the plan to the developers. Since it doesn't involve any permanent changes to the system and is easily reversible, and since it would provide useful, concrete data, I believe the developers would be amenable to the proposal, ''if'' it has support from enough of the community. Presenting it at VP should limit the amount of "surprise" and in any event, getting feedback from editors is pretty much the whole point of the test, so the "surprise" factor isn't really a huge issue. --] (]) 18:26, 10 September 2008 (UTC)

==Poll being conducted==
* For those who might miss it, a poll on a proposed guideline for writing fixed-text dates is shown above. Click ''''']'''''&thinsp; to go to it. <span style="white-space:nowrap;">''']''' (])</span> 22:23, 9 September 2008 (UTC)
**Can I suggest the poll is moved to a subpage to make it easier to find? Do we need to encourage other editors to come and give their views? If so, is it possible to post a notice at the top of the people's watchlist requesting participation? I'm sure this is possible, but haven't got a clue how it works.&ndash;] ('']'') 22:33, 9 September 2008 (UTC)
*** My personal preference is to encourage the maximum number of editors possible to participate in the vote. I rather dislike conducting things in remote backwater venues. Let’s see what Tony thinks would be the best forum since he proposed that I place this here. I ''really would'' like to clearly resolve what exactly we will be voting on before we get too many more votes. It seems to me that options B and D are identical, other than the nature of the wording. <span style="white-space:nowrap;">''']''' (])</span> 00:17, 10 September 2008 (UTC)
****D requires you find out what the non-English speaking country, with no obvious tie to an English speaking country, uses as their English equivalent format, and apply that throughout the article. Right?--<small><span style="background-color: darkblue; color: white">]</span></small>|<small>]</small> 00:22, 10 September 2008 (UTC)
***** Ugh. Too much research and fussing. This is <u>en.</u>Misplaced Pages; editors shouldn’t have to research what date format some central African country uses when writing about how Gorilla habitat is disappearing in that country. What format a non-English-speaking country uses has no more bearing on making the article read smoothly for English-speaking readers than does whether the people in the central African country use tongue clicks when they speak. We really ought to make this simple: Is the article about the U.S. or closely tied to the U.S.? Then use U.S. date format. Otherwise, just use the international format. If we keep trying to make this so complex, by the time we’re done, we can get a Nobel Peace Prize for developing a hybrid of chaos, game, and quantum theories just for figuring out how to write out a God-damned date. <span style="white-space:nowrap;">''']''' (])</span> 01:01, 10 September 2008 (UTC)
******You write the paper and I'll sign it :) --<small><span style="background-color: darkblue; color: white">]</span></small>|<small>]</small> 01:11, 10 September 2008 (UTC)
******* LOL. Thanks for your support. <span style="white-space:nowrap;">''']''' (])</span> 01:24, 10 September 2008 (UTC)
*******Why do we even need the exception? Isn't the easiest way to say "always use day-month-year"? ] <sup><small><small>]</small></small></sup> 02:10, 10 September 2008 (UTC)
******** Because articles such as ] and ] will have a much higher proportion of Americans reading it than other articles not closely associated with the U.S. To keep such articles as natural and smoothly reading as possible and with few (!) brain-process interrupts, such articles should use the date format that is most natural for that audience. Misplaced Pages should not be used as a vehicle to promote change in how the world works. That’s why articles on an American muscle car will have the displacement of the V8 engine in cubic inches first, and as a parenthetical conversion to liters. We’re here to make easy-reading, informative articles that are written appropriately for a given target audience. We are not here to promote the adoption of the SI, the adoption of IEC prefixes like “mebibyte” (symbol MiB), dates formats, or anything else. We go with the flow in order to produce good articles. This mission is made a bit more complex because of the enormous breadth of the readership Misplaced Pages enjoys, the enormous breadth of the topics it covers, and the nature of the ]. <span style="white-space:nowrap;">''']''' (])</span> 02:28, 10 September 2008 (UTC)
*********Most contributors aren't going to read MoS before adding content. You pretty much have to have been an editor for a while before you are a regular user of MoS. I'd rather have good referenced content than drive editors away by hounding them over style. There's always bots or wikignomes to come along and shuffle everything into shape. I don't know what dating rituals mountain gorillas use, but in Africa it's all international format. --] (]) 03:30, 10 September 2008 (UTC)
********** Indeed, most contributors aren’t aware MOSNUM even exists. But it’s still a good thing having rules here or chaos would rule supreme. I think that, in most cases, contributors become aware of MOSNUM’s rules when edit conflict arrise and the more well informed editor cites the rule here. I can pretty much guarantee you that if MOSNUM adopts shitty rules, conflict arrises and Misplaced Pages’s articles suffer. <span style="white-space:nowrap;">''']''' (])</span> 04:15, 10 September 2008 (UTC)
*********My point, Greg, is that the conception that American readers are going to be somehow horribly jolted by the appearance of day-month-year date formats is grossly mistaken. It's a very minor issue, far different from spelling or measurements. Everyone seems to be assuming American brains will freeze when encountering these dates, without providing any evidence of that. I submit that it's not worth instituting an exception to the date formatting rule (and inviting the corresponding a) arguments over whether an article is strongly tied to the U.S. and b) inconsistency in our MOS standards, making it harder for contributors to contribute) to avoid whatever extremely minor "hiccup" in reading might result from a slightly unfamiliar date format. ''At the very least'', a nation-neutral option ought to be available in the poll. ] <sup><small><small>]</small></small></sup> 16:06, 10 September 2008 (UTC)

I am not going to take part in this poll. I have stated my preferences already, feel free to read and repeat them. I hardly noticed date inconsistencies until we started discussing it. Date formatting is less important to me than having raw text appear as WYSIWG without blue links. So I will go along with any of the options proposed by Tony. ] (]) 09:05, 10 September 2008 (UTC)

:::::::* Powers, I agree. As an American, I don’t have a problem with either format. But some editors clearly have strong feelings about it and we need to avoid editwarring and have a guideline that makes the most sense. <span style="white-space:nowrap;">''']''' (])</span> 18:45, 10 September 2008 (UTC)
::::::::* I haven't seen any serious opposition (to deprecating autoformatting, yes, but not to using dd mmmm yyyy format dates in American topics), but I admittedly haven't read all of the megabytes of discussion above. ] <sup><small><small>]</small></small></sup> 22:41, 10 September 2008 (UTC)

==History of date autoformatting and ISO-8601==
Since the recent debate concerning date autoformatting sometimes touched on how the software was originally intended to work, I have gone through old versions of this page and prepared an essay, ]. If it seems too long, skip to the "Summary" section.{{unsigned|Gerry Ashton|10:35, 10 September 2008}}

== Julian dates and templates ==

I have an interest in dates on Wikipeida, in relation to birth (and death) dates for ] and start and end dates for ] ].

Is it not possible that the existing date templates could be used,; modified so that, if a date before a certain point is entered, a prominent warning is generated, requiring a "calendar" flag be set, and, depending on the flag, the date be rendered as "DD MM YYYY (Gregorian) or "DD MM YYYY (Julian), using any DD-MM-YYYY order/format as suits the user? ] (User:Pigsonthewing); ]; ] 14:51, 10 September 2008 (UTC)

:Not everyone edits articles with the edit box, so it wouldn't be possible to raise an interactive warning flag. All that could be done is to refuse to save edits that don't meet requirements. Also, indicating Gregorian or Julian with every date in an article would be excessive. A single statement of the convention followed in a certain article would suffice. --] (]) 15:03, 10 September 2008 (UTC)

::There can be on-page warnings, like those generated, say, when coordinates are entered wrongly. Perhaps the indication could be shorter - say "DD MM YYYY (J)"? We don't seem to have a problem with repeating "BC" (or whatevr0 in articles. ] (User:Pigsonthewing); ]; ] 15:06, 10 September 2008 (UTC)
:::We probably should not; on such articles as ], where there is no possible question on almost all of them, one BC per section or less would be enough. But it is sufficiently short and commonplace (and, above all, does not interrupt the syntax) that it is not deeply intrusive. ] <small>]</small> 15:15, 10 September 2008 (UTC)
*Possible, yes: but that's in the sense that a Turing machine ''can'' perform any computable operation. Several widely supported requests have been made to the developers to change autoformatting in various ways; none have been acted on.
*Prominent warnings can be produced without affecting the software, although one which is triggered by an unlinked July 15, 1581 would be difficult to imagine.
*But is this desirable?
**It would not affect dates between 1582 and 1752 in the English-speaking world, which are a large proportion of the problem, and which may actually need clarification.
**It would not affect dates which mention only ''October 14'' with the year understood,
**On the other hand, it would force parenthetical explanations on every date in ] which mentions the year. This is bad writing, especially if there is a footnote explaining the calendar, as some articles have. Even without, who ever imagined that ''October 14, 1066'' was not Julian? (Some readers have never considered the question, but they are merely confused; they will in all likelihood remain confused by the parenthesis.) ] <small>]</small> 15:10, 10 September 2008 (UTC)

: '''"Several widely supported requests have been made to the developers to change autoformatting in various ways; none have been acted on."''' &mdash; for the record, I have acted upon every single technical request that has been pointed out to me, usually within a few hours. I have submitted '''three''' patches to modify the behavior of date autoformatting, all in response to requests made here or on the bugzilla site. The WikiMedia '''system administrators''' (who are not properly called "developers" though most of them also happen to be developers as well) will no doubt be happy to put in place whatever patches the community decides are appropriate. The problem is (and always has been) getting a broad consensus on what ''should'' be done. Stop blaming the developers and/or system administrators for the inability of editors to come up with a sensible plan. --] (]) 23:22, 10 September 2008 (UTC)

Latest revision as of 15:02, 9 January 2025

This is the talk page for discussing improvements to the Manual of Style/Dates and numbers page.
Shortcuts
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163Auto-archiving period: 2 months 
Peace dove with olive branch in its beakPlease stay calm and civil while commenting or presenting evidence, and do not make personal attacks. Be patient when approaching solutions to any issues. If consensus is not reached, other solutions exist to draw attention and ensure that more editors mediate or comment on the dispute.
This project page does not require a rating on Misplaced Pages's content assessment scale.
It is of interest to the following WikiProjects:
WikiProject iconManual of Style
WikiProject iconThis page falls within the scope of the Misplaced Pages:Manual of Style, a collaborative effort focused on enhancing clarity, consistency, and cohesiveness across the Manual of Style (MoS) guidelines by addressing inconsistencies, refining language, and integrating guidance effectively.Manual of StyleWikipedia:WikiProject Manual of StyleTemplate:WikiProject Manual of StyleManual of Style
Note icon
This page falls under the contentious topics procedure and is given additional attention, as it closely associated to the English Misplaced Pages Manual of Style, and the article titles policy. Both areas are subjects of debate.
Contributors are urged to review the awareness criteria carefully and exercise caution when editing.
Note icon
For information on Misplaced Pages's approach to the establishment of new policies and guidelines, refer to WP:PROPOSAL. Additionally, guidance on how to contribute to the development and revision of Misplaced Pages policies of Misplaced Pages's policy and guideline documents is available, offering valuable insights and recommendations.

Archiving icon
Archives
General Binary prefixes Years and dates See also


This page has archives. Sections older than 60 days may be automatically archived by Lowercase sigmabot III when more than 2 sections are present.
It has been 205 days since the outbreak of the latest dispute over date formats.

Recent edits

A string of edits by Jc3s5h and JMF. introducing and removing changes to Misplaced Pages:Manual of Style/Dates and numbers § Common mathematical symbols, raise issues that I believe should be discussed.

  1. The most recent change, permalink/1247903136, has the comment This page does not cover matrix operations., however, I do not see anything in the article to support a restriction to numerical operations.
  2. The most recent change reinstates the link to dot product, despite the comment.
  3. There seems to be disagreement on the division sign.

The questions that I wish to raise are

  1. Should that section mention {{tmath}} or <math>...</math>?
  2. Are vector operations within the scope of the article? Regardless of the answer, the dot and cross products should be treated consistently.
  3. Should there be two new rows for dot and cross product?
  4. Should there be a row for tensor product?
  5. Is obelus unhelpful since it has three forms?
  6. Should the Division sign (U+00F7 ÷ DIVISION SIGN) be deprecated in favor of Slash (U+002F / SOLIDUS)?
  7. Should U+2215 ∕ DIVISION SLASH be explicitly deprecated in favor of Slash?
  8. Should the use of "x" and "*" as multiplication signs be explicitly deprecated in favor of U+00D7 × MULTIPLICATION SIGN?
  9. Should that section show the LaTeX markup for characters in addition to the HTML character entity references?

-- Shmuel (Seymour J.) Metz Username:Chatul (talk) 10:52, 27 September 2024 (UTC)

  1. I think the page should be devoted to general articles, and <math> should be reserved for advanced math and science articles.
  2. Vector operations are not currently in the scope of the project page, and I'm not thrilled about adding them.
  3. Dot product and cross product should certainly not be addressed in the same row as any scalar operation. The multiplication dot should certainly not be linked to the "Dot product" article nor should the multiplication cross be linked to the "Cross product" article.
  4. Tensor products should not be covered in this project page because they're too advanced.
  5. I'm not willing to spend 5 or minutes figuring out what this line means.
  6. The asterisk as a multiplication sign should be limited to articles about computer languages that use it as such.
  7. LATEX should not be mentioned, since we don't use it in Misplaced Pages. This isn't a style manual for writing outside of Misplaced Pages.
Jc3s5h (talk) 19:45, 27 September 2024 (UTC)
Tbh, I wondered what this extensive list is doing in the MOS in the first place. Glossary of mathematical symbols does it better. It really needs to be reduced to cover only those symbols that have a styling issue: scalar division and multiplication.
  • The grade-school division sign should be formally deprecated, for reasons explained at division sign.
  • The 'ordinary' slash (002F) should be preferred over 2215, same logic as straight quotes and curly quotes.
  • I prefer U+00D7 × MULTIPLICATION SIGN over x, for biology as well as math but maybe that needs debate.
𝕁𝕄𝔽 (talk) 20:04, 27 September 2024 (UTC)
Comments:
  • I see no good reason to prohibit using a division sign to express division. That seems absolutely fine. The division sign article seems to say it might be confusing in Italian, Russian, Polish, Danish, Norwegian, or Swedish, but this is the English Misplaced Pages. We use points as decimal separators also, and we use commas as a thousands separator too, although that might be confusing in other languages.
  • I also see no good reason to prohibit using an asterisk for multiplication; it seems well-understood, easy to type, unambiguous, and common in practice. I agree with not using "x" for multiplication, although I think it's OK to express "by" relationships for 2x4 lumber, 4x8 sheets of plywood, and 4x4 trucks.
  • <math>x</math> (i.e., x {\displaystyle x} ) looks different from ''x'' (i.e., x), and those look different from {{math|''x''}} (i.e., x), at least on my screen, and seeing mixtures of those in the same article can be a bit annoying (especially if they are near each other).
—⁠ ⁠BarrelProof (talk) 21:46, 7 October 2024 (UTC)
Asterisk means convolution (which is somewhat related to the idea of "multiplication" but should not be confused with the usual multiplication). Its use as a substitution for "×" or "⋅" is a bad habit from the old days of poor technology (but it was never used as such in professional typesetting) and has no excuse nowadays. — Mikhail Ryazanov (talk) 22:12, 7 October 2024 (UTC)
Convolution would only be a matter to consider in very mathematically sophisticated specialized contexts. It's not something most people have ever encountered. Even for those who use it, it would often be expressed using summation or integration instead. —⁠ ⁠BarrelProof (talk) 22:21, 7 October 2024 (UTC)
I don't think that this is a good reason to make exceptions to tolerate/promote sloppy typography (moreover, in some computer fonts the ASCII asterisk looks more like a superscript than a binary operator consistent with +, −, = and so on).
I don't think we should feel responsible for how Misplaced Pages is rendered in all possible fonts. We should remember that everyone is supposed to be able to edit Misplaced Pages articles. In an article that isn't about mathematics, or at least isn't using it beyond the 10th grade level, f = 1.8 * c + 32 seems basically OK to describe conversion from degrees C to degrees F. It's tricky enough that we tell people to pay attention to the difference between "-", "–", "—", and "−", and to not use italics for the numbers in that formula, although I support those instructions. —⁠ ⁠BarrelProof (talk) 03:37, 8 October 2024 (UTC)
Nobody should complain about otherwise good edits that include "lazy" typography. Those edits are 100% OK and a net improvement to Misplaced Pages. Other editors who care about typography and MoS can clean up the markup and character choices later. Misplaced Pages is a collaborative project. Indefatigable (talk) 15:46, 8 October 2024 (UTC)
Using an asterisk to represent multiplication is programming language syntax; I don't think this is common or even well-known among non-programmers. isaacl (talk) 01:47, 20 October 2024 (UTC)
I agree we should discourage use of "*" as a multiplication symbol. I agree it's easy to type, so if one editor writes "y = m*x + c" in an otherwise correct edit, the response should not be to revert that edit, but to replace it with "y = mx + c" or other approved alternative. Dondervogel 2 (talk) 10:40, 20 October 2024 (UTC)
Using an asterisk for multiplication is absolutely known to non-programmers because that's what is used on the number pad on most keyboards in the US. --User:Khajidha (talk) (contributions) 14:28, 12 November 2024 (UTC)
Ah, but which came first - the * key, or its use in mathematical expressions? Forty-some years ago, I was taught that in computer code, the * character was chosen to avoid confusion with the letter x, since the × did not exist in either of the character sets that were in use at the time - ASCII and EBCDIC. It's the same with / vs. ÷ and indeed - vs. . --Redrose64 🌹 (talk) 18:15, 12 November 2024 (UTC)
* appeared on many (but not all) early typewriters. When not present it was often replaced by a fraction key (1/2, 1/4, etc) Practically every computer terminal from the 1970s onward has a * key - but that's probably due to it being used by Fortran (1957). Early teletype keyboards typically used Baudot code encoding and did not have * - but these were more for telecommunications rather than programming. Fortran was invented at IBM and used punch cards/tape using IBM's BCDIC. The early variations of BCDIC had *, - and / but not +. + was added soon after. My take is that BCDIC tried to encode whatever was commonly used on typewriters - subject to the limitation of using only 64 characters. Fortran then assigned functionality to whatever was in that set. * looked the most like x without being a letter, so it got the job.  Stepho  talk  23:56, 12 November 2024 (UTC)
It would really behoove participants here, instead of just speculating from the armchair, to take the radical step of doing some research to actually find out the answer. * has been used, in math, to mean multiplication for three hundred years. See the bottom of p. 66 of . EEng 07:15, 13 November 2024 (UTC)
I didn't mention that paper, because I'm not in the habit of searching through 100-year-old academic journals. Now, 100-year-old magazines is a different matter, witness my stacks of boxes of The Railway Magazine back to 1902 (gaps between 1902 and 1939, complete from 1940 onward). --Redrose64 🌹 (talk) 12:02, 13 November 2024 (UTC)
FORTRAN was a decade earlier than ASCII and EBCDIC. What the first FORTRAN compiler used was the scientific BCD character set of the IBM 704, which replaced the older Percent (%) and Lozenge (U+2311 ⌑ SQUARE LOZENGE) with parentheses. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:35, 13 November 2024 (UTC)

Numerals in a sequence

'Phase 1' or Phase one'? This appears to be a case that's not explicitly covered.

The AP Stylebook recommends using figures for sequences in its section on "Numbers": "Also use figures in all tabular matter, and in statistical and sequential forms", from which I infer that for sequences, such as 'phase 1', figures should be used for clarity and consistency.

Similarly, chapter 9 of The Chicago Manual of Style advises using figures when referring to a sequence.

I propose adding similar explicit advice to this section of the MOS.

-- Jmc (talk) 20:10, 19 October 2024 (UTC)

  • As usual, what's needed before something's added to MOS is examples of this being an issue on multiple articles -- see WP:MOSBLOAT. Are editors not able to work this out for themselves on individual articles? Anyway, why does the word "Phase" need this in particular? Why not "Section" and "Part" and any other words like that? The advice from APA and CMS are great if you're making up a new sequence for your thesis, but that's not us. It's hard to imagine an article using a phrase like "Phase 1" or "Phase One" on its own -- that is, other than in imitation of the phrasing of sources. So follow the sources; for example, Economic Stabilization Act of 1970 refers to Phase I and Phase II and Phase III., because that's the form the Act uses. We're not going to override that in the name of consistency with other, unrelated articles. EEng 22:00, 19 October 2024 (UTC)
    To clarify: I'm using 'Phase' purely as an example. The issue of using figures for sequences applies to any sequence. including 'Section' and 'Part' - and other examples: "Game 3", of a sequence of nine; 'Chapter 9' of a sequence of 24; 'Week 4' of a limitless sequence.
    I raise this issue in the context of differing editorial practices in the British Post Office scandal article, where both figures and words have been used to reference the same phases and weeks of the inquiry. I sought guidance from the MOS and found none.
    I'd be content to follow the sources, without adding bloat to the MOS, if I could be confident that that's an accepted stylistic convention in this instance. -- Jmc (talk) 22:27, 19 October 2024 (UTC)
    Such names are very often established by authoritative sources and constitute proper names; we should follow the sources rather than renaming them. Per EEng, we only need a MOS guideline if our sources don't provide clear names and either there is dissent among editors or consistency across articles would be of significant benefit. In the Post Office case, I see the phases have been titled Phase 1, Phase 2 etc by the inquiry so unless the inquiry's inconsistent, we can follow that source. Still, I see that this is a live issue at that British Post Office scandal article, so it would be wrong to establish a new guideline or issue some sort of MOS talk-page ruling without the knowledge of the other editor; pinging MapReader. NebY (talk) 14:56, 20 October 2024 (UTC)
    Between May 1966 and December 1989, multi-episode Doctor Who stories could have titles in any of the four combinations of (i) "Episode ..." or "Part ..."; (ii) numbers as figures or as words. The decision as to which format to use was probably in the hands of the series producer, but in our articles about each story, we give the actual title shown on screen - except that where the on-screen title is all-capitals, we reduce it to title case. Certain Doctor Who reference books do the same, so we're following the sources. --Redrose64 🌹 (talk) 18:18, 20 October 2024 (UTC)
    The question raised was "differing editorial practices in the British Post Office scandal article". Sounds like a matter of internal consistency, which is different. For all manner of things -- this being one IMO -- we might not need consistency among articles, but it does look bad within articles. Surely we already have a rule addressing that general issue tho? Herostratus (talk) 13:24, 21 October 2024 (UTC)
    I think we don't. In articles on TV series it's common to have expressions like "season 3" and "episode 7", which seem to go against our current wording (use words for numbers below 10). Gawaon (talk) 16:37, 21 October 2024 (UTC)
    It is indeed a matter of internal consistency and it does look bad, as Herostratus says. Within the one article (British Post Office scandal), we have (e.g.) both "Phase 3 hearings" and "Phases five and six". Is there in fact a rule addressing this general issue? -- Jmc (talk) 18:47, 21 October 2024 (UTC)
    From Misplaced Pages:Manual of Style/Dates and numbers#Numbers as figures or words: "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." Unless you are dealing only with series with fewer than 10 seasons each with fewer than 10 episodes, it is more in line with MOS to give all season and episode numbers in digits rather than words. --User:Khajidha (talk) (contributions) 13:15, 22 October 2024 (UTC)
    True, but series with less than ten seasons aren't all that rare, and there are also miniseries with less than ten episodes. Gawaon (talk) 16:39, 22 October 2024 (UTC)
    Whether or not it's in line with MOSNUM, we frequently – I suspect in the vast majority of cases – give series/season and episode numbers in digits. I've been dipping into Misplaced Pages:Good articles/Media and drama#Television. Articles on individual episodes do routinely begin e.g. " the ninth and final episode of the first season" but with digits in the infobox. Articles on a season/series list episodes using digits, and articles on a show list series/seasons and episodes with digits, regardless of whether there are more or less than ten, in keeping with the examples in Misplaced Pages:Manual of Style/Television#Episode listing. Articles are often titled <show> season <n> where n is a digit, never a word, in accordance with Misplaced Pages:Naming conventions (television)#Season articles. Sampling our WP:Featured articles#Media, I see the same treatment in titles, infoboxes, and listings.I very much doubt that editors would accept changes to those FAs and GAs to bring them into line with MOS:NUMERAL, that FA and GA assessors will start to apply MOS:NUMERAL in such cases, that any move requests would succeed, or that MOS:TV and WP:TVSEASON will be brought into line with the current MOS:NUMERAL. Changing MOS:NUMERAL might be easier. NebY (talk) 08:20, 23 October 2024 (UTC)
    I agree, a small addition to MOS:NUMERAL might be a good thing. Gawaon (talk) 17:00, 23 October 2024 (UTC)
    Your final sentence doesn't follow from your statement. It would be more in keeping with the MOS to give all in words. MapReader (talk) 11:16, 23 October 2024 (UTC)
  • Generally concur with EEng and NebY. It's clear that certain conventions adhere strongly to certain things, and these conventions will be readily apparent from the source material about those things. WP is not in a position to impose an artificial WP-invented consistency on them that makes no sense for those familiar with the subject (e.g. referring to "issue number seven" of a comic book or "the three ball" in a game of pool). Where nothing like a consistent convention can be observed for the topic at hand, then MOSNUM already provides us with a default to fall back to: use "one" through "nine", then "10" onward. This is the case with centuries, for example. There is no overwhelming source preference for either "third century BC" or "3rd century BC" in reliable sources. (Books tend to prefer the former, journals use the latter more than books do because journal publishers are more interested in compression/expediency. Scroll through first 10 pages of GScholar resuls here and see how much variance there is, and how frequent the numeral style is compared to "traditional" spelling-out. That said, GScholar searches do include some books as well as journals.) Following our default system, we naturally end up with "third century BC" and "12th century BC". (Of course, our material doesn't perfectly follow this; our editors are human, not robots. Well, mostly.)  — SMcCandlish ¢ 😼  15:04, 24 November 2024 (UTC)

μs vs us

Which style I should use for micro seconds? Does μs relative to "Do not use precomposed unit symbol characters"? DungeonLords (talk) 04:44, 30 October 2024 (UTC)

The 2 characters "μ" and "s" are just fine. The precomposed symbols advice is to guard against particular fonts that combine them into a single character because many software readers for the sight impaired do not know all of these symbols.  Stepho  talk  04:53, 30 October 2024 (UTC)
But do use μ, not "u". The latter was something of an early-Internet halfassed approach, but we have Unicode now.  — SMcCandlish ¢ 😼  15:09, 24 November 2024 (UTC)

Day, date month format

Greetings and felicitations. I assume that such constructions as "Wednesday, 24 February" are discouraged, but I can't find it in the text or the this page's archives. (The comma seems unnecessary to me.) May I please get confirmation or refutation? —DocWatson42 (talk) 04:28, 4 November 2024 (UTC)

  • MOS:DATEFORMAT and MOS:BADDATE cover the allowed and disallowed formats. Unless the day of the week is vitally important then we leave it out.  Stepho  talk  06:16, 4 November 2024 (UTC)
    This specifically regards the "Hadaka Matsuri" article, and its Konomiya Hadaka Matsuri infobox, which includes the days of the week. —DocWatson42 (talk) 07:40, 4 November 2024 (UTC)
    Ah, the mysterious East. EEng 08:06, 4 November 2024 (UTC)
  • Salutations and hugs and kisses to you too.
    • If your question is whether day-of-week should be gratuitously included with dates for no particular reason, the answer is No. That is, if the day-of-week is somehow relevant to the narrative, sure, include it, but otherwise no.
    • Assuming we're in some situation where (per the preceding) inclusion of day-of-week is indeed justified, maybe your question is how to append the D.O.W.
      • If the date is February 24 or February 24, 2024, then without doubt the right format is Wednesday, February 24 or Wednesday, February 24, 2024.
      • According to "Elite editing" (whoever they may be -- search the text "inverted style" on that page), the corresponding answers for 24 February and 24 February 2024 are Wednesday, 24 February and Wednesday, 24 February 2024. To me that does seem right -- Wednesday 24 February 2024 (all run together, no commas at all) seems intolerable.
The question naturally arises as to whether MOS should offer advice on all the above. My answer, as usual, is provisionally No, per WP:MOSBLOAT. EEng 08:02, 4 November 2024 (UTC)
Looking at the article, the date is the 12th day of the Chinese year and the day of the week has no significance. I would remove the day of the week from all those dates in the infobox. For what it's worth, I spent most of the 1990s in Hong Kong/China. Major holidays based on the Chinese calendar treat the day of the week in the same way that we treat the day that Christmas falls on.  Stepho  talk  09:18, 4 November 2024 (UTC)
Okay—will do. Thank you both. ^_^ —DocWatson42 (talk) 09:21, 4 November 2024 (UTC)
The new 18th edition of The Chicago Manual of Style gives advice about commas in dates in ¶ 6.14. When giving examples they mostly give examples with words after the end of the date so the punctuation at the end of the date is illustrated. Some examples:
  • The hearing was scheduled for 2:30 p.m. on Friday, August 9, 2024.
  • Monday, May 5, was a holiday; Tuesday the 6th was not.
Jc3s5h (talk) 16:56, 4 November 2024 (UTC)
Concur with EEng on avoiding adding a rule about this, as more WP:MOSBLOAT. It's just a matter of basic writing sense, basic comma usage in competent English. Our MoS's purpose is not that of CMoS or Fowler's, trying to answer every imaginable usage question. Just those that have an impact on reader comprehensibility and/or recurrent editorial strife.  — SMcCandlish ¢ 😼  15:18, 24 November 2024 (UTC)

Spacing with percentage points

A question regarding spacing of percentage point (pp) usage. I have always assumed there is no space between the number and pp (e.g. 5.5pp not 5.5 pp), on the basis that you wouldn't put a space between a number and a percentage sign (5% not 5 %). There is no reference to this in the MOS, but the percentage point article uses it unspaced. It might be good to have it clarified in the MOS as I see regular changes adding spacing, which I am not sure is correct. Cheers, Number 57 23:49, 5 November 2024 (UTC)

  • MOS:PERCENT says "omit space".  Stepho  talk  23:54, 5 November 2024 (UTC)
    Perhaps I am missing something, but as far as I can see, it says to omit space when using the percentage symbol (%) but nothing about when using pp? Number 57 00:21, 6 November 2024 (UTC)
    Apologies, I missed the "point" word in your question.  Stepho  talk  01:49, 6 November 2024 (UTC)
  • % is essentially a constant factor (.01), but pp is more like a unit so my intuition says it should be spaced. I note that the basis point article uses a space before bp (mostly, anyway). I'll be interested to hear what others think. EEng 18:23, 6 November 2024 (UTC)
    You've got this back to front. Percent (%) is a standard unit symbol and should be spaced, whereas pp is a made up abbreviation, meaning you can put it anywhere you want, space or unspaced. I know MOSNUM says otherwise, which is WP's prerogative. In other words, if we need a rule, let's make one up and apply it, but there's no logic involved. Dondervogel 2 (talk) 21:06, 6 November 2024 (UTC)
  • Dondervogel, "Percent (%) is a standard unit symbol and should be spaced". Huh? It's not an ISO unit symbol, is it. No spacing in English, unlike French. On pp, I agree with EEng: space it. Tony (talk) 11:10, 8 November 2024 (UTC)
    Absolutely. When it comes to peepee, always space it . EEng 21:36, 8 November 2024 (UTC)
    Yes, "%" is an ISO standard unit symbol. Dondervogel 2 (talk) 12:45, 8 November 2024 (UTC)
    What is it the unit of? Gawaon (talk) 13:14, 8 November 2024 (UTC)
    Nothing. It's a dimensionless quantity. To the original q: I don't see "pp" used often, in fact rarely. It's probably better written out in full on first use, and if there are subsequent uses, follow the guidance at MOS:ACRO1STUSE. --Redrose64 🌹 (talk) 19:58, 8 November 2024 (UTC)
    It's used widely in election infoboxes where there isn't space to write it out. Number 57 22:25, 8 November 2024 (UTC)
    I will answer Gawaon's valid question in two parts. The first part is a quotation from ISO 80000-1:2009 (emphasis added)
    • In some cases, per cent, symbol %, where 1 % := 0,01, is used as a submultiple of the coherent unit one.
    • EXAMPLE 4
    • reflection factor, r = 83 % = 0,83
    • Also, per mil (or per mille), symbol ‰, where 1 ‰ := 0,001, is used as a submultiple of the coherent unit one.Since the units “per cent” and “per mil” are numbers, it is meaningless to speak about, for example, percentage by mass or percentage by volume. Additional information, such as % (m/m) or % (V/V) shall therefore not be attached to the unit symbol %. See also 7.2. The preferred way of expressing, for example, a mass fraction is “the mass fraction of B is w B = 0,78” or “the mass fraction of B is wB = 78 %”. Furthermore, the term “percentage” shall not be used in a quantity name, because it is misleading. If a mass fraction is 0,78 = 78 %, is the percentage then 78 or 78 % = 0,78? Instead, the unambiguous term “fraction” shall be used. Mass and volume fractions can also be expressed in units such as µg/g = 10-6 or ml/m3 = 10-9.
    Notice the deliberate space between numerical value (e.g., 83) and unit symbol (%). Dondervogel 2 (talk) 22:10, 8 November 2024 (UTC)
    The second part is a partial retraction, quoting from ISO 80000-1:2022, which supersedes the 2009 document:
    • If the quantity to be expressed is a sum or a difference of quantities, then either parentheses shall be used to combine the numerical values, placing the common unit symbol after the complete numerical value, or the expression shall be written as the sum or difference of expressions for the quantities.
    • EXAMPLE 1
    • l = 12 m - 7 m = (12 - 7) m = 5 m, not 12 - 7 m
    • U = 230 ⋅ (1 + 5 %) V = 230 ⋅ 1,05 V ≈ 242 V, not U = 230 V + 5 %
    The space is still there between numerical value (5) and percentage symbol (%), but I could not find an explicit reference to "%" as a unit symbol. I'm unsure how to interpret that change, but I'll report back here if I find further clarification. Dondervogel 2 (talk) 22:16, 8 November 2024 (UTC)
    I found this in NIST Special Publication 811
    • In keeping with Ref. , this Guide takes the position that it is acceptable to use the internationally recognized symbol % (percent) for the number 0.01 with the SI and thus to express the values of quantities of dimension one (see Sec. 7.14) with its aid. When it is used, a space is left between the symbol % and the number by which it is multiplied . Further, in keeping with Sec. 7.6, the symbol % should be used, not the name "percent."
    • Example: xB = 0.0025 = 0.25 % but not: xB = 0.0025 = 0.25% or xB = 0.25 percent
    • Note: xB is the quantity symbol for amount-of-substance fraction of B (see Sec. 8.6.2).
    • Because the symbol % represents simply a number, it is not meaningful to attach information to it (see Sec. 7.4). One must therefore avoid using phrases such as "percentage by weight," "percentage by mass," "percentage by volume," or "percentage by amount of substance." Similarly, one must avoid writing, for example, "% (m/m)," "% (by weight)," "% (V/V)," "% (by volume)," or "% (mol/mol)." The preferred forms are "the mass fraction is 0.10," or "the mass fraction is 10 %," or "wB = 0.10," or "wB =10 %" (wB is the quantity symbol for mass fraction of B—see Sec. 8.6.10); "the volume fraction is 0.35," or "the volume fraction is 35 %," or " φB = 0.35," or "φB = 35 %" (φB is the quantity symbol for volume fraction of B—see Sec. 8.6.6); and "the amount-of-substance fraction is 0.15," or "the amount-of-substance fraction is 15 %," or "xB = 0.15," or "xB = 15 %." Mass fraction, volume fraction, and amount-of-substance fraction of B may also be expressed as in the following examples: wB = 3 g/kg; φB = 6.7 mL/L; xB = 185 mmol/mol. Such forms are highly recommended (see also Sec. 7.10.3).
    • In the same vein, because the symbol % represents simply the number 0.01, it is incorrect to write, for example, "where the resistances R1 and R2 differ by 0.05 %," or "where the resistance R1 exceeds the resistance R2 by 0.05 %." Instead, one should write, for example, "where R1 = R2 (1 + 0.05 %)," or define a quantity Δ via the relation Δ = (R1 - R2) / R2 and write "where Δ = 0.05 %." Alternatively, in certain cases,the word "fractional" or "relative" can be used. For example, it would be acceptable to write "the fractional increase in the resistance of the 10 kΩ reference standard in 2006 was 0.002 %."
    As with ISO 80000-1:2022, there is always a space between numerical value (e.g., 35) and the percentage symbol (%), but no mention of % as a unit symbol. Dondervogel 2 (talk) 22:38, 8 November 2024 (UTC)
    there is always a space between numerical value (e.g., 35) and the percentage symbol (%) – Maybe in NIST-world, but not here on Misplaced Pages (see MOS:PERCENT), so I don't see how any of that helps us with the issue at hand. EEng 23:29, 8 November 2024 (UTC)
    I was correcting a misconception that % is not a unit symbol when it is. At least it was until 2022. I find it best not to leave incorrect statements unchallenged or they take on a life of their own. Dondervogel 2 (talk) 00:24, 9 November 2024 (UTC)
    Um, OK, but you do realize that WP does not follow NIST's advice about spacing it, yes? EEng 00:44, 9 November 2024 (UTC)
    Yep, and I wasn't trying to change that. My contributions have been to
    • correct a factual error (yours)
    • respond to questions from Tony and Gawaon
    I have not weighed in on the main thread regarding percentage points because I don't expect my opinion (based not on NIST's utterings but on the ISO standards on which they are based) to be taken seriously, so why would I waste my e-breath? Dondervogel 2 (talk) 09:41, 9 November 2024 (UTC)
  • It is not conventional to space "%" in English. Nearly no publishers do this, and our MoS doesn't say to do this or incidentally illustrating doing this, so don't do this. "pp" here is a unit abbreviation for percentage point ("the unit for the arithmetic difference between two percentages)", so space it. % is not a unit abbreviation/symbol, but a quantity symbol, so it's in a different class. It's more like the ~ in "~5 ml". That the spelled-out equivalent "approximately", like the spelled out "percent", is spaced apart from the numeral is irrelevant.  — SMcCandlish ¢ 😼  15:24, 24 November 2024 (UTC)

UNITSYMBOLS (1 × 3 × 6 m): “each number should be followed by a unit name or symbol”

MOS:UNITSYMBOLS currently requires a unit symbol after each value when listing dimensions separated by × (“1 m × 3 m × 6 m, not 1 × 3 × 6 m”). Could we have a carveout from this rule, and allow editors to use only a final unit when writing for infoboxes, and perhaps other places where space is limited?

Context: {{Infobox mobile phone}} currently has a preference for listing the dimensions of the product each on a separate line. This, and other parameters, can make the infobox very long. This is especially problematic for pages that cover multiple products or versions of a product; see dimensions in Samsung Galaxy S21 infobox. In order to cut down these infoboxes, we could be using a single line for all three dimensions, but the unit after each value feels unnecessary, and can cause line overflow.

Prior discussion: Misplaced Pages talk:Manual of Style/Dates and numbers/Archive 145#Repeating units in ranges and dimensions, where the potential for confusion with actually multiplying values was pointed out. I think this is a minor concern in general, but worth considering in prose, or in contexts where the values could be ambiguous. — HTGS (talk) 04:17, 11 November 2024 (UTC)

Where space is limited, it makes sense to present a single compound unit, equal to the product of the separate units. For the example given, the compound unit symbol would be m. Dondervogel 2 (talk) 12:13, 11 November 2024 (UTC)
Who ever heard of a phone advertised as 5 cc ? People are more interested in it being wide and tall but very thin. This necessitates stating each individual dimension.  Stepho  talk  22:40, 11 November 2024 (UTC)
No, what Dvogel means is you'd write that a certain phone measures 146 x 71.5 x 7.65 mm. Having clarified that, I'm bound to say that that would, of course, confuse 99% of our readers. EEng 22:47, 11 November 2024 (UTC)
Gotcha. As well as confusing most readers, it would also be different to 1 by 3 by 6 m, which is allowed.  Stepho  talk  23:30, 11 November 2024 (UTC)
To be clear for those playing along at home, while the canonical formuations are 1 m by 3 m by 6 m and 1 m x 3 m x 6 m, MOS currently makes an exception allowing 1 by 3 by 6 m (specifically in the case where all the quantities are in the same unit -- in this case metres), but no corresponding exception allowing 1 x 3 x 6 m. While it may offend purists, I really don't see why the exception shouldn't be extended to that last case as well. Thoughts? EEng 23:39, 11 November 2024 (UTC)
Thank you for clarifying my intent. And for making me chuckle. LoL
For a 3 dimensional object, one can write either 146 mm x 71.5 mm x 7.65 mm or 146 x 71.5 x 7.65 mm. I agree the former is clearer, but the latter uses less space, which can be a consideration. There is no difference in meaning.
I guess one could also write 146 x 71.5 x 7.65 mm, but then we have a length, not a volume. It would be clearer to write that length as 79.86 m. Dondervogel 2 (talk) 23:42, 11 November 2024 (UTC)
one could also write 146 x 71.5 x 7.65 mm, but then we have a length, not a volume – Formally perhaps, but you could say the pretty much the same about 146 by 71.5 by 7.65 mm, and yet we allow it. No one will think that 146 x 71.5 x 7.65 mm means the length 79.86 m (i.e. 79860 mm). In context readers will understand it for what it is. I'd like to hear what others think about my proposal. EEng 23:56, 11 November 2024 (UTC)
Seconded EEng's proposal - simple and clear.  Mr.choppers | ✎  04:36, 14 November 2024 (UTC)
EEng is, of course, correct. At {{convert}} we sometimes are asked how the duplicate mm units can be removed to save space (the trick is to use xx in convert) and we tell them that omitting repeated units is ok if space is limited. May as well make it official. Johnuniq (talk) 05:51, 14 November 2024 (UTC)
EEng is, of course, correct. – Of course -- even Dondervogel says so. EEng 06:37, 14 November 2024 (UTC)
I also support the proposal.  Stepho  talk  05:53, 14 November 2024 (UTC)
I thought this was a joke and burst out laughing on a train, which got me a weird look from a fellow passenger. Anyhow, I too support allowing the single unit after x symbols per EEng and John. Toadspike 17:31, 18 November 2024 (UTC)
:( — HTGS (talk) 23:34, 18 November 2024 (UTC)
  • It's tiresome to have to write (and read) units multiple times when multiplication signs are used. Tony (talk) 09:47, 14 November 2024 (UTC)
  • As the person who proposed this in the first place, I too support EEng’s proposal. I will carry on working on the infobox, and leave the written MOS to others. I imagine the purists might be happy if we left some comment or endnote about making sure the measurements are not potentially ambiguous though?
And, for anyone who cares, there are already pages where this is in sensible use: List of photographic film formats. — HTGS (talk) 23:34, 18 November 2024 (UTC)

Do we have to convert inches for wheels?

I see people adding conversions to mentions of screen sizes and wheel dimensions - is this really necessary? Even in Germany or New Zealand, automobile and bike wheels are universally referred to by inches; rim diameters are expressly defined in inches in the EU regulations. To me, adding conversions for these types of dimensions adds unnecessary clutter, harming readability for no return whatsoever. I haven't read the entire MOS today, apologies if I missed a mention of these situations.  Mr.choppers | ✎  17:24, 13 November 2024 (UTC)

It looks like sizing bike wheels in inches is not universal. I see many charts in the I-net such as this that use both metric and imperial/American units for bike wheels and tires. Whether the convert template handles them correctly is another issue. Donald Albury 17:43, 13 November 2024 (UTC)
On the matter of wheel sizes, not all are inches. See this post and my reply. Even for a conventional non-Denovo wheel, the dimensions are a bastard mixture: "195/65 R 15" means a tyre that is 195 mm wide on a 15-inch rim. --Redrose64 🌹 (talk) 19:10, 13 November 2024 (UTC)
Yes, there is the Michelin TRX and the Denovo. Just as we wouldn't convert the "195" when we write 195/60 R15, I don't think we ought to convert the diameter either. I would treat all of these tire dimensions as one would nominal measurements, rather than inserting unnecessary templates. Bicycle tires, meanwhile, proved more varied than I was aware of.  Mr.choppers | ✎  04:33, 14 November 2024 (UTC)
I agree with Mr.Choppers on this subject. I think wheels sizes on cars are a compromise between the USA and the rest of the world. There are metric rims on older vehicles but pretty rare on new vehicles. Avi8tor (talk) 11:40, 14 November 2024 (UTC)
@Avi8tor: - I was actually triggered by you converting screen dimensions, but five minutes online showed me that the modern world has indeed begun dropping the use of inches for screens. My gut was wrong.  Mr.choppers | ✎  13:36, 14 November 2024 (UTC)
Many people around the planet know only millimetres, so it makes sense to have both. I notice in France the data information on television screen size have it in both inches and millimetres. Avi8tor (talk) 17:57, 16 November 2024 (UTC)

RfC Indian numbering conventions

There is consensus to continue using crore and lakhs when appropriate.

Most participants also generally agreed with SchreiberBike's conditions (or a variant) - Always 1) link it on first use, 2) include what it is a measure of (rupees can not be assumed), 3) also include conventional numbering, and 4) allow it only in articles about the subcontinent.

However, this RFC suffered from structural issues that a precise wording isn't agreed on yet. Any changes from status quo should go through a clearer future discussion or RFC on just that.

(non-admin closure) Soni (talk) 22:02, 24 December 2024 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


I am revisiting an issue that was last brought up 6 years ago here and settled without a strong consensus.

I think we should avoid using Indian numbering conventions unless it is needed for context. For instance, if we want to list the box office take of an Indian movie, don't use "crore", use "millions". This isn't about disrespecting a culture, it's about using internationally favored notation and unit conventions. We should use "millions" instead of "crore" for the same reason we favor meters over feet. There is no reason that India-related articles should be an enclave of Indian conventions. People who are not Indian will struggle with these things, it will weaken Misplaced Pages's role as an information tool for everyone.

This is not the same thing as currency. It is appropriate to list an Indian movie's box office take in rupees. Providing a US$ conversion is optional, but a good idea since the US dollar is widely used around the world as a reserve currency. But write it as "millions of rupees", not "crores of rupees". Kurzon (talk) 16:38, 16 November 2024 (UTC)

What's the common usage in english? GoodDay (talk) 16:45, 16 November 2024 (UTC)
I don't think most people in the US understand what "crore" is, and would not recognize it as part of the English language. The online Merriam-Webster dictionary says it means ten million, specifically, a unit of value equal to ten million rupees or 100 lakhs. I think most people in the US would not even understand that a currency is being mentioned.
--Jc3s5h (talk) 17:00, 16 November 2024 (UTC)
Not just people in the US. Nobody outside of India can be expected to know what a crore is. Kurzon (talk) 17:15, 16 November 2024 (UTC)
We use meters over feet? Where?

In non-scientific articles with strong ties to the United States, the primary units are US customary (pounds, miles, feet, inches, etc.)

Aaron Liu (talk) 17:50, 16 November 2024 (UTC)
You get extra points for saying "US customary" and not "Imperial". 😉 Isaac Rabinovitch (talk) 18:20, 16 November 2024 (UTC)
imperial :3 Aaron Liu (talk) 18:30, 16 November 2024 (UTC)
I agree with Kurzon, do not use "crore", use "millions". Misplaced Pages is for a worldwide audience. Avi8tor (talk) 18:03, 16 November 2024 (UTC)
Kinda like how US units are used for US articles, I don't see the harm in using "crore", and it's way more work to manually convert to millions every time a member of India's vast diaspora in the Global North adds "crore" to an article, not knowing our ManualOfStyle. Aaron Liu (talk) 18:19, 16 November 2024 (UTC)
Except we don't favor meters over feet — we use both. That's what the Convert template is for.
Speaking as a non-Indian, who can never remember what how many is a "crore": I'm fine with it, as long as the international unit is also used. Isaac Rabinovitch (talk) 18:18, 16 November 2024 (UTC)
We already make an exception for feet. I see no good reason for barring a second exception. State in crore and convert to a unit non-Indians can understand (millions of rupees?). Dondervogel 2 (talk) 20:48, 16 November 2024 (UTC)

The article for the French movie Les Visiteurs lists the budget as "9.5 million", using a point as a decimal separator. In France they use commas for this, ie "9,5 million". We don't use the French notation convention for France-related articles. Kurzon (talk) 17:14, 16 November 2024 (UTC)

Is it the French style to use that notation in English? A different unit elicits way less confusion than a reversed decimal separator meaning anyways. Aaron Liu (talk) 17:50, 16 November 2024 (UTC)
This RfC is clearly improperly formatted, Kurzon; thank you to our unregistered friend for pointing this out.
Oh come now. It seems to be developing nicely, I doubt that any editors are swayed by the wording. it's not perfect but perfect is the enemy of good and its good enough. Herostratus (talk) 04:47, 29 November 2024 (UTC)
That reply was before the appropriate discussion centers were notified and before discussion started to develop. It's not just formatting; it's that there was no prior discussion. Now we're effectively having both at the same time, especially when an informal discussion could've resulted in consensus without a time-consuming process. Aaron Liu (talk) 16:08, 29 November 2024 (UTC)
Consistency and clarity to our international readership are valid arguments in favor of prohibiting "crore" and "lakh". However, Aaron Liu makes good points about the fact that we allow local variation in articles with local ties, e.g. all of ENGVAR. I am unsure where I sit on this issue. I would like to see some Indian editors weigh in on this. Toadspike 19:58, 16 November 2024 (UTC)
I also agree that crores are too obscure (as are lakhs), with use limited to South Asia. Feet and inches, while retrograde and infinitely useless, were used across most of the world not many generations ago. The major unit in Japanese is 万 (man), which is 10,000, but we do not use that because most people wouldn't know it. Engvar is somewhat different: we cannot avoid choosing between "colour" and "color", for instance, whereas we can easily write the globally recognized "millions" rather than crores. As for User:Aaron Liu's comment: if someone adds crore, it will be there until fixed – it's not pressing enough of a problem to hunt down every instance.  Mr.choppers | ✎  20:03, 16 November 2024 (UTC)
Good point about 万 – I completely forgot that Chinese has similarly different units. I think that settles it – either we allow crore and lakh alongside the East Asian 万 and 亿 (which I think is ridiculous) and an infinite variety of customary units, or we allow none.
(Two counterarguments: 1. This is a slippery slope argument, which is a logical fallacy. To which I say no, we can't give only one country special treatment, we ought to be fair. 2. The East Asian units are non-Latin characters and thus more impractical than "crore". This is true.) Toadspike 20:15, 16 November 2024 (UTC)
On the subject of the myriad, I agree with Toads's second counterargument: there is no widely-recognized English translation for the unit in some "East Asian variant" of English; they just convert it to short scale in translations.

we cannot avoid choosing between "colour" and "color", for instance, whereas we can easily write the globally recognized "millions" rather than crores.

Part of my argument is that "crore" vs long scale is basically the same thing as "colour" vs "color": anonymous editors are going to add them. A ton. Expecting people to not use crore is like expecting people to not spell "colour". It's not pressing enough to hunt down, sure, but you're going to see sweet summer children adding crore into crore-free articles again and again and again. Aaron Liu (talk) 01:14, 17 November 2024 (UTC)
By the way, I've left a (neutrally-worded) note about this discussion at the Talk page of WikiProject India. Toadspike 20:16, 16 November 2024 (UTC)
Notified: Misplaced Pages talk:Manual of Style/India-related articles. jlwoodwa (talk) 01:04, 21 November 2024 (UTC)
  • Allow, but always ... exactly as Mathglot laid out above (other than, per Stepho-wrs and Redrose64, {{convert}} isn't actually the right template, or at least isn't presently). I would add a further caveat that these traditional Indic units (technically, multipliers) should be given secondarily not primarily, but I could live without that.  — SMcCandlish ¢ 😼  11:55, 21 November 2024 (UTC)
  • Allow when appropriate, under conditions set out by ScreiberBike. Also, this RfC does not meet WP:RFCNEUTRAL. ThatIPEditor 02:18, 22 November 2024 (UTC)
  • Do not allow crore et al. It's not only native English-speakers who haven't a clue what it means when reading India-related articles; it's non-natives too. Tony (talk) 07:32, 22 November 2024 (UTC)
    I don't get what native/non-native speakers have to do with the issue. Aaron Liu (talk) 12:21, 22 November 2024 (UTC)
  • Allow per ScreiberBike for South Asian articles. Johnbod (talk) 17:29, 22 November 2024 (UTC)
  • Allow All Indian academic/professional textbooks and all Indian reliable sources, with few exceptions for specific conditions, use lakhs/crores when denoting INR and millions/billions when denoting foreign currencies. Not allowing is not an option, unless editors want to disregard Indian readers. Using X million rupees is almost as uncommon in India as using Y lakh dollars. My suggestion -- for articles that use {{Use Indian English}} force editors to 1) link it on first use, 2) include what it is a measure of (rupees can not be assumed) with Indian comma separator at 00 after thousands and for articles that don't use that template force editors to always use millions/billions with 000 comma separator. — hako9 (talk) 03:01, 23 November 2024 (UTC)
    Strongly disallow use of Indian comma separator. That would only serve to confuse. We don't permit a French comma separator on English Misplaced Pages. The Indian comma would be much worse. Dondervogel 2 (talk) 09:11, 23 November 2024 (UTC)
    I concur entirely with Dongervogel_2 on this side-point; we cannot mix-and-match numeric separator styles. We've repeatedly had debates in the past about permitting "," instead of "." as a decimal point to suit the preference of some subset of readers, and the answer is always firmly "no", so this isn't going to be any different. I'm not a professional researcher in this area, but I have looked into the matter in the course of various style debates, and the evidence clearly shows Indian publications using "Western" number formatting systems (or whatever you want to call them) on a regular basis, though often alongside the Indic krore, etc., system. That is, it's just not plausible that English-using readers in/from India have any difficulty understanding our numeric material, especially after the rise of the Internet has exposed them to content from all over the world since the mid-1990s and pretty much ubiquitously since the early 2010 with the rise of mobile data.  — SMcCandlish ¢ 😼  14:49, 24 November 2024 (UTC)
    “it's just not plausible that English-using readers in/from India have any difficulty understanding our numeric material …” Of course the same could be said of American readers and the spelling of ‘colour’. — HTGS (talk) 17:41, 28 November 2024 (UTC)
    What isn't the same is how many editors will add "colour" into articles while most wouldn't add numbers in the Indian system. Aaron Liu (talk) 18:30, 28 November 2024 (UTC)
    I’m genuinely not sure what your point is? Editors are more likely to (erroneously) change spelling to ‘colour’, so that gives them more grounds for the MOS giving them parity with American English? I know we should be realistic about what we can control, but I don’t love that logic. — HTGS (talk) 03:18, 29 November 2024 (UTC)
    Yes, that or add spelling that says "colour" is what I'm saying. Aaron Liu (talk) 04:03, 29 November 2024 (UTC)
    Like I would campaign for navboxes to be placed in the "see also" section if it weren't so widespread and unduly investative to correct. The corrections for disallowing crore are the same thing to me. Aaron Liu (talk) 04:11, 29 November 2024 (UTC)
    On this attempt at a color false analogy: "What isn't the same" even more pertinently is that the cases aren't parallel in any way. Crore and lakh are not barely noticeable spelling differences of an everyday word used the same way in every single dialect of English; they're a radically different system of approaching large-ish numbers. There is no audience capable of reading en.wikipedia for whom either colour or color is impenetrable. If HTGS's pseudo-analogy is intended to suggest that ENGVAR should be undone on the same basis that we would rejecte or further restrain use of crore and lakh, that doesn't work since they're not actually analogous at all, plus the fact that not a single element of MoS is more dear to the community than ENGVAR; it is never, ever going away. If HTGS isn't actually suggesting we get rid of ENGVAR but is instead trying to suggest that opposition to crore is pretty much the same as advocating the death of ENGVAR, that's not cogent either, for the same false-analogy reason plus scoops of slippery slope, overgeneralization, and argument to emotion fallacies plopped on top. Aaron Liu's original "what isn't the same" point is that most editors will use color or colour as contextually appropriate in our content, yet very few will ever add lakh or crore to an Indic-connected article. That could be argued to be suggestive of a de facto community consensus already existing against those units' use at en.wikipedia. While it's worth considering, it's clouded by WP:SYSTEMICBIAS in that a comparatively small percentage of our editors are from India or its immediate environs, so the statistics are probably not usefully comparable even if they could be gathered with certainty. I would suggest that the reasons to rarely use crore/lakh and to always convert when used at all, has to do with end-reader comprehensibility, not with editor preference or usage rates.  — SMcCandlish ¢ 😼  12:54, 23 December 2024 (UTC)
    Because, the fact is, we aren’t using varieties of English solely to ensure accuracy or intelligibility. They are also being used to avoid recreating the Anglo-American hegemony that exists in published English, and to foster a connection in the community with the most interest in the subject. — HTGS (talk) 18:05, 28 November 2024 (UTC)
    This is not MakeLocalsAsHappyAsPossiblePedia or EngageInCrossCulturalFeelGoodBackscratchingPedia or RightGreatWrongsPedia. It may be unfortunate in some sense that a "Western" (now globally internationalized) enumeration system dominates nearly everywhere (with arguably more benefits than costs), but it is a fact. And it has nothing to do with "Anglo-American" anything, being the same system used by the French and the Russians and the Japanese and so on, and predating both America and England and even the English language, going back to ancient Eurasia very broadly, from the Rome to China. (There's an incidental British correlation of course: it was largely the English, along with the Dutch, who pushed this system in India. That makes it socio-politically and emotively connected to India–UK and Indian–Western relations, but it is not an Anglic counting system and we are not to be confused by sentiment.) More to the point, the "job" of this site is to communicate clearly with as many English-competent readers as possible. The simple fact is that virtually no one outside of the Subcontinent and nearby islands (plus first-generation emigrées therefrom), think in or even understand lakh and crore; meanwhile pretty much everyone in India and thereabouts also understands millions, and hundreds of thousands, even if it is not their immediate mental model and they have to convert a bit in their heads, like Americans with metric units. There is no bothsides-ism to be had here; the sides are not equivalent. Finally, it is not the goal of our articles on Indic culture, history, geography, economics, etc., to appeal to and primarily serve the interests of people in South Asia, but everyone. For this reason, I'm supportive of retaining the permissibility of crore and lakh in relevant articles as long as they are always converted into the now globally prevalent enumeration system, and usually with that first unless there's an important contextual reason to use lakh/crore first. Best of both worlds: everyone gets to understand the material, and Indic numbering is not deleted. It's pretty much the same situation as American customary ("imperial") units of measurement: most of the world doesn't use or understand them, but we should not ban them, just always convert them to metric. (The only difference I can see is "wiki-political": our American editorial and read bases are so large that it would be very difficult to get consensus to always put American units second after metric even in articles about American subjects. That really should be the rule, but it'll be hard to get there.)  — SMcCandlish ¢ 😼  12:54, 23 December 2024 (UTC)
  • Do not allow crore - I am not convinced that this word is actually English, and this is the English-language wikipedia. It seems that this is a foreign word that is used alongside English in areas that have ties to the language this word is from. Even in these areas, it seems that English speakers there fully understand what "millions", "thousands", etc mean, and there have been attestations linked above where they use both, presumably to help English speaking people understand what number is being referred to. My perspective here is colored by being an American expat living in Japan... in day-to-day speech, I will sometimes mix the languages and say "Oh, this costs 3 man yen." But I am under no circumstances thinking that "man" meaning "ten thousand" is English. I'm using another language's word. That's what it looks like they are doing here. Fieari (talk) 07:01, 28 November 2024 (UTC)
    As an alternative, I would also accept allowing crore only if the "millions" number is included alongside it. Fieari (talk) 07:28, 28 November 2024 (UTC)
    "Gumption" is borrowed from Scots; it is English. "Chutzpah" is borrowed from Yiddish; it is English. "Powwow" is borrowed from East-American indigenous language; it is English. "Crore" is borrowed from Hindustani; it is Indian English. All of the above are attested by dictionaries, while "man" to mean myriads is not. Aaron Liu (talk) 18:28, 28 November 2024 (UTC)
  • Allow crore - my gut feeling is to disallow it because it is not English as understood by the majority of English readers (including native speakers from UK/US/Australia/etc and second language speakers from China/S.America/Europe/etc). However, crore and lakh are words that Indians practically think in even when speaking English. We have a similar problem where an article is marked as British English and has 99 occurrences of "litre" - an American will still add new stuff with "liter" because it is so naturally to them. In the same way, we will be pushing it up hill trying to get them to stop. So, we should let them use it in articles related to the Indian region but never on anything outside that region. Each first usage should link to crore and lakh so that the few non-Indian region readers have a clue what's going on. I would not bother with conversion to millions - once you learn that they are just putting 0's at the end it becomes easy enough in a short time and conversions just clutter up the article. But do not allow grouping like 1,00,000 under any circumstances. Stepho  talk  02:41, 29 November 2024 (UTC)
  • Don't allow crore. If there are people who don't know what "million" is, well some level of literacy is required here, yes. As to "link on first use", no, links are supposed to be "here's some extra/more detailed info about the subject if you want" not "you need to interrupt the flow of your reading and go off the page to understand this word". Herostratus (talk) 04:57, 29 November 2024 (UTC)
    Actually that's exactly what links are for. Readers who know the general topic well can just read an article straight forwardly. But readers new to the general topic are likely to come across words they don't know yet and can follow the links to learn. Eg, in car articles we often talk about the camshaft. If you are new to the detailed study of cars then you can follow that link and then return later.  Stepho  talk  06:09, 29 November 2024 (UTC)
    And if anybody thinks that a politely worded MOS rule will stop them adding crore and lakh then consider that at https://en.wikipedia.org/search/?title=Nissan&diff=1256595427&oldid=1256557060 somebody added a MDY style date in spite of the article having 186 references in DMY style. I fix these (in both directions) practically daily. People do whatever comes natural and do not consider that any other way even exists.
    But I do feel a little better after my vent :)  Stepho  talk  11:35, 29 November 2024 (UTC)
    +1 and it’s worth reiterating that most advocates here are suggesting that the Indic value should always be “translated” into a Western value in parentheses, so most naïve readers would still be able to parse the article without following the link. — HTGS (talk) 06:21, 29 November 2024 (UTC)
  • Do not allow crore—India-related articles are for international readership. No one outside the subcontinent is familiar with crore. It is a disservice to readers to allow it. Tony (talk) 06:24, 29 November 2024 (UTC)
    If they are not familiar with crore they can read the conversion to millions. And if they also want to learn about crore they can click on the link. I see no disservice. Dondervogel 2 (talk) 12:49, 29 November 2024 (UTC)
    Perhaps some are not aware but English Misplaced Pages is heavily used in India. The Top 50 Report from 2023 had five items about Indian movies and movie stars. The latest week's most viewed Top 25 had 2024 Maharashtra Legislative Assembly election and Kanguva. According to Indian English there are 128 million English speakers there. If we say to basically never use crore and lakh, we are sending a discouraging, even insulting, message to many of our readers and editors. SchreiberBike | ⌨  13:51, 29 November 2024 (UTC)
  • Allow in articles with strong ties to India, provided that the conversion is shown at first use. Hey, we could even write In non-scientific articles with strong ties to the United States India, the primary units are US customary (pounds, miles, feet, inches, etc.) multipliers are Crore and Lakh. See sauce for the goose. Also, it is very relevant that a huge fraction of en.wiki readers are Indian. "ccording to a 2011 census, 10.2% of the Indian population speaks English. This figure includes all Indians who speak English as a first, second, or third language. 10% of India's population is approximately 145 million people." Twice as many as in the UK, half as many as in the US. --𝕁𝕄𝔽 (talk) 11:49, 29 November 2024 (UTC)
  • Allow only with linking and conversion as per Mathglot. The most practical solution for both Indian and non-Indian readers. Chaotic Enby (talk · contribs) 23:41, 8 December 2024 (UTC)

Discussion

Maybe this can be solved technologically so that every user sees numbers in the way they are accustomed to? Alaexis¿question? 20:43, 8 December 2024 (UTC)

This could be done for logged in users, but the vast majority of readers are not logged in with an account. Similar solutions have been proposed for date style and variety of English, but they won't work. SchreiberBike | ⌨  20:50, 8 December 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Which era?

I'm inviting fellow editors to figure out whether Religious perspectives on Jesus should use BC / AD or BCE / CE. The issue is that the article mixes eras and when I went back to see which was first, I saw it originally used "BC/BCE" and it stayed like that for years. The thread: Talk:Religious perspectives on Jesus#BC BCE AD CE. Thanks! — Preceding unsigned comment added by Masterhatch (talkcontribs)

MOS:ERA applies so status quo ante should apply. (FWIW, Judaism and Islam have religious perspectives on Jesus of Nazareth, so the neutral style seems entirely appropriate.). --𝕁𝕄𝔽 (talk) 00:18, 22 December 2024 (UTC)
Agreed on the last part. As for the procedural matters, all of our MOS:VAR principles ultimately default/fallback to the style used in the first non-stub version that used one of the competing styles, if consensus fails. MOS:STYLEVAR is the general principle, the root rule: Don't change from one acceptable style without a very good reason. If there is or you expect resistance, discuss to establish consensus. If you don't get consensus for your change (i.e., there is consensus against you), it stays the status quo ante. If there's no consensus on which would be better (which is often the case and likely the one in this case), then use the version established earliest. For particular things covered by MOS:DATEVAR, MOS:ERA, MOS:ENGVAR, WP:CITEVAR, we simply reiterate this principle and process more topically, and these ones also basically resolve to an additional rule: don't change that particular kind of style without establishing consensus first even if you're sure you've got a good reason and don't think there should be resistance.

The STYLEVAR process actually sometimes (namely when there's clearly no firm consensus in favor of the status quo ante, either) overrides the usual Misplaced Pages status quo ante principle, which in practice amounts to "fall back to whatever the discussion closer thinks is more or less a pretty long-term status quo". That usually works for a lot of things, but for these "I will win my Holy Style War or die trying" tedious cyclic bikeshedding typographic disputes, it has proven unworkable, because the dispute lives on and on, simply shifting in stages to: what constitutes a status quo; how long is long enough; whether interruptions in the use of the alleged status quo have reset its tenure; whether this *VAR-imposed consensus discussion was followed when the alleged status quo was imposed; if not, then whether that imposition pre-dated STYLEVAR requiring it; and yadda yadda yadda. There's just no end to it, because it's too often a super-trivial but deeply obsessive PoV-pushing exercise grounded in prescriptivist emotions (mixed sometimes with nationalist, or socio-politically activistic, or my-profession-vs.-yours, etc.). The style-war-ending default of falling back to the first major edit that established one of the competing styles is arbitrary (in both senses), but it is the end of it, and we move on to something more productive.

For this particular article: If "it originally used 'BC/BCE'" in the original post isn't a typo, and really does mean that the style was mixed from day one, then that's a rare edge case, and JMF's "status quo ante should apply" is probably the only reasonable approach. (Even from an excessively proceduralist viewpoint: If STYLEVAR and its application ERAVAR impose an overriding principle that in this case cannot actually be applied, then the default necessarily must be the normal Wikipedian status quo ante principle, even if for matters like this it tends to lead to re-ignition of the dispute again in short order. Not every solution is perfection.)  — SMcCandlish ¢ 😼  12:02, 23 December 2024 (UTC)

But what would be the status quo ante in this case? Surely you can't mean the mixed BC/BCE style? Gawaon (talk) 08:56, 24 December 2024 (UTC)

Four questions

  1. Can 24-hour clock be used in articles with strong ties to United States (I have seen no US-related articles with 24-hour clock) such as: "The Super Bowl begins at 18:40 ET?
  2. Can 12-hour clock be used with UTC time?
  3. How are primary units of an article determined if the article has strong ties to both US and Canada, as Canada-related articles always use metric units first? For example, Great Lakes is such an article, and it currently uses imperial units first, but it would be more logical to use metric units first as a Canada-related article.
  4. Why mixed units are not used with metric units? Why it is either 1.33 m or 133 cm, but never 1 m 33 cm? --40bus (talk) 23:04, 21 December 2024 (UTC)
    I'd add a fifth question: why does Misplaced Pages not use ISO dates, i.e. yyyy/mm/dd? They are becoming more common internationally. Skeptic2 (talk) 00:02, 22 December 2024 (UTC)
    1. I wouldn't recommend it.
    2. Probably?
    3. That should be decided on a case-by-case basis.
    4. No benefit for the additional visual or semantic complexity; that's part of the appeal of the metric system, right?
    5. English-language sources never use this format, and the English Misplaced Pages bases its style on that of other English-language media.
    Remsense ‥  00:58, 22 December 2024 (UTC)
    You write "English-language sources never use this format", but this is untrue. ISO date format is widely used in scientific publishing and it is standard in aviation and for machine processing. Have a look at the Misplaced Pages entry List of date formats by country. You might be surprised.Skeptic2 (talk) 23:35, 22 December 2024 (UTC)
    I personally use ISO format on my devices; if it helps, you can replace "never" with "almost never". Remsense ‥  23:36, 22 December 2024 (UTC)
  1. MOS:TIME says 12 and 24 clocks are equally valid. It's just that the majority of native English speakers use 12 hour clocks, so they choose to use 12 hour clocks. If you create an article (or are the first to mention times within an existing article) then you can choose. Don't change an existing article from one to the other. With the possible exception of US Army articles, you may get kick-back from readers not familiar with the MOS. See the WP:JUSTDONTLIKEIT essay.
  2. UTC is an offset. It is a separate question from how you format that time. UTC can be used with either 12 or 24 hour clocks. See MOS:TIMEZONE but it doesn't actually say much.
  3. Primary units are based on strong ties to a country. If you have multiple countries with a mix of units then you have multiple weak ties and no strong ties. Therefore we default to metric first, as per WP:UNITS. Only articles with strong ties to the US and UK get to use imperial units first.
  4. A major benefit of metric is that we can change from m to cm to mm to km just by shifting the decimal point. Splitting it into 1 m 33 cm makes that harder and is now rarely used in metric countries. It was more common in my country of Australia during the first 20 years after metrication when we copied our old imperial habits but it fell out of favour and we now universally say 133 cm, 1.33 m or 1330 mm as appropriate. Countries using imperial units tend to use split units because it is so hard to convert miles to feet, gallons to ounces, etc in your head.
  5. ISO 8601 dates are allowed in limited cases (mostly references and tables where space is limited). It is not used in prose because it is not yet common for native English speakers to use this in their day-to-day lives. Note that any other purely numeric format is strictly disallowed. See WP:DATEFORMAT  Stepho  talk  01:09, 22 December 2024 (UTC)
    (In terms of accuracy in my own answers, 2 out of 5 ain't bad right?) Remsense ‥  01:11, 22 December 2024 (UTC)
Being OCD helps 😉  Stepho  talk  01:58, 22 December 2024 (UTC)
I'm unsure how to medicalize it, but I'm certainly obsessive and compulsive, and it only helps somewhat! Remsense ‥  02:00, 22 December 2024 (UTC)
Answering #2 and #4 only
  • 2. No. The clarity of UTC is obtained only with a 24-hour clock.
  • 4. You could write 1 m + 33 cm if you want, but why make life so complicated? The plus sign is needed because without it a multiplication is implied (1 m 33 cm = 0.33 m).
Dondervogel 2 (talk) 07:43, 22 December 2024 (UTC)
The answer to Q2 will depend at least in part on whether UTC was chosen because it's local time or because it's the international time standard. It would make no sense to allow the 12-hour clock for events in London between March and October, but ban it for events between October and March. Kahastok talk 14:56, 22 December 2024 (UTC)
@Kahastok: I don't get this reply. The time of an events in London is given according to BST (= UTC+01:00) in summer and according to GMT (= UTC+00:00) in winter – normally without either qualification stated unless it is the weekend when the time changes. It the time zone matters (for an internationally televised live event, for example), the time is normally given both ways: in the local and in the international notations. (Or did you not realise that GMT is just another timezone, not a synonym for UTC though often used that way, especially by seafarers.) 𝕁𝕄𝔽 (talk) 15:58, 22 December 2024 (UTC)
I don't accept that UTC is always distinct from GMT. Usually there is not enough information about the reasons a particular author used one or the other abbreviation to tell if the author intended a distinction or not. Jc3s5h (talk) 17:15, 22 December 2024 (UTC)
Well OK, if we're going to insist that the sub-second formal discrepancy between GMT and UTC is somehow vitally important (despite all evidence to the contrary) the split hairs do not count in the case of Lisbon, where the local time in the winter is defined as UTC, rather than just being UTC in practice. Why would we say that a winter event in Lisbon has to use the 24-hour clock, but a summer event does not?
For the record, I don't think I have ever seen a time recorded at 17:00 GMT (17:00 UTC) and I would like to see examples of that usage. Kahastok talk 19:48, 22 December 2024 (UTC)
and you never will, because it would be pedantic in the extreme. In fact most timestamps you see anywhere will be just one of (a) not stated, because it is for local use; (b) the local timezone (notation adjusted according to whether or not DST is in operation); (c) a poor third at "front of house" (excepting worldwide online systems like Misplaced Pages), UTC time. Use of both (b)&(c) at once is very rare, vanishingly so if b=GMT or even BST.
Jc3s5h is certainly correct for use of GMT in almost all sources pre this century and still quite a few recently – it will take 50 years to fall out of use as a world standard, I suspect. Perhaps more ... who would think that there are still people who insist on chain (unit)s?
Just to be clear, I am not proposing that we introduce an MOS rule mandating any notation. Just clarifying that GMT is not a synonym for UTC. 𝕁𝕄𝔽 (talk) 20:25, 22 December 2024 (UTC)
If you weren't aiming to be pedantic in the extreme, why bring it up? And in particular, why claim - specifically in the context of GMT vs UTC - that the time is normally given both ways: in the local and in the international notations in situations where time zone matters? 'Kahastok' talk 21:22, 22 December 2024 (UTC) s
My 2c:
  1. Not just English speakers, anybody with an analogue wristwatch display does so. BUT (in the UK at least), train, bus and plane timetables are invariably shown using 24 hour clock notation. Basically, anywhere that it matters, where ambiguity might arise.
    1. The application of am and pm to 12:00 noon and midnight seems to be a perennial source of dispute, see 12-hour clock#Confusion at noon and midnight. Good luck with writing an MOS guidance that avoids that minefield.
  2. I was about to declare that UTC offsets never exceeds 12:00 so crisis, what crisis? But I think there is a UTC+13:00 on one of the Pacific islands near the date line?
  3. Stepho, the use of imperial units in the UK is dying out, literally as well as metaphorically since they are preferred by the older generation. Don't be fooled by the rail-fans insistence on chains – all UK railway engineering has been done in metric since 1975. So no, MOS:RETAIN applies to UK articles too. Except articles under the aegis of Misplaced Pages:WikiProject UK Railways, of course. --𝕁𝕄𝔽 (talk) 15:43, 22 December 2024 (UTC)
  4. I concur with Stepho's reply.
  5. Anybody who puts their boiled egg upside down should be taken out and beheaded immediately! (aka, ask us again in a 100 years time but it is a non-starter right now.)
Here endeth the lesson. 𝕁𝕄𝔽 (talk) 15:40, 22 December 2024 (UTC)
You say, the use of imperial units in the UK is dying out. Is it therefore your contention that the British (or even just younger British people) all use kilometres really and just put miles on all the road signs to confuse foreigners? Kahastok talk 19:48, 22 December 2024 (UTC)
Because of the multitude of road signs and therefore the huge cost of moving from miles, that one will likely never change. In most other fields, however, there has been a progressive move toward using metric measurements in the UK over recent decades. MapReader (talk) 04:05, 23 December 2024 (UTC)
Never mind that other countries that went metric changed our road signs just fine.  Stepho  talk  05:09, 23 December 2024 (UTC)
Dondervogel 2@, why must UTC be 24 hours? UTC is just a timezone. Technically it is no different any other timezone and the other time zones can use either 12 or 24 hour times as they wish. Of course, UTC is a little special in that it gets used as the "universal" timezone. And when somebody wants to be unambiguous they tend to use 24 hour time. And when they want to be really unambiguous they write it as UTC rather than local. But a lot of that is just convention. They could equally well say 4:00 pm UTC and still be very precise and unambiguous.
Also, why do you need the "+". In the 1970s in Australia (just after metrication) we used to see "1 m 33 cm" a lot. I've never seen anyone think that it was multiplication. It was more likely from the habit of doing "4 ft 7 in". Once we learnt that writing it as 1.33 m or 133 cm made conversion between them trivial (just shift the little dot), we dropped the complication of mixed units.  Stepho  talk  05:09, 23 December 2024 (UTC)
  • UTC is not a time zone. It's a time standard, and it uses a 24-hour clock.
  • In the language of the SI, symbols have special meanings. If you mean addition (as here) you need a "+" sign. In the absence of any other symbol, a space denotes multiplication. Outside the SI you can invent any conventions you want, and Misplaced Pages sometimes chooses to depart from the SI, via MOSNUM. I don't believe MOSNUM permits this particular departure.
Dondervogel 2 (talk) 08:30, 23 December 2024 (UTC)
Remsense, one reason Misplaced Pages can't rely on ISO 8601 throughout is that some articles express dates in the Julian calendar, or even the Roman calendar, and ISO 8601 only allows the Gregorian calendar. ISO 8601 is fine for airline schedules and hotel reservations, but it truly sucks for history. Jc3s5h (talk) 15:13, 22 December 2024 (UTC)
If we can't get Americans to switch to DMY, or Brits to switch to MDY, what hope do we have of getting both groups to switch to YMD? --Redrose64 🌹 (talk) 00:03, 23 December 2024 (UTC)
I think the biggest problem with YMD, besides unfamiliarity, is that you frequently want to suppress the Y part when it's understood, and that's harder to do when it's at the start. --Trovatore (talk) 00:14, 23 December 2024 (UTC)
I think the UN should enforce use of DMY worldwide on Mondays, Wednesdays and Fridays, MDY on Tuesdays and Thursdays, and of course dedicate the weekends to YMD. Remsense ‥  00:20, 23 December 2024 (UTC)
Whaaaaat? Why would we want the least fun format on the weekend?  — SMcCandlish ¢ 😼  09:02, 23 December 2024 (UTC)
Year-first encourages us to meditate on the long term while many are less occupied at work. Remsense ‥  08:59, 24 December 2024 (UTC)
My responses to these questions would be:
  1. There is no strong tie of "18:40" format to the US, or the UK, or whatever. It's a format used in a variety of military, otherwise-governmental (e.g. transport/transit scheduling), and sometimes scientific and a few other contexts, and that's true inside and outside the US. It's a completely abnormal format outside of those kinds of contexts, and people don't use it on an everyday basis (that I know of; maybe there is some English-using country in which it has been so aggressively imposed that it's become an everyday norm there and people don't know what "3 pm" means any more, but I'm not aware of such a place). MOS:NUM grudgingly permits its use, but 24-hour format verges on "user-hateful" and should be avoided in most circumstances (i.e. where it's not an established norm for the subject in question).
    • On JMF's side point about "12:00 pm", MoS could easily have a rule about this, just to settle the confusion, which is common among the general populace, but not among reliable sources on time and writing, in which it virtually always corresponds to "12:00" in 24-hour time, with "12:00 am" being "00:00". MoS saying something about it, though, should be to avoid it in favor of "midnight" and "noon", because confusion among everyday people persists. (My city is gradually changing all of its "No Parking 12 AM – 6 AM, Street Cleaning, Tu, Th" signs to "No Parking 12:01 AM – 6:01 AM, Street Cleaning, Tu, Th" because of this factor).
  2. Meaningless, confused question. As Stepho-wrs explained, UTC is an offset, not a format. There's a standardized way of writing the name of a UTC time-zone offset, e.g. as "UTC+05:00", but that's not relevant to how times are used or referred to (in various styles) for typical human consumption. Likewise, the Unicode name of "@" is "U+0040 @ COMMERCIAL AT", but this has no implications for use of the symbol or for plain-English references to it; writing "the at-sign" is not an error. When WP puts "3:05 pm, February 3, 2002 (UTC)" in someone's sig to conform to their date settings in the WP "Preferences" panes, that is also not an error.
    • Stepho-wrs (which surprises me, given the above) wondered why UTC offset names use a +. It's because the offsets run both directions, e.g. "UTC−05:00" is US and Canadian eastern standard time, and rendering the positive ones as "UTC 05:00" or "UTC05:00" would be problematic for humans and automation alike in various ways. The + isn't any more superfluous than the leading 0 on 00–09.
  3. A Canada–US squabble over ordering: A) Who cares? We have {{convert}} for a reason. B) This is a pretty good argument (from Stepho-wrs): "If you have multiple countries with a mix of units then you have multiple weak ties and no strong ties. Therefore we default to metric first, as per WP:UNITS." B) If that argument were not persuasive, then MOS:STYLEVAR still already covers this: When there are two competing acceptable styles, do not change from one to the other without an objectively defensible reason. Try to establish consensus on the article's talk page about which should be preferred, if you are convinced a change should happen. Iff such a consensus cannot be reached, then default to whatever was used in the first post-stub version of the article (same as with ENGVAR disputes, and CITEVAR ones). So, we are not missing any rules.
  4. It's "1.33 m" (not "1 m 33 cm") primarily because that is how the metric system is internationally standardized and how it is used in the real world, rather consistently. The two-units version is also less concise, and annoyingly repetitive because of how the units are named. And the system is designed to be decimal from the ground up. Thus Steoph-wrs observation: "Once we learnt that writing it as 1.33 m or 133 cm made conversion between them trivial (just shift the little dot), we dropped the complication of mixed units." It's not WP's role to treat occasionally-attestable but very disused variants away from a near universal system as if they had become norms and must at all costs be permitted. (Much of MoS's role is eliminating unhelpful variation that is confusion or which causes cyclic dispute, even if we settle on something arbitrary; but most of MOS:NUM is not arbitrary but standards-based.) As for US customary (or "imperial" units, never mind the British empire doesn't exist any longer and what's left of it metricated a long time ago), you can find decimal uses of it for various purposes in real-world publications (e.g. "0.35 in"), but it tends to be for special purposes, like establishing margin widths when printing on non-metric paper, and in electronic media when calculation or sorting might be needed. But the typical use of such units is in "3 ft 7 in" form because they are unrelated units, and because the two-unit split format is deeply conventionalized, including in various industries like construction. That's not true of "3 m 7 cm".
    • I don't buy Dondervogel_2's "multiplication implied" argument. Virtually no one outside of some particular ivory towers (and even then only in specialist material that was explicit about it) would ever interpret any "# unit1 # unit2" construction, in any context, as a multiplication operation. The real world routinely uses formats like this and never means multiplication by it. E.g. look at the fine print on any laptop's or other device's power-brick; you'll likely see back-to-back, undivided measurement-and-unit-symbol pairs, like "12 W  3.7 A".
  5. Skeptic2's add-on ISO-dates question: WP doesn't use 2024-12-23 format (except for special purposes) because it is not a norm, anywhere (as an ENGVAR or other geographical or dialect consideration). It's only standardized within specific industries, systems, processes, organizations, and other specialized usage spheres. (I use it very, very frequently in web development and other coding. But it's not something I'd use in a letter or a novel or an op-ed, because it's a format for computers, and for precision and cross-language exchange among engineers and scientists, not a format for everyday communication.) I've never seen one iota of evidence of broad and increasing acceptance of ISO among the general public for daily use, in regular writing (though ability to parse it has likely increased in the last 30 years because of the Internet and the amount of people's exposure to code that uses it). But it does not match anyone but maybe an ultra-nerd's English-language parsing. If you're American, probably (unless you are older and rural) what you think and say aloud to express today's date is "December 23, 2024" or perhaps "December 23rd, 2024". If you're not American, you probably (some Canadians are an exception too) would express it as some variant of "23 December 2024", "23rd December, 2024", or "the 23rd of December, 2024", depending on your age, social background, country of origin, etc. (American yokels often use the last of those; I have relatives in the Deep South who do it habitually.) These correspond closely (between exactly and too-close-to-matter) to MOS:DATE's two "M D, YYYY and "D M YYYY" formats. An ISO date does not. It's very unnatural. It requires the reader (most readers, anyway) to stop and "translate" it in their heads, thinking about which block of numbers means what, and so on. (I've been using ISO dates on a daily basis since around 1990, and I still have to think about it a little, and once in a while get it wrong, especially shortly after transferring from narrative work to coding work.) Worse, many people do not know at all whether that represents YYYY-MM-DD or YYYY-DD-MM; lots of non-geeky non-Americans mistakenly think it's the latter because they are used to D M YYYY order otherwise, and the idea of the month coming before the day is foreign to them, an annoying Americanism. I run into this problem in a great deal of online content.
 — SMcCandlish ¢ 😼  09:02, 23 December 2024 (UTC)
Official documents in South Africa are YYYY-MM-DD, I personally use it to name bank statements etc. on my computer because they are easier to find. It depends on what you are used to. Avi8tor (talk) 12:56, 29 December 2024 (UTC)
It isn’t however very readable, on articles of prose. MapReader (talk) 18:20, 29 December 2024 (UTC)
To reiterate a distinction that's not potentially reducible to cultural acclimation, it's clear that purely numerical formats are less natural in prose. Remsense ‥  18:23, 29 December 2024 (UTC)

Unit formatting

Are any of these formats correct?

  • a 10-cm blade
  • a 10 cm blade
  • a 10-cm-long blade
  • a 10 cm-long blade
  • a ten-cm blade
  • a ten-cm long blade

And why numbers are not spelled out before unit symbols, and why unit symbols are used more with metric than imperial units, where unit names are typically written in full? --40bus (talk) 13:56, 22 December 2024 (UTC)

In answer to your first question I suggest choosing between "a 10 cm blade" and "a ten-centimetre blade".
To the second, there is no internationally accepted standard describing symbols for the imperial unit system. Perhaps that is the reason. Dondervogel 2 (talk) 14:05, 22 December 2024 (UTC)
You can also consult our {{convert}} template which deals with all these edge cases: {{convert|10|cm|adj=on|abbr=on}} produces 10 cm (3.9 in), per MOS:UNITSYMBOLS.
Also, is there a reason you're not just consulting the MOS directly? It more or less covers your questions so far. Remsense ‥  15:07, 22 December 2024 (UTC)
This is possible to output: {{convert|10|cm|adj=on|abbr=on}}, and it produces: ten cm (3.9 in). So, why it is not used? And a sixth question, why fractions are not usually used with metric units? Fractions would be useful indicating repeating decimals, such as one-seventh of a meter, as things like "0.142857142857... m" or "0,142857 m" would look ugly, so 1⁄7 m would be only option. --40bus (talk) 23:13, 22 December 2024 (UTC)
Do you have a real world example illustrating your concern? Dondervogel 2 (talk) 23:22, 22 December 2024 (UTC)
How would 1⁄7 be the "only option"? You yourself just used the obvious other one: simply writing "one-seventh", which isn't broken in any way, and is probbaly easier to read for most people, than 1⁄7, which can mess with line height. It actually copy-pastes as 1⁄7, with inconsistent display on various systems. The use of the Unicode fraction-slash character is interpreted by some OSes, including my Win11 box (but not my Mac, or any Linux I can remember using), as an instruction to superscript the 1 in nearly unreadably tiny font and do the same to 7 but as a subscript. (Win11 even does this to me in a <code>...</code> block!) I'm not convinced we should have that template at all, since the Internet has done just fine with 1/7 for decades. Regarding the other material, Remsense is correct that there's a standard way of abbreviating metric units (and there's also a lot of systemic enforcement of that), but there isn't an entirely standardized approach to other units (perhaps better called "American traditional" at this point), and they are often unabbreviated in the real world. So, despite MoS providing a standard way of abbreviating them (based on ANSI or whatever, I don't remember), there's less editorial habit and desire to bother with it, while editors steeped in metric (everyone but Americans) are habituated to the short symbols. Nothing's really harmful about any of this, with regard to reader comprehension, so we have no need to firmly impose a rigid rule to do it this way or that. (We do have such a rationale for settling on particular American/"Imperial" unit abbreviations, though, since use of conflicting ones from article to article would be confusing for readers and editors alike, and some of them found "in the wild" are ambiguous and conflict with actual standards (e.g. using "m" to mean 'miles' instead of 'metres/meters'). As for the original question, yes it's "a 10 cm blade", and the output of {{convert}} is MOS:NUM-compliant. A construction like this is taken as an strongly conventionalized exception to the MOS:HYPHEN rule of hyphenating compound modifiers (writing "a 10 cm-blade" or "a 10-cm-blade" isn't really any clearer, and probably less so). In long form it would be "a ten-centimetre-long blade" and Dondervogel is correct that "-long" would usually be omitted for concision, unless it was necessary to indicate length versus width of something (which isn't the case with a knife or sword or whatnot, but would be with a shipping box).  — SMcCandlish ¢ 😼  07:12, 23 December 2024 (UTC)

Mixed spelled/figure format

How did we come to this guidance?

Comparable values near 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 were 5, 7, and 32, but not ages were five, seven, and 32.

This goes against the AP Stylebook that pretty firmly enforce that the numbers nine and below should be spelled out, while figures should be used for 10 and above. I’m not as aware as other style guides, is this a case of AP being the odd one out… or is Misplaced Pages style the odd one? -- RickyCourtney (talk) 04:14, 28 December 2024 (UTC)

The example shows it very well. Mixing both types in one sentence like ages were five, seven, and 32 looks very amateurish.  Stepho  talk  05:43, 28 December 2024 (UTC)
I agree, but as the MoS is the only style guide I've perused at length, I'd naturally be inclined to. I wonder what the provenance of this guideline is also—and that of other guidelines of note as well if anyone knows and cares to waste time telling me. Remsense ‥  05:54, 28 December 2024 (UTC)
Saying it “looks very amateurish” is very much a subjective opinion.
But to focus this on my more real-world concerns, this question was prompted by in connection to coverage of the jet crash in Kazakhstan. So in keeping with that, I present how the New York Times handles three such sentences on one article on the topic: Kazakhstan’s Emergency Situations Ministry said that at least 29 people had survived, including two children … Kazakhstan’s transportation ministry said that the flight’s passengers included 37 Azerbaijani nationals, 16 Russians, six Kazakh citizens and three Kyrgyz nationals. … The airline’s last major episode was in 2005, when an An-140 plane crashed shortly after takeoff, killing 18 passengers and five crew members.
Because of editors closely following our current MOS, our introduction on this same topic reads: On 25 December 2024, the Embraer 190AR operating the route crashed near Aktau International Airport, Kazakhstan, with sixty-two passengers and five crew on board. Of the sixty-seven people on board, thirty-eight died in the crash, including both of the pilots and one flight attendant, while twenty-nine people survived with injuries.
If we adopted AP style it would read: On 25 December 2024, the Embraer 190AR operating the route crashed near Aktau International Airport, Kazakhstan, with 62 passengers and five crew on board. Of the 67 people on board, 38 died in the crash, including both of the pilots and one flight attendant, while 29 people survived with injuries.
In my opinion, the AP style is vastly superior to what is suggested by our current MOS. RickyCourtney (talk) 07:29, 28 December 2024 (UTC)
The present guidance not to mix forms has consensus here. If you want that to change you'll need to propose a change to the wording, and explain why it is better. Saying "AP does it that way" seems unlikely to change the consensus. Dondervogel 2 (talk) 07:40, 28 December 2024 (UTC)
Long time editor, but this is definitely the first time I’ve encountered a MOS rule that I found so out of line with how I am used to writing (as you can probably surmise, I use AP in my day job). Frankly, I was just trying to get insight into why this was the consensus. I’m happy to propose something, is this the correct venue? Does it need to be in a formal format? RickyCourtney (talk) 08:17, 28 December 2024 (UTC)
Go ahead and suggest an improvement. This is the right place for it. Indeed it is the raison d'etre of this talk page. There is no formal format. Just make sure the proposed change is clear, and explain how it results in an improvement. Dondervogel 2 (talk) 08:21, 28 December 2024 (UTC)
It's pretty clear they're suggesting the AP style, right? I don't think it'll catch on here, though. However, one point in its favor one could argue is it doesn't depend at all on the surrounding context. Remsense ‥  08:24, 28 December 2024 (UTC)
I agree the verbatim AP wording, including “You should use figures for 10 or above and whenever preceding a unit of measure or referring to ages of people, animals, events or things”, would be unlikely to gain acceptance here, mainly because of its far-reaching consequences for other parts of MOSNUM. Let’s judge the proposal when it comes. Dondervogel 2 (talk) 08:50, 28 December 2024 (UTC)
No one has yet replied to the "why?" question. One would need to check the archives to be sure, but I imagine one reason is to avoid bizarre combinations like "the sum of 11 and two is 13". Dondervogel 2 (talk) 09:18, 28 December 2024 (UTC)
I suspect a significant part of the answer to “why?” is that, unlike other publications that set down a preferred style which they then use universally, Misplaced Pages explicitly tolerates a variety of styles across its ‘publications’ - most obviously for the national varieties of English, and date formats, but also in many other respects (‘AD’ or ‘CE’ being just one example) - with the MoS itself being guidelines that are widely respected, but not policy that can be rigidly enforced. This is a pragmatic compromise, given our global reach and multitude of editors of all ages and nationalities, and the practical impossibility of enforcing any single way of writing. But it does make consistency a policy issue for WP, which it simply isn’t for any other publisher (since by definition their style guides ensure that everything is consistent). Thus WP guidelines put a lot of emphasis on style choices being internally consistent within articles, because they aren’t between articles. When it comes to number format this means using either words or figures, but not a confusing jumble of both. Personally, I think this is a sensible guideline and would expect to oppose any proposed change, unless the argumentation is exceptionally convincing. MapReader (talk) 14:08, 28 December 2024 (UTC)
I'd say that Of the 67 people on board, 38 died in the crash, including both of the pilots and one flight attendant, while 29 people survived with injuries is absolutely fine and in agreement with our guidelines. The numbers one and 29 are so far from each other that there's just no reason to consider them "comparable" (except in the trivial sense that you can compare anything with anything, but that's certainly not the intended one here). I'd also consider with 62 passengers and five crew on board as fine since crew members and passenger numbers aren't really comparable either – there'll likely to be an order of magnitude or more away from each other, as in this case. That's very different from people's ages (the example given), which all come from a population's age distribution and rarely exceed 100. Gawaon (talk) 08:49, 28 December 2024 (UTC)
I would argue the present guidance should result in "62 passengers and 5 crew", not "62 passengers and five crew". I have the impression RickyCourtney would like to change the guidance to reverse that preference. Dondervogel 2 (talk) 08:58, 28 December 2024 (UTC)
62 passengers and 5 crew is certainly possible if we consider this as falling under the guideline. However, Of the 67 people on board, 38 died in the crash, including both of the pilots and 1 flight attendant, while 29 people survived with injuries is certainly too odd to consider! My point, of course, was that these sentences don't fall under the guideline anyway, due to these numbers not really being "comparable". Gawaon (talk) 09:39, 28 December 2024 (UTC)
Re: 'Saying it “looks very amateurish” is very much a subjective opinion.' Sure. But your follow up of "in my opinion" is also subjective. There are no objective measurements here. The alternatives are:
  • Existing MOS: "with 62 passengers and 5 crew on board" or the equally allowed "with sixty two passengers and five crew on board". Both are consistent and do not require me to do a mental switch between styles. I like the all numbers version and hate the all words version - subjectively of course ;) The disadvantage is that it disagrees with a couple of major US style guides - which WP is not required to match anyway.
  • AP/Times style: "with 62 passengers and five crew on board" Advantage is that it is the same as a couple of major style guides used in the US. Do British style guides agree? Disadvantage is it requires that mental switch halfway through the sentence.
It is entirely subjective whether the mental switch or matching an outside style guide is more important to you. If you like consistency (like me) then consistency is more important. And naturally, if you grew up in the US then matching major US style guides is possibly important.
Re: 'The numbers one and 29 are so far from each other that there's just no reason to consider them "comparable"'. They are in the same sentence and are comparing similar things (people). Why would you consider crew and passengers as different when listing fatalities?
Re: 'Of the 67 people on board, 38 died in the crash, including both of the pilots and 1 flight attendant, while 29 people survived with injuries certainly too odd to consider.' Why too odd? Its the form that I personally prefer and allowed by the current MOS.  Stepho  talk  13:09, 28 December 2024 (UTC)
29 only has meaning to me in that it is comparable to 1. Remsense ‥  13:15, 28 December 2024 (UTC)
This isn’t just “US style.” AP is US-based, but they serve news organizations across the world. Reuters, which is UK-based, uses the same style in this article. As does Euronews. As does the Irish Mirror. RickyCourtney (talk) 15:40, 28 December 2024 (UTC)
Fair enough - not just US. But still an external style that is just one among many and one that we are not necessarily compelled to match.  Stepho  talk  22:44, 28 December 2024 (UTC)
@Gawaon this is an extremely helpful interpretation. Thank you. I wonder if you and others would weigh in on another sentence in the Azerbaijan Airlines Flight 8243 article: The aircraft was carrying sixty-two passengers. Of those, thirty-seven people were citizens of Azerbaijan, sixteen of Russia, six of Kazakhstan, and three of Kyrgyzstan. Four minors were on board. My preferred way to rewrite this would be: The aircraft was carrying 62 passengers. Of those, 37 people were citizens of Azerbaijan, 16 of Russia, six of Kazakhstan, and three of Kyrgyzstan. Four minors were on board. That would be in alignment with how it’s been written in the New York Times, Euronews and the Irish Mirror. -- RickyCourtney (talk) 15:58, 28 December 2024 (UTC)
But is more readable as it was. MapReader (talk) 18:01, 28 December 2024 (UTC)
My choice would be all numeric: The aircraft was carrying 62 passengers. Of those, 37 people were citizens of Azerbaijan, 16 of Russia, six of Kazakhstan, and 3 of Kyrgyzstan. 4 minors were on board. No mental context switch required between numeric and spelt out words within closely related sentences — which could easily be a combined: The aircraft was carrying 62 passengers. Of those, 37 people were citizens of Azerbaijan, 16 of Russia, six of Kazakhstan, and 3 of Kyrgyzstan — 4 minors were on board.  Stepho  talk  22:44, 28 December 2024 (UTC)
+1 to this, though I admit my preference is biased because I've been taught in business correspondence to write related numbers either in words or figures, with figures taking precedence if the largest number is at least 10. —Tenryuu 🐲 ( 💬 • 📝 ) 04:20, 2 January 2025 (UTC)

Okay, so I did some more research this morning and found the answer I was looking for. This is a case of journalists adopting a style different from academics, and the MOS adopting the academic style. The APA has strict rules about consistency within categories, requiring numerals for all items in a list if any number is 10 or above. But it appears our MOS most closely matches the Chicago Manual of Style, which requires consistency, but allows for context-specific judgment if numerals or spelled-out numbers are used. -- RickyCourtney (talk) 20:46, 28 December 2024 (UTC)

Acceptable Date Format: Month Year

Right now, "Month Year" is listed as an acceptable format, with an example of September 2001, but this is *bad grammar*, violating the basic rules of English. There are two acceptable ways to convey this, grammatically:

  1. Month of Year (September of 2001), which is listed as unacceptable but is correct grammar in the form Noun of Noun, e.g. Juan Esposito of Peru.
  2. Month, Year (September, 2001), also listed as unacceptable, but again, correct grammar, of the same shape as general dates (September 1, 2001), which *is* listed as acceptable, which is correct but inconsistent, because September, 2001 and September 1, 2001 are two uses of the *same format and grammar*.

"September 2001" is bad grammar and an unacceptable format and should be labeled as such. Quindraco (talk) 15:48, 30 December 2024 (UTC)

MOS:CENTURY appears to be incorrect

I'm surprised that this hasn't been fixed already but MOS:CENTURY currently incorrectly claims that "the 17th century as 1601–1700", for example. I was about to fix the 21st century article which incorrectly claims that the 21st century started in 2001, not 2000, but then noticed that it's only like that thanks to this MoS guideline!

There have been quite a few news articles analysing the 21st century recently, many of them because the first quarter of the century (2000-2024) is now over: Guardian, Bloomberg, Billboard, IFIMES, New York Times.

I can only assume the current MOS wording came out of the mistaken assumption/hypercorrection that a century must begin in a year ending in "1" thanks to the lack of a year zero in the calendar system, but that is of course not how the term is actually used in any sources. Thoughts on the best way of fixing this? I imagine quite a few articles will be affected by this error given it's somehow ended up in the MOS. Chessrat 13:29, 1 January 2025 (UTC)

  • If it ain't broke, don't fix it. MOS:CENTURY is correct. Ask yourself when the 1st century CE (using the proleptic Gregorian calendar ) began and then work your way forward. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 15:22, 1 January 2025 (UTC)
    But there wasn’t such. The dating system was invented many years later (and incorrectly, as it turned out) and applied retrospectively. Such that it doesn’t matter whether there was a year zero, or not. Centuries nowadays are commonly recognised as 1900-1999, 2000-2099, and it’s only the WP pedants that hold out for 1901-2000. MapReader (talk) 17:55, 2 January 2025 (UTC)
    Where did you hear that. I was taught for 60 years it was 1901-2000. Did schools change their courses recently? I guess it wouldn't be the first time, but this sounds like since so many get it wrong we should make sure that Misplaced Pages follows that same wrong thinking. Like people following a printing error on the term "Blue Moon" so they think it's the second full moon of a month. Fyunck(click) (talk) 09:38, 3 January 2025 (UTC)
    That sounds like a case of Lies Miss Snodgrass told you. (I'm not saying it's actually a lie, but it's a lie that that's the only way in which centuries can be spliced.) Gawaon (talk) 11:01, 3 January 2025 (UTC)
  • Chessrat didn't explain where they looked for sources to justify the assertion "but that is of course not how the term is actually used in any sources." Misplaced Pages guidelines do not need to cite sources, since they announce the community's consensus on various matters. It is articles that must cite sources. A number of sources are cited at "Century" including
"century". Oxford Dictionaries. Archived from the original on December 30, 2019. Retrieved 20 January 2021.
Jc3s5h (talk) 15:43, 1 January 2025 (UTC)
  • “Incorrect” is not the way I would put it. Either you treat it as a style decision, with both systems being valid ways to designate the years (using either 1–99 or 1–100 for the first century) or you treat it as a logical / mathematical system, ending at 100 because you want every century to actually be 100 years, and the first year wasn’t 0. I could see it either way, but I don’t see a lot of sense trying to change it now.
What might be more sensible to pursue is a footnote that acknowledges and explains the two common ways of counting. — HTGS (talk) 03:28, 2 January 2025 (UTC)
+1 EEng 04:27, 2 January 2025 (UTC)
I don't think there's any evidence that there are two different common ways of counting? As far as I can tell from looking into this, use of the term for the period beginning in a year ending in "1" is very rare, and the only sources that mention the "ending in 1" definition (such as the Oxford dictionary entry mentioned by @Jc3s5h: mention that it is a technical definition only and not used that way in practice. It is not the case that there were widespread celebrations of the new millennium both on 1 January 2000 and also 1 January 2001!
If there were two equally-used systems then I would agree with your comment, but that isn't the case; Misplaced Pages has a duty to provide accurate information even if it does take a significant amount of work fixing this across various articles. Chessrat 16:15, 2 January 2025 (UTC)
How many years were there in the 1st century? Dondervogel 2 (talk) 18:27, 2 January 2025 (UTC)
100, obvs. 1 AD to 100 AD. Next question please? --Redrose64 🦌 (talk) 21:12, 2 January 2025 (UTC)
My question was in response to Chessrat's post claiming that centuries start in 00, in which case they must end in 99. If the 1st century had 100 years, its first year would therefore have been 1 BC (and the 1st century BC would have ended in 2 BC). Alternatively, if the first year of the first century was 1 AD, it would have been a century with 99 years. Just trying to understand how it works (I don't know which of the two is more bizarre). Dondervogel 2 (talk) 21:44, 2 January 2025 (UTC)
It is a matter of personal preference. I find it logical and satisfying that the 19th century ended with 1900 and the 20th century ended with 2000. There are many people, though, who are more comfortable with the 19th century consisting only of the years that began with 18-- and the 20th century consisting only of the years that began with 19--. I remember that Stephen Jay Gould, someone I have long admired for his adherence to logic, stated that he was willing to accept that the First century consisted of only 99 years (although I think he was wrong). We do need to be consistent in Misplaced Pages, however, and if anyone feels strongly enough about the current guidance being wrong, RfC is thataway. Donald Albury 22:10, 2 January 2025 (UTC)
Again, the numbering of years AD/BC wasnt actually devised until over five centuries after the purported BC to AD break point, and such numbering was not widely used until over eight hundred years afterwards. And it was then applied retrospectively to historical events (with, historians now believe, an error of four years in terms of when they were trying to pitch the start), relatively few of which during that period can be fixed to a particular year in any case (not insignificantly because when these events were recorded, the AD/BC calendar system didn’t exist). So it’s an artificial construct and it doesn’t really matter what the first year was purported to have been. MapReader (talk) 22:24, 2 January 2025 (UTC)
Sources are fairly clear that in common usage, a century starts with a year ending in –00, so yes, by implication that means that the 1st century had 99 years (albeit of course the Gregorian calendar did not enter use until far later so this is purely retroactive)
I didn't really expect that there would be any disagreement with this– will probably start an RfC to gain wider input as it seems like this will be a matter which there is somehow internal disagreement on. Chessrat 22:38, 2 January 2025 (UTC)
Why should all centuries have the same length? Years haven't always the same length, so why should centuries be any different? Gawaon (talk) 08:08, 3 January 2025 (UTC)
@Chessrat and Gawaon: A century doesn't have to be 100 years, but it must be 100 somethings, for example 100 runs in a cricket innings, or a military unit comprising 100 Roman legionaries. This is because the word "century" is derived from "centum", which is Latin for "hundred". If you had a span of 99 years, it couldn't be called a century. Also from "centum" we get words like "cent" for the hundredth part of a dollar. If I gave you 99 cents, you probably wouldn't give me a dollar in exchange. By contrast, the word "year" doesn't have a comparable derivation from 365 (or 366). --Redrose64 🦌 (talk) 22:24, 3 January 2025 (UTC)
Common usage having the 21st century starting in 2000 is utterly irrelevant to the Latin etymology of the word "century". The calendar system came into use long after 1 CE so analysis of the durations of past centuries is purely retroactive and simply a case of how society largely agrees to define it.
If one were to strictly assume Latin etymology is always fully indicative of how a word is used, then the article on September would say that it is the seventh, not the ninth, month of the year. Chessrat 07:40, 4 January 2025 (UTC)
Yes, the argument by name origin is fairly weak, since actual meanings don't always live up to their origins – or certainly not exactly. Centurion say: "The size of the century changed over time; from the 1st century BC through most of the imperial era it was reduced to 80 men." So if a century can have just 80 men, surely it can have just 99 years too! Gawaon (talk) 15:06, 4 January 2025 (UTC)
I agree the etymology argument is weak, but a century has 100 years, regardless of etymology. That's what we were all taught at school and that's what all credible sources say. Misplaced Pages should not take it upon itself to make up an exception. Dondervogel 2 (talk) 19:11, 4 January 2025 (UTC)
@Chessrat:
1) I actually don’t hate the idea of doing it your way, I just don’t see the need or the community interest. As you point out, socially and culturally we do treat it this way; we did have a special party on 31 Dec 1999, and not so much 31 Dec 2000. But the effort to shuffle it all around still comes with the need for a footnote explainer for our choice of convention and that now the 1st century is just the “first century” in name, and covers only 99 years. Honestly this is (imo) not a big deal, just not a hill I’d be looking to die on, and such a change will need a whole bunch of annoying cleanup. As everyone else has said, the old way has the seductive logic that 100=100. This area of Misplaced Pages especially was built early and therefore done so by those net-denizens more inclined towards “logic” than social convention.
2) As far as I know, articles on the subject of centuries are either covering the entire period broadly, or just giving a timeline of events that occurred in such years (or really, both). Presumably there’s not much worry whether we start with 1900 or 1901 when the topic is “world war, atomic energy, the end of empire, mass telecommunication and the beginnings of the internet” (etc). Alternatively, the specific events occurring on those crossover years is just arbitrarily dumped into whichever list-like article we like, and if it has carry-over effects on future events, that should get a mention either way. I guess this point (2) actually cuts both ways though, in the sense of “both work fine”. — HTGS (talk) 06:50, 3 January 2025 (UTC)
I assume by "we" you mean you personally. I also had a 31 Dec 1999 "2000" party, but my big millennium party for the century change came on Dec 31 2000. And my tickets to the event are on that date. Fyunck(click) (talk) 09:49, 3 January 2025 (UTC)
That’s honestly surprising to me. Whereabouts were you? I was in New Zealand, but my impression was that the big deal end-of-millenium in “Western” (global “North”? Anglosphere?) popular culture was 1999 to 2000. — HTGS (talk) 08:23, 4 January 2025 (UTC)
Yes, it would be a significant amount of work, but retaining an incorrect status quo is not desirable. If Misplaced Pages lasts to reach 2100, there would be the ludicrous scenario where it's impossible to cite the large number of sources stating the arrival of the 22nd century because Misplaced Pages policy defines the word "century" differently to the rest of the world.
You're probably right that regardless, a hatnote/explanatory note of some nature is needed. For instance, a lot of sources such as Reuters, The Telegraph, The Atlantic, The Guardian France 24, Times of Israel report that Emma Morano (1899–2017) was the last surviving person born in the 19th century. However, there are also a few sources such as Slate, the Washington Post, and Sky News which report that Nabi Tajima (1900–2018) was the last surviving person born in the 19th century, using the ending-in-1 definition.
At the moment, the implication of Misplaced Pages policy is that Tajima is described as having been the last person born in the 19th century on her article section, but Morano is not described as having been the last person born in the 19th century despite the numerous reliable sources stating that she was. The current policy effectively overrides any amount of sourcing of facts like that- every article treats the uncommon ending-in-1 definition as not only being a common definition but as the only definition. I don't see how a policy which arbitrarily overrides established facts and sources like that can possibly be justifiable. Chessrat 09:03, 3 January 2025 (UTC)
So your suggested change would also affect many other articles such as our own sourced 19th century article. Fyunck(click) (talk) 10:08, 3 January 2025 (UTC)
Usage such as 20th century for 1900 - 1999 simply reveals the source as being unable to perform basic counting. Any such source is immediately rendered unreliable. --User:Khajidha (talk) (contributions) 13:06, 8 January 2025 (UTC)
I'm usually one to say that we should accept that language changes and that we in the language police should go along with it, but in this case, many, especially the mainstream press, looking for headlines, are wrong. Saying the first century has 99 years, is like saying 99 cents is sometimes a dollar. Sometimes a misused word becomes acceptable, but not in this case. SchreiberBike | ⌨  14:42, 8 January 2025 (UTC)

As per WP:RS (with the emphasis on reliable), I asked Mr Google when does the new century start, then looked at any hit that seemed reliable (typically government or scientific time orientated organisations) and ignored anything like quora, mass media (I gave Scientific American a pass as they are scientific) and forums. The first 3 pages gave me the following list, plus I added the Greenwich observatory. Note, I choose them based on the sources before looking at what they said.

Organisation URL 00 or 01
Hong Kong Observatory https://www.hko.gov.hk/en/gts/time/centy-21-e.htm#:~:text=The%20second%20century%20started%20with,continue%20through%2031%20December%202100. 01
timeanddate.com https://www.timeanddate.com/counters/mil2000.html 01
Scientific American https://www.scientificamerican.com/article/when-is-the-beginning-of/ 01
US Navy Astronomical Applications Department https://aa.usno.navy.mil/faq/millennium 01
US Library of Congress https://ask.loc.gov/science/faq/399936
https://www.loc.gov/rr//scitech/battle.html (Battle of the Centuries)
01
Merriam Webster https://www.merriam-webster.com/grammar/centuries-and-how-to-refer-to-them says it used to be 01 but that public opinion is swinging
Greenwich Observatory http://www.thegreenwichmeridian.org/tgm/articles.php?article=12 01

Seems like the scientific community has a solid consensus on new centuries starting in the year xx01. The "Battle of the Centuries" is a good read. To be fair, does anybody have any authoritative sources backing the xx00 change date?

This is, of course, counter-intuitive to the layman who just sees 1999 tick over to 2000 and therefore assumes that change in the 3rd digit means a new century. But as we all know, intuition and truth do not always agree.

So why did the world celebrate the new century on 1 Jan 2000 ? I'm going to digress into armchair philosophising but bear with me. Image that you are a major newspaper, news channel, magazine, etc and you want readers to buy/subscribe. You can research it, find out that 1 Jan 2001 is the correct date and make a big thing on that date. But your competitors celebrated way back on 1 Jan 2000 and the public goes "meh, we did all that last year - get with the times you out of date moron!" The big news companies know this, so they all go with the earlier date to avoid their competitors getting the jump on them. Never let the truth get in the way of profit! Joe public naturally follows the mass media and ignores the nerds saying "2001" - why listen to boring nerds when you can party now! Party, party, party!

So, here we are, arguing whether to follow the truth or to follow Joe Public with both of his brain cells following news companies who are chasing the almighty dollar.  Stepho  talk  11:44, 3 January 2025 (UTC)

  • There are some known inconsistencies/anomalies in our treatment of centuries, including categories or articles covering decades. For example, Category:1900s in biology is a subcategory of Category:20th century in biology, but includes 1900 which the MOS puts in the 19th century. If we were starting again, I think it would have been better to avoid using century in categories or articles, e.g. use "1900–1999" instead of "20th century", but we are where we are. Peter coxhead (talk) 12:36, 3 January 2025 (UTC)
I'm not sure why you're focusing only on the specific niche of science-related sources? If the scientific community chooses to adopt an unorthodox definition of the duration of the centuries, but most other sources follow the common definition, obviously the latter is more accurate. Chessrat 13:45, 3 January 2025 (UTC)
@Chessrat: the century beginning in XX01 is not unorthodox, quite the reverse. As people above have said, it's the definition that has been taught for years, but one that I agree is increasingly being replaced by the century beginning in XX00 definition. Obviously the latter is more accurate, well, no – as pointed out above, this definition leads to the first century having only 99 years, so can hardly be called more accurate. Orthodoxy and accuracy are not the important issues in my view; the most important issue is what most readers now think 'century' means, which does appear to be the XX00–XX99 definition. Peter coxhead (talk) 14:21, 3 January 2025 (UTC)
Back in 2000 it was suggested that a year zero be created with (since years have variable numbers of days anyway) zero days. That way the first century would have 100 years in it. Hawkeye7 (discuss) 22:06, 3 January 2025 (UTC)
At least we can all agree that that would be the ugliest possible solution. — HTGS (talk) 08:26, 4 January 2025 (UTC)
@Chessrat: Scientists put much thought into the matters that they comment upon, it's a poor scientist who states something as fact when they have no demonstrable evidence. So I would take a scientist's view over a newspaper's view any day. --Redrose64 🦌 (talk) 22:52, 3 January 2025 (UTC)

RfC on the wording of MOS:CENTURY

Please consider joining the feedback request service.
An editor has requested comments from other editors for this discussion. This page has been added to the following lists: When discussion has ended, remove this tag and it will be removed from the lists. If this page is on additional lists, they will be noted below.

Should MOS:CENTURY specify the start of a century or millennium as a year ending in 1 (e.g. the 20th century as 1901–2000), as a year ending in 0 (e.g. the 20th century as 1900–1999), or treat both as acceptable options with the use of hatnotes for clarity in the case of ambiguity in articles? See the discussion above. Chessrat 14:57, 3 January 2025 (UTC)

  • The year ending in zero, which is nowadays the most common understanding. Whether or not there was ever a year zero is irrelevant, given that AD year numbering wasn’t invented until the 500s and wasn’t widely used until the 800s. MapReader (talk) 21:21, 3 January 2025 (UTC)
  • As the 1st century is 1–100, the 20th century is 1901–2000, as its article says. Let us not turn this into another thing (like "billions") where English becomes inconsistent with other languages. —Kusma (talk) 22:22, 3 January 2025 (UTC)
    Also, I do not understand what "hatnotes in case of ambiguity in articles" should mean: whenever any article uses the word "20th century", it should have a hatnote explaining whether it follows the centuries-old convention of numbering centuries or the "starts with 19 is 20th century" approximation? Perhaps it would be easier to outlaw the word "century". —Kusma (talk) 22:26, 3 January 2025 (UTC)
    In short, oppose change. —Kusma (talk) 17:46, 4 January 2025 (UTC)
  • First year of a century ends in 01, last year of a century ends in 00. This has been extensively discussed above. --Redrose64 🦌 (talk) 22:52, 3 January 2025 (UTC)
  • The RfC does not make clear what specific change is being proposed to MOSNUM wording, and I fear will lead only to a continuation ad nauseum of the preceding discussion. For what it's worth, I oppose any change resulting in a century of 99 years. Dondervogel 2 (talk) 23:06, 3 January 2025 (UTC)
  • Oppose change Century and Millennia begin in 01 and ends Dec 31, 00, like it always has and per the discussion above. Just because people make errors, like with Blue Moon, doesn't mean an encyclopedia has to. Why would we change from long-standing consensus? Fyunck(click) (talk) 09:28, 4 January 2025 (UTC)
  • Treat both as acceptable options. Century already explains both viewpoints, without describing one of them as "correct". Generally our business it not to arbiter truth (which in this case doesn't exist anyway, as either viewpoint is just a convention), but to describe common understandings of the world, including disputes and disagreements where they exist. Century doesn't privilege a particular POV here, and neither should MOS:CENTURY. Gawaon (talk) 16:31, 4 January 2025 (UTC)
    All of our articles on individual centuries mention only the traditional point of view where the first century starts in year 1 and each century has 100 years. There is no need for MOS:CENTURY to do anything else. —Kusma (talk) 17:46, 4 January 2025 (UTC)
  • Oppose. If this matters to you, convince the academic sources to adopt the change, then Misplaced Pages can follow. Jc3s5h (talk) 18:14, 4 January 2025 (UTC)
  • Oppose change I prefer centuries to begin with --01 and end with --00. I'll not bother with any arguments, since I think this boils down to personal preference. I do oppose allowing both options, as that leads to confusion and edit wars. Donald Albury 18:20, 4 January 2025 (UTC)
    Why is it personal preference to favour 1-100 AD over 1 BC-99 AD? The latter choice leads to the first century BC running from 101 to 2 BC. I find the asymmetry highly unorthodox (and hence hard to justify). Dondervogel 2 (talk) 12:37, 6 January 2025 (UTC)
    You wouldn’t start at 1BC for the first century AD in either case though. You would just treat “century” as the name for the period, and ignore that it only has 99 years. — HTGS (talk) 19:22, 6 January 2025 (UTC)
    You seem to be saying the choice between a century (the first, whether AD or BC) of 99 or 100 years amounts to personal preference. Do you have credible sources showing they are equally valid? Dondervogel 2 (talk) 19:23, 7 January 2025 (UTC)
  • Oppose treating both as acceptable This would lead to endless confusion. Peter coxhead (talk) 22:02, 5 January 2025 (UTC)
  • Oppose change; century starts at ###1 and ends ###0 — Preceding unsigned comment added by Mr Serjeant Buzfuz (talkcontribs) 23:18, 5 January 2025 (UTC)
  • Strongly oppose any change resulting in more than one definition of a century. The reasons seem self-evident, and others have spelt them out above. In a nutshell, such a change would be a retrograde step, against the spirit of the MOS. Dondervogel 2 (talk) 23:21, 5 January 2025 (UTC)
  • Just use '00s. Why on Earth should MoS ever encourage using wording that will be misunderstood by many or most people? To most people, "20th century" means 1900-1999. To pedants of history, it means 1901-2000. Cool. We should try to not confuse either of those groups. If I had to pick one, I'd say confuse the pedants, but fortunately we don't have to pick, because a third option exists: "1900s" (etc.). That's the phrasing I've always used on Misplaced Pages, for this exact reason. It's consistent with how we refer to decades (see vs. ). It's universally understood. It avoids silly arguments like this one. Let's just do that. -- Tamzin (they|xe|🤷) 23:36, 5 January 2025 (UTC)
    And to put this in terms of what the wording should be, I would suggest something like

    Because phrases like the 18th century are ambiguous (sometimes used to mean 1700–1799, sometimes 1701–1800), phrases like the 1700s are preferable. If the former is be used—for instance, when quoting a source—an explanatory note should be included if the two definitions of nth century would lead to different meanings.

    -- Tamzin (they|xe|🤷) 23:52, 5 January 2025 (UTC)
    Is this a joke? Sorry if I ruined it by asking. — HTGS (talk) 23:56, 5 January 2025 (UTC)
    No? From any descriptive point of view, there is no widely-accepted definition of "nth century". Some Wikipedians thinking there should be a widely-accepted definition doesn't make it so. And MoS should not be in the business of encouraging ambiguous wording. Instead we should encourage solutions that avoid ambiguity, much as we do with ENGVAR. -- Tamzin (they|xe|🤷) 00:05, 6 January 2025 (UTC)
    Ah, sorry. This is all just not the question at hand though, and it directly contradicts current (well-positioned) guidance.
    In any case, I’m sure we’re better off with the ambiguity between 1900–1999 and 1901–2000, which, in most cases, is not really a problem. Your idea introduces an ambiguity between 1900–1910 and 1900–. This is explicitly called out by MOS:CENTURY, of course. And does “1700s” even solve the issue of which year to start or end with? It implies that the century starts with 1700, but not explicitly. — HTGS (talk) 03:05, 6 January 2025 (UTC)
    We should avoid use of "1900s" to mean anything other than 1900-1909. Dondervogel 2 (talk) 12:29, 6 January 2025 (UTC)
    What's funny is I have never heard people talk about the 1500s, 1600s, 1700s, 1800s or 1900s, as anything except Jan 1 00 to Dec 31 99. Always 100 years. I checked and I'm shocked our wikipedia article only covers 1900-1910. The only time it gets used as a decade is when the parameters are specifically talking about the 1930s, 1920s, 1910s, and 1900s. Without that fine tuning it's always 100 year period. It would be used like the Library of Congress does, or US history lesson plans. Usually I would say the "first decade of the 1900s" with no other context. I would amend your comment to say we should never leave 1900s dangling without context. And that's only for 1900s, not anything else.Fyunck(click) (talk) 19:36, 6 January 2025 (UTC)
  • Oppose treating both as acceptable; otherwise indifferent to 31 Dec 1999 vs 31 Dec 2000. This is a style decision, but one that affects a lot of content. To use both would be a terrible solution. — HTGS (talk) 23:52, 5 January 2025 (UTC)
  • Oppose change; continue using "20th century" for 1901–2000 and "1900s" for 1900–1999. Doremo (talk) 03:48, 6 January 2025 (UTC)
  • Oppose change - The n century is 01-00, you can feel free to use "the xx00s" for 00-99. Neither is prefered to the other, but the meaning is determined by which you use. Fieari (talk) 04:53, 6 January 2025 (UTC)
    Per the MOS, and as Dondervogel 2 most succinctly puts it above: We should avoid use of "1900s" to mean anything other than 1900-1909. — HTGS (talk) 19:25, 6 January 2025 (UTC)
    I somewhat disagree. It is a very ambiguous term so we should avoid use of 1900s at all without context, because obviously readers will be confused. I sure would since I would immediately think a 100 year period just like 1800s , 1700s, and 2000s (25+ years thus far). Fyunck(click) (talk) 07:16, 7 January 2025 (UTC)
  • Oppose treating them both as acceptable. I imagine this could lead to headaches concerning inclusion in categories, list articles, timelines, templates, etc. Photos of Japan (talk) 01:23, 8 January 2025 (UTC)

Sorting of numerical data with mixed units

I need to implement sorting for a table column that mixes different units, but there is no existing guidance on how to do this. For example, the half-life column on Isotopes of thulium uses values with different units, ranging from nanoseconds to years. (For years, NUBASE2020 uses a conversion calibrated to the tropical year: 1 year = 365.2422 d.) –LaundryPizza03 (d) 04:48, 6 January 2025 (UTC)

Try this:
value name
100 years big
2 days tiny
10 days tiny
20 days tiny
10 years mid
2 years small
Note that anything less than a year is NumDays/365. Of course, you can choose your own base unit.
See Help:Sortable_tables#Specifying_a_sort_key_for_a_cell  Stepho  talk  05:04, 6 January 2025 (UTC)
I don't understand your proposal. I'm pretty sure that sort will need numerical sorting with all values converted to a common unit. –LaundryPizza03 (d) 05:24, 6 January 2025 (UTC)
It is more obvious when you look at the wiki mark-up:
{|class="wikitable sortable"
!value!!name
|-
|data-sort-value="100"|100 years||big
|-
|data-sort-value="{{#expr: 2/365.2422}}"|2 days||tiny
|-
|data-sort-value="{{#expr: 10/365.2422}}"|10 days||tiny
|-
|data-sort-value="{{#expr: 20/365.2422}}"|20 days||tiny
|-
|data-sort-value="10"|10 years||mid
|-
|data-sort-value="2"|2 years||small
|}
The data-sort-value is what the sort looks at. In this case I have chosen 1 year as the base unit. So 10 days is 10/365.2422 -> 0.027379092558308 . The rest is just for display. Click on the up/down arrows to sort increasing, sort decreasing or return to original (unsorted) order.  Stepho  talk  05:35, 6 January 2025 (UTC)
Sure, why not. –LaundryPizza03 (d) 02:10, 7 January 2025 (UTC)
  1. Kondev, F. G.; Wang, M.; Huang, W. J.; Naimi, S.; Audi, G. (2021). "The NUBASE2020 evaluation of nuclear properties" (PDF). Chinese Physics C. 45 (3): 030001. doi:10.1088/1674-1137/abddae.
Category: