Wikipedia talk:Manual of Style/Archive 193

This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Please note that this thread follows on immediately to the OP's prior thread on the same subject, Wikipedia talk:Manual of Style/Archive 191#MOS:NOTUSA. EEng 00:27, 24 May 2017 (UTC)

The exact reason for this policy remains unclear.LakeKayak (talk) 22:16, 23 May 2017 (UTC)

It's a matter of style. I think most style guides (at least the ones I see) advise 'US' or occasionally 'U.S.'. -Sb2001 (talk) 22:27, 23 May 2017 (UTC)

The reason for having a manual style is to create greater consistency and coherence in our work than would happen if we allowed editors to write in whatever style they chose. What is difficult to understand about this? —David Eppstein (talk) 22:32, 23 May 2017 (UTC)

@

WP:ENGVAR says that no spelling is preferred over another. That's what's hard to understand. You are going to be open-minded when it comes to spelling but not an abbreviation?LakeKayak (talk

) 22:35, 23 May 2017 (UTC)

That's a grotesque oversimplification of ENGVAR, which actually says that we *should* use a specific national variety of English spelling on articles associated with that nation, and should stick to a consistent (but unspecified) spelling preference otherwise. —David Eppstein (talk) 23:26, 23 May 2017 (UTC)

• LakeKayak, we're not going to excise something just because you, personally, don't see its justification within 6 hours of posting your query. In fact, MOSUSA is one of the more self-explanatory bits of the guideline. From your edit history it appears you just don't understand what a manual of style is. Please, don't make a Federal case out of this. Every publication has manual of style, and this is Wikipedia's. While exceptions are possible, I've reviewed the conflict you're having and that's not one of them. EEng 23:29, 23 May 2017 (UTC)

@EEng: No ad hominem attacks are allowed.LakeKayak (talk) 23:33, 23 May 2017 (UTC)

Correction: You don't know what a manual of style is, and you don't know what an ad hominem attack is. It looks like you have valuable expertise in a special topic area, and Wikipedia could really use your contributions. Please, be guided by the advice of the several experienced editors who have commented (here or on your talk page) and are unanimous: you're tilting at windmills. Don't waste your time (and -- if that doesn't convince you -- others' time) on something so, so trivial like this.

And since we're on the question, by the OP's logic we shouldn't write UK but rather

UKGBNI all the time (or, at least, leave that up to editors on each article). Absurd. EEng

23:45, 23 May 2017 (UTC)

• Oppose The reason for the policy is crystal clear. One person's
  WP:NOTGETTINGIT is hardly a reason to demote it. I also don't like to think of the edit warring that would ensue if it was demoted. MarnetteD|Talk
  23:52, 23 May 2017 (UTC)

For one, could we avoid straw man arguments? I only want someone to explicitly state why this policy is in effect. Not why we have a manual of style. And also the difference between whether UKGBNI and whether or not USA should be allowed is that USA is in common use. I have never seen UKGBNI in use at all.LakeKayak (talk) 00:12, 24 May 2017 (UTC)

There's something very unpleasant about your demand that everyone else drop everything to satisfy your curiosity. You go search the 200 pages of WPT:MOS archives, analyze the discussions there, and then, if you have something new to offer, come back here. Or you could just go back to improving articles. EEng 00:31, 24 May 2017 (UTC)

This page has seen plenty of silly arguments but fortunately this one can be ignored. As has been explained, one person not understanding something does not mean that everyone else has to fall in line. The current MOS:NOTUSA is fine. Johnuniq (talk) 03:46, 24 May 2017 (UTC)

@Johnuniq: Then can you explain why that specific policy is in effect? I am still waiting for an answer.LakeKayak (talk) 16:49, 24 May 2017 (UTC)

What part of There's something very unpleasant about your demand that everyone else drop everything to satisfy your curiosity. You go search the 200 pages of WPT:MOS archives did you not understand? EEng 18:46, 24 May 2017 (UTC)

• Oppose IDONTLIKEIT is no argument. Andy Dingley (talk) 17:02, 24 May 2017 (UTC)
• Oppose I too have never seen a crystal clear argument for US rather than USA: however consistency of style is important, even if the choice were arbitrary.
  • It has been noted that "USA" is the United States Army.
  • It has been said that US is more popular in the um.. US, than USA.
  • US is shorter.
  • A search of the archives will reveal many additional arguments on both sides, but the guideline hasn't been overturned on over a decade.

All the best: Rich Farmbrough, 18:32, 24 May 2017 (UTC).

@Rich Farmbrough: Thank you. That was the argument I was looking for.LakeKayak (talk) 19:49, 24 May 2017 (UTC)

For the record, that's not the "the reason" the guideline is what it is -- it's just Rich's guesses as to the reasons. What we're trying to get you to understand is that the reasons for many of these arbitrary decisions are lost to history. Only searching the archives will tell (and often not even then). EEng 21:36, 24 May 2017 (UTC)

The short version is that "USA" is disused in high-quality publications, and the style guides MoS is largely based on recommend against it.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:07, 2 June 2017 (UTC)

• Oppose - There is no country "United States of America"; its name is "United States" and there's no sense in putting an extra letter on the acronym. I also feel there are tone issues: for Wikipedia's voice, US is more formal and professional than USA. Reidgreg (talk) 16:07, 2 June 2017 (UTC)
  • Comment That is factually incorrect. The full name of the country is "the United States of America". It's is stated as such in the constitution. And on every piece of currency produced in the country. The short form "United States" is widely used, especially in international contexts, but the full name remains "United States of America". oknazevad (talk) 00:46, 3 June 2017 (UTC)
    • Retracted. I guess I never got past the first line of the constitution, though after checking a transcript at archives.gov I notice that it has United States of America 3 times and United States alone 51 times. Then again, how often does one hear United States of Mexico/United Mexican States/Estados Unidos Mexicanos. Reidgreg (talk) 10:47, 3 June 2017 (UTC)
• Oppose demotion and Support US over yoo dot es dot. d.g. L3X1 (distænt write) )evidence( 02:07, 26 June 2017 (UTC)

If we were to change any advice relating to this at all, it would be to deprecate "U.S." in favor of "US". Several years ago here I presented evidence of a declining use of the dots, and this decline has increased since then. That style is also used very inconsistently when used at all: Some publishers use it only in headlines, not in regular prose; some never; some always; and many leave it up to individual writers/editors and are not consistent about it across their publication. The only real rationale for it is that "US" and "us" are hard to distinguish in all-caps headlines. WP does not use all-caps, so we have no reason to use "U.S.", when we avoid the periods/stops in all other acronyms and initialisms. Use of the dots version frequently produces inconsistent results in our prose, e.g. "a summit attended by representatives of France, the U.S., and the UK".  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:07, 2 June 2017 (UTC)

• Support US over U.S. – Reidgreg (talk) 16:07, 2 June 2017 (UTC)
• Support: I certainly agree. Although 'we avoid the periods/stops in all other acronyms and initialisms' is not true - some editors demand the full stops in eg, ie and etc. In fact, you said specifically WP should 'definitely keep the periods/dots/stops, whatever you like to call them', describing the practice as 'lazy and sloppy'. -Sb2001 (talk) 00:23, 3 June 2017 (UTC)
  • I've addressed your side complaint in a separate sub-thread below; you're talking about a different class of objects in the language (and etc. is a contraction).  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  22:42, 6 June 2017 (UTC)
• Oppose all changes No reason to drop the current guideline, nor to depreciate the dotted form, as the latter remains common enough in outside writing. oknazevad (talk) 00:46, 3 June 2017 (UTC)
  • All kinds of inconsistent stuff remains "common" and we don't use it here.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  17:22, 6 June 2017 (UTC)
• Note This wasn't meant to be a !voting proposal. Rather, I'm suggesting that the matter should be re-examined again with 2017 research, and be an RfC. Given some of the emotionality attached to U.S., I would suggest RfCing this at
  MOS:JR debate about "Xerxes Y. Zounds Jr." versus "Xerxes Y. Zounds, Jr.," style.  — SMcCandlish ☺ ☏ ¢
   ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  22:42, 6 June 2017 (UTC)
• Support changing "U.S." to simply "US". Having both permissible doesn't seem useful to me. If all it requires is that a given article maintain consistency within it; any editor could just change all the US's to "U.S." in a given article or vice versa, simply based on one's individual attachment to either. A potential
  WP:EDITWAR or quarrel all over nothing really. Its those small "pet peeves" that tend to get people to make changes; which is why I appreciate that wikipedia has set outlines for the British vs American English spelling debate, instead of allowing a "free for fall" with the disclaimer that there be "consistency" within the article. Well, who decides which article gets to maintain all "US" and which ones "U.S."? DA1 (talk
  ) 06:38, 10 June 2017 (UTC)

"British vs English"! Perhaps you mean "British English vs US English". :-) Martin of Sheffield (talk) 10:46, 10 June 2017 (UTC)

@Martin of Sheffield: Yes! I mean't to say "British vs American English spelling", must have been a typo. DA1 (talk) 19:42, 11 June 2017 (UTC)

• Support US over U.S. – The dots are archaic, vestigial leftovers from generations ago when acronyms and initialisms were uncommon in print and conversation. The inconsistent use between articles, and often within a single article, is inconsistent and unencyclopedic. Also, as others have pointed out: we don't afford the same treatment to the UK, NZ and SA. — GS ⋙ ☎ 07:51, 14 June 2017 (UTC)

"generations ago" - stop and think before going off in hyperbole please. I'm not yet of pensionable age and was certainly taught to use full stops in abbreviations. You assertion about other countries is also questionable. Call then "us", "uck", "nuz" and "sar" if you want, that is consistent, but historically they were "U.K.", "N.Z." and "S.A.". Martin of Sheffield (talk) 10:47, 14 June 2017 (UTC)

User:Martin of Sheffield: the important word there is 'historically'. In education more recently (ie the last 10-15 years at least), you have been taught to omit the points from initialisms (and - for that matter - other abbreviations (although somewhat more leniently)). Please stop with this way of thinking that we should stick to what people did however many years ago. It is 2017. I change my language to get with this fact (accepting '4:30pm' instead of '4.30pm', and writing 'v' instead of 'vs' are just two examples). I think everyone on WP should. -Sb2001 (talk) 16:30, 14 June 2017 (UTC)

Sb2001, I think you are mixing up a number of issues here. GrapefruitSculpin was being downright offensive by implying anyone over 50 was archaic from generations ago. Probably thoughtless ignorance, but offensive nevertheless. I didn't actually state whether dots should or should not be used, only that the usage is consistent. As you observed I did use the word "historically". I suggest you read Orwell's 1984. Telling people to stop thinking in ways you don't like and seeking to change the language to cover it up is not a new idea. Anyhow, before you or I say something we (or the admins) regret I suggest this subthread is closed. Martin of Sheffield (talk) 17:12, 14 June 2017 (UTC)

