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.
Talk:1925 Tri-State tornado#Requested move 26 December 2024 – involves a number of style and title questions, including capitalization, disambiguation preferences, what the most common name in RS is, etc.; reopened after move review (Dec. 2024 – Feb. 2025)
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.
Talk:Tri-State tornado outbreak#Requested move 18 December 2024 – Was this a "Tri-State tornado outbreak" or a "tri-state tornado outbreak"? Result: Year added ("1925 Tri-State tornado outbreak"), but no explicit conclusion was expressed about capitalization (an initial move to lowercase was changed by the closer to uppercase the next day), then a move review was opened
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.
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]
Me also. It’s a straightforward grammatical rule that ‘s indicates a possessive singular and ‘ ,following on from an s, indicates a possessive plural. That is clear to both casual and expert readers alike, and the large majority of our readership nowadays wont have any familiarity with the archaic or traditional forms used for a handful of mostly ancient historical figures. MapReader (talk) 05:30, 7 February 2025 (UTC)[reply]
MOS:ELLIPSIS says: "Wikipedia's style for an ellipsis is three unspaced dots (...); do not use the precomposed ellipsis character (…) or three dots separated by spaces (. . .)".
Do this cover only the U+2026 character …, or also the U+22EF midline horizontal ellipsis ⋯ (a.k.a. centered dots), in which case this should be mentioned?
It definitely only covers lowered dots, U+2026. The other kinds of ellipsis are used primarily in mathematical formulas and replacing them by individual dots would break the formatting of those formulas. Hairy Dude has stated in Wikipedia talk:Manual of Style/Mathematics that the supposed "uncontroversial technical request" (which per that discussion turned out to be controversial and was reversed) was based on a misunderstanding: they incorrectly believed that the dots in the article in question were lowered dots, U+2026, possibly because of technical limitations of their browser. Centered dots are typographically correct for this formula, and uncentered dots are incorrect. (The meaning is still conveyed but the formatting is not good, kind of like writing the name Lefèvre without using the grave accent.) —David Eppstein (talk) 18:15, 27 January 2025 (UTC)[reply]
I read that to be Wikipedia's style for an ellipsis is three unspaced dots (...) prohibits all other types of ellipses; the other things after the semicolon appear to be "including but not limited to". The purpose of MoS is consistency.
The centering can easily be done with {{DISPLAYTITLE:1 + 2 + 3 + 4 + <spanstyle="position:relative;bottom:0.3em">...</span>}}. In fact with this CSS, the dots render more centered on my computer. 173.206.40.108 (talk) 08:06, 6 February 2025 (UTC)[reply]
n-th versus nth
Is n-th or nth supposed to be used? If you do know, please add it to the dash/hyphen section of the page as that's where people will probably look for it, (idk if a hyphen or en dash is supposed to fall between "n" and "th") and if there is not a standard set for Wikipedia I think that it should be set to be "n-th" with a hyphen to match the OEIS, as n-th is typically referring to a sequence and the OEIS is probably the organization to look to when handling sequences. Apersoma (talk) 19:47, 28 January 2025 (UTC)[reply]
The OEIS, great as it is, is not eminently viable as a style guide, since its choices seem to be made toward facilitating plaintext representations. Since we're typically meant to italicise variables, wouldn't nth be correct? Remsense ‥ 论19:50, 28 January 2025 (UTC)[reply]
My preference would actually be nth, as a specific exception to the rule about not using superscripts here, because it extends better to (n+1)st and so on. I think (n+1)st is kind of confusing. --Trovatore (talk) 20:23, 28 January 2025 (UTC)[reply]
Reasonable minds may differ here I think. Given variables are theoretically italicized, I think I prefer the other method as more parsimonious. Remsense ‥ 论21:18, 28 January 2025 (UTC)[reply]
I strongly prefer nth, not n-th. The OEIS choice is not standard elsewhere and appears to be a hack to allow them to continue to use plain-text ASCII formatting and still distinguish the formula part from the text part. Because we do not limit our content to plain-text ASCII we do not need and should not use this hack. —David Eppstein (talk) 21:03, 28 January 2025 (UTC)[reply]
Understanding perfectly well orthography need not adhere to phonology when semantics is what matters—is it common to pronounce it "n plus first"? Remsense ‥ 论21:59, 28 January 2025 (UTC)[reply]
I'm sure you can hear it pronounced that way but I think it is incorrect. We are using the numerical value of 1 in the expression, not using 1 in the positional sense, so it is "one" not "first", and then the suffix "th" applies to the whole expression. —David Eppstein (talk) 22:00, 28 January 2025 (UTC)[reply]
I don't agree with David about it being incorrect. Both forms are found in the wild, but in my experience "first" is more usual, and I prefer it because it just sounds better. --Trovatore (talk) 22:07, 28 January 2025 (UTC)[reply]
Only until you think about it some more. It is a type error. "First" is grammatically ordinal, but the 1 in the subexpression is not mathematically ordinal. The meaning of the expression is ordinal(plus(n,1)), not plus(n,ordinal(1)). There are natural-language ways of combining ordinals (by which I mean positions, not mathematical ordinals): "second best" or "second from last") but the operation they represent is not quite addition. —David Eppstein (talk) 22:58, 28 January 2025 (UTC)[reply]
I mean, I understand what you're saying. But you could make the same argument about twenty-first. In Italian (for example) you'd say ventunesimo, not *ventiprimo, but in English the suffix "agrees", so to speak, with the last numeral in the expression, which I think makes (n+1)-st or however you want to handle hyphen/superscript/etc more natural for English. --Trovatore (talk) 23:07, 28 January 2025 (UTC)[reply]
I don't think we need any guidance about this in MOS:DASH. We needn't list all the cases where dashes/hyphens aren't used, and I imagine anyone pondering whether to use one would end up at nth, which has an example of correct formatting. pburka (talk) 00:05, 29 January 2025 (UTC)[reply]
Apparently WP:BECONCISE, WP:SUCCINCT redirect to WP:TLDR, a stupid term with bad redirects. One of my professors is on a team editing the world's (maybe formerly) largest science/mathematics book--on abstract algebra--which was 20,000 pages (multi-volume). It was made more efficient (saying more with fewer words) while describing same, so they reduced to maybe 5,000 pages (or in range of 10% to 1/3). Isn't that what conciseness/succintness is, though for most people, still too long to read? Redirects should be to more (less unintellectual) details here (or WP:CONCISE), not a crass Internet meme term mostly used by Millennials, Zoomers who grew up reading few books; there's an article how even freshmen at USA's elite colleges feel they can't read books, because they never got in the habit. I'm not deletionist, but I'd say delete WP:TLDR, because people saying that about one full-length standard (not extended) Twitter/X statement (increasingly common) may not want knowledge.--dchmelik☀️🦉🐝🐍(talk|contrib) 06:18, 9 February 2025 (UTC)[reply]
Yes, well people are throwing many of these around maybe implying they should be followed, and 'WP' could look official. What about the redirects?--dchmelik☀️🦉🐝🐍(talk|contrib)
Yeah but TLDR is an insult. "I didn't read your whole paper, it was [not succinct enough, not concise enough, too prolix, whatever] might sting but is not an insult and is constructive criticism. "Here's your paper back, TLDR" is just dismissive. Herostratus (talk) 01:05, 11 February 2025 (UTC)[reply]
Good; thanks. I don't consider 'TL;DR' an insult, but indeed dismissive, anti-intellectual, and not conducive to discussion: if they won't read what others say, why should anyone read what they say, and why say it at all? It's often a waste of others' time just like many people only replying 'me too' when Eternal September started on Usenet and then early world wide web (WWW) forums--dchmelik☀️🦉🐝🐍(talk|contrib) 18:32, 19 February 2025 (UTC)[reply]
More input wanted at Talk:IMEC regarding the brand's capitalisation
Hi, I would like some more input at Talk:IMEC § Spelling, regarding whether the name should be capitalised in all-upper-case to comply with MOS:TMRULES point number 3, or capitalised in all-lower-case which is the company's official way of writing their name. That point number 3 says, "as long as this is a style already in widespread use", however an issue here is that there are just as many secondary sources that spell the company name as "imec" as there are sources spelling it "IMEC".
There just isn't enough watchers of the article to form a proper consensus, so more opinions from the people who know the MoS well would be appreciated! — AP 499D25(talk)05:07, 15 February 2025 (UTC)[reply]
RfC: Gentilic form of Botswana
How should the gentilic (adjective and noun) form of the country Botswana be written on Wikipedia articles?
A: Botswanan (pl. Botswanans) in all cases, without exception
B: Motswana (pl. Batswana) in all cases, without exception
C: Motswana in articles with strong national ties to Botswana or South Africa, otherwise Botswanan
D: Retain whichever word is used first in the article, either Botswanan or Motswana
Comment: I am opening this RfC because I believe a decision here will affect many articles over Wikipedia. Articles are inconsistent with usage, with many using Botswanan and many using Motswana. There was a previous discussion on the matter, but it went for a week without agreement, so I hope by inviting more people we can come to a conclusion. I am inexperienced when it comes to opening RfCs so I apologize if this was malformed or unnecesary. ―Howard • 🌽3312:09, 15 February 2025 (UTC)[reply]
C: Considering that the Dictionary of South African English lists Motswana but not Botswanan as the gentilic of Botswana and the Historical Dictionary of Botswana (page xiii) uses MoTswana (alternate capitalization), it can be established that common usage within the countries of Botswana and South Africa is Motswana. This word is included in some foreign English dictionaries (OED, CALD) and by the CIA World Factbook, but the OED and CALD do also include Botswanan and two dictionaries (MW, AUH) include Botswanan but not Motswana. Therefore the only resolution, as far as I see it, is to use Motswana as the gentilic in articles with strong national ties to Botswana or South Africa and otherwise using Botswanan. ―Howard • 🌽3312:28, 15 February 2025 (UTC)[reply]
C or D - Per MOS:TIES - however, mention both in the article text at least once. It will be helpful to readers (especially those not from Southern Africa) to explain that people from Botswana are called “Botswanans” externally, but use “Motswana” internally. Once this is explained, the reader will understand whichever usage is used in the rest of the article. Blueboar (talk) 14:08, 15 February 2025 (UTC)[reply]
Gentilic is the proper word for it, no? Otherwise it would have to be something longer like "the adjectival and demonymic form." ―Howard • 🌽3300:44, 16 February 2025 (UTC)[reply]
I think you can just link the term "gentillic" to either the Denonym article or a soft redirect to Wiktionary to help readers, would that help? —Sparkle and Fade (talk • contributions) 01:42, 16 February 2025 (UTC)[reply]
C or D per Blueboar's rationale, it would help readers to explain the above and thus the usage in the article. It may also help to treat the usage similarly to MOS:ENGVAR, retaining it unless there is broad consensus against it, MOS:TIES, etc. —Sparkle and Fade (talk • contributions) 23:47, 15 February 2025 (UTC)[reply]
Didn't we just have this discussion already? Use option A. Use plain English, not terms that are familiar to nearly no one who is not from the area. I would grudgingly accept C as a compromise, but only barely. We need to get away from the idea that, e.g., articles about India are written only for Indians, that articles about Texas are intended specifically for (and to appease the preferences of) Texans, etc. That's not what Wikipedia is about or is for. But C would produce a bit less inconsistency than D (the "do nothing" option), and would impose fewer (than opt. B) instances of unfamiliar terms (arguably non-English at all, using a pluralization scheme that doesn't pertain to this language) on our readers. So C is slightly better than nothing. But A is clearly the proper course of action at this site, even if Motswana/Batswana might make more sense in a blog written in southern Africa with a Batswana audience in mind. This case isn't really any different from Navajo; the fact that their own endonym is Diné, and this term can be found sometimes in English-language sources (mostly specialist or activist literature), does not impose on Wikipedia a requirement to use it broadly (and we have good reasons not to, starting with intelligibility to the average reader). Some occurrence of it will be sensible in an ethnological context, such as the Navajo article itself. But we should not and generally do not use it in more general articles, e.g. on the history of the American Southwest or on the present demographics of New Mexico, Arizona, and Utah. The same logic applies to Botswanan vs. Motswana/Batswana. What next? Shall we start writing about Ireland as Éire and the Irish as Éireannaigh? — SMcCandlish☏ ¢ 😼 02:07, 16 February 2025 (UTC)[reply]
Are you sure that these terms don't just fall under MOS:ENGVAR? I don't think that the concept of it not being Plain English applies here as readers can presumably infer that "Motswana" or "Batswana" refers to "Botswanan" in articles involving Botswana in some way, regardless if readers are familiar with the term. There are some cases where it is inappropriate, such as in articles that only briefly mention Botswanans (e.g."He later met the Motswana president" where this is the only mention of it in the article) and "Botswanan" should be used instead, but most readers can infer the meaning of it as a denonym of Botswana easily. —Sparkle and Fade (talk • contributions) 02:37, 16 February 2025 (UTC)[reply]
Elaborating on this, I don't think the terms differ significantly from English enough to justify using Botswanan in place of it. While foreign-language terms such as "à la" are generally avoided on Wikipedia per Plain English, descriptive terms that do not differ enough from English such as "jeepney" in Philippine English (see Template:Philippine English) seem to be an exception of this, which I believe these terms fall under; but this is ultimately up to an editor's judgement to decide. The question is whether or not these terms are covered by ENGVAR or not. —Sparkle and Fade (talk • contributions) 02:52, 16 February 2025 (UTC)[reply]
I've yet to see any indication this is an obscure word considering the various sources which I have listed above, which come from both in and outside Botswana. Likewise, Google Scholar hits for Botswanan (5,170 results) are not drastically higher than for Motswana (3,050 results). I want to be clear I do not intend on promoting endonyms above exonyms in all cases. But what I do want to ensure is a consistency across all Wikipedia articles while conforming to the correct variety of English. By looking at the vocabularies of South African and Motswana English, I have found that Botswanan is nonstandard and Motswana is the standard and commonly used form. ―Howard • 🌽3322:21, 16 February 2025 (UTC)[reply]
D because RETAIN is a better rule than TIES in general. I understand (and feel) the impulse to avoid weird words that are not understood by most English speakers, but I have to admit that my sense of "weird" here is likely specifically Western; it's not a good look to allow (say) Irish-origin terms (e.g. Taoiseach) but not African. --Trovatore (talk) 23:04, 16 February 2025 (UTC)[reply]
Question: I wasn't familiar with these terms prior to this discussion, but, as a westerner and a native English speaker, I don't find them surprising or difficult to understand. However, I do have some questions about nuance. According to Wiktionary, "Batswana" means "A member of the Tswana tribe of southern Africa, especially an inhabitant of Botswana; a Botswanan". Is it accurate that everyone from Botswana is Matswana, even members of minority ethnic groups? What about inanimate or abstract nouns? Is it correct to write the "Batswana economy" or "Matswana lakes"? pburka (talk) 23:38, 16 February 2025 (UTC)[reply]
Great question! The demonyms for Botswana are:
1. Motswana (singular)
2. Batswana (plural)
For example, 'He is a Motswana' and 'They are Batswana'.
In contrast, Setswana refers to the language spoken in Botswana and can also describe something originating from or related to Botswana, such as 'a Setswana lake' or the 'Setswana economy' it's akin to saying 'the French economy'. However, the use of "Botswana" in this regard is still okay and more widespread e.g., 'the Botswana economy'.
C: In Botswana, as well as in neighbouring countries with shared cultural and linguistic ties, the terms "Motswana" and "Batswana" are the standard and authoritative ways to refer to people from here. We do not use any other terms as they are nonstandard and foreign.
I am inclined to vote in favour of Option C, because of MOS:TIES and for feasability's sake as juxtaposed to, say, options A & B.
I also agree with the thoughtful point raised by @Sparkle & Fade, who rightly notes that readers are unlikely to encounter difficulty understanding these terms to begin with. They do not appear in isolation and are almost always accompanied by contextual clues that make their meaning apparent, even to those unfamiliar with Setswana.
In the same vein, @Trovatore’s observation about the usage of “Irish-origin terms” on the Wiki (such as Taoiseach or Teachta Dála) that may confuse non-Irish speakers is a good one. Unlike such esoteric terms, "Motswana" and "Batswana" fit within a clear linguisti framework that allows for intuitive understanding. Through context, even readers encountering these words for the first time can readily grasp their meaning.
Considering these factors—strong ties to national identity, the ease of comprehension and feasability—Option C stands out as the most fair, logical and respectful choice. Aficionado538 (talk) 02:52, 17 February 2025 (UTC)[reply]
" "Motswana" and "Batswana" fit within a clear linguisti framework that allows for intuitive understanding. Through context, even readers encountering these words for the first time can readily grasp their meaning." Would they, though? If I hadn't come across a discussion about this a few years ago, I would probably see these words and think that someone had vandalized the page in a manner similar to an old children's song ("Billy, Billy, bo-billy / Banana-fana fo-filly / Me my mo milly.") --User:Khajidha (talk) (contributions) 15:26, 26 February 2025 (UTC)[reply]
Yes, readers encountering "Motswana" and "Batswana" for the first time can indeed understand their meanings intuitively.
Even if someone has never seen the terms before, they are almost always introduced in a way that makes their meaning clear. For example, an article or discussion might say, "A Motswana is a citizen of Botswana," or "The Batswana people have a rich cultural heritage." These contextual cues make it pretty much easy to infer that "Motswana" is singular and "Batswana" is plural. Even in languages that don't use prefixes like "Mo-" and "Ba-" for singular and plural distinctions, people naturally pick up on patterns. If "Motswana" or "Batswana" appear a sentence, it doesn’t take much effort to deduce that they follow a singular/plural structure—just as English speakers recognize "goose/geese" despite these being irregular.
English speakers frequently encounter non-English words and intuitively grasp them through context. Consider "alumnus/alumni" from Latin or "samurai" (which remains the same in singular and plural). Even unfamiliar terms like shiitake are understood quickly through how they are used in sentences. Wikipedia consistently uses the term Taoiseach to refer to the head of government of Ireland, despite it being unfamiliar to many English speakers at first glance. While an alternative, more immediately recognizable title such as "Prime Minister" could be used, Wikipedia prioritizes the official terminology used by the country itself. Readers encountering"Taoiseach" for the first time may not immediately grasp its meaning, as it does not resemble any commonly known English words, yet its use remains.
These terms are directly related to Botswana, making them far more intuitive than "Taoiseach". Even if a reader is unfamiliar with them initially, their similarity to the country’s name provides a clear linguistic link, making their meaning easy to deduce. Given that Wikipedia does not replace (for the sake of example) "Taoiseach" with "Prime Minister", there is no justification for replacing "Motswana" and "Batswana" with Botswanan, a term that lacks local legitimacy. If Wikipedia trusts readers to understand "Taoiseach", a term with no obvious cognates, then it should certainly extend the same respect to the authentic demonyms of Botswana.
Oh, and the claim that "Motswana" and "Batswana" might look like random syllables strung together (as in a children’s rhyme) simply overlooks the way humans process language. Vandalism typically consists of outright gibberish without clear meaning, whereas "Motswana" and "Batswana" consistently appear in contexts i.e., in articles with strong national ties to Botswana where their meanings are evident. Unless a reader completely disregards context clues, they are unlikely to mistake these terms for non-sense. Aficionado538 (talk) 16:05, 26 February 2025 (UTC)[reply]
Option C. In articles without strong ties to the country/ies, where the word is presumably not very important to comprehension of the article, we would be confusing more people than we are educating. In articles with strong ties, we want to be correct. --GRuban (talk) 17:19, 24 February 2025 (UTC)[reply]
Meh. We should not use what (in English) amount to regional colloquialisms when they are not intelligible to the majority of our readers; ENGVAR is not license to confuse just to try to make a sociopolitical point. To revisit a point above more clearly: We do not use Diné (outside narrow contexts in the article on the subject) to refer to the Navajo, despite the fact that it's their name in their own language, some of them prefer it in English, and plenty of people in the Four Corners region are aware of it. We don't because hardly anyone else is. These are directly parallel cases. — SMcCandlish☏ ¢ 😼 15:35, 25 February 2025 (UTC)[reply]
You seem to forget that:
these aren't "colloquialisms". These are formal words used in countries to describe people from a country/ethnic group and not some slang terms;
these terms are in fact English terms as said countries have their own form of English i.e., South African English and as pointed out earlier by a user on this RfC, the Dictionary of South African English (as well as other foreign dictionaries) lists Motswana and nothing else as the terminology used;
the point you make about Diné doesn't really hold the same weight with "Motswana" and "Batswana" as the suffix "-tswana" will easily give readers a hint that these are the gentilic terms to refer to citizens of Botswana or people of Tswana ancestry as these words are virtually always used in the context of someone or people from Botswana.
Question (for my own education): is “Motswana” restricted to a particular ethinic group within Botswana… or is it applied to any citizen of that nation. For example, would someone of European ancestry who emigrated to Botswana be a Motswana? Blueboar (talk) 18:12, 26 February 2025 (UTC)[reply]
According to the Historical Dictionary of Botswana and the DSAE, Motswana refers to "a citizen of Botswana," and OED says it can refer to "a native or inhabitant of Botswana." ―Howard • 🌽3318:26, 26 February 2025 (UTC)[reply]
B per MOS:TIES. Botswanan is simply wrong and as jarring to those familiar with the subject as Switzerlandish or Walesian would be. That some sources use the incorrect form merely points up that they do not have a properly constructed MoS like we do, but luckily we have MOS:TIES. We also have many discussions of this over the years at Talk:Botswana and eg at Wikipedia talk:WikiProject Africa/Archive 1#Botswanan. John (talk) 18:49, 26 February 2025 (UTC)[reply]
Why should MOS:TIES be used to justify using Motswana exclusively across all articles? American English dictionaries only include Botswanan (MW, AHD, NOAD) so this appears to be an Engvar issue. The only American English source I could find which recommends Motswana is the CIA World Factbook. ―Howard • 🌽3319:05, 26 February 2025 (UTC)[reply]
When applied to linked titles appearing between <ref>...</ref> tags, title parameters in citation templates, or similar text that is linked, the syntax of the template may be adjusted to {{sic|nolink=y}} (producing [sic] in the resulting linked text).
Should the abovementioned MOS:SIC text not rather be changed to:
When applied to text that is linked, the syntax of the template may be adjusted to {{sic|nolink=y}} (producing [sic] in the resulting linked text; for example in the link: [sic] template).
Can we add Manual of Style: as an alias for the namespace MOS:?
Or more likely the other way around. I do agree a single namespace for all manual of style pages is useful for consistency, searching, etc. It should not just be used for shortcuts but also for actual manual of style pages (and proposals). Aasim (話す) 15:16, 21 February 2025 (UTC)[reply]
Support. The MOS is already gargantuan enough to warrant its own namespace, and sometimes I'm left scratching my head trying to find a particular section that has a WP: shortcut aliased to it instead of an MOS: one. —Tenryuu 🐲 ( 💬 • 📝 ) 19:36, 24 February 2025 (UTC)[reply]
Are we just talking about creating a Manual of Style alias namespace or actually moving the Manual of Style pages into that namespace? I'd support creating that namespace if we are actually moving the pages there. If not, that seems pointless as no one is going to use the longer name over "MOS". Gonnym (talk) 19:49, 24 February 2025 (UTC)[reply]
We can move all MOS pages into their own namespace. It would also help with a lot of manual of style pages that are not part of the formal MoS but are followed by a lot of users anyway. [2] seems like enough to fill a namespace. Aasim (話す) 19:54, 24 February 2025 (UTC)[reply]
This seems unnecessary complexity. There is zero advantage in having yet another namespace alias. Subpages work perfectly and scale nicely even for truly gargantuan things like WP:AN and subpages. If we do not want pages that behave differently, we do not need a new namespace. —Kusma (talk) 20:59, 24 February 2025 (UTC)[reply]
Usage of quote-page paramenter
I strongly support the use of the quote parameter when adding a citation to an article. I recently noticed that some of the citation templates have a field:
|quote-page=
I am intrigued by this option, and thought I would begin using it.
In my typical usage I often cite a single page as support for the claim, so the cited page(s) will be identical to the page number for the quote, but I can imagine a situation where I want to cite a source for the claim as a range of pages, then identify the single specific page for the specific quote.
Rabinowitz, Harold; Vogel, Suzanne (2009). The manual of scientific style: a guide for authors, editors, and researchers (1st ed.). Amsterdam Burlington, MA: Elsevier/Academic Press. p. 363. ISBN 978-0-12-373980-3. p. 363: The primary designation system for bright stars, called Bayer designations… The Greek letters are assigned in order (α,ß,γ,δ etc.) according to brightness.
Simply has "p. 363" in two different places. If I saw this in another article I think it was a malformed citation. I don't know exactly what I was expecting but I thought there would be some indication that one of the page ranges would be related to the overall reference in the other would be related to the specific quote.
I think it's quite strange that Wikipedia has existed for 24 years, yet there still isn't a policy section about this. Input is appreciated. Cheers, Manifestation (talk)19:16, 24 February 2025 (UTC)[reply]
Generally, we avoid having policy restricting editors if we don't have to. On Zhuangzi (book), I have parentheses for the number of each chapter being discussed, etc. etc. This seems totally reasonable and uncontroversial, as do the examples you present. Remsense ‥ 论07:56, 26 February 2025 (UTC)[reply]
RSK language code
Hello, I am not sure if this is the most appropriate place for my question. I noticed that the language code RSK in infobox templates leads to Ruthenian language instead of Pannonian Rusyn language (see Novi Sad for example). Do we maybe have some different language code for Pannonian Rusyn or the fact was simply not updated since the language received it's code recently? MirkoS18 (talk) 11:05, 25 February 2025 (UTC)[reply]
This is determined by the ISO 639 standard.[3] The two relevant codes afaik: Type: language Subtag: rsk Description: Ruthenian Description: Rusnak Added: 2022-02-25
Type: language Subtag: rue Description: Rusyn Added: 2009-07-29
I see! Thanks for clarifying. Maybe we actually need disambiguation page for Ruthenian language page in a sense where it is related to historical/wider language, and the term when it is used to name Pannonian Rusyn. I think the code RSK in fact relates to Pannonian Rusyn and not to the wider concept used in academia. RUE would not be the right choice as it is northern version of the language which is more closely related to Ukrainian.--MirkoS18 (talk) 10:11, 26 February 2025 (UTC)[reply]