Misplaced Pages

This is an old revision of this page, as edited by SMcCandlish (talk | contribs) at 02:38, 12 July 2017 (Collapse-boxing various huge tracts of noise.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This is the talk page for discussing improvements to the Manual of Style page.

Put new text under old text. Click here to start a new topic. New to Misplaced Pages? Welcome! Learn to edit; get help. Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed Shortcut WT:MOS

Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228Auto-archiving period: 7 days

Manual of Style

This page falls within the scope of the Misplaced Pages:Manual of Style, a collaborative effort focused on enhancing clarity, consistency, and cohesiveness across the Manual of Style (MoS) guidelines by addressing inconsistencies, refining language, and integrating guidance effectively.Manual of StyleWikipedia:WikiProject Manual of StyleTemplate:WikiProject Manual of StyleManual of Style This page falls under the contentious topics procedure and is given additional attention, as it closely associated to the English Misplaced Pages Manual of Style, and the article titles policy. Both areas are subjects of debate. Contributors are urged to review the awareness criteria carefully and exercise caution when editing. For information on Misplaced Pages's approach to the establishment of new policies and guidelines, refer to WP:PROPOSAL. Additionally, guidance on how to contribute to the development and revision of Misplaced Pages policies of Misplaced Pages's policy and guideline documents is available, offering valuable insights and recommendations.

For a list of suggested abbreviations for referring to style guides, see this page.

faq page Frequently asked questions Misplaced Pages's Manual of Style contains some conventions that differ from those in some other, well-known style guides and from what is often taught in schools. Misplaced Pages's editors have discussed these conventions in great detail and have reached consensus that these conventions serve our purposes best. New contributors are advised to check the FAQ and the archives to see if their concern has already been discussed. Why does the Manual of Style recommend straight (keyboard-style) instead of curly (typographic) quotation marks and apostrophes (i.e., the characters " and ', instead of “, ”, ‘, and ’)‍? Users may only know how to type in straight quotes (such as " and ') when searching for text within a page or when editing. Not all Web browsers find curly quotes when users type straight quotes in search strings. Why does the Manual of Style recommend logical quotation? This system is preferred because Misplaced Pages, as an international and electronic encyclopedia, has specific needs better addressed by logical quotation than by the other styles, despite the tendency of externally published style guides to recommend the latter. These include the distinct typesetters' style (often called American, though not limited to the US), and the various British/Commonwealth styles, which are superficially similar to logical quotation but have some characteristics of typesetters' style. Logical quotation is more in keeping with the principle of minimal change to quotations, and is less prone to misquotation, ambiguity, and the introduction of errors in subsequent editing, than the alternatives. Logical quotation was adopted in 2005, and has been the subject of perennial debate that has not changed this consensus. Why does the Manual of Style differentiate the hyphen (-), en dash (–), em dash (—), and minus sign (−)? Appropriate use of hyphens and dashes is as much a part of literate, easy-to-read writing as are correct spelling and capitalization. The "Insert" editing tools directly below the Misplaced Pages editing window provide immediate access to all these characters. Why does the Manual of Style recommend apostrophe+s for singular possessive of names ending in s? Most modern style guides treat names ending with s just like other singular nouns when forming the possessive. The few that do not propose mutually contradictory alternatives. Numerous discussions have led to the current MoS guidance (see discussions of 2004, 2005, 2005, 2006, 2006, 2007, 2008, 2008, 2008, 2009, 2009, 2009, 2012, 2013, 2015, 2016, 2017, 2017, 2017, 2018, 2018, 2019, 2021, 2022). Why doesn't the Manual of Style always follow specialized practice? Although Misplaced Pages contains some highly technical content, it is written for a general audience. While specialized publications in a field, such as academic journals, are excellent sources for facts, they are not always the best sources for or examples of how to present those facts to non-experts. When adopting style recommendations from external sources, the Manual of Style incorporates a substantial number of practices from technical standards and field-specific academic style guides; however, Misplaced Pages defaults to preferring general-audience sources on style, especially when a specialized preference may conflict with most readers' expectations, and when different disciplines use conflicting styles.

This is the talk page for discussing improvements to the Manual of Style page.

Put new text under old text. Click here to start a new topic. New to Misplaced Pages? Welcome! Learn to edit; get help. Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed

Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228Auto-archiving period: 7 days

Proposed demotion MOS:NOTUSA 23 May 2017

Please note that this thread follows on immediately to the OP's prior thread on the same subject, Misplaced Pages 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)

@David Eppstein: Over which abbreviation to use is like which spelling to use. And 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 Misplaced Pages'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 Misplaced Pages 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 Misplaced Pages'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 WP:VPPOL, where we have successfully resolved other contentious style matters with a more site-wide audience. A weak apparent consensus to use US emerging from a subthread of a thread about USA on the MoS talk page is unlikely to be accepted as a legit consensus by fans of U.S., so we'd just have to RfC it anyway. Since I'm seen as "partisan" on the matter, someone else should write the RfC (I have a broken wrist, anyway; typing more than 10 minutes is painful). I'm happy to contribute style guide and other source research. As in my last round of it, I would include material in favor of U.S. as well – also as with the similar research I did for the 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)

@Martin of Sheffield:: So, this is my first time participating in a community discussion here, and I didn't think it'd be possible to deeply offend someone by sharing an opinion on punctuation. No need for the snark, telling me to "stop and think" before I join the conversation, even if you figure my contribution is "thoughtless ignorance." That's awfully WP:UNCIVIL. If you feel I'm "implying anyone over 50 was archaic from generations ago," well that's on you. You're reading way too deep and have extracted an interpretation so far out of left field, I had to double-check and see if you were actually replying to me. I'm not slighting an age group, I'm simply saying dropping periods between capital letters is a holdover from the past and has become increasingly aberrant in modern writing. And while we're offering anecdotes, I'll add that I received all of my formal education in the US, and dot-free is my normal. @Sb2001: Didn't have an issue understanding. I appreciate you filling in the gaps for me. — GS ⋙ ☎ 08:32, 15 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:NOTUSA and 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 Misplaced Pages. 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. Misplaced Pages 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 Rhode Island is actually the State of Rhode Island and Providence Plantations, and the official name of the UK is actually the United Kingdom of Great Britain and Ireland, but 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

That vs. which for restrictive clauses

I am writing in support of Primergrey's recent edit to Misplaced Pages:Manual of Style. I also agree with the accompanying edit summary. I can understand Jon C.'s position, but I take issue with this edit summary:

It's only US English that has a problem with the "thing which…" construction.

US English is spoken by over 250 million people, many of whom read, and contribute to, Misplaced Pages. For most of those readers, the use of "which" for a restrictive clause is ungrammatical. How would you feel if in nearly every article on Misplaced Pages you might read, you come across a grammatical error that is repeated throughout the article? Since in British English and at least some of the variants such as Canadian, Australian, and Indian English both "which" and "that" are acceptable for restrictive clauses, why not use the word (at least in the Manual of Style if not elsewhere) that would make reading for speakers of US English easier and more pleasant? Speakers of US English who read and edit articles on Misplaced Pages already have had to adjust to the many articles written in British English, with the spelling differences and words such as "whilst" and "learnt", and some constructions, that are not even used at all in US English.  – Corinne (talk) 23:15, 29 June 2017 (UTC)

• How about a big no to instruction creep? Curly "JFC" Turkey 🍁 ¡gobble! 23:26, 29 June 2017 (UTC)

Given that we're instructed to strive for commonality, "that" seems like the obvious choice. Primergrey (talk) 23:34, 29 June 2017 (UTC)

So encourage it—don't regulate it. Curly "JFC" Turkey 🍁 ¡gobble! 23:39, 29 June 2017 (UTC)

• I also support the edit. Observing the that/which distinction is often recommended in Canadian English guides.--Trystan (talk) 23:45, 29 June 2017 (UTC)
• A big N-O, no. Before anything else let me say that Corinne and Primergrey are two of my favorite talk page stalkers. Nonetheless, if we apply Corinne's logic here on this page, then why not in articles too? MOS has long been an ecumenical zone where ENGVARs coexist. People just have to get used to that. (And see WP:MISSSNODGRASS#whichthat.) EEng 23:53, 29 June 2017 (UTC)
• I also support Primergrey's's edits. @Curly Turkey: there is no instruction creep here, in that the edits did not add any new instructions to editors to the MOS. All they did was to reword the existing instructions to avoid the problem that they were ungrammatical for US English. —David Eppstein (talk) 23:56, 29 June 2017 (UTC)

  You mean, prescribed against in formal American writing—average Americans have no problem with it. Curly "JFC" Turkey 🍁 ¡gobble! 00:01, 30 June 2017 (UTC)

  I question whether it's any longer an issue in any American writing. EEng 00:05, 30 June 2017 (UTC)

  I have honestly never met anyone in America who doesn't follow it in speech. -- Noneofyourbusiness (talk) 09:42, 30 June 2017 (UTC)

• I also support Primergrey's edit. I'm British, now live in Australia, and have worked for many UK, US and Australian book publishers. In my experience, "that" is far more commonly used than "which". JG66 (talk) 04:44, 30 June 2017 (UTC)

As little as buzzwords like "instruction creep" help at the best of times, it is of no relevance to this discussion. Reading the edit in question will reveal that it is not an addition of anything but is merely clarifying existing language. I actually had no idea this was an ENGVAR thing. I thought it was a "people that read closely deserve to not encounter the ambiguity that impresice writing can convey" thing. Primergrey (talk) 03:01, 30 June 2017 (UTC)

In other words, you buy into baseless prescriptions. Curly "JFC" Turkey 🍁 ¡gobble! 04:31, 30 June 2017 (UTC)

My position is based on clarifying meaning, as I've already said, so I don't know what you're on about. Further, no one is suggesting anything be prescribed. The change is to the language of the MOS itself. In other words, your assessment of what I do or do not buy into is light-speed wrong. Primergrey (talk) 05:44, 30 June 2017 (UTC)

Merriam-Webster also have something to say on the matter. --Boson (talk) 05:07, 30 June 2017 (UTC)

Hmm. We Brits, and I believe many Commonwealth English speakers, are rather relaxed about relative pronouns, and we wish to be allowed to stay that way. We use "which" differently from Americans, certainly. Much of the time they feel like close synonyms, and it is an effort to distinguish them. They do indeed have different applications, but we do not wish to be forced to write in a stilted way because American is different, or worse because American says so. A phenomenon up with which we will not put, even. Chiswick Chap (talk) 05:57, 30 June 2017 (UTC)

Support for a relaxed approach, i.e., rejecting Primergrey's edits, also comes from Australian English: Pam Peters (1995), The Cambridge Australian English Style Guide says that "that" is often used to lend an informal flavor to prose. Also, "The choice between that and the wh- relatives is sometimes said to depend on whether it prefaces a restrictive or nonrestrictive relative, with that for the restrictive type and which for the other ... This is an oversimplification of Fowler's original suggestion that they could be used that way, though even he admitted: It would be idle to pretend it was the practice either of most or of the best writers. Later style commentators note that while which is indeed preferred for nonrestrictive relative clauses, both that and which can be found with the restrictive type." Sminthopsis84 (talk) 02:24, 1 July 2017 (UTC)

My point above being that American is not (here) different—American prescriptivism is. Curly "JFC" Turkey 🍁 ¡gobble! 06:05, 30 June 2017 (UTC)

• There's a good case for commonality in pages, whether in mainspace or WP space, not marked as being in one ENGVAR or the other. However, it's not quite as simple as Corinne's statement that "both 'which' and 'that' are acceptable for restrictive clauses" in British English, so you don't get full commonality by sticking to American prescriptivism. As Chiswick Chap wrote, sometimes the American prescriptivist usage seems stilted to a British reader. In relation to the two changes under discussion, I find "an acronym is considered to be an initialism that is pronounced as a word" fine – I think because it can also be written as "an acronym is considered to be an initialism pronounced as a word" – "that" works well in British English when it can effectively be omitted. However, I would naturally write "do not mimic the style of local newspapers which refer to their municipality as 'the City'" – "that" here seems slightly odd to me. "Which" here corresponds to "who" in the equivalent sentence "do not mimic the style of local newspaper editors who refer to their municipality as 'the City'". Would US editors write "that" in this last example? Or perhaps insist on a comma if "who" is used? Peter coxhead (talk) 06:59, 30 June 2017 (UTC)

There's no support in the MoS or elsewhere for insisting on just one variety of English, nor should there ever be. That would be outrageous. Chiswick Chap (talk) 07:10, 30 June 2017 (UTC)

That's a different issue, though. Some pages are marked as being in one ENGVAR rather than the other, and no-one is going to argue (I assume) that differences in the usage of "that" vs. "which" shouldn't be upheld on these pages. The issue here is pages like the MoS that aren't marked as being in one particular ENGVAR. On these pages, there's a strong argument for communality where possible (e.g. using "-ize" spellings as in the Oxford variant of British English rather than "-ise" spellings). My point is that Corinne assumed that American prescriptivism over "that" and "which" equals commonality, and it doesn't. Hence I support the points made by Jon C and Pbsouthwood below: there's no good reason to make the change to the American prescriptivist style. Peter coxhead (talk) 08:37, 30 June 2017 (UTC)

(edit conflict) My view is that there's absolutely no good reason different varieties of English can't coexist on the MoS. They coexist elsewhere on WP, so why not here? Also, are you seriously suggesting the average American wouldn't understand a restrictive cause containing "which"? If you're not, there's no reason to make the change. — Jon C.ॐ 06:59, 30 June 2017 (UTC)

Does anyone seriously think the average American gets confused reading favour? Or the average Brit scratches their head when reading aluminum? If you read about the Grand Canyan wouldn't you know immediately what was meant? Based on your sole criteria, none of these would need addressing, ever.Primergrey (talk) 16:51, 1 July 2017 (UTC)

• Ain't broke, don't fix. (leave it as it was) Agree with Chiswick Chap, Jon C. etc. • • • Peter (Southwood) : 08:25, 30 June 2017 (UTC)

I've just checked in Thompson & Martinet where this issue is discussed. Summarising (§75, ¶¶A-C): as a subject, use either – which is more formal, as the object of a verb either (but which is proscribed in some circumstances), as the object of a preposition use which or separate the two. Clearly this is an English view (it is published by OUP) and may be criticised by inveterate modernisers as "archaic". Martin of Sheffield (talk) 08:56, 30 June 2017 (UTC)

The issue of formality is very relevant, I think. I definitely would use "which" more in writing in Misplaced Pages than in, say, an e-mail, because "which" does often feel more formal in British English, and it's one reason why "that" sometimes seems inappropriate to me. Peter coxhead (talk) 09:16, 30 June 2017 (UTC)

I agree with Primergrey, Trystan, David Eppstein, JG66 and Corinne. The Spell Check tool on my Microsoft Word underlines in green any use of "which" in such clauses instead of "that" and explains that there is a rule that either it must be "that" or, for it to be "which", it must follow a comma. Anyone using the same program would also be tripped up by the presence of "which". Whereas "that" doesn't make anyone go "hey!". I would also consider the fact that JG66 has UK, US and Australian publishing experience and supports "that" relevant. -- Noneofyourbusiness (talk) 09:30, 30 June 2017 (UTC)

Word also automatically superscripts the "nd" in "2nd", "th" in "4th", etc., which no one has done since Victorian times. Quite aside from the fact it's an American program, Word's not a reliable source.

Re publishing experience, I'm a journalist, FWIW. — Jon C. 10:22, 30 June 2017 (UTC)

Re superscripting – I thought that was due to typewriters and the need to move the platen roller down. Certainly I was taught to superscript at school and I can assure you the monarch then was our present Queen, not Victoria! I'd certainly superscript when handwriting, it avoids confusion between 1st and lst for instance. Agreed with your other points about Word though. Martin of Sheffield (talk) 10:48, 30 June 2017 (UTC)

• That which doesn't kill me makes me stronger. But this discussion kills me. EEng 11:57, 30 June 2017 (UTC) From comments elsewhere, it's apparently necessary for me to say explicitly that this post is something of a pun: that which – get it?

A few points:

1) I have read many articles on WP where it seems "which" is used exclusively for all relative clauses. The word "that" hardly appears in the article at all. Is that an indication that the word "that" is disappearing from British English? I think an article that uses "which" almost exclusively, leaving the article heavily sprinkled with the word, or any one word for that matter, is not elegantly written. Besides that, I agree with Primergrey that the distinction that is made by the use of "that" for restrictive clauses is an important one. Precision of meaning is lost when "which" is used nearly exclusively for both restrictive and nonrestrictive clauses. Speakers of American English who come across "which" used for a restrictive clause have to pause and quickly figure out whether it is a restrictive clause, or a nonrestrictive clause with the comma inadvertently left out – not necessarily using those terms, but conceptually. The nice thing about "that" for restrictive clauses is that it can often be left out, so it is used only when needed for clarity.

2) Thank you, EEng for your comments. Regarding your statement, above,