User:Martin of Sheffield: I don't like to make a habit of saying regrettable things. Anyway, I have read Nineteen Eighty-Four - an excellent novel. Comparing me to BB is perhaps a little extreme. My previous comment actually stated that I was the one changing my views. The example I gave re time notation is an example of my open-mindedness (although I would never employ the colon myself), and the versus example shows where I have changed my opinion completely. Unfortunately the MoS is effectively an opinionated instruction book. Unless something is actually wrong, what it says should be effected, and reflect one view of language. There will always be people who disagree. Believe me, there is plenty about it I do not like. And I must note, I cannot see what is offensive about Grapefruit's comments. The hyperbole 'archaic' is just used for effect. I interpret 'generations ago' to mean around thirty of forty years. -Sb2001 (talk) 18:27, 14 June 2017 (UTC)

@

• Strongly oppose all changes: The USA is either the United States Army or the Union of South Africa. As for the dots, just use them in US-Eng articles and omit them in UK-Eng ones. – Illegitimate Barrister (talk • contribs), 02:42, 16 June 2017 (UTC)
• Oppose all (with fire) – "USA" is just clumsy, and "U.S." is properly abbreviated "U.S." Both
  MOS:U.S. should be left as is. --IJBall (contribs • talk
  ) 19:19, 23 June 2017 (UTC)
• Strongly oppose removing the guideline. The current guideline is useful and correct. It should be kept. However, I support deprecating the use of U.S., and changing it to US in all articles. LK (talk) 19:34, 23 June 2017 (UTC)
• Example: United Kingdom–United States relations is a good case study in why to get rid of "U.S." on Wikipedia. Otherwise-sensible editors will freely mix "U.S." and "UK" in the same article.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  07:58, 11 July 2017 (UTC)

USA in sports results

While this is up for discussion, I've been having concerns regarding sports results. There's an exception in the guideline for FIFA codes, and I understand that if the article is actually discussing the FIFA codes themselves. However, I see USA being frequently used in tables giving results of international athletic competitions, where it seems to me that US should be used. (Results are given by country, not team name, so it isn't referring to Team USA. Wikipedia prefers US, so it shouldn't matter if results are reported in sources as USA.) It's possible this might be the result of local consensus among sports editors, but I haven't found any record of discussion on talk page archives. I've also been wondering about the validity of USA being output from some of the {{flag}} templates. I'd appreciate any clarification, especially if anyone is aware of past discussion on this. – Reidgreg (talk) 16:07, 2 June 2017 (UTC)

The IOC and it's sport-specific member associations also use "USA", as, again, the full name of the country is "the United States of America". oknazevad (talk) 00:46, 3 June 2017 (UTC)

Right. We should use "USA" as a code used by a sports federation (or other entity with a three-letter country code system with "USA" for that country), when a table or list is using those codes, but not use "USA" otherwise.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  17:22, 6 June 2017 (UTC)

As already mentioned more than once, the official name of the country is "the United States of America". That's in the Constitution, which is sufficient, but also in ISO 3166-1, which has 2-letter country code US and 3-letter country code USA. Therefore, USA is a valid code or initialism in any context. — Stanning (talk) 21:04, 6 June 2017 (UTC)

Consensus for years and years here disagrees with this interpretation. The official name of

WGaF? WP has no policy that we use ISO country codes, so WGaF? All we do with them in any reader-facing manner is provide them as details in the infobox on the country. The ISO rationale is bogus for other reasons; many of the ISO codes are based on French not English names, and several are just made-up character strings that don't correspond to anything. We do not use them as abbreviations in encyclopedic text.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:01, 6 June 2017 (UTC)

So USA should be used as a code when using those codes? I get what you're saying, but it sounds a bit circular, and the

MOS:USA wording could be improved from "in certain technical/formal uses". Is there another section of the MOS which discusses use of those codes, to which the reader could be directed? It still seems problematic to me, that use of USA in tables could easily leak into the prose. FIFA World Cup uses USA throughout the prose (and, somewhat ironically in terms of this discussion, uses "United States" and other common country names rather than FIFA codes in the numerous tables). – Reidgreg (talk

) 15:29, 12 June 2017 (UTC)

• I much prefer "US"—no dots, no olde-worlde "USA". So does usage outside the US; and increasinly Americans prefer it, although it's baked into so many organisational titles, sadly. But IMO neither version should be banned: just article consistency (with exceptions for titles, refs, and quotes, of course). Tony (talk) 13:20, 7 July 2017 (UTC)

US, UK, NATO acronyms versus etc., i.e., e.g. abbreviations

Moved to

Wikipedia talk:Manual of Style/Biographies

"Sir" is an honorific prefix, not a forename. As such, it belongs in the honorific prefix section of an infobox, not immediately precedent to and on the same line as the article subject's name. It functions exactly as other honorific prefixes — "Mr", "Mrs", "Ms", "Dr", "Rev.", and so on.

--Vabadus91 (talk) 00:37, 11 July 2017 (UTC)

Yes, but why state that here? This is already covered at

MOS:BIO.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:32, 11 July 2017 (UTC)

"Sir" is exceptional in that Sirs are called "Sir" at Deaths in 20xx articles when they die, no matter their article name. I tried to argue they should be treated like a Doctor or Reverend, but was utterly destroyed. Perhaps this means the normal rules also don't apply to them in infoboxes (and elsewhere). InedibleHulk (talk) 05:00, 12 July 2017 (UTC)

• @
  WT:MOSBIO. — Stanning (talk
  ) 09:35, 12 July 2017 (UTC)

@Stanning: With respect, I still disagree. Honorific prefixes vs honorific titles are a semantic distinction without a difference. Generally, both are simply called "honorifics" in English (see Wikipedia's own page on English honorifics). Mr, Mrs, and Ms are in fact titles, just as Dr, Rev'd, and Sir are. The most accurate term for all of them is "pre-nominal honorific" (it might be an idea for honorific prefix to be changed to pre-nominal honorific for infoboxes). Even if there were a meaningful difference (the only difference is what the title signifies — marital status, knighthood, academic achievement, etc. — not its linguistic categorisation as a pre-nominal honorific in all cases), Sir remains an honorific of some kind, so wherever it belongs, it isn't as part of a name as though it were a forename.

I have posted this here because here is where I was directed following a previous disagreement over an edit.

Vabadus91 (talk) 14:25, 12 July 2017 (UTC)

@

MOS:HONORIFIC says honorific prefixes vs honorific titles is a distinction with a difference! Either comply with it or, since you don't agree with it, propose a change on the relevant talk page. — Stanning (talk

) 14:48, 12 July 2017 (UTC)

@Stanning: And I shall do exactly that. Thank you for the discussion.

Vabadus91 (talk) 22:36, 12 July 2017 (UTC)

Is this an ENGVAR issue? Specifically, Thronecast is a British programme discussing an American programme, and each "series" of the former coincides with a "season" on the latter.

I think For the third series [of Thronecast], Thronecast became a 15-minute on-air show that [followed] each episode of the third season [of Game of Thrones] looks particularly weird, because if the British terminology was changed to American or vice versa, it would read like the third series was the same thing as the third season; it appears that the different terms are being used to disambiguate inline.

I'm actually not sure if this is a problem, though, as I have heard Americans (specifically Chuck Sonnenburg) use the word "series" when describing British shows like Red Dwarf and Doctor Who, which leads me to believe that the "terminology" is mutually intelligible, but it still seems weird...

Hijiri 88 (聖やや) 01:07, 13 July 2017 (UTC)

I don't think there can be much of a case for mixing the terms. They are both television shows (programs) and using different terms creates an impression of a substantive difference. In your specific case, the article is about a British show so BrEng seems obvious (to me). Primergrey (talk) 04:44, 13 July 2017 (UTC)

Agreed. They're synonyms in this context; as long as it's clear that "series" here means "series of episodes presented during a broadcasting season" not "entire TV show", use "series" consistently. By way of direct comparison, an article on autos (cars) would not compare the "boot" size of a BMW four-door sedan to the "trunk" size of comparable type of American-manufacturer car, much less in the same sentence.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:14, 13 July 2017 (UTC)

I'm not sure this is really significant enough, but I can't think where would be better to ask. Periodically I see articles which say "Fred McSubject is a

There are two issues here.

1. The attempt by the Roman Catholic Church to appropriate the term "Catholic" is deeply offensive to some other Christians. It's a biassed claim to universality. As an Anglican, I consider myself a member of the "holy Catholic Church" as per the creed I say weekly. Wikipedia should be neutral as to claims of being "the" Catholic Church, just as it should be when some branches of Islam claim that other branches cannot be called Islamic. The correct neutral description is "Roman Catholic".
2. Even within its own usage, "Roman Catholic" is not the same as "Catholic". There are non-Roman churches recognized by the Roman Catholic Church as "Catholic", such as the Eastern Catholic Churches. An example of the confusion that comes from eliding usage is in the statement at the head of that article: This article is about Eastern churches in full communion with the Catholic Church The Eastern churches that are in full communion with the Roman Catholic Church form part of what they call the "Catholic Church"; to say they are in communion with the "Catholic Church" is to say they are in communion with themselves.

So, no, "Catholic" is not the same as "Roman Catholic". Peter coxhead (talk) 17:49, 10 July 2017 (UTC)

If I remember correctly from my GCSE RS, you can have Catholic Christianity, but not Roman Catholic Christianity. Roman Catholicism exists as something else. So it is almost like they are entirely separate ideas/belief systems. –Sb2001 ^{talk page} 18:02, 10 July 2017 (UTC)

Agreed with these comments; the distinction is encyclopedically important. Lots of "how people say stuff in daily life" matters are not how we write at Wikipedia, usually for similar precision, disambiguation, and other clarity reasons.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  19:11, 10 July 2017 (UTC)

