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, 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 articles
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 articles
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.
Help talk:Table#Indenting tables – Help page is conflicting with MOS:DLIST and MOS:ACCESS on a technical point. No objection to fixing it, and a suggestion to just do it WP:BOLDly, but the work actually has to be done. (Aug. 2023 –Jan. 2024)
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. 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. (Nov.–Dec. 2023)
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. 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. (Oct.–Dec. 2023)
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". Result: "nearly unanimously opposed". (Oct. 2023)
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. 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). (Aug.–Sep. 2023)
Talk:Bayes' theorem#Requested move 23 August 2023 – MOS:POSS stuff. 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). (Aug. 2023)
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". 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. (Aug. 2023)
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? 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. (July 2023)
Talk:Famous Players-Lasky#Requested move 24 June 2023 – proposal to use dash instead of hyphen. 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. (June–July 2023)
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?" 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. (May–June 2023)
Wikipedia talk:Manual of Style/Biography#2022_archive#Neopronouns RfC (moved) – several options were under discussion, including singular they, using neo-pronouns like xie, always referring to subject by surname, etc. Result: strong consensus to use singular they for subjects who use neopronouns. (Oct.–Nov. 2022)
Talk:Winston-Salem, North Carolina#RfC about Info Box – involves MOS:INFOBOX and MOS:ICONS and should be a broader discussion than just about this single article. Summary: about 50% of our US city articles include highway signs in the infobox, which is very inconsistent. Result: Near-unanimous agreement to remove them, though this does not appear to have resulted in changes at other articles and probably should. (June–Sep. 2022)
Wikipedia talk:Manual of Style/Linking#RfC on self-linking within article prose – Result: "There is a consensus that self-links within prose should be allowed and that linking should be based on editorial discretion." This is about linking to one section of an article from another section of the same article. (Nov. 2021 – Jan. 2022)
Talk:Rolling block#Case and hyphen – "rolling block action" vs. "rolling-block action", and "Remington Rolling Block breech" vs. "Remington rolling-block breech". Result: inconclusive discussion (May–Dec. 2021).
Talk:Love On Top#Requested move 25 April 2021 – Revisiting whether to capitalize the first word of a compound preposition even when that word is a short preposition; MOS:5LETTER might need a revision. Result: No consensus, not moved.
Talk:Woman on Top#Requested move 6 April 2021 – Multiple proposals like "Receiving partner on top", "On top (sex)", etc., motivated by gender and language-reform advocacy views. Result: essentially a WP:SNOW: "not moved, and with a reception likely to strongly discourage near-future requests. ... Consensus in this discussion is strongly in the direction that any such move would be OR/SYNTH violating article title policies."
Talk:Bolognese School#Requested move 26 July 2024 (15 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.
The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion.A summary of the conclusions reached follows.
There is consensus that ‘serve’, ‘served as’, etc. is acceptable in many contexts without concern for neutrality, and while in other contexts it may be bad writing or poor phrasing, these questions are superseded by the overwhelming consensus that the MOS should not have a rule on this language. — HTGS (talk)03:35, 17 August 2024 (UTC)[reply]
In many articles about living persons, and particularly about persons in positions of authority, e.g. member of parliament, corporation CEO, city councilor, etc, the lead paragraph often uses the verb "to serve" in denoting the person's work." E.g. "Ms Smith serves/has been serving/has served as member of the XYZ Board of Directors." In this related discussion, the issue was raised about the potential for meaningless excess in that term's use. (Here's a useful essay on that.) This, of course, applies to biographies about persons no longer living.
Comments are invited on the following options:
A Use any simple form of "to be," e.g. "Smith is Acme Ltd auditor."
B Continue to use "serve" in biographies, e.g. "Smith serves as Acme Ltd auditor."
I would go with B, which does continue to reflect both formal proper, and common, usage, particularly in fields like politics and public office. But both forms are of course perfectly correct and acceptable. MapReader (talk) 19:56, 12 August 2024 (UTC)[reply]
Neither. This is not something that needs a broad rule. Either form is acceptable, as are other options. My most common experience is that people use "serve" to capitalize a title while complying with MOS:JOBTITLE, going for "served as President of Aybeeceedia" instead of "was the president of Aybeeceedia", which seems like a silly workaround but whatever. Firefangledfeathers (talk / contribs) 22:51, 12 August 2024 (UTC)[reply]
A is/was reflects everyday speech. To my ears 'served as' always sounds either pompous or somewhat euphemismistic, he "served as President of Aybeeceedia", but wasn't really 'up to scratch'!Pincrete (talk) 07:00, 13 August 2024 (UTC)[reply]
Neither per FFF, the euphemism angle is understandable in some cases but this also seems within the bounds of quite common language variation. CMD (talk) 07:12, 13 August 2024 (UTC)[reply]
Neither – is should be fine most of the time, but synonyms are not forbidden, and the occasional usage of serve, even if maybe a bit pompous and not strictly needed, does no harm. Gawaon (talk) 07:20, 13 August 2024 (UTC)[reply]
A is preferable in almost all cases; "serve" is appropriate for military personnel and the like (and also for waiters and tennis players!), but is empty WP:PEACOCKery in other cases. Better to stick to plain English (but hoping this is not something we're going to embody or enforce in yet another MOS rule). Justlettersandnumbers (talk) 08:16, 13 August 2024 (UTC)[reply]
Neither - both are acceptable. Also, it isn’t a dualistic choice… consider that there are other verbs besides “served” and “was” that might be appropriate. Don’t be formulaic when writing. Blueboar (talk) 12:18, 13 August 2024 (UTC)[reply]
A since any variant of "serve" denotes a positive attribute, which goes against WP:NPOV. It's not a neutral verb no matter how many clothes we try to dress it with. The opening paragraph of WP:WTW is explicit: "Certain expressions should be used with caution because they may introduce bias. Strive to eliminate expressions that are flattering, vague, or endorsing of a particular viewpoint." -The Gnome (talk) 14:14, 13 August 2024 (UTC)[reply]
It's not positive or negative. Adolf Hitler served as Führer of the Third Reich! Reinhard Heydrich served in the SS. It's completely neutral. I'm mystified as to why anyone should think it was not NPOV. -- Necrothesp (talk) 14:44, 13 August 2024 (UTC)[reply]
Neither because we don't need any more WP:CREEPY rules. He served as president, he was the president, he held the position of president, he worked as president, he became president, he was elected/appointed as president, he took office as president... Any of these will do under most situations. The idea of Public service being a form of service (as in servants, as in the opposite of powerful people seeking their own aggrandizement) is not a form of peacocking, nor is it a euphemism. It may be aspirational (the rest of us hope that the politician will serve the country instead of his own interests), but there's nothing inherently or egregiously non-neutral about it, especially when applied to people who didn't exploit their roles to harm others. WhatamIdoing (talk) 17:47, 13 August 2024 (UTC)[reply]
No rule needed. Here, there is more than one way to say something, and variety can still make for good, and interesting writing (also, 'serve' is not hard to understand in the example given, rather the NPOV or related arguments are much too strained, when not baffling). As an aside, we should probably not usually write, 'someone is job', rather than, 'someone is broad occupation', followed by where they have served in that occupation. Alanscottwalker (talk) 18:07, 13 August 2024 (UTC)[reply]
No rule, please. Either one could be at least annoying to too many editors and possibly disruptive if applied to existing text. There are figures in history of whom I wouldn't use "serve" – Caligula served as emperor from AD 37? – but we wouldn't need a MOS rule for that. NebY (talk) 18:16, 13 August 2024 (UTC)[reply]
Neither, as both are appropriate for many articles and editors can use their heads—even if this freedom results in the occasional awkward lead sentence. As my troublesome nitpick, I actually do think serve has a vaguely positive connotation compared to the bare copula—but I don't think it matters enough, as every word has a web of connotations and none is truly neutral in every situation. Doesn't register as a WP:W2W in any case. Remsense诉18:21, 13 August 2024 (UTC)[reply]
Neither --- WP:LOCATIONLOCATIONLOCATION, which The Gnome linked in his OP, is my essay, and I'm flattered. However, we don't need a rule on this. My objection to served as is that it's usually surplusage; but it has its uses now and then, and I don't see any kind of flattery or peacock-iness in it. But I will say that, applied to Hilter, it does take some of the edge off to say he "served". That's for sure the wrong word to use for him. EEng19:38, 13 August 2024 (UTC)[reply]
This needs to be said: The term "to serve" is being pronounced neutral in this discussion by sundry contributors. Is it really? Because if an ostensibly neutral term cannot be used at the extremes, it cannot be used anywhere. The Hitler example trumps all arguments to the contrary. It cannot be made more clear. -The Gnome (talk) 19:59, 13 August 2024 (UTC)[reply]
That sounds a bit extreme. Remsense said it well: no word is truly neutral in every situation. So if that's the thing to aim for, we may as well shut down this website and all go home. Gawaon (talk) 20:03, 13 August 2024 (UTC)[reply]
I think us editors are particularly vulnerable to logocentric fallacies—i.e. we're liable to treat the lexical word as the predominant or even only issuer of meaning, while affording phrases, sentences, and other composites no credence to really influence what connotations individual words must themselves possess. Remsense诉20:48, 13 August 2024 (UTC)[reply]
Neither I have no problem with Richard Nixon saying that he served as the 37th president of the United States from 1969 to 1974. That's not euphemistic and is normal English, even though most presidential historians rank him poorly. Cullen328 (talk) 20:19, 13 August 2024 (UTC)[reply]
That’s because some of us are imputing some sense of merit or sacrifice into the term “serve”, which isn’t really there. Serve can mean simply fulfilling a purpose, or function, and there is plenty of common usage where no merit is implicit, such as “serving as a bad example”. MapReader (talk) 04:28, 14 August 2024 (UTC)[reply]
So, me saying to someone Thank you for your service, for example to a veteran soldier, denotes nothing positive whatsoever; it is an abject expression of thanks for wearing a uniform, and nothing more. And, logically, I could express the same thankful sentiment to a traitor soldier. -The Gnome (talk) 14:41, 14 August 2024 (UTC)[reply]
Really you are making my point for me. Your quoted phrase does, but not because it includes the word “service”. It is positive because of the “thank you”. Had you said “I confirm your service” or “I note your service”, your comment wouldn’t have been received as positive despite the word ‘service’. Whereas, had you said “Thank you for your time in the army” or “Thank you for your work”, that would be received as a positive comment without any need to refer to serving. MapReader (talk) 17:12, 14 August 2024 (UTC)[reply]
Either, see wikt:serve#Verb, particularly entries 1.2, 1.4, 8, 12. There are contexts where the word "serve" is non-neutral, such as smiling politely whilst putting meals in front of customers in restaurants despite a torrent of verbal abuse, but the original post gives "Ms Smith serves/has been serving/has served as member of the XYZ Board of Directors." as an example, and that is different from plate-juggling. --Redrose64 🌹 (talk) 21:06, 13 August 2024 (UTC)[reply]
A or some other neutral alternative that suits the context. "Serves/served/serving" is a WP:NPOV failure, in being promotional and (positively) judgmental language. An argument could possibly be made to retain those terms for military and maybe even governmental functions, but even those uses have their long-term opponents. It's entirely inappropriate for corporate and other misc. organizational (school, team/squad, nonprofit/NGO, etc.) roles. PS: The fact that we have a bunch of articles doing this just means we have a bunch of articles to clean up. Cf. WP:FAITACCOMPLI and WP:NOWORK. — SMcCandlish☏¢ 😼 02:18, 14 August 2024 (UTC)[reply]
Comment Sorry to say, but this is yet another RfC out of the blue, with no discussion on how to frame it. There certainly should have been an option C -- a new rule saying either A or B is OK, and D -- meaning nothing new added to MOS at all. This RfC is already a complete mess out of which nothing useful can possibly come. EEng20:20, 14 August 2024 (UTC)[reply]
A Is there a specific case where anyone feels that "served as" is better, not just as good? Is it the case that "served as" has WP:NPOV problems in some people's idiolects, but not others? If so, does that mean that it has WP:NPOV problems? McYeee (talk) 01:15, 15 August 2024 (UTC)[reply]
That's what consensus is for in the abstract, and the examples proffered to illustrate why served should be generally proscribed have not really attracted consensus. Remsense ‥ 诉01:18, 15 August 2024 (UTC)[reply]
I might just be out of my depth here, and I might not have been clear, but I just don't really understand any argument in favor of the usage of "served". I think my preconceived definition of the word is just less neutral than yours. I'll bow out for now. McYeee (talk) 01:32, 15 August 2024 (UTC)[reply]
Aye, it's worth making explicit—no one is really saying it's superior in any or as good in all situations, but the MOS is meant to be as frugal as possible. We try to allow editors flexibility in things like word choice as much as possible, and we don't want to tell them what not to do unless it's almost always wrong (roughly, if it's more work to fix than it's good for to allow). See WP:CREEP. Remsense ‥ 诉01:38, 15 August 2024 (UTC)[reply]
No rule needed. The claim that "served" is pov in general has no basis. Argue specific cases on the respective talk page, but don't impose a general rule where none is needed. Zerotalk07:54, 15 August 2024 (UTC)[reply]
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.
According to the semicolon article, the semicolon is one of the least understood punctuation marks, and is not frequently used. Therefore, I'm of the opinion that semicolons should be used sparingly, and only when an alternative sentence structure is clumsy. Should MOS:SEMICOLON be updated to give this advice?
In addition, on any introduction pages to Wikipedia, such as Help:Introduction_to_Wikipedia and Wikipedia:Five_pillars, I think that the semicolons should be removed in order to make the pages more accessible to potential new editors. I've already updated those pages, one of which has been reverted so far.
I thought I'd ask for opinions and guidance here before making any more changes.
We should not encourage such use of comma splices (thanks for the diffs, Johnuniq), whether by setting such a poor example or by amending MOS:SEMICOLON. As the current Fowler's says, the semicolon is extremely useful, though it is the punctuation mark "least in evidence to anyone riffling through the pages of a modern novel." NebY (talk) 10:58, 15 August 2024 (UTC)[reply]
Admittedly I'm a priori certain that this is not a good idea. That said, I think the flaw in your specific argument here. Assuming it's true: just because many people do not generally demonstrate a working understanding of the semicolon when writing, does not mean they are confused by it when reading, or even that it is not helpful to them when reading.
What's more: new editors do literally everything wrong—frankly, if for one reason or another a semicolon encounter scares someone off, then I'm certain that in its absence another hangup would take its place. Writing is never going to be easy, and many norms are as they are for very good reasons after centuries of iteration. Remsense ‥ 诉11:14, 15 August 2024 (UTC)[reply]
There may be a minor ENGVAR-ish dynamic going on here. I have the impression that British teachers, or perhaps even more particularly English-as-a-second-language teachers in Continental Europe, have this prejudice against semicolons, but it is not widespread in the States.
To be sure, it's possible to overuse semicolons. When you first learn about them you want to put them everywhere. It gets to be a bit of a lazy habit, almost a rhythm of writing to put sentences in pairs and connect them with semicolons, irrespective of whether the two ideas being joined are really closely related.
But the fact that they can be misused is not a reason to avoid using them when they are helpful, and I don't think they cause readers any trouble worth consideration at all. --Trovatore (talk) 23:02, 16 August 2024 (UTC)[reply]
No, don’t do any further such edits. Punctuation use should be correct, for sure, but you don’t edit articles simply because of personal preference for or avoidance of certain forms of punctuation. MapReader (talk) 04:32, 17 August 2024 (UTC)[reply]
While first-person pronouns are considered poor writing for an encyclopedia, MOS:WE currently allows exceptions for the figurative we in history and science articles. A brief search in this page's archives didn't turn up any recent discussions on this, so I'd like to see whether it's still supported by the community. I believe this is outdated now that Wikipedia's voice has developed and it's not good practice for writing in an encyclopedic tone, even if it's often used in this fashion in primary and secondary sources. Thebiguglyalien (talk) 00:24, 16 August 2024 (UTC)[reply]
I would only keep we in a quote if I were quoting a full statement; otherwise, a we statement can otherwise be summarized or quoted in part and changing we to they. voorts (talk/contributions) 01:45, 16 August 2024 (UTC)[reply]
Using the portion of a quote with "we" in it is going to be essential to the meaning in some cases, clearly inappropriate in some others and somewhere between the two in the majority. Thryduulf (talk) 03:27, 16 August 2024 (UTC)[reply]
I think that there's a difference between "encyclopedic" and "stiff", and insistence on stiffness does not suit the project. "We now know that Venus is a planet" is fine, and more comfortable than "It is now known that Venus is a planet." -- Nat Gertler (talk) 01:01, 16 August 2024 (UTC)[reply]
I don't have a violent objection to We now know that Venus is a planet, but between that and Venus is now known to be a planet, I'd probably pick the latter. I don't think it's stiff, just slightly less chatty, and chatty is kind of bad for an encyclopedia. --Trovatore (talk) 01:37, 16 August 2024 (UTC)[reply]
The construction We used to believe X, but now we know Y is vague and informal. Our goal is to summarize what reliable sources say, not dissertate in asides to the reader. To use your Venus example, an article should instead say: The scientist Carl Sagan discovered that Venus is a planet in 2040.voorts (talk/contributions) 01:43, 16 August 2024 (UTC)[reply]
I find the we constructions to be stiff-sounding. Maybe I'm associating it with the "Royal We". Also, not to get hung up on an example, but presumably the first sentence of the article would be "Venus is a planet..." so there wouldn't be a need to craft the big surprise part way through. Primergrey (talk) 01:47, 16 August 2024 (UTC)[reply]
I'm certainly not expecting this to be in the lede of the entry on Venus; more along the lines of "While we now know that Venus is a planet, in Shakespeare's day it was commonly assumed to be a star, and thus his references to..." -- Nat Gertler (talk) 04:15, 16 August 2024 (UTC)[reply]
The opening clause is extraneous and this can be rephrased more formally: Shakespeare, like his contemporaries, believed Venus was a star, and thus he referred to ...
To my reading, "we" is common and suitably formal in mathematics articles. I see it in a lot of FA-class articles, but I don't have a sense of new vs. old work. I'm a non-expert, but I would suggest consulting the WikiProject before moving ahead with a broad change. Firefangledfeathers (talk / contribs) 02:58, 16 August 2024 (UTC)[reply]
That's not how I'd interpret the guidance, which reads "While opinions vary on the most edifying style, authors should generally strike a balance between bare lists of facts and formulae, and relying too much on addressing the reader directly and referring to "we".Firefangledfeathers (talk / contribs) 03:46, 16 August 2024 (UTC)[reply]
You beat me to it. I don't think anything more prescriptive than a recommendation should be adopted in general either. It just isn't possible to cover all the circumstances which may arise. Zerotalk03:49, 16 August 2024 (UTC)[reply]
Was your use of first-person plural intentional, or merely an example of how this grammatical form is so natural that one doesn't even notice when one is using it?
I don't see a strong reason for discouraging it, but as doing so has been adopted for years as a house style within Wikipedia (including in mathematics articles as discussed above) I also don't see a strong reason for lifting that discouragement. I don't think it should be forbidden. —David Eppstein (talk) 23:46, 24 August 2024 (UTC)[reply]
I'm not particularly fond of the Venus construction given earlier, but completely prohibiting such things would be counterproductive IMO. At the end of the day it's rare in enwp and doesn't hurt anyone, and as Firefangledfeathers points out mathematicians are accustomed to such verbiage. ― novov(tc)10:40, 16 August 2024 (UTC)[reply]
"We now know" begs questions – who are "we" – and isn't in our usual Wikivoice. I'd rather we described it as acceptable but best avoided in scientific writing, rather than simply acceptable. But yes, we have worse: Afterwards, we pass a car retail company and a petrol station on our left, with some allotments and Market Harborough cemetery on our right. ... We also now have to say goodbye to Kelmarsh, and hello to Maidwell... (A508 road). NebY (talk) 11:38, 16 August 2024 (UTC)[reply]
Although there are not many cases where it's useful, I don't know if it's really worth explicitly forbidding it, as it's already quite rare and most unjustified uses of it already fall under another interdiction (e.g. We know Venus is a planet is as much a WEASEL as Some have said that Venus is a planet.) — Alien333 (what I did & why I did it wrong) 14:19, 16 August 2024 (UTC)[reply]
strongly discouraged may be enough. But to achieve a FA rating first person should be removed, otherwise it is a style fail. Certainly for science articles, where I mostly work on, "we" or "our" or "us" is inappropriate. Graeme Bartlett (talk) 02:15, 18 August 2024 (UTC)[reply]
As far as I can tell, there's broad interest in such a change. Is it time to create the RfC proposing the removal of But some of these words are acceptable in certain figurative uses. and the corresponding examples from the MoS? Thebiguglyalien (talk) 16:59, 24 August 2024 (UTC)[reply]
As David Eppstein said above, the status quo (it's discouraged but not altogether forbidden) seems fine enough. I too see no good reason to forbid it altogether, so I don't think an RfC is called for. Gawaon (talk) 04:54, 25 August 2024 (UTC)[reply]
I think the proposal is to make it discouraged across the board, rather than accepted (but not encouraged) in a couple of areas and discouraged everywhere else. I would support such a change. Thryduulf (talk) 11:07, 26 August 2024 (UTC)[reply]
I'll leave it to the experts to give the definitive answer but it is important to know whether the article is about "I voted" (in which case "(sticker)" would be a disambiguator that may be redundant unless there are other "I voted" articles) -or- about the sticker (in which case, the "I voted" is an adjectival phrase and the word "sticker" should not be in parentheses). 𝕁𝕄𝔽 (talk) 09:53, 16 August 2024 (UTC)[reply]
The article is about the sticker, but the title should match the (correct) usage found in the first sentence: It's an "I Voted" sticker. "I Voted Sticker" should then redirect to that. Largoplazo (talk) 16:18, 16 August 2024 (UTC)[reply]
I have long wondered why any entry of a biographical nature manages to list the dates of service or position in government in a particular order. Personally, especially for deceased persons, I would prefer to have the dates of life itself at the top of the order, instead of any honorific or notable achievement which may or may not reflect the most notable of many possibilities. I think this is also supportive of first valuing others as human beings and necessarily descriptive of any subset of time in which a position is held. Maybe this is not the place to raise the question, and I have no idea if this is already discussed in some other style guide that mandates the current practice. But I am amenable to follow the topic wherever it is listed. Wikipedia has become a very valued resource for me who grew up spending hours upon hours as a child reading printed Encyclopedias done by World Book or Encyclopedia Britannica. 65.129.144.172 (talk) 04:48, 17 August 2024 (UTC)[reply]
I think you are talking about listings in the infobox? So for example, at Winston Churchill, his infobox lists his political details (as prime minister), then his personal details, then his military service.
If that’s what you mean, the more appropriate forum is probably Wikipedia talk:Manual of Style/Infoboxes, to discuss infobox layout in general, but it may also be that for the specific type of bios you’re talking about, most decisions have been made at Template:Infobox officeholder, where you could ask about that specific infobox on the talk page (Template talk:Infobox officeholder). I would imagine that editors of that infobox believe the political info will be more pressing for readers than the personal info, but you would have to dig through the archives to see whether that decision has even been discussed explicitly.
I will say that I don’t know the answer to any of these questions, but I have found that the layout of politicians’ infoboxes are often more complex than they need to be, and less helpful than they could be—mostly as a consequence of trying to include too much, relative to other biographies. — HTGS (talk)05:54, 17 August 2024 (UTC)[reply]
OK, I boldly changed the unsupported assertion that "it is often preferable to place images of people so that they 'look' towards the text", to an acknowledgement that some people do prefer this, but the more important part of the bullet point is that you shouldn't reverse images to achieve this.
Mandruss reverted me, so let's talk about it.
Why is it "often preferable"? Frankly I think this is just a superstition, or an aesthetic preference that some people do have but which has no actual value for the encyclopedia, beyond not triggering a reaction in the people that have that preference.
Of course a lot of things come down to aesthetic preferences, so if enough people really do have it, then that is an answer in itself. The eye, one might say, wants what it wants. But do enough eyes really want this to justify this (in my opinion irrational) guidance? --Trovatore (talk) 05:56, 21 August 2024 (UTC)[reply]
It's because the gaze of the reader will track the gaze in the portrait. So, readers are directed into the text by the faces looking inward. DrKay (talk) 07:06, 21 August 2024 (UTC)[reply]
I mean, I understand the theory. I just think it's nonsense. I can recognize a face whichever way it's pointing, and read the text just fine. --Trovatore (talk) 07:10, 21 August 2024 (UTC)[reply]
A majority of the community either supports the concept or it doesn't. As I understand it, guidelines are for keeping us all on the same page, all moving in a common direction. Not for accommodating the personal preferences of all editors or even all significant subsets of editors—on relatively inconsequential issues. I think we do too much of that. When a guideline has been watered down to the point of complete impotence, it's time to retire it per CREEP.This was the very meta reason for my revert. While I don't have a strong opinion on this specific issue, it does seem to "feel" better to me when the image subject faces the text. I can't really explain why; it could be because I've lived with this guideline for ten years and it has become imbedded in my DNA; I don't know. If you think the guideline is nonsense, it seems to me the proper action is to seek community consensus to remove it. Or boldly remove it, for that matter, but I doubt that would be accepted. ―Mandruss☎07:34, 21 August 2024 (UTC)[reply]
Well, the default position of the MoS on any given issue should be no position. I like the way EEng put it, something like "if the MoS does not need a rule, then the MoS needs to not have a rule" -- I forget the exact wording. Articles do not all have to be the same.
So why do we need a rule on this?
I do agree that, whatever the outcome, we should keep the guidance about not reversing pictures, as that is actively misleading. But we could do that by itself, something straightforward like "do not reverse pictures of persons just to make them 'look' towards the text". --Trovatore (talk) 07:41, 21 August 2024 (UTC)[reply]
Articles do not all have to be the same. I would agree with that, but the raison d'être of any style manual is consistency, and any deviation needs to have a better reason than somebody's personal preference. The encyclopedia is more important than any individual's sensitivities—we're not here to please editors—but for some reason we seem to disregard that because people aren't being paid, as if there would be a mass exodus if editors were asked to be team players (there would not). I just smh. ―Mandruss☎08:05, 21 August 2024 (UTC)[reply]
To be frank I don't value "consistency" as highly as some do in this context. Would it really detract from Wikipedia to have some photos facing one way and some facing another? I don't think so.
Since 2007[1], portraits looking to the centre has been part of Wikipedia's house style. Even if it's merely an arbitrary aesthetic choice, it's served in that and in quelling potential disputes. There's no point in weakening it with a "some prefer (but do as you please)" explanation. In 2008 we briefly had because the reader's eye will tend to follow their direction[2] but after some to-and-fro that was dropped in favour of the simple It is often preferable to place images of faces so that the face or eyes look toward the text.[3] Justifications in the MOS are often more trouble than they're worth, so if "it is often preferable" is being read as one, it might be better to phrase it as more of an injunction (to normally/generally place etc) than an observation. Has that been an issue since 2008? NebY (talk) 11:43, 21 August 2024 (UTC)[reply]
"[I]t's served in that and in quelling potential disputes". What's "that"? Being an arbitrary aesthetic choice? Are arbitrary aesthetic choices good? Really?
Sure - aesthetic choices are all around, from the choice of newspaper fonts to brick colours to logo design, and consistency in their application matters.
EEng's common and sensible response when someone seeks a MOS change is to ask where the status quo is resulting in a problem in our articles or their editing. What problems is this longstanding MOS guidance causing? NebY (talk) 16:40, 21 August 2024 (UTC)[reply]
EEng's formulation is not about the status quo; it's about whether we need a rule. If there's no active justification for a rule, that rule should be removed.
My feeling is that you should ordinarily not reverse photos, and you should put them wherever they look best, not artificially put them in a different place just because of this arbitrary shibboleth. --Trovatore (talk) 16:54, 21 August 2024 (UTC)[reply]
If you're concerned that people may be reversing photos to make them fit this style guide direction, the MOS does say Do not achieve this by reversing the image.Belbury (talk) 17:44, 21 August 2024 (UTC)[reply]
The whole point of manuals of style is to make a decision once about a design style matter, so even if the decision is arbitrary, editors don't have to spend any time on it again. This lets them focus on content. Now it's certainly possible that this specific design choice ought to be revisited in our current world with a large range of viewing widths. Readers might be better served by placing all images on the right, for example, when there is sufficient available viewing space, and centred when there is not, in order to better support flexible layout design that is responsive to the viewing width. isaacl (talk) 17:26, 21 August 2024 (UTC)[reply]
In fact, I'd go one step farther than @Isaacl and say that the entire purpose of a style manual is to codify especially the arbitrary stylistic choices that go into collaboratively producing something.
There are plenty of design, editorial, artistic, literary, etc. questions which come down to there being N pretty-much-equally valid options, and you can either pick one/some for the sake of consistency, or decide not to decide and just let anarchy reign. When you pick a lane, that decision goes into the style manual. The other times don't, because it's not helpful to dictate a non-choice as a point of style — which I think is the real crux of @EEng's point about the necessity of non-rules.
The Manual of Style is meant to dictate the choices made for editors, not to legislate the areas where they have the freedom to choose for themselves. There's room for that sort of discussion, and for its documentation, but it shouldn't be cluttering up the MoS. FeRDNYC (talk) 13:34, 23 August 2024 (UTC)[reply]
If the entire purpose of our style manual were to codify arbitrary stylistic choices, we would have a much simpler guide for citations, and probably a more complete guide for colours and other arbitrary details. — HTGS (talk)20:01, 23 August 2024 (UTC)[reply]
TLDR but this has been discussed many times, and the policy upheld. This is a basic principle of picture placement, which we should follow (and generally have done, for 20+ years). Johnbod (talk) 14:41, 23 August 2024 (UTC)[reply]
For what it’s worth, I don’t have strong opinions on whether portraits should face text, but if we do collectively believe that, then we should probably use the word “should”. That would probably resolve Trovatore’s (and my) issue with “it is preferable”. — HTGS (talk)20:02, 23 August 2024 (UTC)[reply]
We need an MOS for policies and guidelines. Something along the lines of use must or should, as appropriate, but otherwise don't worry about constantly softening guidance, as WP:IAR exceptions are always presumed to be possible. —Bagumba (talk) 03:50, 24 August 2024 (UTC)[reply]
I agree that this guideline, MOS:IM and MOS:PORTRAIT, has been in place for every long time and is widely followed (and, IMO, it's substantially sound). Discussions about language, 'often preferable" vs. 'should', approaches "how many angels" territory – a waste of time. -- Michael Bednarek (talk) 02:40, 24 August 2024 (UTC)[reply]
The distinction is whether the MOS actually recommends the first part, or whether it’s saying the first part is just a thing people do, because the MOS has a stance on the second part. If we only care to guide editors on the second, then we may as well remove the first. If we actually care that editors do the first, then we should say so. I don’t care if it’s “Images of people should "look" toward the text” or “Under normal conditions, where other concerns are not raised, images of people should be placed so that they "look" toward the text”, but the current wording sounds like: “Some people like peanut butter; those people who like peanut butter must use the knife that’s designated for peanut butter.” — HTGS (talk)05:31, 28 August 2024 (UTC)[reply]
I just disagree that this is preferable. I think it's nonsense. But I have to concede that I haven't seen a lot of people jumping in to agree with me, so not worth pursuing at this time. --Trovatore (talk) 20:33, 3 September 2024 (UTC)[reply]
I think "some editors prefer" is weasel-ly, especially since "some editors" doesn't mean much usually. In this case, what is meant is that some editors have a sense of aesthetics and a feel for article layout and others have none. We do however have a guideline of not reversing images just so they face the right way. (A common practice in some newspapers and magazines.) Hawkeye7(discuss)08:48, 5 September 2024 (UTC)[reply]
I just noticed this edit by User:Nikkimaria on 8 October 2023, which linked to a 2018 RFC I had never heard of.
Then I traced the talk page archive for this article and saw why: because User:SMcCandlish initiated a RFC on the village pump on 6 July 2018 and then linked to it on this talk page from a subheader under an earlier heading initiated by User:Netoholic. As User:Netoholic correctly pointed out at the time, this was highly improper. User:Netoholic had merely proposed planning for a RfC, not initiating one immediately.
Even worse, the subheading was worded in a cryptic fashion, "RfC opened at WP:VPPOL". Because this talk page gets so much traffic, it would have been very difficult for WP editors who do not read through every post to this talk page on a daily basis to immediately recognize the importance of what that subheading meant.
It would have been much more fair to all interested editors to give notice of the 2018 RfC under a new heading that clearly and expressly advised that User:SMcCandlish was trying to alter the community consensus on such a hot-button issue, such as "Request for Comment opened on U.S./US debate at village pump". But from the circumstances under which it was initiated, I suspect that developing a true community consensus was not the purpose of the 2018 RfC.
I have reviewed the archived discussion from July 2018. I fully concur with User:Pyxis Solitary's accurate analysis of the situation in response to User:SMcCandlish: "You are trying to push your position down everyone's throat".
As I have argued elsewhere, the Chicago Manual of Style's adoption of the irritating British English tendency to drop periods in abbreviations makes zero sense as a matter of style or policy (which is why other American style guides continue to resist it). I have long suspected that the sloppy tendency of British writers to drop periods arose from the UK's egregious mismanagement of primary and secondary education, perhaps because it wasted too much money on idiotic things like nationalizing healthcare and railways. So there weren't enough resources to go around to adequately train and hire enough teachers to teach British children how to punctuate properly.
California is full of British expats fleeing their nation's decaying educational system in search of greener pastures. American parents are happy to pay a premium to put their kids through college prep schools where they can read Chaucer with a Cambridge alum (as I did as an adolescent).
The RfC discussion is full of dubious statements such as, "half the people I argue with have the style guide". No, they don't. Most people own, learn, and use the style guides appropriate to their occupational fields.
There are over 1.33 million lawyers in the United States. They are drilled in law school on the Bluebook or the ALWD Guide to Legal Citation, which both adhere to the traditional American preference for U.S. over US. As far as I am aware, only three states omit periods in abbreviations in their state court citation styles: Michigan, New York, and Oregon. The rest of the states, the territories, and the federal courts consider those three states to have gone insane on that issue.
The vast majority of American lawyers continue to use U.S. in their personal and professional writing and expect others who work for or with them to do the same. In turn, U.S. continues to be used extensively in American English, because of how lawyers tend to dominate the management ranks of government agencies and also some corporations.
None of these points were raised in the 2018 RfC. I would have definitely raised them immediately, if I had known of the RfC at the time.
In the next two months, I plan to visit a public library to consult a variety of style guides to assess the current style situation in other fields, then initiate an RFC to switch MOS:US back to the pre-2017 version. --Coolcaesar (talk) 17:14, 3 September 2024 (UTC)[reply]
To compare major English-language legal style guides: Bluebook uses full stops for every abbrev. term and acronym, including looong ones, as a matter of style. By contrast, the UK's OSCOLA uses no stops for any abbrev or acronyms (and uses commas instead of stops to separate elements of citations). Open-access legal style guides in the US (which see more acceptance now) will either copy an old version of BlueBook (The Indigo Book) or emulate their university publisher style (Maroonbook). For the rest of the Anglosphere (except Canada iirc), it either looks very much like OSCOLA (e.g. AGLC) or a hybrid with some mix of stops.
Fwiw, I learned "U.S." in my school newspaper's MOS because we voted every 2 years on a what newspaper's MOS to use. (A now-ancient version of AP, which has the similar inconsistencies of "U.S. and UK"; the sole reason is "US" looks like the uppercase word "us".) Bluebook and OSCOLA by contrast aim largely for consistency with stops: yes vs no. But note that nobody outside of the respective legal communities uses either style, even though they have extensive style guides for general citations and prose. By contrast, AP, NYT, Chicago, Harvard, MLA, APA, etc all see wide general adoption in the US -- whether by inertia or no, general audience publishers continue to use it or adopt house variants based closely around it. SamuelRiv (talk) 17:41, 3 September 2024 (UTC)[reply]
My tldr is that for the millions of lawyers in the U.S. who put stops on everything, there's an equal (or greater?) millions of lawyers in the Commonwealth who put stops on nothing. I sympathize with feeling blindsided by the RfC, but if having ignored the BlueBook is your primary argument, then I can't see how it's not neutralized. SamuelRiv (talk) 17:46, 3 September 2024 (UTC)[reply]
I was tempted to quit reading this rambling wall of text at the point where you tied punctuation to health-care policy and railways; but I soldiered on! Then when you said that some US (or U.S.) states judge other states' sanity based on period non-usage, I again was tempted to quit. But I read on to the end. Final analysis: I should have never started, since there's little more here than your personal musings. EEng18:15, 3 September 2024 (UTC)[reply]
Why we should focus so much on lawyers? "Law" appears not at all nor "legal" more than three or four times in the RFC, so I know it isn't a reprise of a major subject from that debate. English legal writings today remain full of fossilized languages that goes back pratically to the French. UK barristers even still wear wigs in court. Not the best role models for us in matters of style, in my opinion. Largoplazo (talk) 23:02, 3 September 2024 (UTC)[reply]
Some soldiers, yesterday, expressing their opinion about the suggestion that they update their uniforms Barristers wigs are really a kind of hat. You wouldn't expect a soldier, police officer or McDonalds crew to work bareheaded. --Redrose64 🌹 (talk) 23:19, 3 September 2024 (UTC)[reply]
Yes, but if for some reason anyone proposed that any of those people start wearing wigs, the withering response would be, "Huh? Come join us in the 21st century, please." Which is kind of the point here. EEng23:52, 3 September 2024 (UTC)[reply]
Those all serve practical purposes. A McDonald's crew member's hat keeps hair out of other people's food. A soldier's helmet protects from head trauma. Even a policeman's cap provides a visor to shade the eyes. And I do often see police officers without any headgear. --User:Khajidha (talk) (contributions) 15:18, 9 September 2024 (UTC)[reply]
But many of these people's uniforms are updated every so often. No soldiers or police officers are dressed like their 1900 counterparts. Not sure how often McDonalds updates its outfits but in that case the headwear is designed to keep their hair out of the food. I'm not seeing what purpose a hat on a barrister serves other than to make them a target for mockery. (Which I suppose some might think they deserve.) Largoplazo (talk) 16:41, 9 September 2024 (UTC)[reply]
Have you been hiding under a rock? For over five years I have seen article after article making sure we use US over USA or U.S. and this is just now being contested? Sports articles have been complying on a slow but steady basis. Not sure why we would want to change back even though the original RfC was shady. Fyunck(click) (talk) 22:37, 3 September 2024 (UTC)[reply]
Indeed. Skipping over the OP’s obvious expertise in winning friends and influencing people, McCandlish et al are right that the tide of change is slowly moving towards not punctuating acronyms. You don’t see such horrors as ‘U.N.E.S.C.O.’ very often nowadays. CNN is an example of a widely-read media source - both within the US and beyond - that now doesn’t use punctuation even for shorter acronyms like ‘US’. But we should note that the current consensus doesn’t outlaw or deprecate ‘U.S.’, but simply requires consistent non-punctuation when there are always-unpunctuated acronyms, like UK or EU, in the same article. Which seems very sensible to me. MapReader (talk) 23:22, 3 September 2024 (UTC)[reply]
Circa 1900 "educated" meant knowing the classics (Chaucer, Shakespeare, Homer, etc) and fluent in Latin. Knowledge of engineering, science, etc counted for nothing. So most engineering projects were headed by somebody who knew no engineering but could quote Chaucer. Stepho talk05:52, 4 September 2024 (UTC)[reply]
Citation needed! IIRC, Victorian engineering - manufacturing, power generation, chemical, construction; railways, ships, armaments, consumer goods - was still being carried out by people who knew more than a bit about engineering, but Chaucer was rarely studied in UK universities circa 1900, when e.g. Oxford had only recently (and against much resistance) established a faculty of English literature. NebY (talk) 08:58, 4 September 2024 (UTC)[reply]
Something about Britishdepravity and the price of private education and healthcare in the US and adolescence? I'm too worried about a lawyer making threats like In the next two months, I plan to visit a public library. NebY (talk) 09:26, 4 September 2024 (UTC)[reply]
I just noticed this edit by User:Nikkimaria on 8 October 2023, which linked to a 2018 RFC I had never heard of. ...So, if you're trying to sell us on why this is an emergent crisis requiring swift and decisive action, you're really whiffing it. Explain again how this 11-month-old action, based on a 6-year-old decision by the WP:CABAL, was the product of a deliberate conspiracy to sneak in rushed changes without having to obtain your personal seal of approval? FeRDNYC (talk) 11:09, 5 September 2024 (UTC)[reply]
Not sure why about 80% of the OP is devoted to personally bashing me. Some people seem to have too much time on their hands and a bad habit of personalizing style disputes. Instead of blathering on and on about "intent" to open an RfC, just open an RfC. Sheesh.<To get to the meat of the matter, WP style (per MOS:ABBR) is to not use dots in initialisms or acronyms.
We've been tolerating a sometimes-exception of "U.S." because of rather widespread use of it, but the only reason it has that use is that it looks like the word "us" in an ALL-CAPS HEADLINE. Wikipedia never uses those, so there is no real rationale for making a MOS:ABBR exception to avoid "US", which is increasingly common in external source material as well, since fewer and fewer publishers use all-caps headlines and headings. There's sometime an strange assumption that "U.S." is somehow "required" for references to the US government, but this clearly isn't reality; e.g. the US Air Force's official abbreviation is "USAF" not "U.S.A.F." But WP really doesn't care about "officialness" of spellings anyway.
PS: This has nothing of any kind to do with British (and broader Commonwealth) English style of dropping the stops/periods from contraction abbreviations (those that begin and end with the same letters as the full word: Dr, St, Bt or Bart); the major British style guides, that are not house-style of particular news publishers, continue to recommend dots for truncation abbreviations: Prof., Fr., etc.; none of the recommend retaining dots in acronyms and initialisms. The pretense that "U.S." is an "American English" spelling is a silly red herring distraction. — SMcCandlish☏¢ 😼 05:26, 10 September 2024 (UTC)[reply]
Never link part of a word, link the whole thing, including the possessive suffix. In fact, as I can tell from your examples that you've noticed, if you use the wikicode [[Batman]]s you'll get Batmans, and if you use [[Batman]]esque you'll get Batmanesque, precisely because linking a partial word wasn't wanted. (Though that technical trick doesn't work for apostrophe-s, but the style rule still applies.) Largoplazo (talk) 12:04, 6 September 2024 (UTC)[reply]
@Largoplazo, the apostrophe case is why I'm asking. The technical part of it could be fixed, but I want to make sure that's the right way to go. I've noticed the Batman's example at Help:Wikilinks, where 's is not wikilinked, though it says "This does the right thing for possessive". So what's the right thing? Ponor (talk) 12:12, 6 September 2024 (UTC)[reply]
Help:Wikilinks may be wrong. I believe it's wrong. Maybe [[Batman]]'s did produce Batman's when the help page was written. WP:MOS should tell us what's wrong or right, and whether it matters. Ponor (talk) 13:37, 6 September 2024 (UTC)[reply]
What do you think about removing it? That can be done in the same way as we do on Vector currently (phab:T265947 if you want to review that affair, but please stick to read-only). It would look something like this at the same resolution (my apologies for any back and forthing you may do where you are irritated by where the borders of the images are drawn, since I am imperfect in taking screenshots).
Just looking at the differences in the two screenshots there, and knowing that the needs of blockquoting were originally written for works not intended to be presented on mobile resolutions, I'd say the bar might be necessary/desirable at small resolutions. We might feasibly be able to come up with some other solution, but I don't find that there's enough padding in the current styles to support a good look at a blockquote as a blockquote rather than as Just Another Paragraph in the story we're writing (rather than the story that someone else wrote). And adding more padding might be infeasible lest we be unable to fit any words in the quote on the page. ;) (That said, we set things up a long time ago for a bit more padding and now the desktop skin styles are overriding that unintentionally to be smaller than what we added, so that might also need adjustment.)
The bar has also been there for a very long time. So our users aren't surprised by it these days. (They probably can't meaningfully distinguish a quotation and a pull quotation anyway.)
There are other stylistic differences besides the left bar which may influence the question (particularly, the different fonts selected, but also the slightly increased font size), so you can bring those up, but that's not the most pertinent question.
I can noodle with some other resolutions if we want to see if there's any point where we're happy with the horizontal visual separation of blockquotes from at least paragraphs, but just wanted to get that out there. Above images were taken around 380px width which is absurdly small for most smart phones these days, but we're catering not solely to smart phone users.
(I know that this all sounds fairly positive a review of the bar, but I want to give it a fair shake moreso than a desire to keep it.) Izno (talk) 04:03, 7 September 2024 (UTC)[reply]
On Vector, we quickly reversed their addition. But they've been in mobile practically since the mobile website was rolled out, where I think there's sufficient room for debate about their use. Izno (talk) 22:22, 7 September 2024 (UTC)[reply]