Nonetheless, if we apply Corinne's logic here on this page, then why not in articles too?

I would say, why not in articles, too? I repeat my main point: since both "which" and "that" are acceptable (which does not mean that it is necessarily one's preferred word) for restrictive clauses, why not use the one that is considered correct for most speakers of US English? I assume you would not support someone going through articles and changing "that" to "which" just because it sounds better to them. See this edit and the one just previous to it.

3) In reply to the question posed by Peter coxhead, above,

Would US editors write "that" in this last example? Or perhaps insist on a comma if "who" is used?

in reference to this sentence:

do not mimic the style of local newspapers which refer to their municipality as 'the City'.

Americans would use "that" after "newspapers", but because "refer" is more naturally applied to a person, it would probably read better as:

do not mimic the style of local journalists who refer to their municipality as 'the City'

with no comma after "journalists" because "who" begins a restrictive clause.

or: Do not mimic the style of newspapers that refer to the local municipality as 'the City'.

or: Do not mimic the newspaper style in which the local municipality is referred to as 'the City'.

4) In response to editors who object to the consistent use of "that" for restrictive clauses on the basis that it often sounds too formal, or "stilted", what about speakers of US English who find "whilst" and "learnt" not just stilted, but archaic, even foreign? If an American editor happened to change "whilst" to "while", a speaker of British English would vociferously object.  – Corinne (talk) 15:34, 30 June 2017 (UTC)