I'm afraid I don't quite agree with the replies above. The salient point about the "attempt by the Roman Catholic Church to appropriate the term "Catholic"" is that it has been entirely successful. In every context save discussion about flavours of Christianity, "Catholic" is clearly and unambiguously understood to mean Roman Catholic. It has been for hundreds of years (eg Pepys and his contemporaries write about "Catholiques", when they don't write about "Papists") and it is today.

There's no issue of precision or clarity. If you read "X is a Catholic" there is no actual doubt as to what is meant. Wikipedia is already littered with unqualified "Catholics" none of which produces the slightest confusion in the reader. Pinkbeast (talk) 14:18, 12 July 2017 (UTC)

Nonsense. There are many churches which use "Catholic" in their names. And I have been to enough funerals to know that the Roman Catholic Church itself often refers to itself that way ("Roman Catholic"), as shown by the use of that term in hymnals and prayer books.

Kablammo (talk

) 20:18, 12 July 2017 (UTC)

And in response to a comment further up: The Roman Catholic Church is a Christian church, full stop.

Kablammo (talk

) 20:25, 12 July 2017 (UTC)

Agree with Peter. "Roman Catholic" is a member of the group "catholic", so the two are not interchangeable in an encyclopaedia. This is complicated, though, by the existence of our article Catholic Church. Now there's a can of worms (or is it "diet"?). Still, I don't see that it's necessary to address that in order to do this in the right way. Formerip (talk) 20:59, 12 July 2017 (UTC)

One of many articles which use an unqualified "Catholic" without producing any confusion whatsoever. Pinkbeast (talk) 13:08, 13 July 2017 (UTC)

If there is more than one catholic church, and we have an article with that title dealing with only one of them. then that's potentially confusing. Formerip (talk) 01:50, 14 July 2017 (UTC)

The Vatican itself uses "Roman Catholic".[2]

Of course "Roman Catholic" is itself correct. My argument is that one word in it is unnecessary. Pinkbeast (talk) 13:08, 13 July 2017 (UTC)

[3] [4]

This -- the use of "Louis' father", etc. in the

Thoughts?

Hijiri 88 (聖やや) 08:33, 12 July 2017 (UTC)

Nice one. Basically, of course, follow

MOS:POSS which says to follow the pronunciation. In the case of Louis, I guess it depends whether you pronounce the name with a silent s as in French and as in British English, or whether you pronounce it "Lewis" as in American English (don't know how it's pronounced in other flavours of English). In British English the possessive form of Louis is pronounced with only one s, not two as in Morris's or Lewis's, certainly when the Louis in question is French, so when writing British English I'd write Louis' as I think most Brits do, although some British writers have used Louis's. I'd suggest that any article where the question arises should specify its flavour of English (with {{Use X English}}) and use the approproiate possessive for that flavour. — Stanning (talk

) 10:16, 12 July 2017 (UTC)

@Stanning: My experience of American English is somewhat biased in this case, since I grew up in Ireland learning French since primary school (my mother was also a French teacher), and so when I heard "incorrect" pronunciations of French names my mind might have just zoned them out, but... do Americans actually pronounce the king's name as "Lewis"? The only American source I can think of off the top of my head is two lines spoken by David Hyde Pierce in episodes (2:17 and 4:22) of the sitcom Frasier, and he didn't pronounce the s, which leads me to believe that if it had been possessive he would have pronounce it with an additional /ᵻz/ at the end. Hijiri 88 (聖やや) 08:11, 13 July 2017 (UTC)

@

MOS:POSS does cover the case of a silent s implicitly, where it gives the example Descartes's philosophy, and indeed a silent x in Verreaux's eagle (though it's not clear from the context how the writer expects Descartes or Verreaux to be pronounced). Following those examples, Louis's is correct in Wikipedia. MOS:POSS does perhaps need a clarification, though. — Stanning (talk

) 10:20, 13 July 2017 (UTC)

We borrowed that directly from New Hart's Rules and Chicago Manual of Style, the main sources of inspiration (and of specifics) for MoS. Since there's not a different rule for silent-s/x/z, there isn't any need to say anything about the matter. Those paper style guides include a separate segment on it because they're huge and attempt to be comprehensive (perhaps to a fault), and because some guides (including CMoS) have historically had different rules for silent-s/x/z (which is why anyone even asks about it). We're trying to keep MoS short, at least on the main page (there's really no way to make

MOS:NUM short!), so the examples illustrating the silent-s/x endings are sufficient.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:27, 14 July 2017 (UTC)

In American English, it is pronounced both ways. I think the pronunciation that should be considered is the French one with the silent 's', so Louis's should be used. AHeneen (talk) 15:17, 13 July 2017 (UTC)

I agree, at least for the name of the king. In case you're interested, there is further discussion at Apostrophe#Possessive apostrophe.  – Corinne (talk) 15:41, 13 July 2017 (UTC)

• Louis pronounced /LOO-iss/, and French /Loo-EE/ are two different names with the same spelling (the formerly clearly being an Anglicization of the latter, influenced by Lewis). In the Southwest and other areas with a lot of Spanish-speakers, we're also familiar with Spanish Luis, /Loo-EES/. (No, I'm not going to IPA all that; too much hassle.) The name Louie, pron. /LOO-ee/, is a diminutive of the /LOO-iss/ version of Louis, though many mispronounce the French name this way. As an American, I've never heard an American (or anyone else) above an elementary-school education level refer to any "King /LOO-iss/ of France", except in jest.

  The usual pronunciations, English-wide, of Louis in reference to a French monarch, are /Loo-EE/ or /LOO-ee/ depending on French familiarity. The possessive is Louis's, here and in most other styles. (Chicago Manual of Style tried switching to Louis' in the 15th ed. for unknown reasons, and after getting slammed for it, switched back in the 16th and current edition, with an almost apologetic note.) Other major, modern style guides back this, including New Hart's.

  But there's no WP-related rationale to use Louis' in the possessive of St. Louis - /LOO-iss/ – Missouri, either, or similar constructions like Kanasas's, Marx's, showbiz's. The various and contradictory "punctuate based on the sound of the word/name where you grew up" approaches are a [bad] joke, abandoned by more style guides as time goes on. It's untenable except in local-to-regional publishing, because pronunciations change from area to area, and there is a lot of dialectal variation in the UK, US, Canada, Ireland, etc.

  I firmly predict that the "huge pile of style guides" sourcing run I've started will show that there's an overall preference in academic and general-audience guides for "Jones's" style as a consistent approach to all the "what if it ends with ...?" questions; that in journalism, marketing, and business stylesheets there's a preference for "Jones'" as yet another typical, niggling big of compression for its own sake from that sector; and that newer works are less apt to try to justify complicated exceptions. MoS almost always lands on the academic-through-general side of this broad rift in English style. I'm doing the source research mainly for

  WP:CREEP stuff we avoid here). Fowler's is even worse for our purposes in this regard; but both mostly treat their declared exceptions as optional. CMoS no longer goes there at all; since 2010, it sticks with apostrophe-s, including for Jesus's and Camus's, and explicitly declares in two places that it is overruling previous editions on these matters, for increased consistency and logic. Plus ça change ...
   — SMcCandlish ☺ ☏ ¢
   ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:27, 14 July 2017 (UTC)

Lower-case as adjectives, both words refer to technologies (protocols, standards, applications, etc.) that can be used for intranets as well as the Internet. These are thus properly lower-cased most of the time; it is hard to think of any such technology that cannot be used for an intranet. Both can also be capitalized as adjectives when used to refer specifically to the Internet or the Web ("he had no Internet access while on the island").
 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:31, 11 July 2017 (UTC)

You probably know we have

Capitalization of "Internet". I recently said the above on its talk but I have a feeling there is an enwiki recommendation to use lowercase per everyone does it. Johnuniq (talk

) 04:27, 12 July 2017 (UTC)

Everyone's been wrong before. I recommend caps. InedibleHulk (talk) 04:54, 12 July 2017 (UTC)

If you recommend caps then I suggest hatting this discussion. EEng 05:03, 12 July 2017 (UTC) That's a joke.

I almost toque it seriously. InedibleHulk (talk) 05:18, 12 July 2017 (UTC)

Well played. You are cordially invited to join my glittering salon of talk page stalkers. EEng 05:48, 12 July 2017 (UTC)

(talk page stalker) Sometimes the only thing on EEng's mind is a hat. ^{Atsme📞📧} 12:26, 13 July 2017 (UTC)

Ya'll are brimming with humor. Now off to EEng's talk page if you want to continue this. --Izno (talk) 12:33, 13 July 2017 (UTC)

"Everyone's been wrong before" indeed, and "everyone" doesn't write the internet; it's something news journalists do (only for about the last ten years, and not universally – New York Times didn't make the switch until 2014), and something that (non-tech-industry) people writing business memos do, and something that people who send "hi jane, CU at 7" in SMS messages do. People in tech professions know better, and care. Just like doctors know and care about the difference between a canker sore (a bacterial lesion from biting the inside of your lip or cheek) and a chancre sore (a viral lesion caused by a sexually transmitted disease). In both cases, they sound the same, are hard to distinguish for the non-expert, and have a similar linguistic origin, but a provably different meaning. To the average schmoe, both sores are a similar "ouch, this hurts" thing that is alarming but not life-threatening. To the average schmoe, an internet[work] and the Internet are "ooh, I can get my computer to do something, if I'm lucky, and it will probably be in a browser or a web app" things, that work in ways they don't understand and can't tell apart.

But the "distinction" argument isn't even necessary; "the Internet" is a proper name/proper noun in both the philosophy and linguistic senses, so it's capitalized per our style guide (which is not NYT's or The Guardian's), no different from the Pacific Coast Highway and the International Space Station – unique, monolithic human creations. I chose these examples carefully, because there's more than one major thoroughfare on the US Pacific Coast and more than one orbital habitat/lab created through multinational cooperation. "A Pacific Coast highway" and "an international space station" are valid expressions, referring to real categorizations, just like "an internet" (or internetwork or WAN). The PCH, the ISS, and the Internet all are the most notable but not exclusives entries in their respective categories.
 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:01, 14 July 2017 (UTC)

Hello, as I think I might be interpreting

@Anakimi: Not a robust approach. Output is going to be highly variable by device and browser, and I suspect the results are going to be negative on mobile. In Chrome on MacOS with a big monitor, I see a pointless vertical scroll bar appearing and that is all. At any window width, the vert. scroller remains. If I markedly reduce window width, I start getting a horizontal scroller, but only briefly, when the field images are inlined with text between the Di Stéfano and Amarmo images. If I make it smaller still, the field images all snap to below the two player pictures, and the horiz. scroll goes away. At a very narrow width I get the horiz. scroller back, only when the viewport is finally too small to hold the field images on one line. Which of course raises the question: Why are you trying to force them all to be on one line? It would be a more usable and accessible approach to just let them flow naturally, and appear on two or more lines as needed (especially on mobile browsers). It's said that ~60% of our users are on mobile devices now (of which probably 4/5 are phones and phablets).

See Real_Madrid_C.F./sandbox for a robust approach that should work regardless of OS and browser. On a big monitor, the images are all on one line. They'll auto wrap and re-center as needed on smaller devices, the way <gallery>...</gallery> works. I've applied this fix to both sets of field (pitch) layouts, and to the uniform (home kit) material. The CSS can be put into templates; you need a wrapper div with text-align: center; created that as {{Gallery layout}}, since this isn't really footy-specific. The image templates themselves can be edited to have a parameter to use display: inline-block for such layouts. That would probably save time in implementing this solution on other articles. PS: I also fixed a typo and an venue infobox parameter error.
 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  22:29, 9 July 2017 (UTC)

That was very helpful! Thank you very much! — Anakimi_talk   02:25, 10 July 2017 (UTC)

@Anakimi: You're welcome. If you need help integrating the display: inline-block into templates, let me know. It should work regardless what the surrounding element of the template is, so for some templates it can just be passed in a |style= or |css= parameter to a parent template. For templates that aren't meta-templated, the template's own code may need to be changed to be wrapped in a <span>...</span> or <div>...</div> to which this CSS is applied when requested, e.g. by a |gallery=y being passed to the template.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  19:14, 10 July 2017 (UTC)

Update: Manual CSS no longer needed, due to {{Gallery layout content}}.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  02:48, 16 July 2017 (UTC)

There's an editor at

Ha! As it happens, I've got a Museum on that very subject! EEng 05:50, 16 July 2017 (UTC)

That's perfect, and the AP one I could find agrees too, but we don't list that here at MOS, hence why we might want to 1) make sure we agree that this is right, and 2) add that style to be clear to the MOS. --MASEM (t) 06:02, 16 July 2017 (UTC)

