Wikipedia's Manual of Style contains some conventions that differ from those in some other, well-known style guides and from what is often taught in schools. Wikipedia's editors have discussed these conventions in great detail and have reached consensus that these conventions serve our purposes best. New contributors are advised to check the FAQ and the archives to see if their concern has already been discussed.
Why does the Manual of Style recommend straight (keyboard-style) instead of curly (typographic) quotation marks and apostrophes (i.e., the characters " and ', instead of “, ”, ‘, and ’)?
Users may only know how to type in straight quotes (such as " and ') when searching for text within a page or when editing. Not all Web browsers find curly quotes when users type straight quotes in search strings.
This system is preferred because Wikipedia, as an international and electronic encyclopedia, has specific needs better addressed by logical quotation than by the other styles, despite the tendency of externally published style guides to recommend the latter. These include the distinct typesetters' style (often called American, though not limited to the US), and the various British/Commonwealth styles, which are superficially similar to logical quotation but have some characteristics of typesetters' style. Logical quotation is more in keeping with the principle of minimal change to quotations, and is less prone to misquotation, ambiguity, and the introduction of errors in subsequent editing, than the alternatives. Logical quotation was adopted in 2005, and has been the subject of perennial debate that has not changed this consensus.
Why does the Manual of Style differentiate the hyphen (-), en dash (–), em dash (—), and minus sign (−)?
Appropriate use of hyphens and dashes is as much a part of literate, easy-to-read writing as are correct spelling and capitalization. The "Insert" editing tools directly below the Wikipedia editing window provide immediate access to all these characters.
Why does the Manual of Style recommend apostrophe+s for singular possessive of names ending in s?
Most modern style guides treat names ending with s just like other singular nouns when forming the possessive. The few that do not propose mutually contradictory alternatives. Numerous discussions have led to the current MoS guidance (see discussions of 2004, 2005, 2005, 2006, 2006, 2007, 2008, 2008, 2008, 2009, 2009, 2009, 2012, 2013, 2015, 2016, 2017, 2017, 2017 (the RfC establishing the present consensus), 2018, 2018, 2019, 2021,
2022).
Why doesn't the Manual of Style always follow specialized practice?
Although Wikipedia contains some highly technical content, it is written for a general audience. While specialized publications in a field, such as academic journals, are excellent sources for facts, they are not always the best sources for or examples of how to present those facts to non-experts. When adopting style recommendations from external sources, the Manual of Style incorporates a substantial number of practices from technical standards and field-specific academic style guides; however, Wikipedia defaults to preferring general-audience sources on style, especially when a specialized preference may conflict with most readers' expectations, and when different disciplines use conflicting styles.
This page falls within the scope of the Wikipedia: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
This page falls under the contentious topics procedure and is given additional attention, as it closely associated to the English Wikipedia 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.
This page is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.Wikipedia HelpWikipedia:Help ProjectTemplate:Wikipedia Help ProjectHelp
Add a link to new discussions at top of list and indicate what kind of discussion it is (move request, RfC, open discussion, deletion discussion, etc.). Follow the links to participate, if interested. Move to Concluded when decided, and summarize conclusion. Please keep this section at the top of the page.
RfC needed on issue raised at Wikipedia talk:Manual of Style/Biography/2024 archive#British peer titles in infoboxes (June–July 2004, archived without resolution). Presently, the royalty/nobility wikiprojects have imposed putting British peerage titles in place of names in biographical infoboxes, against MOS:BIO, MOS:INFOBOX, and the template's documentation. Either the community will accept this as a best practice and the guidelines changed to accomodate it, or it should be undone and the infobox used consistently and as-intended.
Various simultaneously executed RMs by the same proponent all concluded against the desired over-stylizations (usually ALL-CAPS) – some by affirmative consensus against, some by no consensus to move.
Talk:Shays's Rebellion#Requested move 27 April 2024 – MOS:POSS: "Shays'" or "Shays's"? Result: "Shays's". No objective rationale was presented for an exception to the guideline, and evidence shows "Shays's" common in source material even if "Shays'" is also common, especially in older sources.
Template talk:Infobox university/Archive 23#Type – Should multiple entries be formatted as a list or a single phrase? (Apr.–May 2024) Result: 4:1 against proposed change to a list format; alternative idea at end neither accepted nor rejected.
Wikipedia talk:Image use policy/Archive 16#Collages in infoboxes – Primarily on a recent habit of military-conflict articles having collages of 4, 6, or even more images in their infobox. (Mar.–May 2024) Result: No formal closure, but a clear consensus against this practice; image galleries (when appropriate at all per WP:GALLERY) belong in the article body.
Wikipedia:Requests for comment/Names of deceased trans people (moved from WP:VPPOL) – Yet another round of this long-term, multi-RfC process. Consensus about "deadnames" seemed possible this time but was mostly elusive. (Dec. 2023 – Jan. 2024) Result: no consensus to change the wording of MOS:GENDERID based on this proposal; consensus against changing "should be included" to "may be included".
Related: See numerous previous deadname-related and more general GENDERID discussions listed below.
Wikipedia talk:Manual of Style/Accessibility/Archive 16#Making redundant table captions screen-reader-only – About use of {{sronly}} around table captions (which are primarily for screen readers) to hide them from the usual non-screen-reader view, only when their content repeats what is in the table headers. (Nov.–Dec. 2023) Result: Archived without firm resolion. As there was but one opposer of the idea, there is no consensus against doing this. If more opposition arose or some reason, open an RfC about it.
Wikipedia talk:Manual of Style/Trademarks#Minor consolidation merge – To merge a line-item (about stylization of stage/pen names) out of MOS:INITIALS (where the one of the examples is only semi-pertinent anyway) and into MOS:TM, leaving behind a cross-reference to MOS:TM from MOS:NAMES. (Nov.–Dec. 2023) Result: Because of some things that apply to personal not corporate names, this ended up not being practical; intead the MOS:BIO material was cleaned up and cross-references between the two MOS sections was improved; description at: Wikipedia talk:Manual of Style/Biography#Minor overhauling. No objections or other issues have come up.
Wikipedia talk:Manual of Style/Dates and numbers#MOS style for odds – About changing MOS:RATIOS to specify a format (new or otherwise) for betting-odds ratios. (Oct.–Dec. 2023) Result: No formal closure, but apparent general agreement that the : style for ratios in general applies to odds ratio in particular like the rest, and MOS:RATIOS updated to say this.
Wikipedia:Village pump (policy)/Archive 187#Proposed change MOS:TERRORIST – On how WP uses terms like "terrorist/terrorism" and "freedom fighter", specifically to add a requirement "these words should only be used in quotations or referencing third-party use of the term". (Oct. 2023) Result: "nearly unanimously opposed".
Talk:2023 Hawaii wildfires/Archive 2#Use of Hawaiian symbols in names – Involves MOS:HAWAII and could have implications for what the guideline says due to wildfire news bringing many more editorial eyes to that page than to WT:MOSHAWAII. (Aug.–Sep. 2023) Result: Archived without closure or any clear consensus; the general gist seems to be that the state of Hawaii is named Hawaii, the island is named Hawaiʻi, and diacritics (ʻokina and kahakō) should not be suppressed in the more localized names (and the US Geological Survey, which sets official placenames, along with the Hawaiʻi Board on Geographic Names, which basically tells USGS what to do in Hawaii/Hawaiʻi, both agree).
Talk:Bayes' theorem#Requested move 23 August 2023 – MOS:POSS stuff. (Aug. 2023) Result: Not moved. Lots of invalid arguments, and confused attempt to pit WP:COMMONAME against MoS (COMMONNAME is not a style policy, never has been one, and never will be; every proposal to incorporate a style matter into a policy has failed).
Wikipedia:Help desk/Archives/2023 August 5#Hyphen vs. En dash usage (Wikidata)? and d:Wikidata:Project chat/Archive/2023/08#Hyphen vs. En dash to separate years of birth/death? – Relating to concordance between wikidata descriptions and enwiki "short description". (Aug. 2023) Result: Good summary: "as long as you choose a comprehensible form, your edits are fine. However, you should not change existing descriptions for stylistic reasons, and also not to unify desriptions for a given set of items"; also observations that various languages, e.g. Spanish, do not use an en dash for this purpose. So, Wikidata will not be changing away from hyphen as default, and any desire to have WD material, like automatically provided short descriptions, will have to do that change on our end.
Talk:SAG-AFTRA#Requested move 20 July 2023 – move to SAG–AFTRA like AFL–CIO, or is there a reason to hyphenate as SAG-AFTRA? (July 2023) Result: Not moved. The closer actually misunderstood the guideline wording badly, and this has created a WP:CONSISTENT policy failure with titles of other such entities including AFL–CIO, and the Famous Players-Lasky decision covered just below. This probably needs to be re-done.
Talk:Famous Players-Lasky#Requested move 24 June 2023 – proposal to use dash instead of hyphen. (June–July 2023) Result: Use the dash per MOS:DASH; a followup RM to add "Corporation" to the title rejected that idea despite WP:NCCORP supporting it, one of several recent RM incidents suggesting that at least some portions of the page do not enjoy consensus.
Wikipedia:Village pump (policy)/Archive 182#RFC: MOS:GENDERID and the deadnames of deceased trans and nonbinary persons – Primarily about "When should Wikipedia articles include the former name of a deceased trans or nonbinary person who was not notable prior to transitioning?" (May–June 2023) Result: "there is a consensus against using the former names of transgender or non-binary people, living or dead, except when of encyclopedic interest or when necessary to avoid confusion. Also, there is clear consensus that a former name is not automatically of encyclopedic interest. Where, exactly, the lines of encyclopedic interest and avoiding confusion are is not simple or clear and will likely need discussion on individual articles, although there is definitely space for more guidance in the MOS". This has let to a lot of follow-on discussion and dispute.
Talk:Bolognese School#Requested move 26 July 2024 (14 articles) – Lowercase school for "schools" of artistic styles of painting that are not the names of actual institutions? Result: Lowercase except two that were found frequently uppercased in sources
Talk:War of 1812/Archive_29#Capitalisation of "house" and "senate" – as stand-alone terms in prose. Result: Not a formally closed discussion. In summary, shortened forms of names for institutions are not capitalized unless they are "a shorter but still specific form", not just a single generic word. The material at MOS:INSTITUTIONS probably could be clarified on the question, as this isn't the first time the matter has come up.
Talk:Hurricane Alley#Requested move 11 July 2024 – Call this the "Main Development Region" or "Main development region"? Result: "Main Development Region" without prejudice against considering "Main development region"; new RM opened.
Talk:Popverse#Redirect templates – Should the "avoided double redirect" tag to applied on a correctly capitalized redirect when there's a similar but miscapitalized redirect? Or should only the miscapitalized one be so tagged? Result – Removed tag from correctly capitalized Popverse as inappropriate, and left it on PopVerse which is miscapitalized.
Talk:IMP.#Requested move 9 June 2024 – All-caps for this shortened form of "Impactors"? Result: All-caps retained since sources seem to do that.
Talk:Pied-Noir#Lowercase – Lowercase "Pied-Noir" (or use "Pied-noir" or "Pieds-Noirs" or "Pieds-noirs" or "pieds-noirs")? Result: Lowercase "noirs", leaning lowercase for "pieds" as well.
Talk:Toy boy#Requested move 17 December 2023 – Should lowercase indicate a boy that is a toy rather than the title of some published works? Result: Yes; disambiguation moved to uppercase.
WT:WikiProject Freemasonry#Capitalization – Where do we draw the line of capitalization of offices and such in Freemasonry? Result: Some say just follow MOS:OFFICE, others want to follow Freemasonry's conventions. No clear consensus.
Talk:NTV Plus#Requested move 15 September 2023 – Is all-caps an appropriate distinction between Russian and Nepali TV channels? Result: No; use ordinary title case for proper name, not all-caps.
Talk:Sangaku#Capitalization: is the article title just an ordinary Japanese word borrowed into English, or a proper noun? (note – while the discussion was not formally closed, all instances are now in lowercase
Talk:Welsh Revolt#Requested move 30 July 2023 – Initially Welsh Revolt → Glyndŵr Rebellion but subsequently a question of capitalising the second word in any choice. Result: Lowercase "rebellion".
Talk:In Search of...#Requested move 10 October 2022 – Should the "of..." become "Of..." because it is the last word of the title? (a two-article RM) Result: Retain lowercase since truncation of a longer title is implied.
Talk:Lost Decades#Requested move 7 July 2022 – Lowercase "Decades", among other issues? Result: Not moved. The closer commented about primary topic status but did not comment about capitalization.
User talk:Snickers2686#MOS:JOBTITLES – "until [JOBTITLES is] applied consistently, which it isn't in this set of articles, then to me, it doesn't apply at all". – judges generally lowercased
Talk:National Historic Landmark#Requested move 18 January 2022 – Multimove to lowercase for "National Historic [Capitalized singular]", "National [Capitalized plural]", and "List of Historic [Capitalized plural]"? Result: Withdrawn after near-unanimous opposition to the central principle based on the linguistic concept of a proper name, noting consistent capitalization in sources.
Talk:g-force#Requested move 7 January 2022 – "g-force" or "G-force"? Result: RM procedurally closed (made no difference) and usage in article prose already changed to "g-force".
2021
RMs on capitalization of "Attorneys" and "Ambassadors" (or rephrasing to avoid the plural formal title): – all downcased
WT:AT#RFC on dash-separated titles for sports events 2 January 2022 – Capping of "Men's Singles" and "women's doubles"? Result: No consensus to ban dashes, no consensus on capitalization; consensus that capitalization should be worked out at WikiProject Tennis.
from looking at MOS:COMMA, there isn't any guidance on how to deal with names with Inc.. multiple articles do any of the following, either with no comma, a comma only before and a comma around the word.
Mumumu Inc. is a company ...
Mumumu, Inc. is a company ...
Mumumu, Inc., is a company ...
I am aware that the commaless and comma style may coexist (sometimes in the same article!), however the second and third styles should likely be decided upon. Juwan (talk) 01:09, 26 December 2024 (UTC)[reply]
Oh boy, oh boy, oh boy, oh boy, oh boy! I cannot wait for someone to say that Inc. is an "appositive", and therefore the commas have to come in pairs. EEng01:20, 26 December 2024 (UTC)[reply]
When I read Wiki policy and guidance pages, I sometimes find shall used instead of will to indicate what must be done — for example, in the Signs of Sockpuppetry article, we find: "The more signs that are present, the more likely sockpuppetry is occurring, though no accusations shall be made unless, beyond a reasonable doubt, one is really certain."
Granted that shall is often used this way in government and judicial documents, I think it sounds somewhat at odds with the more user-friendly ambience Wikipedia has tried to create for editors. Besides, shall is not consistently applied throughout the policy and guidance pages — for example, in the same Signs of Sockpuppetry article, we find: "The closing administrator will be required to follow the consensus, even if they personally disagree."
— For the above reasons, wouldn't it be in Wikipedia's best interests to avoid using the conversationally archaic shall in these articles and replace it with will?? I doubt that this would make editors with wrongdoing on their minds less likely to behave as desired.
— But if the decision is made to continue "shalling," then for the sake of consistency couldn't a search-and-replace be done throughout the policy and guidance articles to replace will with shall where the word needs to indicate what must be done? Augnablik (talk) 16:53, 28 December 2024 (UTC)[reply]
It's fine, really. This is one of those things the MOS exists to obliquely neutralize—i.e. this is a pretty conjectural position and not worth getting into all-in or all-out discussions over. Remsense ‥ 论17:16, 28 December 2024 (UTC)[reply]
“Obliquely neutralize” — there’s a new one for me! 😅
I just thought it would help lighten the bureaucratic tone of these articles to dial down the legalese, as many editors feel increasingly on edge with all the rules and regulations they discover the more they wade into Wikipedia. Augnablik (talk) 17:31, 28 December 2024 (UTC)[reply]
The classic rule is that, in the first person (I/we) the unmarked form is "shall", whereas "will" connotes a deliberate choice, but in the second and third person, the unmarked form is "will", whereas "shall" connotes a demand based on the speaker's authority.
There are two good ways to remember this. The classic one is the English canard about the Irishman in trouble in the lake, who said "I will drown and no one shall save me", so to respect his wishes, they let him drown.
Just be aware that you’ve entered the purview of a global encyclopedia, and that means you will encounter forms of English that aren’t necessarily common locally to wherever you live. MapReader (talk) 17:57, 28 December 2024 (UTC)[reply]
@MapReader, Although I’m aware of different styles of English in different parts of the world, the shall/will issue I’ve raised here is more about how Wikipedia wants to show officially expected actions in particular situations.
Not like , “Today I shall go to the beach” … but like, “Administrators shall hold discussions on the matter for one week before reaching a decision.” Augnablik (talk) 12:10, 30 December 2024 (UTC)[reply]
Nevertheless, ‘shall’ is still reasonably common usage in formal, official or legal written texts, in the UK, in a way that I don’t think you can say for the US (but willing to be corrected…), and is not considered particularly user-unfriendly. Your observation to the contrary above is therefore pitched from the perspective of a particular Engvar, which was my original point. MapReader (talk) 15:16, 30 December 2024 (UTC)[reply]
@MapReader, you're probably right about "how official" shall sounds to UK and US readers of official documents. And frankly, that word is still used from time to time in official documents in the US, even though much more rarely these days. Even so, here's a thought: if will would work equally well as shall in Wikipedia policy and guidance documents, why not use it consistently here so as to make "official stuff" sound a bit less bureaucratic but at the same time affirming of expected behavior?
Though I'm American, I doubt that any of our UK cousins across the pond would feel affronted if Wikipedia consciously adopted will in its policy and guidelines. Wouldn't it simply be one more example of Wikipedia's intentions of providing as welcoming and user-friendly environment as possible in which to work, while in no way demeaning other varieties of writing?
Alternatively, to avoid the whole shall/will issue, there are still other ways wording could be done. For example, instead of "Administrators shall hold discussions...,” we could say, "Administrators are to hold discussions ....” Augnablik (talk) 11:04, 31 December 2024 (UTC)[reply]
Onbiously, you're free to edit how you want, but as a general rule, surely it isn't WP's object, nor that of the MoS, to try and enforce general language preferences on our editors? MapReader (talk) 11:41, 31 December 2024 (UTC)[reply]
Well, @MapReader, I think it’s time for me to gracefully bow out of the discussion now. My only Intent in making my suggestion was far from an attempt to enforce, though I see how it might be interpreted that way.
Instead, I was trying to make a case for a slight change in wording that seemed to me could help Wikipedia accomplish its very positive goal of creating an open, light, friendly ambience — just as seniors helping in the Teahouse and elsewhere are asked to do with those who ask questions. I know that as some editors get involved with Wikipedia, they come to feel weighed down by many rules and regulations and even become fearful they might make a slip and face serious consequences.
Just for the record, I detest and/or, which the MOS backs me on, but (besides ... instead of the clearer [...] in quotations) I also detest Archimedes's. Can't we just use the Latinate genitive Archimedis? --Florian Blaschke (talk) 04:56, 11 January 2025 (UTC)[reply]
It seems to be required by MOS:WAW that any statement that uses constructions like:
This concept is called Example, ... (also termed, known as, referred to as, etc.)
italicize the term. However, this is almost never consistently done even in many of our FAs (see Introduction to general relativity, used as an example in the MoS), and many other publications are unbothered. Am I worrying about something that doesn't make a difference in the clarity of many passages?
The mainstream script's slow, gradual evolution continued during the Zhou dynasty until assuming the form now known as small seal script within the state of Qin. Other scripts in use during the late Zhou include the bird-worm seal script, as well as the regional forms used in non-Qin states. Historically, these forms were collectively known as large seal script, a term which has fallen out of favour due to its lack of precision.
”
It just looks weird that maintaining a natural flow in more jargon-y passages requires two terms to be italicized and one not to be. It looks arbitrary, and might even confuse readers if they notice? Remsense ‥ 论01:56, 11 January 2025 (UTC)[reply]
I don't think that either of the phrases in the example qualify as words as words. WAW, I think, applies to things like, "Of all the nouns, birdcage is the best." Or, "...some egghead discovered a misprint of the book, with relative misspelled." I would use quotation marks in the example you provided.
I am finding an increased number of refs in the middle of text, and I wondered if it could be confusion to the current wording. If the editor/reader deos not read more/further than the first sentence of this section of the paragraph, they may well put the ref in the middle of a sentence and not after punctuation as it appears to first suggest that:
"All reference tags should immediately follow the text to which the footnote applies, with no intervening space. Apart from the exceptions listed below, references are placed after adjacent punctuation, not before."
Can we consider rewording this to:
"All reference tags should immediately follow the text to which the footnote applies, and should be placed after the next adjacent punctuation with no intervening space. The exceptions to this are listed below."
This would then read as a two-part instruction rather than the current which appears to be one instruction to place it directly after the text.
No, it's saying that if there is adjacent punctuation, the ref goes after, but it does not preclude placing a ref immediately after the relevant text when there is no adjacent punctuation. Schazjmd(talk)14:12, 19 January 2025 (UTC)[reply]
I've always understood the part about punctuation to mean only that if the text to which the footnote applies ends in a punctuation mark, treat that mark as part of the text you're footnoting and put the footnote after it. There's no implication that you have to defer placement of the footnote to the next punctuation mark that appears. And certainly not to the end of the sentence: the guideline covers commas as well. Largoplazo (talk) 14:53, 19 January 2025 (UTC)[reply]
Honestly I think we should use "persons" as the unmarked plural of "person" Wikipedia-wide. Encyclopedic writing is a very formal register, and "people" has other baggage, often not intended.
There has been no negative intent on my part when using 'people', but so it goes.
These articles have been on various communities and I have made such changes for years, but till now have never had any editor state that grammar is immaterial. Hushpuckena (talk) 11:08, 17 January 2025 (UTC)[reply]
Some section headings are either by guideline, like WP:ELORDER for "External links" or MOS:NOTES for "Notes" and "References" etc., or by tradition and common usage, like "Notable people", "Awards", "Published works", written as plurals, even if there's only one entry. -- Michael Bednarek (talk) 11:37, 17 January 2025 (UTC)[reply]
Agreed; keep it plural, also like "Languages" in the sidebar (even for only one language) and like "Media" in the Commons template (even for only one file there). Doremo (talk) 11:55, 17 January 2025 (UTC)[reply]
As far as I'm aware, serial comma inclusion/omission is always treated separately from spelling conventions; MOS:SERIAL doesn't say anything related to MOS:TIES. However, when an article employs Oxford spelling ({{British English Oxford spelling}}), would it be reasonable to require the serial comma? (Of course, this wouldn't prohibit removing it to avoid local ambiguity.) On one hand, it seems a bit odd that editors of a specific article must follow one prominent component of a specific style guide's instructions while being free to ignore another component, and because en-gb-oxondic is a narrow group of articles and compliance requires a little training, these articles are already having their spelling/grammar watched by editors who are familiar with everyone else not being aware of the standards. But on the other hand, I can imagine it being awkward to require serial commas on a small portion of the encyclopedia, while the rest of the encyclopedia merely requires internal consistency; it might lead to confusion because a small set of articles has rules different from the rest. Nyttend (talk) 22:18, 19 January 2025 (UTC)[reply]
The serial comma and Oxford spelling are not related to one another save from the fact that Hart's Rules and the Oxford English Dictionary share the same publishing house on the River Isis, and they are not intended to complement one another in any particular way. As you've noticed, this is conflating apples with oranges stylistically. More concretely, our guidance on serial commas is not dependent at all on what variety of English is being used—instead, it should be consistent, and possibly depend on what is best for eliminating ambiguity in each article on an individual basis. Remsense ‥ 论22:23, 19 January 2025 (UTC)[reply]
So Hart's Rules doesn't demand the use of Oxford spelling? My thought process:
Oxford spelling says that Hart's Rules follows Oxford spelling
Style guides are created to be prescriptive on this kind of thing, so Hart's Rules will require a specific spelling system
Hence, it's highly likely that Hart's Rules will require the spelling system that it uses
Oxford spelling is just that—spelling. As an ENGVAR, it is merely British English with etymologically-minded spelling conventions. Remsense ‥ 论22:42, 19 January 2025 (UTC)[reply]
I remember reading a while ago that Wikipedia does not use honorific titles in referring to people, e.g. Albert Einstein or Einstein instead of Dr. Albert Einstein or Dr. Einstein. I can't find anything like that today. Did I imagine that? Is there any style guidance on use of titles such as Doctor? MOS:HONORIFIC is just about using special honorifics associated with a person who is the subject of a biography. Bryan Henderson (giraffedata) (talk) 03:51, 21 January 2025 (UTC)[reply]
As a general rule, we also don't use even less specific honorifics or courtesy titles (I'm not super-sure of the distinction between the two), like Mr, except in quotes. See MOS:MR. --Trovatore (talk) 08:28, 21 January 2025 (UTC)[reply]
Based on a dispute at Bicolor cat. Does the fact that the article has, and has always had, a clear ENGVAR title control what variety the body uses? Seems obvious to me, but the guideline doesn't actually state what to do.
In this particular case, the article was created as the stubbiest of stubs in 2002, with the creator using "bicolor" in the title (and the article has never been moved, I double checked) while using "bicolour" in the one-paragraph body. Over the next few years contributions included both spellings, and both appeared in the body at the same time. However, noting the inconsistency, a wikignome edited the body in 2008 to consistently use "color" and that ENGVAR was used consistently and continuously for 16 years until last September when, citing the ancient stub in Theo edit summary, someone changed the body ENGVAR to use "colour" making it inconsistent with the title. I changed it and was promptly reverted. I argue that there was no consistent variety at all until 2008, and that having a variety consistent with the title (which again, has never changed) is the only logical and valid ENGVAR. oknazevad (talk) 23:15, 21 January 2025 (UTC)[reply]
Flip a coin if you want, but pragmatically a move is a "more substantial" alteration, so I would go with the title form. Remsense ‥ 论23:22, 21 January 2025 (UTC)[reply]
A quick spot check of the article's early history confirms that it started as "bicolor". Since there are no close ties to any country for this term, there is no reason for it to prefer either British or US spelling, so we fall back to the spelling used when the article was created. The use within in the article should match the articles name, so "bicolor" is the correct spelling for this article. As said above, this is all following WP:ENGVAR. Note: I say this as an Australian who would naturally use "bicolour". Stepho talk23:27, 21 January 2025 (UTC)[reply]
I agree with oknazevad that it never had a consistent style until oknazevad's change to make the body consistent with the title. The previous change to use "colour" throughout the body does not count because the title remained inconsistent. I agree with the comments above that going with the original title is a smaller change and therefore better, but we can reach the same outcome by a different argument: oknazevad's version was the first consistent version so we should go with that. —David Eppstein (talk) 23:45, 21 January 2025 (UTC)[reply]
To be clear, I was not the editor who made it consistent in 2008 (which was done with this edit. In fact, I had never edited the article until today, after I noticed the obvious clash between the title and the body. A quick look at the history showed that it had been changed last September. I was just changing it back to the consistent ENGVAR the article had for over a decade and a half. oknazevad (talk) 01:33, 22 January 2025 (UTC)[reply]
Please stop making this claim. It was inconsistent before I edited it: [2]. I noticed the inconsistency and looked at the oldest revisions to decide on which variety to change to. Traumnovelle (talk) 02:18, 22 January 2025 (UTC)[reply]
Your implied claim that it was never consistent until you edited it is clearly false: the 2008 version that oknazevad links to is consistent. And your implied claim that your edit (I assume in this version) made it consistent is also false: there is no consistent spelling even if one ignores the obvious inconsistency between article and text. One could interpret your comment here as meaning merely that the version immediately prior to yours had inconsistencies (as did the version after your edit) but that is not a valid reason to choose one spelling over another; one has to look at the history. —David Eppstein (talk) 04:43, 22 January 2025 (UTC)[reply]
Exactly. The version before the one you just linked to has one errant ENGVAR use. The alternate spelling in the first sentence is not only typical but expected. The only other use is in the title of a reference, and that should not be altered. oknazevad (talk) 10:24, 22 January 2025 (UTC)[reply]
I understand that there is generally something of a taboo about breaking the entirety of a section into subsections without leaving any "independent" content; i.e., having all of the information under a given level two heading further located under level three subsections. I can see the appeal of having a separate paragraph at the beginning of the section as a sort of mini-lead, but as far as I can tell, there is nothing in the MOS requiring this. Is there truly anything wrong with having part of an article formatted like this, even if it isn't the most popular? — Anonymous00:57, 24 January 2025 (UTC)[reply]
No, there's nothing wrong with this. I've done this in multiple Good Articles including Antiparallelogram, Binary logarithm, and BIT predicate. I don't recall seeing any complaints about this from the GA reviewers. As long as the section title is self-explanatory enough and its subsections independent enough, one doesn't need a section summary paragraph first. In all of these cases, one could add a paragraph briefly summarizing each subsection, but it wouldn't add much useful content to the article. —David Eppstein (talk) 02:37, 24 January 2025 (UTC)[reply]
Per above, there are obvious cases when it is advantageous versus when it is not. It depends on which structure feels more or less natural for discussing the subject at hand, as obvious as that may sound.
(Someone tell me if I'm wrong here, but iirc German academia actually has particular preference for perfect cover by the subsections within monographs etc. A bit different than ordinary technical writing esp. since it's doing something very particular, but the infamous Tractatus comes to mind as the total reverse.)Remsense ‥ 论03:08, 24 January 2025 (UTC)[reply]
Just to be clear, executive order titles do not have quotations, correct? Across such articles, I have seen some with and some without, and MOS:NEITHER is not too explicit. I am asking due to the influx of executive order pages being created. Why? I Ask (talk) 10:53, 24 January 2025 (UTC)[reply]
I'd say that yes, quotation marks should be used around them. We generally use quotation marks around titles of the kinds of works that are typically short and rarely published stand-alone (newspaper and journal articles, short stories, poems etc.), and use italics for long, stand-alone works (novels and other books, films and TV series etc.). Executive orders seem to fall into the short category and so get quotation marks. Gawaon (talk) 04:12, 25 January 2025 (UTC)[reply]
I find capitalization sufficient for executive orders, laws, acts, etc. I don't see them in quotes in sources. I've noticed that Australian acts, etc. seem to be italicized, but I've never made the effort to investigate it. If something is capitalized on Wikipedia, that identifies it as a proper noun, a specific thing. That's enough. SchreiberBike | ⌨ 12:53, 25 January 2025 (UTC)[reply]