@Corinne: let me say first of all that I'm a great admirer of the work you do copy-editing and clarifying articles. Some points:

• Actually in British English in those cases where "which" and "that" are interchangeable, it's "which" which is felt to be more formal not "that" (as is said in one style guide referred to above by Martin of Sheffield). This is, I suspect, why you find what seems to you to be too many uses of "which" in some articles, since they are written in a formal style.
• I'd be extremely happy if you changed "whilst" to "while"; it seems somewhat archaic to me, which given my age suggests it really is!
• "Learnt" is a different issue. It's consistent with other words, like "meant", "sent", "bent", all of which can be derived from reduction of an "ed" ending after "n" or "nd". I see no reason to suppose that it's an archaism; it's just a different choice in the two dialects. It also clarifies "learned" as in "a learned scholar".

All of this is entertaining to those of us interested in discussing language (and annoying to those like EEng who clearly don't), but actually a bit off the point, which was how should we write in pages like the MoS which aren't specifically in one ENGVAR?. We all agree, I take it, that where commonality is possible, it should be adopted, but sometimes it isn't. What then? Must we all bow to US English? Peter coxhead (talk) 17:22, 30 June 2017 (UTC)

I am slightly disturbed by this thread centring on the idea that English should be written to make sense for those in the US. I do believe 'which' is more common in UK English, although I would use either. 'That' can often sound a bit odd. It does not seem necessary for an engvar to be applied. Americans need to learn to accommodate the original language which they are trying to take over, ie English ... the language of England. This will never go through to the MoS. Push for an engvar if you wish, just do not try to enforce your ridiculous Americanisms on those of us residing in the UK. -Sb2001 (talk) 18:05, 30 June 2017 (UTC)

Having now properly read the page, 'an acronym is considered to be an initialism pronounced as a word' sounds wrong. Totally incomprehensible. And, 'that is' is like 'ie', which means something different. Using 'which is' would avoid this problem. -Sb2001 (talk) 18:11, 30 June 2017 (UTC)

Please take your jingoism elsewhere. Primergrey (talk) 05:09, 1 July 2017 (UTC)

User:Primergrey: I very much hope that was not directed towards me...-Sb2001 (talk) 12:19, 1 July 2017 (UTC)

• This is one of the most confused MOS discussions I've seen, and that's saying a lot. Half the discussants are mixed up about which usage is British and which American. EEng 07:17, 1 July 2017 (UTC)

Is this actually an ENGVAR issue? from the discussion, I get the idea that the two words are somewhat interchangeable in both U.K. and US English. It seems to be more a question of formality than one of national variety. Blueboar (talk) 11:30, 1 July 2017 (UTC)

• It seems that neither which or that should be the default option: just allow editors to use whichever they like. They both make sense, and I am sure people will have no problem understanding them.-Sb2001 (talk) 12:39, 1 July 2017 (UTC)
• I support the edit Primergrey made to MOS's own usage; there's nothing ungrammatical about it, in any dialect or register, and it's helpful in preventing any ambiguity or confusion. Oppose any new rulemaking or changes to existing rulemaking on the matter, at least at this time. The ground truth of the matter is that some people draw a distinction, and few people can define it, so the results end up being inconsistent, even within the same dialect. If we made a change, it should be to avoid "which" when not explicitly restrictive (i.e., use "that" more).

  The rule-of-thumb, common-sense approach: "which" is best reserved for cases that are definitely restrictive, and usually also include a comma, dash, or other "parentheticalizing" clause separator in the construction. "The train that stops in Fremont" is a general, unrestrictive reference. It is equivalent to "Of all the trains in this transit system, the one (or possibly ones) that stop in Fremont ...". By contrast, "the train, which stops in Fremont," is highly restrictive; we are already referring to a particular train in a particular context. It is equivalent to "this train we've been talking about – and it happens to stop in Fremont – ...". Usage of "The train which stops in Fremont" is ambiguous and should be avoided, more so every day as comma habits become more and more sloppy, though the influences of various forces as diverse as SMS laziness to explicit anti-punctuation efforts by certain circles (especially UK newspaper publishers). We can no longer depend upon readers being able to automatically distinguish that "the train which stops in Freeont" means "the train that stops in Fremont" rather than "the train, which stops in Fremont," because a non-trivial number of writers drop the commas in the latter. It's stupid, but it's demonstrably happening.
   — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  22:31, 4 July 2017 (UTC)

User:SMcCandlish: Interestingly enough, I never would have thought that I had anything against use of 'that'. This discussion has prompted be to think differently: 'the train which' reads much more freely than 'the train that'. I suppose it is just what I am used to. I think that readers in the UK will be more familiar with 'which', and 'that' may seem somewhat clunky. On the other hand, those in the US (and wherever else it is a rule) may think that 'which' is wrong and confusing. I think it is probably best left as is. I do not think it is new in the UK to use 'which' for non-restrictive clauses. It is pretty much all you hear: my surprise at seeing 'that' in one of your sentences - I cannot remember which - is a clear example of this. -Sb2001 (talk) 22:39, 4 July 2017 (UTC)

This is another WP:IKNOWIT argument, though. No one is asking "who is more familiar with what?"; the question is "what are the ambiguity or other comprehensibility problems, and how are they best avoided?" Avoiding them often involves doing things that aren't the most familiar option (which will usually be an informal one) for some people. The fact that variation exists probably means it will necessarily be the case that any solution will be not-the-most-familiar option to some people. Given the ubiquity of trans-Atlantic communication today, it isn't credible that either approach is unfamiliar to anyone; one is simply less likely to be ambiguous or confusing. But, as I said, I don't support changing MoS about this, only changing it in this direction should a change be deemed necessary by consensus, against my view that we need no change. PS: I habitually use "the train which stops in Fremont" myself; I just concede that it's not the clearest option.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  02:48, 6 July 2017 (UTC)

MOS:TIME

I do not know whether other editors have found this to be an issue, but MOS:TIME states that 'colons separate hours, minutes and seconds'. The problem here is that UK standard is to use a full stop for 12-hour time. I have yet to find a UK style guide which advises otherwise, including New Hart's Rule, of which I am not a massive fan (please do tell me if there is one). Editors seem to come to UK articles and change the tie notation, quoting MOS:TIME as the reason. My query is whether it would be too much of a problem to just drop this line. Editors in the US may continue to write time using a colon, and those in the UK may use either (: is often used for 24-hr). -Sb2001 (talk) 19:11, 30 June 2017 (UTC)

Occasionally time is expressed as hours and a decimal fraction of an hour, such as 10.5, 10.25, or 10:255 (10:30, 10:15, and 10:15:30 respectively). So there is a potential for ambiguity. Jc3s5h (talk) 19:27, 30 June 2017 (UTC)

University of Oxford and BBC use a colon. Use a colon. DrKay (talk) 19:29, 30 June 2017 (UTC)

Oxford says, 'The 12-hour clock uses a full stop between the hours and minutes; the 24-hour clock uses a colon and omits am/pm' and the BBC says, 'We use the 24-hour clock (with a colon) in all circumstances', so does not address 12-hour time. In response to the decimal point, it never seems to confuse people. I do understand what you are saying, though. We should - therefore - limit full stop usage to 12-hour time and require an am/pm suffix, eg 4.30pm. -Sb2001 (talk) 19:35, 30 June 2017 (UTC)

OK, try UK government (go to T for times) or University College London. DrKay (talk) 19:53, 30 June 2017 (UTC)

I feel using a colon for 24 hour times but a full stop for 12 hour times would be confusing. Very few readers would ever guess that this comes from the advice of a handful of UK style guides. I fear readers will suspect a hidden meaning that doesn't actually exist. Jc3s5h (talk) 20:07, 30 June 2017 (UTC)

People in the UK use this format, so the idea that it would not be understood is not appropriate. -Sb2001 (talk) 20:45, 30 June 2017 (UTC)

It isn't good enough that people in the UK wouldn't be confused; as far as possible, no one who is proficient in English should be confused. If the full stop confuses quite a few people and the colon confuses hardly anyone, we should stick with the colon. Jc3s5h (talk) 21:25, 30 June 2017 (UTC)

You are taught in UK education (every establishment I have attended/know people who have attended) teaches that use of the colon is incorrect for 12-hour. Yes, they actually teach you how to write the time in the later stages of education! I am sitting here, in front of the television. The BBC, ITV, Channel 4 and Channel 5 have ALL displayed television listings with 12-hour time using the full stop. It is standard. The colon is not widely used, and I know some people who are confused by it: people who have little experience of the slowly globalised UK in which we seem to be living do not understand what the colon shows. The Guardian, the Times, the Telegraph, the Mirror, the Sun, the Mail ... all use the full stop. As does the bus timetable I have in my house. I received an email today advertising a meeting at '6.30pm'. I saw a poster telling me of a class at '4.10'. I have looked through the paperwork I have here, and NONE of it has a colon to show time. There should be no requirement to follow an American standard. The MoS should allow freedom, ie not specify a punctuation mark to use. Please do not say 'the colon confuses hardly anyone': this is simply untrue. -Sb2001 (talk) 21:53, 30 June 2017 (UTC)

I'm writing this logged out deliberately, so that you can locate my IP and prove that I'm in England. Not once, ever, has any teacher told me to use a dot instead of a colon. I've worked as a copy editor and published professionally. No-one in Britain is confused by a colon between hours and minutes. 109.158.111.186 (talk) 06:19, 1 July 2017 (UTC)

I think this is a better of personal experiences. I am sure you will accept that the very vast majority of people do use a full stop, though. -Sb2001 (talk) 12:37, 1 July 2017 (UTC)

• Fine, some do say colon. This is only two. Common usage is for a full stop, and the overwhelming majority of style sides in the UK use that. Let us now debate/discuss the issue properly, rather than quoting style guides. I do appreciate the contribution: it is good to know from where advice comes. Also, barely anyone uses a colon for 12-hour in the UK and there are never any problems. I would show you some examples from my experiences - letters, posters, timetables etc - if possible. -Sb2001 (talk) 20:12, 30 June 2017 (UTC)

Please go through the archives of this page, and of WP:MOSDATES, review the many discussions on this subject, and then, if you feel you have some new argument no one's thought of bring it back here. We just can't keep relitigating everything over and over from scratch. EEng 20:22, 30 June 2017 (UTC)

I have looked at many pages of archives. There are not many specifically relevant discussions. I think we should wait for some UK editors to contribute to this. I am sure there will then be some reassurance that there is no confusion in full stop usage. -Sb2001 (talk) 20:45, 30 June 2017 (UTC)

EEng 21:08, 30 June 2017 (UTC)

Thank you, User:EEng: I have reviewed this link. There are some good points raised by both sides. I do not see why it would be unreasonable to allow the use of the full stop, instead of effectively discouraging its usage when it is often said to be incorrect for 12-hour time. I am sure everyone will understand that 4.30pm is a time. -Sb2001 (talk) 12:37, 1 July 2017 (UTC)

It's not unreasonable, it's just that so far it appears to be a change you'd like because you'd like it. In general I'm against MOS overprescribing – editors on any given article should work out little choices like this for themselves. But I'm also in favor of not fixing that which isn't broken. What problem are you solving here? Huge amounts of time have been spent tinkering with the rules on units of measure (choice of units, which is primary/secondary, how to present conversions) because they've been a chronic source of trouble and there's real benefit to putting an end to such conflict. In contrast, in ten years I can't think of a single dispute, ever, over colon-or-dot for time of day. I can only vaguely remember one or two times I've ever run into an article that used dot, and there was no trouble over regularizing those to colon.

I have no doubt that, as you say, there were good arguments on both sides in past discussions. But in the end the consensus was for colon only, and so far everyone seems perfectly happy with that – except you. EEng 14:46, 1 July 2017 (UTC)

"4.30pm" is not fine outside of UK. I'm in US, and that looks like some unknown mistake to me -- info loss. Per MOS:COMMONALITY, we should use common spelling/styles where available -- that's ":". --A D Monroe III (talk) 17:19, 1 July 2017 (UTC)

• My concern is that using the dot will cause actual confusion for US readers... if a US reader sees "4.25" he may think it is a decimal reference, meaning 4 and 25/100 (or four and a quarter) - which would be "4:15". However, UK readers will not be confused if they see "4:25"... she may think the colon stylistically archaic, but at least she knows what it actually means. The potential for confusion (and even harm) outweighs any ENVAR arguments here. Blueboar (talk) 21:28, 1 July 2017 (UTC)
• Maybe it is a good idea to avoid 12-hour time then, and use your beloved colon for 24-hour instead. I have spoken with some people I know in the US (British), and they have informed me that whilst people do generally use the colon, you will occasionally encounter the full stop being used. They write it, and NOBODY has had any problem understanding it. -Sb2001 (talk) 23:41, 1 July 2017 (UTC)

It may be useful to note that hotels in the UK provide information for breakfasts etc with a full stop being used. I am staying in one at the moment. It employs that style. Surely they would not do something which confuses some people. After all, the majority (?) of their guests are not from the UK.-Sb2001 (talk) 23:43, 1 July 2017 (UTC)

• Concur this is not an ENGVAR matter. It's a style variant we do not need to entertain. It adds nothing useful but has an enormous potential for confusion. The claim that it's a norm and that UK style guides agree on it has been refuted. The "4:01 p.m." (or "4:01 pm") format MOS and MOSNUM already recommend is universally recognizable. Finally, ENGVAR only applies to situations in which which MOS and WP have no reason to prefer one version over the other, e.g. neighbor versus neighbour, and one better fits the subject matter due to strong national ties. In a case like this, there is a very clear reason (the ambiguity of "4.01") for us to prefer one over the other, so ENGVAR cannot apply, even if the "it's a British norm" argument were not bogus. (As with several other things under discussion lately, like "eg" for "e.g.", and lowercasing acronyms to things like "plc", it's something observable and common primarily in British news and government writing (styles WP does not use) but it is not consistently used, in any dialect, so who cares?

  PS: Both the UCL and gov.uk links are to house style guides for use internally (and specifically for web pages) only by those entities; they are not guidance for the public, but for employees of specific entities, and are specific to that particular insider context. If you've ever worked on an in-house style book, you know how disconnected from external concerns such things are, and that they are products not of expertise but of political and personal wrangling in committees full of people who don't know what they're talking about, and principally motivated by marketing concerns.
   — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  02:38, 6 July 2017 (UTC)

• I favour the colon for 12- and 24-hour times. It's readily apprehendable by everyone; it's not an engvar issue; and it avoids potential confusion with a decimal point. Tony (talk) 13:28, 7 July 2017 (UTC)
• Update: Date and time notation in the United Kingdom now has a bunch of additional sourcing. Styles vary, and the MoS-prescribed "1:45 p.m." and "13:45" are well-attested in British usage, though "1.45 p.m.", "1.45 pm", "1.45pm" and "13.45" are as well.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  00:47, 10 July 2017 (UTC)
  PS: Decimal time systems do exist, and some of them use the "." in this manner. Not sure that really equates to a confusion potential (how many readers use decimal time, and how many of those expect to see it used on a website like ours?). But still, it is "a thing".  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  00:52, 10 July 2017 (UTC)

Well I for one regularly use it. If I've worked from 09:30 to 11:15 on a particular project that is 01:45 which is booked on my time sheet as 1.75hrs. Martin of Sheffield (talk) 22:53, 10 July 2017 (UTC)

Using parenthetical disambiguation

Which article title format is correct according to the Manual of Style?: Party government XXXX–XX or Party government (XXXX–XXXX). Below are several of the articles I am thinking of moving:

• Whig government 1714–17
  • Whig government (1714–1717)
• Tory government 1783–1801
  • Tory government (1783–1801)
• Canningite government 1827–28
  • Canningite government (1827–1828)
• Liberal government 1859–66
  • Liberal government (1859–1866)
• Conservative government 1866–68
  • Conservative government (1866–1868)
• Unionist government 1895–1905
  • Unionist government (1895–1905)

One user has put it to me that the "Party government XXXX–XX" format is a natural disambiguation, but I'm not so sure.--Nevé–selbert 18:45, 3 July 2017 (UTC)

I don't know about parens vs. no parens, but for a long time MOS expressed a general preference (not specifically in article titles) for ranges of the form XXXX–XX. This was changed a year or two ago to a preference for XXXX–XXXX. I think this may be part of the issue. EEng 19:04, 3 July 2017 (UTC)

One reason for that change is that 2004-05 is ambiguous: does it mean the two year range 2004–2005, or does it mean May 2004? The hyphen vs en-dash can disambiguate it (hyphen for YYYY-MM, en-dash for YYYY–YY) but that can be hard to see and is not always used consistently. But I'm not convinced the parens are needed here. We use titles of the form "Title (disambiguator)" only when there is a good reason not to choose a different title that would be unambiguous without the disambiguator. And here the year range is an important part of the title. It's not like the real title should be "Tory government" and you're only adding the 1783–1801 to disambiguate it from all those other topics whose title is also "Tory government": the actual title of the article and not just the disambiguator should have the year range. So I would prefer the current title, "Tory government 1783–1801". But the two-digit years should be changed to four-digit years. —David Eppstein (talk) 19:16, 3 July 2017 (UTC)

I can understand both. My preference is for XXXX-XX, but I am unsure of whether it is a good idea to ignore a style which goes against the MoS. This creates inconsistency: if you see it, change it. -Sb2001 (talk) 19:33, 3 July 2017 (UTC)

It would be permissible to use commas in these constructions, e.g. Whig government, 1714–1717. An argument could be made that moving many pages to this format away from parenthetic will better comply with both WP:NATURAL and WP:CONCISE. This would apply to any case in which what is presently in parentheses is not a clarifying classifier (as in "Robert Smith (biologist)") but a scope-narrower indicating a WP:SUMMARY/WP:SPLIT situation of a single topic being broken up over many articles. But this is all really a discussion for WT:AT; this isn't MoS material. PS: Yes, the primary reason for moving from "1714–17" to "1714–1717" was date amibiguity is some ranges, but it's also just a readability matter. It is much easier to parse "1714–1717" than "1714–17" as a date range without even having to stop and think about it. We made the same move much earlier for page number ranges in citations, for the same reason.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  19:22, 4 July 2017 (UTC)

Note... regarding the question of whether to have parens or not... according to our WP:Article titles policy, both parenthetical and non-parenthetical disambiguations are allowed. The policy lists several disambiguation methods, and leaves the determination of which method is best up to editorial opinion (to be determined by project consensus - or even local article level consensus). This is one of those areas where we intentionally chose NOT to set firm wiki wide "rules", but have allowed editors latitude to do what they would prefer. I would agree with SMC as to the date presentation. Blueboar (talk) 12:18, 6 July 2017 (UTC)

whether to have parens: Parens should be treasured. When you're older you'll appreciate all they've done for you. EEng 12:22, 6 July 2017 (UTC)

Overcapitalization of "vol." and "no."

Presently we have text in WP:MOS that says "write volume two, number seven or Vol. 2, No. 7." This appears to conflict with common practice, and with MOS:CAPS. Under no other circumstance would we permit capitalization of a common noun simply because it's abbreviated (and "no." is an abbreviation, of Latin numero, which is not written Numero; see also "etc.", "cf.", "e.g.", and a zillion other Latinisms in English, which are uniformly lowercased). I would suggest that this be changed to "vol. 2, no. 7".

Regardless, this section should probably also be moved to MOS:NUM, and only summarized here in compressed form. MOS:NUM doesn't have anything on this, but it is the obvious place to look, and we're trying to move nit-picks out of the main MOS to the, well, nit-pick pages.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  22:06, 4 July 2017 (UTC)

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_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:CAPS says, "Misplaced Pages avoids unnecessary capitalization." Let's stick with that philosophy. It might be good to put the advice into MOS:CAPS or WP:CITE rather than (or in addition to) 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 WT:Citing sources. If you don't want to discuss citations in general, only the ones produced by Citation Style, 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 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 parenthetical references, should continue to follow WP:CITESTYLE/WP:CITEVAR. I do not believe there is a compelling reason to have a policy for citations that would force capitalization in citations to go against the citation style being used (unlike 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)

• Update: Additional sources (UK, Australian, Canadian):

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)

Related matters: dropping the dot, and MOSABBR

Some side issues: Despite MOS and WP:MOSABBR discouraging dropping of dots (points, periods, stops) from abbreviations except where utterly conventional and non-ambiguous (e.g., "Dr Smith" and "St Stephen" in British ENGVAR), I keep running into "No 1" in various articles (e.g. here). This is intolerably ambiguous, especially for users of screen readers, though it produces confusing gibberish for everyone, like "No of discs" in infoboxes . Worst of all (so far): table header labeled "No" . Also saw a "No total" in one of these. We need to explicitly state that No. (whether we keep that capitalized or not) must retain the dot and is not an ENGVAR matter (sourcing above demonstrates this; both New Hart's and Fowler's retain the dots).

Second, neither vol. nor no. appear at MOS:ABBR but of course should be listed, since we use them frequently. I'll wait until the discussion above concludes before adding them, so that what gets added doesn't have to be changed later.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  02:55, 11 July 2017 (UTC) PS: Ha ha, I rickrolled Misplaced Pages.

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)