It's not a big deal, but I'm wondering about the logic of excluding from italics the bit that changes the grammatical function of a titular item. In languages that signal some of their grammatical changes by morphology, I'm pretty sure they include the pre- or post- addition in italics. And what about that in English? "How many Futuramas are there? Just one. Tony (talk) 06:11, 16 July 2017 (UTC)

a titular item: Tony, you're not channeling Neelix, are you?^[FBDB] EEng 10:18, 16 July 2017 (UTC)

Presently we have text in

Regardless, this section should probably also be moved to

Is it true to say that most academic reference styles don't use Vol and No at all any more, but just use the order of the two numbers, typically separated by a colon or comma, to denote those? Just sayin'. Martinevans123 (talk) 22:16, 4 July 2017 (UTC)

Sure, and our citation templates also do this, but this has nothing to do with usage in prose. We should not be advocating overcapitalization of abbreviations of non-proper nouns. It's just baseless and without any apparent precedent. What I think has happened here is that someone was thinking of how something like this is presented in subtitle style on a book cover or frontispiece ("My Adventures with in Elbonia, Vol. II") and has overgeneralized.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  01:42, 5 July 2017 (UTC)

I would always favour 'No' and 'Vol'. Caps seems to be well-established, and recommended by most style guides I see. I am not sure of the reasoning, though. Maybe it has something to do with their origins in titles. There is possibly an argument for dropping them (as well as the full stops!).-Sb2001 (talk) 22:22, 4 July 2017 (UTC)

I would tend to agree. If we have to use those abbreviations, I think they should be capitalised. Would also be happy to lose the full stops. Martinevans123 (talk) 22:30, 4 July 2017 (UTC)

Fullstops are grammatically correct for abbreviations, and are especially useful when as in this case the abbreviations could easily be mistaken for words.--JohnBlackburne^words_deeds 23:42, 4 July 2017 (UTC)

JohnBlackburne: Americans seem to dot everything in sight, though there's a glacial move toward easing up on that count. Outside North America, it is usual to dot an abbreviation that doesn't end with the last letter of the expanded version, but not otherwise ("St", "Dr"). Acronyms and initialisms are now not normally dotted. I think "No." and "Vol." should be dotted in references; but conventional "22(3)" is fine if consistently used in a reference list. Tony (talk) 06:04, 6 July 2017 (UTC)

• LowercaseWhat David Eppstein and Trappist said (below). And I'm all for moving as much detail from main MOS into subsidiary pages; the main MOS is grossly bloated for what ought to be its function, which is to give the high points for a newcomer who cares, but doesn't care that much. EEng 23:49, 4 July 2017 (UTC)
• Lowercase: As the first sentence of
  MOS:NUM. —BarrelProof (talk
  ) 23:52, 4 July 2017 (UTC)
• Mixed. Capitalized when it is in the middle of a title-case title: "The Art of Computer Programming, Vol. III: Sorting and Searching", or when it's after a full stop (as used to separate things in Citation Style 1, except that CS1 doesn't use the Vol. abbreviation). Lowercase in other situations, including in the example sentence at the start of this discussion section. —David Eppstein (talk) 00:13, 5 July 2017 (UTC)

  cs1: {{cite magazine |title=Title |magazine=Magazine |volume=75 |issue=11}}

  "Title". Magazine. Vol. 75, no. 11.

  lower case numero because there isn't a terminal stop after volume number.

  cs2: {{citation |title=Title |magazine=Magazine |volume=75 |issue=11}}

  "Title", Magazine, vol. 75, no. 11

  —Trappist the monk (talk) 00:35, 5 July 2017 (UTC)

Agreed it can be capitalized when used in a subtitle like "Vol. III: Sorting and Searching"; that's already covered by

MOS:TITLES at least in theory if not in specifics. No objection to explicitly clarifying that.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  01:42, 5 July 2017 (UTC)

If the idea is to follow a full stop with an uppercase letter, doesn't that cs1 example break down a bit when "{{cite magazine |title=Title |magazine=Magazine |volume=75 |issue=11 |page=93}}" becomes ""Title". Magazine. Vol. 75, no. 11. p. 93."? —BarrelProof (talk) 02:30, 5 July 2017 (UTC)

MOS and MOSNUM cover the body of the article, infoboxes, etc. If you want to discuss citations, please discuss at

Help talk:Citation style 1. Jc3s5h (talk

) 04:45, 5 July 2017 (UTC)

How does the example break down? We would expect "... blah blah blah. Vol. 1, blah blah blah ..." to have "Vol." because it follows "." as terminal punctuation.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  04:24, 6 July 2017 (UTC)

• Grammar point The phrases "Volume 3" or "Page 74" are proper noun phrases in English – for example, they cannot be preceded by a determiner (you say Look at Volume 3 not Look at the volume 3). The equivalent common noun phrase uses the ordinal (Look at the third volume). Traditionally, proper noun phrases are capitalized, although the modern trend seems to be to de-capitalize almost everything except proper nouns and noun phrases used purely as labels rather than for any descriptive element. Peter coxhead (talk) 06:36, 5 July 2017 (UTC)
  • Does that point apply if we have abbreviations? And to my eye Page 74 looks stranger than Volume 3. But that's just my unsourced subjective UK opinion, of course. Martinevans123 (talk) 07:37, 5 July 2017 (UTC)

@Martinevans123: it may be an age thing (I'm British too). I was only making a grammar point. There's never been a 1:1 relationship between being grammatically a proper noun or noun phrase and being capitalized. Once there was much more capitalization (see e.g. the 1662 Prayer Book); then there was a trend to capitalize only proper nouns and noun phrases (I was taught to write "in Chapter 3" or "on Page 4" as opposed to "in this chapter" or "on the following page", and I taught the postgraduate students I supervised to do the same in their theses); now there's a trend to decapitalize further. Who am I to stand against such trends? :-) Peter coxhead (talk) 14:36, 5 July 2017 (UTC)

I'm happy to admit that the 1662 Prayer Book was a little before my time. :-) Martinevans123 (talk) 15:33, 5 July 2017 (UTC)

That's just one philosophical approach to the meaning of "proper name" and it's highly dependent on language (some languages would use a definite article there, but it doesn't change the underlying nature of the term "vol."/"volume" or its meaning in any way). For purposes of style discussions. "proper name" and "proper noun" are essentially interchangeable. The "Mixed" argument presented by Eppstein and others is cognizant of this; the "Vol." in The Art of Computer Programming, Vol. III: Sorting and Searching should be capitalized because it's part of the title (or subtitle, more specifically), and thus part of a proper name (proper noun phrase). Lots of things do not take a definite article in English by convention, and are not capitalized, even if some philosophers want to classify them as proper names. E.g., "entry 2349499393 in my database", "See example [number] 32 in the list below", "I cracked thoracic vertebra 4" (or "I cracked vertebra T-4"), "at 6 o'clock", etc., etc. Most of these can be replaced by ordinals, at least when given numeric designations; that breaks when they aren't ("See example F in the list below"). No doubt some would write "Example F", but few would do this upper-casing to all the examples here. It's no longer conventional.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  04:24, 6 July 2017 (UTC)

• Mixed as with David Eppstein's comments. I think the proper nouns can be used for the citation section and for the title if it is part of the title as with the Vol. 3: Sorting and Searching, but that when referring to "vol. 3, no. 15" in the text body, "volume 3, issue number 15", "part 2", or "chapter 5", it can be lower-case. This is comparable to cite episode template where they use "Season 1. Episode 15". in the citation but refer to season 1, episode 15 in the text body. With Episode, however, it's in capitals because the cite episode can be done without specifying a season number for television series that has a single season. AngusWOOF (bark • sniff) 16:24, 5 July 2017 (UTC)

• Mixed: Citations, including
  WP:IBID). For example, the Bluebook citation style used by the US legal profession doesn't use a full stop until the end of a citation, but uses capitalized "No." in certain cases where the docket number of a case needs to be included, eg. "Matal v. Tam, No. 15-1293, slip op. at 5 (June 19, 2017)." As for prose, they should be capitalized as part of a title or at the start of a sentence. If used as a proper noun, except as a title or in a quote, then the word should be written, eg. "Smith's writing in volume 3 was regarded by his contemporary Johnson as 'abysmal.'" In other cases, they should be lowercase. AHeneen (talk
  ) 17:06, 5 July 2017 (UTC)

The combined two blocks of sourcing I've provided here (plus that done yesterday in the footnotes at

Exempli gratia) indicate an overwhelming preference for "vol." and "no." (lower-case and punctuated) in professionally published material today, regardless of English variety. MoS should follow this practice; it is not just better supported in the real world, it's also more consistent with our treatment of other abbreviations and other Latinisms, and is less ambiguous (at least in the case of "no"/"No"). Style guides in favor of "No." and "Vol." are mostly one of: only addressing a particular citation format, not recent, of low to middling reputability, or some particular entity's house style. Those in favor of "No", "no", "vol", etc., are primarily the house stylesheets of particular news publishers. The main guides for writing fairly formal English – Chicago Manual and New Hart's, on which MoS is largely built – both use "no.", "nos.", "vol.", "vols."

Again, this would not lowercase either abbreviation in a) the title of a work or b) a citation in a format that capitalizes either or both. These are the concerns the Mixed comments above have in mind.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  22:00, 11 July 2017 (UTC)

If you keep running into No 1 in various articles, why don't you try frequenting articles where there are people around? Then you wouldn't be so lonely. At Christmastime, try the No L articles. EEng 03:09, 11 July 2017 (UTC)

LOL.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:36, 11 July 2017 (UTC)

