# Nitpick your fellow Dopers

**URL:** <https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583>\
**Category:** Miscellaneous and Personal Stuff I Must Share\
**Created:** [June 15, 2023, 8:49pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583 "2023-06-15T20:49:28Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![commasense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/commasense/32/3017_2.png) [@commasense](https://boards.straightdope.com/u/commasense)\
**Post date:** [June 15, 2023, 8:49pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/1 "2023-06-15T20:49:29Z")

</div>

Here’s your chance to (gently) scold your fellow Dopers for all the little things they do that annoy you, reasonably or not. No need to name names, and since this isn’t the Pit (yet), please keep it civil.

I’m a former copy editor, so many of my nitpicks fall in that realm.

**Quoting multiple paragraphs of text:** First of all, here on the SDMB, why not just use the [quote] function? That would obviate the need for my nitpick.

Which is, that in book and periodical publishing for well over a century, the nearly universal standard for multi-paragraph quotations has been to put an open quote mark at the _start of each paragraph,_ but a close quote mark _only at the end of the entire quotation._ Like so:

"Paragraph 1.

"Paragraph 2.

“Paragraph 3.”

Although this style may seem illogical, especially for those who may have done some computer coding, it serves a practical purpose: it indicates to the reader at the start of each new paragraph that you are still quoting. The alternative I often see here, putting open and close marks only at the start and the end of the whole body, can make the reader think that the second and subsequent paragraphs are the original author speaking again. Or alternately, it can break the readers’ flow by sending them to the ends of the next few paragraphs searching for the close quote mark.

Along with this style is the necessity to change any double quotation marks within the quoted text to single, and any nested single quote marks within _them_ to double, and so on. Or if you’re British, you start with single quotes on the outside and do the opposite.

**Verbs ending -ead whose past tense is -ed.** The past tenses of the verbs lead, mislead, and plead are led, misled, and pled, respectively. They are not, like “read,” spelled the same in past and present tense. (ISTM that “pleaded” is an acceptable alternative, but “plead” pronounced as “pled” is not. )

**Lose vs. loose.** You can lose a game and have loose trousers. You can loose (ie, let loose or release) the dogs of war. But you can’t loose a game.

Your turn.

---

<div class="post-metadata">

**Author:** ![Little\_Nemo](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/little_nemo/32/3120_2.png) [@Little\_Nemo](https://boards.straightdope.com/u/Little_Nemo)\
**Post date:** [June 15, 2023, 8:55pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/2 "2023-06-15T20:55:41Z")

</div>

> [@commasense](#):
>
> But you can’t loose a game.

My understanding is plenty of companies loose underdeveloped games on to their customers.

---

<div class="post-metadata">

**Author:** ![Little\_Nemo](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/little_nemo/32/3120_2.png) [@Little\_Nemo](https://boards.straightdope.com/u/Little_Nemo)\
**Post date:** [June 15, 2023, 8:57pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/3 "2023-06-15T20:57:20Z")

</div>

But to get in the spirit of the thread, I get annoyed by the overuse of ellipses. They serve a purpose but they should be reserved for situation where the writer intends a pause and not just indicate he’s run out of thoughts.

---

<div class="post-metadata">

**Author:** ![Crafter\_Man](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/crafter_man/32/458_2.png) [@Crafter\_Man](https://boards.straightdope.com/u/Crafter_Man)\
**Post date:** [June 15, 2023, 8:57pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/4 "2023-06-15T20:57:56Z")

</div>

There’s one long-time Doper that does something that (slightly) annoys me every time he does it. He likes to use colons in sentences, and the next word after the colon starts with an uppercase letter. Like this:

> An electron is a point particle: **I** t doesn’t have a known or defined radius, and it’s likely the radius is zero.

The I in “It” should be lowercase, not uppercase.

---

<div class="post-metadata">

**Author:** ![Pleonast](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pleonast/32/1183_2.png) [@Pleonast](https://boards.straightdope.com/u/Pleonast)\
**Post date:** [June 15, 2023, 9:03pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/5 "2023-06-15T21:03:47Z")

</div>

> [@commasense](#):
>
> **Verbs ending -ead whose past tense is -ed.** The past tenses of the verbs lead, mislead, and plead are led, misled, and pled, respectively. They are not, like “read,” spelled the same in past and present tense. (ISTM that “pleaded” is an acceptable alternative, but “plead” pronounced as “pled” is not. )

Also, “lit” is the past tense of “light”, not “lighted”.

But I think these are dialectal variants becoming more widespread. There seems to be a strong inclination to make all verbs regular.

---

<div class="post-metadata">

**Author:** ![Chefguy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chefguy/32/138_2.png) [@Chefguy](https://boards.straightdope.com/u/Chefguy)\
**Post date:** [June 15, 2023, 9:05pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/6 "2023-06-15T21:05:09Z")

</div>

People who use semicolons; it’s so pedantic.

---

<div class="post-metadata">

**Author:** ![Maserschmidt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/maserschmidt/32/18829_2.png) [@Maserschmidt](https://boards.straightdope.com/u/Maserschmidt)\
**Post date:** [June 15, 2023, 9:05pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/7 "2023-06-15T21:05:34Z")

</div>

Hmmm, the AP style book says capitalize the first letter if it’s a complete sentence after the colon. The Chicago style book says not to.

> **[How to use the colon](https://archives.cjr.org/language_corner/how_to_use_the_colon.php#:~:text=The%20Associated%20Press%20Stylebook%20says,it%20is%20a%20complete%20sentence.%E2%80%9D)**
>
> Understand its usage once and for all

---

<div class="post-metadata">

**Author:** ![Pardel-Lux](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pardel-lux/32/20182_2.png) [@Pardel-Lux](https://boards.straightdope.com/u/Pardel-Lux)\
**Post date:** [June 15, 2023, 9:11pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/8 "2023-06-15T21:11:20Z")

</div>

I like using colons, but I never thought of using uppercase letters after it: I think I will start now. In this case, I had no other option.

---

<div class="post-metadata">

**Author:** ![SCAdian](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/scadian/32/3292_2.png) [@SCAdian](https://boards.straightdope.com/u/SCAdian)\
**Post date:** [June 15, 2023, 9:22pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/9 "2023-06-15T21:22:21Z")

</div>

> [@Pleonast](#):
>
> Also, “lit” is the past tense of “light”, not “lighted”.

“Sailors get lit – lamps get lighted.”

---

<div class="post-metadata">

**Author:** ![solost](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/solost/32/11776_2.png) [@solost](https://boards.straightdope.com/u/solost)\
**Post date:** [June 15, 2023, 9:57pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/10 "2023-06-15T21:57:54Z")

</div>

> [@Chefguy](#):
>
> People who use semicolons; it’s so pedantic.

How about people who criticize you for ending a sentence with a proposition? That is the kind of arrant pedantry up with which I will not put!

---

<div class="post-metadata">

**Author:** ![needscoffee](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/needscoffee/32/1076_2.png) [@needscoffee](https://boards.straightdope.com/u/needscoffee)\
**Post date:** [June 15, 2023, 10:09pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/11 "2023-06-15T22:09:16Z")

</div>

> [@commasense](#):
>
> (ISTM that “pleaded” is an acceptable alternative

Actually, “pleaded” is the preferred form (at least in law).

---

<div class="post-metadata">

**Author:** ![ThelmaLou](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/thelmalou/32/390_2.png) [@ThelmaLou](https://boards.straightdope.com/u/ThelmaLou)\
**Post date:** [June 15, 2023, 10:28pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/12 "2023-06-15T22:28:43Z")

</div>

One of my major peeves is someone using an _apostrophe-s_ to create a plural. Just don’t do it! The apostrophe-s is for possessives and contractions (leaving out a letter).

For example, when referring to multiple members of the Biden family, the word is “Bidens” not “Biden’s.” _The Bidens are going to Mars for their vacation._ The Decade of Luv was the “1960s” not the “1960’s.”

If a person isn’t 100% sure about apostrophe rules, you will look less like an uneducated ignoramus if you sometimes leave out an apostrophe than if you use lots of them wrong.

I’m not even going to bother mentioning ITS and IT’S, as that is a lost cause.

[![](https://i.imgur.com/oiivCWk.jpg) ](https://i.imgur.com/oiivCWk.jpg)

---

<div class="post-metadata">

**Author:** ![Walken\_After\_Midnight](https://avatars.discourse-cdn.com/v4/letter/w/b487fb/32.png) [@Walken\_After\_Midnight](https://boards.straightdope.com/u/Walken_After_Midnight)\
**Post date:** [June 15, 2023, 10:38pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/13 "2023-06-15T22:38:42Z")

</div>

> [@commasense](#):
>
> Or alternately, it can break the readers’ flow…
> 
> Or if you’re British, you start with single quotes on the outside and do the opposite.

Should there not be a comma after “or” in these cases?

---

<div class="post-metadata">

**Author:** ![Walken\_After\_Midnight](https://avatars.discourse-cdn.com/v4/letter/w/b487fb/32.png) [@Walken\_After\_Midnight](https://boards.straightdope.com/u/Walken_After_Midnight)\
**Post date:** [June 15, 2023, 10:40pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/14 "2023-06-15T22:40:42Z")

</div>

Yeah, it was the '60s, not the '60’s.

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [June 15, 2023, 10:42pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/15 "2023-06-15T22:42:03Z")

</div>

> [@commasense](#):
>
> **Quoting multiple paragraphs of text:** First of all, here on the SDMB, why not just use the [quote] function? That would obviate the need for my nitpick.
> 
> Which is, that in book and periodical publishing for well over a century, the nearly universal standard for multi-paragraph quotations has been to put an open quote mark at the _start of each paragraph,_ but a close quote mark _only at the end of the entire quotation._ Like so:
> 
> "Paragraph 1.
> 
> "Paragraph 2.
> 
> “Paragraph 3.”
> 
> Although this style may seem illogical,

That is a ghastly 1940s anachronism that I find very hard to understand or agree with. It certainly WAS accepted style at some time when my long-dead parents were in high school. To (very much non-expert) me that’s the sound of fingernails on a chalk board.

Around here, either use [quote] as you say if you’re quoting a poster, or the blockquote function for stuff from other sources e.g.  
The New York Times article said:

> Paragraph 1. Blah blah blah. Lorem ipsum super califragilistic expialodocious. Blah blah blah. Lorem ipsum super califragilistic expialodocious. Blah blah blah. Lorem ipsum super califragilistic expialodocious.
> 
> Paragraph 2. Blah blah blah. Lorem ipsum super califragilistic expialodocious. Blah blah blah. Lorem ipsum super califragilistic expialodocious. Blah blah blah. Lorem ipsum super califragilistic expialodocious.
> 
> Paragraph 3. Blah blah blah. Lorem ipsum super califragilistic expialodocious. Blah blah blah. Lorem ipsum super califragilistic expialodocious.

---

<div class="post-metadata">

**Author:** ![Al128](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/al128/32/16541_2.png) [@Al128](https://boards.straightdope.com/u/Al128)\
**Post date:** [June 15, 2023, 10:47pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/16 "2023-06-15T22:47:19Z")

</div>

about 90% of all posters implicitly assuming “everybody around me IRL is american, hence everybody here on SD must be american” …

what you claim as universal truth, might be the case in america, is not necesarily true for England, Namibia or Easter Island.

nitipicking “english language mistakes” … especially if you only speak one language 😉

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [June 15, 2023, 11:12pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/17 "2023-06-15T23:12:34Z")

</div>

I’m impressed at how much less often we get posters loudly explaining how something governmental IS, when they really mean that’s how it is in the one and only US _county_ they’ve ever lived in. With ~4000 counties and ~55 states and territories there are a LOT of governmental things in the USA which are totally NOT standardized.

IOW “Here’s how we do it around [someplace]” is great. “Here’s how it’s done.” is not.

That used to be a perennial problem. Now it still happens, but not so much. Still jarring when I see it.

---

<div class="post-metadata">

**Author:** ![Slow\_Moving\_Vehicle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/slow_moving_vehicle/32/291_2.png) [@Slow\_Moving\_Vehicle](https://boards.straightdope.com/u/Slow_Moving_Vehicle)\
**Post date:** [June 15, 2023, 11:33pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/18 "2023-06-15T23:33:59Z")

</div>

My pet peeve us the misuse of _y’all._ I’ve posted about it frequently, and recently, but I am zealous in my proselytizing for it to become the standard second person plural pronoun in English. And I get stabs of annoyance when I see it misspelled _ya’ll_ or used as a singular pronoun, like it’s just a quaint dialect word that those funny Southerners use instead of _you_, which is the _real_ word.

No. _Y’all_ is a perfectly cromulent contraction of _you all_, completely legal by the rules of American English grammar.

> [@Little\_Nemo](#):
>
> But to get in the spirit of the thread, I get annoyed by the overuse of ellipses. They serve a purpose but they should be reserved for situation where the writer intends a pause and not just indicate he’s run out of thoughts.

I disagree. Like periods, commas, semicolons _et al._, ellipses are a graphical indication of a pause, a longer one in their case; and can be used to suggest a voice trailing off…

---

<div class="post-metadata">

**Author:** ![needscoffee](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/needscoffee/32/1076_2.png) [@needscoffee](https://boards.straightdope.com/u/needscoffee)\
**Post date:** [June 15, 2023, 11:38pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/19 "2023-06-15T23:38:03Z")

</div>

> [@Slow\_Moving\_Vehicle](#):
>
> I disagree. Like periods, commas, semicolons _et al._, ellipses are a graphical indication of a pause, a longer one in their case; and can be used to suggest a voice trailing off…

I suspect he’s referring to the people here who post using no punctuation _except_ ellipses in the entire post. At least, that’s something that bugs me. In most of the instances, a simple period would have worked better and made it look less like a stream-of-consciousness ramble.

---

<div class="post-metadata">

**Author:** ![Moriarty](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/moriarty/32/49_2.png) [@Moriarty](https://boards.straightdope.com/u/Moriarty)\
**Post date:** [June 15, 2023, 11:38pm UTC](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583/20 "2023-06-15T23:38:10Z")

</div>

Judgment does not begin with the word “judge”.

Leave out the E.

[Next page](https://boards.straightdope.com/t/nitpick-your-fellow-dopers/985583.md?page=2)