Using plc (not PLC) after British company names

Please see discussion at Misplaced Pages talk:Manual of Style/Abbreviations#Widely used abbreviation for public limited company

Someone recently changed MOS:ABBR to permit "plc", in imitation of the preference of particular companies. This appears to conflict with: a) WP:MOS on treatment of acronyms, b) the rest of MOS:ABBR on treatment of acronyms, c) MOS:TM on not emulating trademark stylization, and d) MOS:CAPS on treatment of acronyms.

Cleanup work

MoS talk fragmentation

• BTW, when I raised this at the MOS:ABBR talk page 3 months ago, as suggested above, I was pretty much "trying to move nit-picks out of the main MOS to the, well, nit-pick pages". Was that a mistake? Should I have generally waited longer, or done something else to draw attention from knowledgeable and interested editors? – Reidgreg (talk) 11:27, 6 July 2017 (UTC)
  • We should probably consider centralizing MoS discussion, by redirecting all the MoS subpages' talk pages to this one. As the editorial pool shrinks, these subpages are increasingly likely to wander off into WP:CONLEVEL problems, PoV forking from the main MoS page. This has happened intermittently since at least 2012, and seems to be happening more frequently now. The remaining editors who watch these pages do not have the time or energy to go to all of them every day or even every week. Centralization of discussion is generally recommended, and doing it here would also prevent a lot of discussion forking, and the obviate the ncessity to notify MoS talk page A of discussions on MoS talk page B that are relevant to both. The problem with MoS itself is it's too much information in one page, needing some details merged off of it into subpages; but the discussion problem is one of fragmentation into numerous and often redundant threads that do not get enough input to reach consensus.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  23:32, 6 July 2017 (UTC)