I do the best I can with the material available. EEng 03:40, 11 July 2017 (UTC)`

As a screen reader user, it doesn't really bother me that much that the full stop is omitted. "no." is read as no with a pause after it, rather than "number", and all educated blind people should know what "no." stands for. (IIRC the local

talking book catalogue says things like "Book no. 12345".) Even without the full stop I can figure out what's meant. Yes it's less ambiguous and more correct with the full stop, but I've never thought about it before as an accessibility issue. Graham87

07:38, 11 July 2017 (UTC)

Good to know, though I'm surprised that's still true today; I would think that "No."or "no.", followed by zero spaces or a single space, then a numeral or string of numerals or a spelled out number word, would be read as "number". Maybe the logic to pick it out is more complicated by false positives than I imagine. Even if so, it seem that more cases would be correct that false matches, and that this would be preferable to every case being read as the word "no". Hmm. Well, I've never tried writing a screen reader so I guess this is kind of akin to an "I am no a lawyer, but ..." musing.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:09, 14 July 2017 (UTC)

Opinions are needed on the following matter:

Users Adûnâi and Dank are in disagreement with me over how MOS:COMMA should be applied.

It started when I pointed out an error (my opinion) on the Main Page, adding this remark:

Per WP:Copyedit#Punctuation, a comma is missing in "The British North America Act of July 1, 1867 (now celebrated as Canada Day) united the colonies of ... ". A comma is required after mdy dates, unless it's followed by other punctuation, for instance period/full stop at the end of sentence. Parentheses are not punctuation, and so there should be a comma after the end of the parentheses.

Adûnâi disagreed, writing:

Wouldn't it be a comma between a subject and a verb?

Dank agreed with Adûnâi:

That comma rule is overridden by comma conventions that avoid a comma both before and after those parentheses.

User Khajidha agreed with me:

What conventions are those? By what I've always been taught, User:Handsome Fella is correct.

The discussion was removed as a new day arrived.

I then contacted both editors on their talkpages, but was unable to convince them, despite pointing out the explicit "Burke and Wills" example:

• Do not be fooled by other punctuation, which can distract from the need for a comma, especially when it collides with a bracket or parenthesis, as in this example:

Incorrect:	Burke and Wills, fed by locals (on beans, fish, and ngardu) survived for a few months.
Correct:	Burke and Wills, fed by locals (on beans, fish, and ngardu), survived for a few months.

Adûnâi claimed this was "a completely unrelated example", while Dank re-iterated that "a comma separates each element and follows the last element unless followed by other punctuation", ignoring the explicit part I had pointed out: "Do not be fooled by other punctuation, which can distract from the need for a comma, especially when it collides with a bracket or parenthesis, as in this example (which appears above the "Burke and Wills" example).

Let's look at another example:

• In the article Mary Jo Kopechne, this sentence is found in the first section: "Her father, Joseph Kopechne, was an insurance salesman, and her mother, Gwen (née Jennings), was a homemaker".

In it, "and her mother, Gwen, was a homemaker" is interrupted by the parenthetical expression "(née Jennings)", resulting in the above sentence. Do Adûnâi and/or Dank mean that the comma after "Gwen" should be removed? I don't know. I have not understood how either of them explains why the comma shouldn't be there, which is why I'm starting this discussion.

Could someone please clarify this?

Thanks.

HandsomeFella (talk) 12:12, 19 July 2017 (UTC)

I completely agree with all of your examples here. But they are different than the sentences in question. On my talk page, you wrote this.

• The British North America Act of July 1, 1867[,] united the colonies of ...

In the current version of the article, there are three points which are comparable (searching by "July 1, 1867"). The third one looks like the following.

• The enactment of the British North America Act, 1867 (today called the Constitution Act, 1867), which confederated Canada, was celebrated on July 1, 1867[,] with the ringing of the bells...

I'm not sure about the comma because I haven't seen a clear example that proves it should always follow dates such as July 1, 1867.--Adûnâi (talk) 12:49, 19 July 2017 (UTC)

Luckily it's in the MOS, right under the Burke Willis example. Primergrey (talk) 13:27, 19 July 2017 (UTC)

Ok, it finally dawned on me what Adûnâi means. He means (I think) that "[The] British North America Act of July 1, 1867" is the subject, and that the comma in question would separate the grammatical subject from the verb (right?). Ok, I guess that could be argued – it could also be discussed – but when in a full sentence, punctuation rules still apply, in my opinion. So we still disagree. HandsomeFella (talk) 13:42, 19 July 2017 (UTC)

It would also mean that the comma is superfluous even when there's no parenthetical. I think that's wrong too. HandsomeFella (talk) 14:03, 19 July 2017 (UTC)

I'm going to guess from the lack of response that people are happy with our understanding of the MOS guideline. Please ping me if not. - Dank (push to talk) 21:11, 22 July 2017 (UTC)

Dank What MOS guideline are you referring to? If you mean what you wrote above,

That comma rule is overridden by comma conventions that avoid a comma both before and after those parentheses.

Where is this taken from? I never heard anything like this. Though I know some editors think the comma after the year in m-d-y dates is optional, traditionally it is required, and I think it often prevents confusion, so I use it, and it does belong after the parenthetical phrase. One way to avoid having to place a comma after a parenthesis (which doesn't bother me, but apparently bothers some) is to remove the parentheses around "now celebrated as Canada Day" and instead use a pair of commas or a pair of en-dashes:

• The British North America Act of July 1, 1867, now celebrated as Canada Day, united the colonies of ...

• The British North America Act of July 1, 1867 – now celebrated as Canada Day – united the colonies of ...

As an additional note, I think I was told that parentheses slow down readers who use screen readers more than other punctuation.  – Corinne (talk) 21:40, 22 July 2017 (UTC)

WP:MOS says "Dates in month–day–year format require a comma after the day, as well as after the year, unless followed by other punctuation." Agree, disagree? That word "Dates" is linked to

WP:MOSNUM, which gives an example: "Everyone remembers July 21, 1969 – when man first landed on the Moon". The example illustrates that that sentence from MOS is meant literally. This corresponds to what I've seen at FAC. - Dank (push to talk

) 21:58, 22 July 2017 (UTC)

@Dank, Adûnâi, and HandsomeFella: The comma does not belong this time. Yes, we have a rule for "July 1, 1867, ..." with two commas (so do other style guides). Commas that serve a parenthetical purpose are always in pairs, unless replaced by:

• Terminal punctuation: "It happened on July 1, 1867."
• Other punctuation that introduces another parenthetical that pertains to the surrounding material not to the first parenthetical: "The murder happened on July 1, 1867 – the day my great-great-great-grandmother was born." The parenthetical introduced by the dash pertains to the entire subject, not to "1867".

I.e. we don't use pointless double punctuation, like a comma before a period/stop or a dash.

Much of the above has been red-herring discussion. Yes, this case differs from the guideline's and the Kopechne article's examples. The beginning of "(now celebrated as Canada Day)" is a "(" introducing another parenthetical, which applies to the subject, not to the year, so it cancels the need for a comma to balance the first one in ", 1867". Without the date, this would read "The British North America Act (now celebrated as Canada Day) united the colonies of ...", with no commas. Contrast the other examples: "her mother, Gwen (née Jennings)," has a parenthetical that applies to the material in another parenthetical (the ", Gwen ...," structure) and is part of it, all of it ultimately referring to "her mother". Without the second parenthetical, it would read "her mother, Gwen, ..." with both commas. Without the first parenthetical, it is a non-sequitur: "her mother (née Jennings)"; makes little sense without the first name also included. "Burke and Wills, fed by locals (on beans, fish, and ngardu), survived for a few months" is essentially the same as the mother example, and would read "Burke and Willis, fed by locals, survived ..." without the second parenthetical clause, which pertains to the feeding not to B&W. Without the first parenthetical, it is again broken: "Burke and willis (on beans, fish, and ngardu) survived ...". Both are broken when their first parentheticals are removed because the second parenthetical is an internal reference to the first, not to the subject directly. [Aside: Both could be unbroken with a rewrite if information was genuinely missing: "her mother, née Jennings, first name unknown," and "Burke and Willis survived for a few months on beans, etc., but it is not known if they locals provided this food or they gathered it themselves."] In the case at issue, the holiday name pertains to the entire subject, not to the "1867" fragment, and it works regardless what you do to it, because the parentheticals are independent of each other: "The British North America Act of July 1, 1867, united ...; and "The British North America Act (now celebrated as Canada Day) united ...".

Another way of putting it: The Canada thing could very reasonably be rewritten as "The British North America Act of July 1, 1867 – now celebrated as Canada Day – united ...". But no sane writer would do "... her mother, Gwen – née Jennings ...", or "Burke and Wills, fed by locals – on beans, fish, and ngardu ...". They're a different kind of structure from the Canada case.

PS: Technically, the "1867" is not a parenthetical, but is conventionally formatted as one. The nature of this kind of confusion/dispute is one of the reasons (source: Garner's Modern American Usage) that another pseudo-parenthetical, the "Firstname Lastname, Jr, ..." style, has gone out of fashion, in favor of "Firstname Lastname Jr ...". It's also probably (my speculation) got something to do with why "July 1, 1867, ..." date formatting has been abandoned in most of the world, when it was neck-and-neck with "1 July 1867" style in the 19th century (source: Google N-Grams).
05:04, 28 July 2017 (UTC) — Preceding unsigned comment added by SMcCandlish (talk • contribs)

Hello everyone, I stumbled across Special:Contributions/5.107.140.121, who has made numerous edits of this form [7]. Am I correct in reverting these, or am I missing something? @5.107.140.121:. Tazerdadog (talk) 19:12, 22 July 2017 (UTC)

I would say your reverts are correct. Blueboar (talk) 19:25, 22 July 2017 (UTC)

Definitely. We have a rule about this somewhere, but I didn't find a version of it in

MOS:ABBR, so I added it. People will expect that page to have every acronyms-related rule in it, and we can't figure that people are going to dig up out of some other page. I see the anon doing those "treat our readers like morons" edits has received a pack of warnings about inappropriate editing. And did at least one after the warnings, but it was a day ago and maybe too stale for action.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  06:52, 28 July 2017 (UTC)

The above redirect points to a very short section here. That section seems to be missing links to where we would otherwise use non-breaking spaces (at least a reference to MOSNUM). Maybe it would be a good idea to add some pointer links? --Izno (talk) 11:56, 25 July 2017 (UTC)

MOSNUM itself keeps pointing to another page for more info on non-breaking spaces (or nonbreaking, whatever spelling you like; I note that MOSNUM is not using a consistent spelling of it, either).  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  06:54, 28 July 2017 (UTC)

The MoS asks for a space before per cent/percent, but does not make clear whether this should be non-breaking. Do you know? –Sb2001 ^{talk page} 14:07, 18 July 2017 (UTC)

Clarified [8]. Reverted myself. I must be losing my mind. EEng 16:08, 18 July 2017 (UTC)

EEng, I read the question as asking whether the space before the words "per cent" or "percent" should be non-breaking, that is, whether one should write x per cent or x{{nbsp}}per cent. (IMHO a nbsp might be a good idea.) — Stanning (talk) 17:11, 18 July 2017 (UTC)

Yes, User:Stanning: that is exactly what I meant. Although, User:EEng: your edit was still more than worthwhile, and does prevent ambiguity. –Sb2001 ^{talk page} 17:17, 18 July 2017 (UTC)

IMO, there should be a non-breaking space between a numeral and the first word of a unit or "percent/"per cent", eg. "133{{

MOS:NBSP (discussed below). AHeneen (talk

) 18:09, 18 July 2017 (UTC)

[edit conflict] Actually, the MoS says NOT to use a space before the percent sign. Before the previous edit, it said: Write 3%, three percent, or three per cent, but not 3 % (with a space) or three %. "Percent" is American usage, and "per cent" is British usage (see § National varieties of English, above). In ranges of percentages written with an en dash, write only a single percent sign: 3–14%. AHeneen (talk) 17:14, 18 July 2017 (UTC)

OK, now that I've had some coffee... I would say regular space, not nbsp, by analogy to the fact that we code a regular space in 5 kilograms but nbsp in 5 kg. See the table at WP:Manual_of_Style/Dates_and_numbers#Unit_names_and_symbols, in the section of the table labeled Numeric values. EEng 17:30, 18 July 2017 (UTC)

Yes - that does make sense. –Sb2001 ^{talk page} 17:58, 18 July 2017 (UTC)

That page only mentions an NBSP before a unit symbol: "Use a nonbreaking space ({{

nbsp}}MB in prose, it may be counterproductive in a table (where horizontal space is precious) and unnecessary in a short parameter value in an infobox (where a break would never occur anyway)." I think usage of an NBSP before percent or per cent should follow that guideline. I don't have time right now, but talk page archives should be checked to make sure this issue hasn't been discussed before. AHeneen (talk

) 18:09, 18 July 2017 (UTC)

I'd say % is analogous to a unit symbol, while per cent and percent are analogous to a unit name. Coding 15{{nbsp}}per{{nbsp}}cent creates an overlong unbreakable string. EEng 19:37, 22 July 2017 (UTC)

• Any time MoS is advising that a numeric figure be followed by a space and a something, it means a non-breaking one.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  04:02, 28 July 2017 (UTC) I was wrong on this; we only require it when what follows the number is a symbol or abbreviation (50 dB, 4:29 p.m., 1252 BCE, etc.). Using a nonbreaking space it is harmless when what follows is a regular word that is a unit or something comparable.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  06:16, 28 July 2017 (UTC) Corrected 06:18, 28 July 2017 (UTC)

I take it you feel it's reasonable to expect editors to somehow intuit that? If not, you feel it's reasonable to educate the community about that one misled editor at a time, forever? Besides, how do you know what MoS intent is?
My take on this: 1. There is little need for site-wide consistency on this. If some cases break "5 percent" and other cases don't, that's really ok. Nobody will notice except a few obsessive Wikipedia editors. We are here to serve our readers' needs, not our own.

WP:CREEP. 2. Where there is disagreement in a specific case, MoS is not a substitute for discussion and consensus, the cornerstones of Wikipedia editing. ―Mandruss ☎

04:39, 28 July 2017 (UTC)

Not sure what you're on about. I am was agreeing that the page needs to be updated to say to use a nonbreaking space, not just a space. I said nothing about anyone intuiting anything, or doing anything editor by editor. There is a need for site-wide consistency on this, or we would have no nonbreaking space rules of any kind at all; we use them because it keeps the digit meaningfully grouped with what it refers to. [Correction: The rule is narrower than I remembered, and applies to symbols/abbreviations only.] If every other time you post to an MoS talk page you cannot refrain from aspersion-casting about other editors' mentalities, you need to stop posting to them (

WT:MOSNUM. I tend to agree, but while they are the rule, they are, and we should do it consistently.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  06:07, 28 July 2017 (UTC) Corrected 06:18, 28 July 2017 (UTC)

I'm not taking the bait, but I would be very interested to see your evidence - on my talk page - any evidence at all - that I cast aspersions "every other time [I] post to an MoS talk page" (

speaking of aspersion-casting). ―Mandruss ☎

06:26, 28 July 2017 (UTC)

I'm being hyperbolic about the frequency, of course. Please don't label MoS editors, and editors at articles doing MoS compliance, as "obsessive". It's a direct insult and an aspersion about their mentality. Just don't.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  06:58, 28 July 2017 (UTC)

Ah, so "every other time" is your "hyperbole" for "once". Wow. Ok. Anyway, as much as I'd love to debate the point with you, it would be too tangential and distracting, as well as being pointless. My comments stand, and I wouldn't make a fuss if somebody collapsed the whole thing. ―Mandruss ☎ 07:08, 28 July 2017 (UTC)

Anyway, what SM said isn't true. We don't call for an nbsp in 29 newton-meters. EEng 04:57, 28 July 2017 (UTC)

I stand corrected. I thought MOSNUM was explicit that all numeric measurements/values are followed by a nonbreaking space then the unit name or symbol or whatever; it's only symbols and abbreviations.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  06:07, 28 July 2017 (UTC)

Should the names of blogs be italicised? Most of the articles for entries on List of blogs do not have italic titles (although some do). I was about to italicise the title of a blog article but was quite surprised to find this was not the general practice. SpinningSpark 17:17, 19 July 2017 (UTC)

From

MOS:ITALICTITLE

:

Website titles may or may not be italicized depending on the type of site and what kind of content it features. Online magazines, newspapers, and news sites with original content should generally be italicized (

Merriam-Webster Online

). Other types of websites should be decided on a case-by-case basis.

I think the titles of blogs should be italicized. Be sure the article is about the blog and not primarily about a company who publishes a blog of the same name. For example (I could only think of examples of websites): BuzzFeed (about the company) and Politico (also about company) versus The New York Times (about newspaper/website, as company has separate article: The New York Times Company). AHeneen (talk) 01:29, 21 July 2017 (UTC)

• Yes, they should be italicized, unless they're part of a larger work, in which case quotation marks. The same rules apply regardless of medium: major, stand-alone works get italics, minor works and sub-works get quotes. The New York Times doesn't become The New York Times or "The New York Times" if you're referring to an online article instead of one printed on dead trees. Our citation formatting templates (and various external citation style) are going to apply italics to titles of blogs as the |work= or |website= or |journal= parameter value, so deciding on your own not to use italics is going to cause a conflicting style in the same article. If you're dealing with something like a newspaper's official blog, use |work=Newspaper Title |at="Blog Title" (official blog) |title=Article title; resulting in a cite like: Persson, J. Randome (27 July 2017). "How I Survived a Vicious Salamander Attack". Newspaper Title. "Blog Title" (official blog). {{cite web}}: Missing or empty |url= (help) Publications get italics except when referred to as a business (use the company name), or a computer system (no styling, use domain name): "He writes for Salon"; "She took over as the CEO of Salon Media Group"; "The DDoS attack also affected www.salon.com for two hours." For online publications that use their domain name as their title, complete with the ".com" (or whatever), it still goes in italics when discussed as a publication rather than a legal entity or a stack of hardware. This, too, is what our cite system will do, so just deal with it and don't introduce a conflict style, please. :-) PS: Abusing parameters of the cite templates to get an alternative style (e.g. using |at= for the work title) will emit incorrect COinS metadata and is to be avoided. Anyone may revert/fix that on sight.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  05:12, 28 July 2017 (UTC)

  I think I would prefer to see the blog in the work parameter (if cited at all) since it is also a major work of many articles of content. But this is a quibble with your comment. --Izno (talk) 12:47, 28 July 2017 (UTC)

I thought that we have an existing rule about this, but cannot find it.

Is "A

Follow the pronunciation. Anyway, UARTS are so 70s. EEng 20:22, 28 July 2017 (UTC)

Most people who work with microcontrollers pronounce it "Yoo-Art" but a lot of people who work with the telephone system pronounce it "Ooo-Art", but there is a lot of overlap. Regional dialect differences?

https://books.google.com/books?id=I9FtDQAAQBAJ&pg=PA198&lpg=PA198&dq=%22an+UART%22+-%22a+UART%22&source=bl&ots=YDN08a39BK&sig=CBhJLVIucLv8Fd4h9o67D9W0r70&hl=en&sa=X&ved=0ahUKEwj_iKG9gq3VAhUpjlQKHfoHDn8Q6AEIcDAM#v=onepage&q=%22an%20UART%22

https://www.microchip.com/forums/m578823.aspx

https://www.ieeexplore.ieee.org/document/7342320/

https://forums.xilinx.com/t5/Welcome-Join/adding-an-uart-on-zc702-with-PMOD2/td-p/752074

https://stackoverflow.com/questions/40607345/how-to-communicate-with-an-uart

--Guy Macon (talk) 22:33, 28 July 2017 (UTC)

Intrinsic-Harmony.jpg If you combined an

Ooo-art? I give up.You're on your own. EEng 22:50, 28 July 2017 (UTC)

Pro tip: If you ever have a problem with someone using a voodoo curse of you, just use a standard hex inverter.[9] -Guy Macon (talk) 13:37, 30 July 2017 (UTC)

I'd have to discount evidence from newbies on question forums, but there are clearly differences in practice. I have to say from personal experience since around 1980 dealing with relevant tech from the computer side (I never got a lot of exposure to the telecom side), I've never heard it pronounced as "ooo-art". If I were trying to make an argument, I might try looking at Google n-grams, but it claims not to be able to find instances of "an uart". Or I could say that, absent solid evidence to the contrary, the leading word of the acronym should govern: "universal". But I'm glad I asked Guy Macon the reasoning behind his edit; this has been enlightening! — jmcgnh^{(talk) (contribs)} 23:13, 28 July 2017 (UTC)

Saw these online which says if the U is a Y sound then treat it like a consonant. [10] [11] This Merriam-Webster one talks about acronyms too: [12] AngusWOOF (bark • sniff) 02:09, 29 July 2017 (UTC)

I think they might pronounce it as Ooo-Art in the West Country, where brand new combine harvesters come from. (Not really.) nagualdesign 13:10, 29 July 2017 (UTC)

Based on the feedback above, I am going to use "a UART" from now on. The interesting aspect here is determining how most people pronounce an acronym/initialism. I can look around me and see that most people I talk to pronounce "FAQ" as "fack" and not "eff-ay-cue" and that most people I talk to pronounce "RfC" as "Arr-Eff-Cee" and not "Refsee", but is this universal among English dialects? I recently worked with some Australians, and when they read something like "E-Z-Off" they read it as "Eee-Zed-Off". And what pronunciation should I assume for "FUQ (Frequently Unanswered Questions"? --Guy Macon (talk) 13:37, 30 July 2017 (UTC)

I'll never tell. EEng 14:08, 30 July 2017 (UTC)

Back when, the university computer lab people tended to spell it out F-A-Q, while the dialup crowd used /fak/ a lot.

The Jargon File gives both, prefers the spelled-out version, and dates to the era. "RFC" or "RfC" is usually spelled out; the /ref-see/ thing is uncommon (barely attested in N-grams). N-grams show a spike in "a FAQ" usage, but it fell off, and usage is now stably parallel. Because of the FUQ thing, I'd recommended going with the spelled-out version, thus "an FAQ". Another option would be to use "a FAQ" except in a) technical contexts, or b) in the same article as FUQ appearing, since "a FAQ" appears to be more common outside geeky contexts, though no longer by much of a margin. Also agree it's "a UART"; the /oo-art/ pronunciation seems to be poorly attested.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:06, 30 July 2017 (UTC)

I recently started placing nbsps after 'p.' and before the number. It then became clear that the citation insert tool does not do this. Other editors do not, either. Is it A/ bad/something to go back to undo, B/ something which is harmless, but unnecessary or C/ something which we should all be doing? –Sb2001 ^{talk page} 11:40, 28 July 2017 (UTC)

Inside a

citation template, A: this corrupts the citation metadata emitted. Other places, probably B (unless we have guidance otherwise at present). --Izno (talk

) 12:42, 28 July 2017 (UTC)

For the last two years I've been routinely adding a non-breaking space template {{

nbsp}} should not mess up even that kind of citation), and no one has ever said it messes up anything.  – Corinne (talk

) 13:33, 28 July 2017 (UTC)

What I've said for many years is that if the citation templates can't handle some of the ways of inserting the same thing (i.e. literal nbsp vs.   vs. {{

nbsp}}) then the priests that control those templates should fix them, so that editors don't have to remember a bunch of extra rules for no apparent reason. EEng

16:27, 28 July 2017 (UTC)

You should not be using "p." at all within the citation templates; they add that themselves (with |page= instead of |pages= if you want p. instead of pp.) If you're formatting citations yourself instead of using a template, I would go somewhere between C and B: I think it's preferable to use a non-breaking space, but not actually harmful not to. —David Eppstein (talk) 21:29, 28 July 2017 (UTC)

David Eppstein Since you say the citation templates are formed automatically, does the template somehow contain a hidden no-break space after "p." and "pp." – and, if it doesn't, could it be added? Doesn't it make sense to do so? It would save a lot of adding of no-break spaces. I think everyone would agree it would be preferable to avoid having "p." or "pp." end up alone at the end of a line.  – Corinne (talk) 15:40, 29 July 2017 (UTC)

Those cs1|2 templates that prefix pagination with p. or pp., insert a   character between the prefix and the first page number. It has been this way for a very long time.

Not all cs1|2 templates render pagination with the p. or pp. prefix. If you are writing |page=p. ... or |pages=pp. ... in the cs1|2 templates that render page numbers with a colon prefix, {{cite journal}} and {{citation}} (when |journal= is set), then you should stop doing that. Typical professional, academic, or scientific journals usually do not use p. or pp. prefixes so {{cite journal}} and {{citation}} follow that style.

—Trappist the monk (talk) 16:23, 29 July 2017 (UTC)

I never add a non-breaking space after "p." or "pp." if an equals sign or a colon follows either of those, and I usually don't touch any ref that's within curly brackets. It's mainly in the citations that use the < ref>...< /ref> format that I would add the non-breaking space template. Is that safe to do?  – Corinne (talk) 16:44, 29 July 2017 (UTC)

This is a false dichotomy: "any ref that's within curly brackets" versus "citations that use the <ref>...</ref> format"; most uses of the citation templates are inside <ref>...</ref>; they're only not when people are using the separate-refs-and-bibliography-sections system, which is mostly at longer articles, especially those repeatedly citing the same sources at different pages. Anyway, I agree with the gist above: The templates already handle this. For non-templated citations, C is probably the ideal answer, but B is fine, too (see elsewhere on this page for consternation about non-breaking spaces; not everyone agrees that the end result, for the reader, of using them is worth the instruction creep of inserting rules about them into MoS). It's generally a safe bet to include one, in regular (non-templated) text any time you don't want a number or other tiny string to separate from something else. As noted in the other thread, we don't actually have a rule to use, e.g., 47 metres, just 47 m, but many of us do the former as well for the same rationale, even in absence of it being demanded by MoS.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:22, 30 July 2017 (UTC)

Because of how rare it is, I had not even considered the refs in braces. As long as there is nothing wrong with me adding the nbsp, I will continue to do so. –Sb2001 ^{talk page} 23:29, 30 July 2017 (UTC)

Whenever I see 'No.' or 'No' (now you have all brainwashed me into meticulously eradicating all non-MoS styles of writing), I place the {abbr|No.|number} tag on it, for clarity. I understand that both versions, ie dotted and non-dotted may seem slightly confusing. Although, I maintain that most instances of it in the UK drop the full stop (or, full point as the MoS now likes to use). My question is whether this is actually worthwhile: very few editors seem to bother doing this outside infoboxes, which makes me wonder whether I should be doing it at all. If it is advisable, why does the MoS not require editors to add the abbr tag? It is the same with circa. I always tag that if I see it (and – as much as it hurts – put the full point on the end). The MoS is, as usual, rather ambiguous on this matter. –Sb2001 ^{talk page} 11:37, 28 July 2017 (UTC)

It would not be unreasonable to suggest that editors use {{abbr}} (or its HTML equivalent--perhaps we can be silent on that option) when using an abbreviation for the first time in a document, as this increases the accessibility of the abbreviation. My preference is usually to link a phrase first if the word is relevant to the topic, though. And perhaps an abbr isn't necessary when the phrases immediate context makes the definition clear (as in an infobox on a page about a taxonomic group). --Izno (talk) 12:40, 28 July 2017 (UTC)

And when used, it only need be done at first occurrence within the article, same as with linking it. If you do it a bunch of times in the same page, it's annoying; it browbeats the reader and implies they can't remember an abbreviation from one paragraph to the next. There effectively is not difference between <abbr>...</abbr> markup and a wikilink, in the sense that a string has been marked up such that doing something with it with the pointer leads to additional contextual content; one goes to another page, the other results in a tooltip. Sso does <span title="Tooltip text here.">...</span> (or same on some other element that doesn't have a reserved use for title=). I mention that last bit, because I keep running into cases of people abusing <abbr>...</abbr> to generate tooltips for things that are not abbreviations, which is an HTML spec violation (a well-formedness rather than validation error, in the extended definition of "well-formed" which includes "follows all the syntactic rules").  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:57, 30 July 2017 (UTC)

I'ld like to ask if there is a guideline on using diacritics in commonly used words like naïve and café. The reason I ask is that someone just did this: [13], and I'm not sure whether that's appropriate or not. LK (talk) 08:16, 22 July 2017 (UTC)

There doesn't seem to be, since it's one of those common-sense, follow-the-sources things. We don't use anything that dictionaries label obsolescent, and that includes diacritics on foreign words fully assimilated into English and consistently used without them, and words that used to use them to indicate pronunciation (e.g., no one writes "rôle-playing games", or "they decided to coöperate", or "he's a very learnéd man" in 21st-century English). The "café" spellings is not obsolete, and preferred by many; "naîve" is getting rare. A tiny handful of words have survived assimilation and retained the diacritics almost universally, e.g. "née" and the uncommon masculine form "né" (sometimes encountered without, but I've been in genealogy circles long enough to see it usually retained, especially after the effective demise of ASCII-only e-mail by the late 1990s). Another example is "façade", which retains the cedilla so people don't think it's said "fakade". But we've lost the umlaut in the English [mis-]borrowing of "uber", and along with it the alternative German spelling "ueber", which is unrecognizable to most English speakers. The acute accents are also retained (except in very sloppy writing) in "résumé", to avoid confusion with "resume" meaning "to continue".

General rule of thumb: check some dictionaries, and use the spelling that is listed first by the majority of them. In your cases, the results are "café" but "naive". Regardless of the answer on the latter, the diacritic would be retained in non-assimilated words (e.g. naîf) and in a foreign word that has an English non-diacritic equivalent: "naîvete" but "naivety". The very existence of "naivety", "naiver", "naivest", and other derived forms, which never have the umlaut, discourages "naïve" in English. Zero dictionaries of the eight or so I checked listed "naïve" as preferred, and three did not list it at all, only "naive". All of them preferred "café" over "cafe".  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  06:49, 28 July 2017 (UTC)

I wouldn't say no one uses "coöperate". Famously, The New Yorker still uses umlauts on double vowels to indicate separate pronunciation instead of a long vowel sound. But it's so rare as to be essentially obsolete. Though I vaguely remember an editing dispute not long ago with someone who insisted on it's use in a baseball article. I think the person was blocked as a series sockpuppeteer not long after, though. oknazevad (talk) 21:06, 28 July 2017 (UTC)

Yeah, The New Yorker and a few other publications (e.g. The New York Times) intentionally do a few obsolete things in their house style, as a branding mechanism. It seems to have no detectable impact on usage by others.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  00:13, 31 July 2017 (UTC)

In that related article, Café Royal is a proper noun place, so that accent can be retained. Also, if certain words are quoted without the diacritics, then you can leave those alone. AngusWOOF (bark • sniff) 21:27, 28 July 2017 (UTC)

It would definitely be retained in a proper name, regardless of anyone's spelling preferences. If the owner was quirky and had spelled it Kafé Royal, that's the spelling we'd use; we wouldn't rename the restaurant to "correct" spelling. But

MOS:TM limits apply; we're not going to mimic something even more quirky, like K^afé·Я^oyal, where the alterations are just typographic logo-design gimmicks.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  00:13, 31 July 2017 (UTC)

We've been over this many times before. Time to add a rule about this to MOS:CAPS, since it comes up again and again; I can think of at least three previous discussion of this just in the last year or two.  — 

specialized-style fallacy is rearing its ugly head, with someone unhappily suggesting that the MoS is "bad" on this and should be changed, so he/she can continue capitalizing "Endangered". I explained why that can't happen.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  08:06, 28 July 2017 (UTC)

Begging your pardon, but my suggestion was not an unhappy one, nor do I wish to 'continue capitalizing "Endangered"'. In fact the only edit I have made to any article in this regard was to switch "Critically Endangered" to lowercase once[14], which was reverted, hence I began a

WP:BRD

). As I have repeatedly stated, it doesn't matter to me one way or the other if we use caps or lowercase, I'm just trying to push for consistency, like yourself.

While I appreciate your input at WikiProject Tree of Life I think you ought to lay off being so antagonistic. You make a lot of good points but then keep slipping in comments about other editors' motivations and thought processes; all unnecessary assumptions on your part. The discussion may well smack of some previous discussion that you once took part in, but there's no need to take out your frustrations on those involved here.

When I read comments about "editorial resignations due to the heat generated over style trivia" I can't help thinking that you're probably part of the problem, and referring to such discussions as "trivia" or "pointless style disputes" doesn't help quell the heat. So please, try to be more like Sisyphus and less like the boulder. Regards, nagualdesign 12:53, 29 July 2017 (UTC)

A few more commenters on this issue would be much appreciated. nagualdesign 23:31, 1 August 2017 (UTC)

Does anyone have any pertinent information or strong preferences on whether the labels for the various earthquake magnitude scales should be italicized (like this M_L, M_w, M_S, mB, mb, mb_Lg, etc.) or not (like this M_L, M_w, M_S, mB, mb, mb_Lg)?

It might be noted that this is entirely a matter of style, not nomenclature, and that some seismological authorities italicize, and some do not. Also: these terms are not variables: they are labels, analogous to "F" and "C" for temperature scales. ~ J. Johnson (JJ) (talk) 21:43, 29 July 2017 (UTC)

I think italics are more difficult to read than Roman (regular) font, so I prefer Roman font, but I guess it's important to know what most experts in the field use. Pinging Vsmith and Jo-Jo Eumerus.  – Corinne (talk) 20:20, 30 July 2017 (UTC)

You might be surprised, but earthquakes are not really my thing. That said: One of the problems I see is that some sources appear not to use italic font period, so it is not clear whether the absence of such around earthquake magnitudes means anything. Jo-Jo Eumerus (talk, contributions) 21:16, 30 July 2017 (UTC)

Our basic rule about all stylization is that if the sources don't do it consistently, we drop it, unless there's a good reason to retain it. This appears to be a vestige of italicizing mega- as a Latinism, which is something we no longer do in English since the assimilation of that and related prefixes into everyday language via the computer industry. It's inconsistent to apply the italics in this one case but not in MB, etc.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:12, 30 July 2017 (UTC)

That's good info. My take on this is: there are no strong preferences. For various reasons I will go with non-italic (unless something comes up). And we can let this discussion time-out. ~ J. Johnson (JJ) (talk) 21:26, 4 August 2017 (UTC)

The article

I have started an RFC at Wikipedia talk:Manual of Style/Abbreviations# RFC: Periods in abbreviations for degrees. Anyone interested in this issue should comment there, please. DES ^(talk)_{DESiegel Contribs} 22:20, 6 August 2017 (UTC)

In my opinion,

Please take part in the following discussion at the MoS Trademarks talk page; Wikipedia talk:Manual of Style/Trademarks#MOS:TMRULES –Sb2001 ^{talk page} 23:15, 10 August 2017 (UTC)

I happened across

If you mean the spaces around the ndash in the in-office dates, they belong.

MOS:DATERANGE. EEng

21:12, 1 August 2017 (UTC)

Right. I was not aware of that ... another sensible part of the MoS. –Sb2001 ^{talk page} 22:45, 1 August 2017 (UTC)

All parts of the MoS are sensible. --Izno (talk) 02:19, 2 August 2017 (UTC)

Well,

MOS:DASH says the same thing, though maybe not in as organized a way. EEng

03:19, 2 August 2017 (UTC)

Yes, it's been an irritant for many years. This is why it happens: whoever first designed the field on the infobox template must have had in mind a dash between two full dates (3 February 1961 – 15 April 1962). Or they just didn't care and decided to slip-slop it. But they can't have it both ways. The field should not be automatised in that way. Is it so hard for editors to write the date range / year range manually? Tony (talk) 03:21, 2 August 2017 (UTC)

What sort of justification is there behind having no spacing for some ranges, but spaces either side of the – for others? As I interpret it, Tony is saying that this rule is present because of the infobox templates. Is this the case? –Sb2001 ^{talk page} 15:07, 2 August 2017 (UTC)

As described both in

MOS:DATERANGE, spaces are added around the en dash if either element in the range contains a space, presumably to flag that the en dash is linking at least one boundary indicated with multiple words. isaacl (talk

) 16:31, 2 August 2017 (UTC)

'The 1940 peak period was May–July': I assume that you meant to say that if both sides have spaces, there should be a space either side of the –. Well, I think that the policy is confusing. It should be either space everything, or nothing. But, if that is the way it is, I cannot argue. –Sb2001 ^{talk page} 16:45, 2 August 2017 (UTC)

• I just don't have the energy to explain why the rules on when to space around the ndash, and when not to, are they way they are, but they make sense and are there for good reason; SMcCandlish will explain it comprehensively I'm sure.
• My speculation is that no one noticed that the template is inappropriately always spacing because it's so rare that both "sides", in this particular template, contain no space. Whatever the reason, I have little doubt our template wizards can add some magic to check that data and space, or not space, the ndash as needed.

EEng 01:27, 3 August 2017 (UTC)

• From
  MOS:DASH: The en dash in a range is always unspaced, except when either or both elements of the range include at least one space. In the example you quote, the elements bounding the range are "May" and "July". isaacl (talk
  ) 15:01, 6 August 2017 (UTC)

What example who quotes? EEng 16:26, 6 August 2017 (UTC)

I would imagine that it is my last comment, just before the outdent. –Sb2001 ^{talk page} 17:11, 6 August 2017 (UTC)

Got it. Are we done with this? EEng 17:35, 6 August 2017 (UTC)

I don't think I need to explain it comprehensively; in the example given, 'The 1940 peak period was May–July', the two linked elements are "May" and "July" which have no spaces, so the whole "if both sides have spaces" thing never arises with this example. It's about spaces in the elements being juxtaposed, not spaces that incidentally are on the outside of them, e.g. between "was" and "May". If either side has spaces in it, then space the en dash: "the Australia – New Zealand trade agreement". Otherwise you get a confusing mess like "Australia–New Zealand", which in many fonts looks almost (or even entirely) indistinguishable from "Australia-New Zealand", e.g. in the popular Lucida Sans Unicode, which has better Unicode support than most fonts.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  04:09, 13 August 2017 (UTC)

The example is attempting to show ambiguity. Chaning it to "The author thanked Sinéad O'Connor, Bob Marley, and her parents" is unambiguous unless you posit that Bob Marley was female. The comment "did she thank her own parents, or O'Connor's parents?" indicates that the writer of this example did in fact mean "The author thanked Bob Marley, Sinéad O'Connor, and her parents".

The next paragraph develops the theme: "The author thanked her mother, Bob Marley, and Sinéad O'Connor".

Personally I think the whole section needs a good going over, particularly the interaction of serial commas with appositives. Martin of Sheffield (talk) 13:45, 9 August 2017 (UTC)

The purpose of the example was to show how to remove ambiguity resulting from (in this case) a lack of the serial comma: "In such cases of ambiguity, there are three ways to clarify: [...] Recast the sentence (first example above):". The problem was that the proposed clarification added a new ambiguity, as the invisible comment in the wikicode even talked about. Of course, you still have to know that Bob Marley was male, but that's another issue. --Deacon Vorbis (talk) 14:02, 9 August 2017 (UTC)

So pick a better example. We clearly still need one, since one of the most common cleanup edits I do is inserting necessary serial commas into ambiguous sentences, without even actively looking for them. It's a very frequent "poor writing" matter, mostly caused by people who habitually avoid all serial commas and just think its okay to force people to read something several times to understand it. Well, it's not.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  04:11, 13 August 2017 (UTC)

Opinions are needed on the following matter:

Okay, what is it that you guys don't understand about how the correction I'm trying to make to #3 usage of hyphens is to correct a self-contradiction? #3 says never to use a hyphen in a proper name, but #1 already said to use a hyphen in a personal name if it was designed that way, and personal names are proper names/proper nouns. So why should we supposedly not clarify the exception using a wording like I tried to use?

2600:100E:B149:8DAB:F80C:D7D2:437F:F3BC (talk) 15:41, 19 August 2017 (UTC)

The original text made perfect sense. There was no need to change it. You really should have brought this here before making the edit. Further to this, your edit directly contradicts

MOS:NUMERO, which instructs editors to use No., rather than the hash. I will warn you now—certain editors around here like to see evidence of the MoS causing problems before it is changed. Also, you need to show that you have a good understanding of the MoS itself: not adhering to NUMERO is probably not the best idea when you want editors to accept your change. It proves that you have no experience making stylistic edits, or working with the MoS in other ways. –Sb2001 ^{talk page}

15:51, 19 August 2017 (UTC)

How do you figure "Never insert a hyphen in a proper name" isn't a direct contradiction of thee instruction to use hyphens in names that already have them? How can that possibly "make perfect sense" to you?

And I never said anything to anyone about any numbering format that I thought they should use. Where did you get that idea?

2600:100E:B149:8DAB:F80C:D7D2:437F:F3BC (talk) —Preceding undated comment added 15:58, 19 August 2017 (UTC)

No, you use a hash instead of the numero sign. That is against the MoS. Drop the aggression; it really will to help your case. The word insert suggests to anyone with a basic understanding of English that it is an alteration. Come back with a draft of a more sensible edit, ie fix the hash issue, and we will consider allowing you to apply it. –Sb2001 ^{talk page} 16:09, 19 August 2017 (UTC)

Oh, so your whole "hash" thing--the number sign, as in "example #1"--is causing your "style" complaint, making you falsely think I "have NO experience" in stylistic edits? Wow. That by itself is not proof of that. But okay, I can easily change from using the so-called "hash" to just not using one, haha!

Drop what supposed "aggression:" defending myxelf? Where did you get the idea that simply defending my position constitutes "aggression"?

2600:100E:B149:8DAB:F80C:D7D2:437F:F3BC (talk) 16:27, 19 August 2017 (UTC)

The hash is its common name in the UK, as you would know if you had any stylistic knowledge. You are supposed to come here to convince us, not mock our language. I assume that you make no stylistic edits from your contributions list: [15]. You only started editing today, according to this. Another reason why you should make an account. My point regarding the hash is that

MOS:NUMERO instructs editors to use the numero sign. User:EEng—thoughts on this matter? –Sb2001 ^{talk page}

17:16, 19 August 2017 (UTC)

Your edit is difficult to follow, and really just unnecessary. This is all in the section on compound modifiers, not personal names. Do you have an example of where this might cause a problem? --Deacon Vorbis (talk) 16:00, 19 August 2017 (UTC)

Exactly. No evidence of having to change it regularly, no evidence of edit-warring, etc. –Sb2001 ^{talk page} 16:09, 19 August 2017 (UTC)

How is plain English so "difficult to follow"? I know #3 is about modifiers, but without some exceptional language it contradicts the instruction from instruction #1. A personal name is a proper noun/name, is it not? So #1 says to use a hyphen there if the name has it already. OK, fine.

But then as-is, the "NEVER" from #3 turns right around and undoes the instruction from #1, because #1 gives a time to use it in a proper name, but then #3 takes it all away. That's why some kind of "unless" or "except" clause needs to be included: Never, except when..., etc.

2600:100E:B149:8DAB:F80C:D7D2:437F:F3BC (talk) 16:27, 19 August 2017 (UTC)

No. 3 says don't insert a hyphen (i.e. add a hyphen where there wouldn't otherwise be one); it doesn't say you must remove a hyphen that's already there for some other reason. Maybe a solution would be to change "never insert a hyphen into a proper name" to "never insert a hyphen into an unhyphenated proper name" (but strictly speaking this change is unnecessary if you understand what "insert" means). -- Dr Greg  talk  17:21, 19 August 2017 (UTC)

Just as I think, and said. This was met with the IP criticising my use of the word 'hash'! Your proposed change makes sense, so you have my support. –Sb2001 ^{talk page} 17:28, 19 August 2017 (UTC)

• How about, instead, changing never insert a hyphen into a proper name --> never add a hyphen to a proper name. Some intuition tells me that add a bit more connotes "putting one in where there wasn't one before" than does insert (though the denotation is the same).

Side note: MOS does not apply to MOS itself, with good reason. Trouting someone for using # in this context is uncalled-for. EEng 18:37, 19 August 2017 (UTC)

I would have said that a lot of your complaining about my comments was something for which there was no call. Why does MoS not apply within MoS? Your suggestion is good, though. –Sb2001 ^{talk page} 18:46, 19 August 2017 (UTC)

MOS doesn't apply to MOS for the same reason advice on writing a college essay isn't written like a college essay: they serve different purposes and need not – should not – be written the same way. MOS is written in a more relaxed style than is an article (e.g. uses contractions), sometimes refers to or addresses the reader, uses all kinds of formatting we'd never use in a articles, promiscuously mixes ENGVARS, and more. EEng 19:05, 19 August 2017 (UTC)

As I previously discussed, the importance of following a common writing style is lessened on the manual of style pages themselves, and by social convention Wikipedia editors will typically be more lax on non-article pages, to avoid going down uncollaborative sidepaths. So whether or not the manual of style strictly applies, for less formal pages intended for community interaction, it's generally best to not get in a slap flight over things like using the number sign. isaacl (talk) 20:32, 19 August 2017 (UTC)

(