it's and its

Is there a MoS for the spelling of the term which means "belonging to it"? I note that wiktionary claims that it's is depreciated and non-standard use. However I don't see this reflected in the MoS. It seems to me that if Joshua's car means a car belonging to Joshua then it ought to be correct to say "It's car" meaning a car belonging to it. I'd agree it isn't a very elegant way to write, but I'd say it is different to the use in the phrase The tree had lost all of its leaves because we wouldn't say The tree has lost all of Joshua's leaves, which seems clumsy and wrong. In the latter case we'd say "The tree has lost all of his leaves" so it is possible to replace his with its in that context. JMWt (talk) 09:01, 6 July 2017 (UTC)

• It's = it is (less commonly it has).
• Its = belonging to it.

See apostrophe. Martin of Sheffield (talk) 09:09, 6 July 2017 (UTC)

Yes but I'm asking about the MoS. And thinking harder about it, if its is interchangeable with his/her then it ought also to be correct to say "its car" in the same way as "his car", but the problem is that we wouldn't say "ones car", I think we'd use the apostrophe to say "one's car", so somehow we're saying it is wrong to use the apostrophe on it but not on one or when indicating the noun's possession at the start of a phrase. JMWt (talk) 09:13, 6 July 2017 (UTC)

This is the English Wiki, so MOS follows standard English grammar. Modern English does normally form the genitive with apostrophe-s but there are special cases. Consider ox-oxen or child-children. "His" is an irregular genitive of "he", were you to use "he's" it would be mistaken for "he is". Likewise "its" is the only genitive form of "it". "It's" is always a contraction of "it ...s" which reflects speech patterns: "it's a nice day today" , "it's been a while since I saw you" . Martin of Sheffield (talk) 09:47, 6 July 2017 (UTC)

MoS doesn't cover spelling or grammar basics, and doesn't need to. This is a matter of basic fluency/competence. It's for its and vice versionversa are common typographical errors, including among professional writers. Just fix it when encountered.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  23:42, 6 July 2017 (UTC)

"Vice version"? Let's see... would that be, for example, My Secret Life, Second Edition? EEng 17:14, 7 July 2017 (UTC)

Fixed. With a broken arm, I'm a bit reliant on software auto-correction and sometimes it is wrong and I don't catch it.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  21:02, 8 July 2017 (UTC)

Bodie and Doyle sure ain't got nothing on you two. Martinevans123 (talk) 21:31, 7 July 2017 (UTC)

There may be an exception for Cousin It or It (film), but possessive for a regular it is "its". AngusWOOF (bark • sniff) 23:47, 9 July 2017 (UTC)

Wicked me, I was tempted to try to add an actual example based on The Addams Family, but it turns out the proper spelling is Cousin Itt. EEng 00:09, 10 July 2017 (UTC)

Scrolling lists?

Hello, as I think I might be interpreting MOS:SCROLL incorrectly, could somebody tell me if the usage I have made here (the six images) is acceptable or not? Without it, the last image overflows outside of the white frame and into the gray space. I would've put them into a gallery, but the fact that they are templates doesn't let me do that easily. — Anakimi_talk   18:44, 9 July 2017 (UTC)

@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)

Roman Catholic

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 Roman Catholic". I usually alter this to say "Catholic", given that the word "Roman" seems entirely redundant. I appreciate that - well, essentially, the stuff in the lead of Catholicism is so - but AFAIK in ordinary usage the word "Catholic" alone is always interpreted as referring to the Catholic Church, and as such "Roman" doesn't alleviate any actual confusion on the part of the reader. Comments? Pinkbeast (talk) 16:57, 10 July 2017 (UTC)

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. Misplaced Pages 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 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 Misplaced Pages, usually for similar precision, disambiguation, and other clarity reasons.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  19:11, 10 July 2017 (UTC)

Use of "foot per inch" instead of "feet per inch" in article titles

Please see Misplaced Pages talk:Naming conventions (plurals)#'Measurements involving two or more units (such as pounds per square inch or miles per hour) should usually have the first word in the plural'; while this discussion isn't strictly an MoS matter, changes to title style often affect in-article usage, and attempts to gather more editorial input into the question by "advertising" the discussion haven't been very successful so far, so posting about it here might bring some additional eyes and brains.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅_ᴥⱷ≼  19:09, 10 July 2017 (UTC)

"Sir" is an honorific prefix, not a forename

"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)

"The internet" and "the web"

Somewhere I thought we were already addressing this, but I don't find it in MOS:MAIN, MOS:CAPS, or MOS:PN. We really should address this. The Internet and the Web (short for the World Wide Web, which no one says any more) are proper names; they are specific, unique things like the Pacific Ocean and the language French. Journalism style guides (Misplaced Pages is not written in news style) have been pushing hard to lowercase these, but they're factually wrong to do so when the do it to the Internet and the Web.

Lower-case internet as a noun means "a (i.e. any) network of networks". Various internets combined to form the Internet, and there are internets that were not and still are not part of it (though various internets are also part of the Internet today). Due to ambiguity, internetwork or inter-network – or more recently a completely different term, wide-area network – has usually been used instead.

Lower-case web as a noun is something a spider makes, with various metaphoric applications of the word ("a web of trust", etc.).

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)