# Acceptable English grammar/semantics that you hate

**URL:** <https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984>\
**Category:** In My Humble Opinion\
**Created:** [May 23, 2024, 8:21pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984 "2024-05-23T20:21:45Z")\
**Posts on this page:** 20\
**Page:** 13

<div class="post-metadata">

**Author:** ![DPRK](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@DPRK](https://boards.straightdope.com/u/DPRK)\
**Post date:** [June 21, 2024, 3:59am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/241 "2024-06-21T03:59:04Z")

</div>

They are at least consistent in that anything below mega is lower-case, and mega and above are upper case. As for confusing prefixes like myria (my? M?) they just got rid of them from the official list 🙂

The original prefixes (deca, hecto, kilo, myria, deci, centi, milli, and myrio) were all lowercase, so that accounts for kilo.

---

<div class="post-metadata">

**Author:** ![Johanna](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/johanna/32/8318_2.png) [@Johanna](https://boards.straightdope.com/u/Johanna)\
**Post date:** [June 21, 2024, 4:22am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/242 "2024-06-21T04:22:09Z")

</div>

Because _mega_ means ‘big’.

---

<div class="post-metadata">

**Author:** ![rowrrbazzle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rowrrbazzle/32/414_2.png) [@rowrrbazzle](https://boards.straightdope.com/u/rowrrbazzle)\
**Post date:** [June 21, 2024, 4:23am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/243 "2024-06-21T04:23:20Z")

</div>

> [@teelabrown](#):
>
> And: something that’s zany is “wacky”. “Whacky” would describe someone who likes to whack things.

This.

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [June 21, 2024, 4:24am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/244 "2024-06-21T04:24:41Z")

</div>

> [@Johanna](#):
>
> Because _mega_ means ‘big’.

That’s a great point, thank you!

---

<div class="post-metadata">

**Author:** ![Stratocaster](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/stratocaster/32/16393_2.png) [@Stratocaster](https://boards.straightdope.com/u/Stratocaster)\
**Post date:** [June 21, 2024, 10:45am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/245 "2024-06-21T10:45:25Z")

</div>

> [@teelabrown](#):
>
> “Whacky” would describe someone who likes to whack things.

And that would indeed be pretty wacky, right? Pretty meta…

---

<div class="post-metadata">

**Author:** ![Earl\_Snake-Hips\_Tucker](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/earl_snake-hips_tucker/32/3269_2.png) [@Earl\_Snake-Hips\_Tucker](https://boards.straightdope.com/u/Earl_Snake-Hips_Tucker)\
**Post date:** [June 21, 2024, 2:46pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/246 "2024-06-21T14:46:43Z")

</div>

Well, yeah, that is the way they are properly written. I personally don’t see the need to capitalize the part derived from a person’s name. Not that I get to make the rules.

---

<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 23, 2024, 7:28pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/247 "2024-06-23T19:28:03Z")

</div>

The reason for mega being abbreviated uppercase is pretty obvious to me. Namely to disambiguate from milli. A “MW” is a megawatt and a “mW” is a milliwatt. That’s also why micro uses a lowercase Greek mu rather than an ordinary single Latin alphabet letter.

Of the common prefixes only micro, milli, and mega share a common first letter. Damned inconvenient the Ancients didn’t work harder at disambiguating their number grouping words by having them all start with different letters. Idjits.

  

Unrelated to the above …

> [@wolfpup](#):
>
> Apparently your teacher’s didn’t also instruct you to not throw random apostrophe’s into plural word’s, also known as the grocer’s apostrophe. 😉

Considering how common this is, ISTM that should be “Grocers’ Apostrophe”; they all seem to use it. Certainly far more than just one grocer uses it. 😉

---

<div class="post-metadata">

**Author:** ![Left\_Hand\_of\_Dorkness](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/left_hand_of_dorkness/32/7156_2.png) [@Left\_Hand\_of\_Dorkness](https://boards.straightdope.com/u/Left_Hand_of_Dorkness)\
**Post date:** [June 24, 2024, 10:44am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/248 "2024-06-24T10:44:30Z")

</div>

I normally don’t have much patience with pedantic complaints about the language, but yesterday, my own pet peeve showed up.

I was eating breakfast with my daughter, discussing plans, and she said, “So are you not going to visit that place?”

I had just taken a bite, but this was a yes/no question. I could answer it with a simple nod or shake of my head, or a thumbs up or thumbs down.

Except for my peeve: yes/no questions that include a negative in the main clause. They cannot be unambiguously answered with a yes or a no, or any gesture equivalent.

I have never encountered a grammar snob who objects to this form of question. Everyone consider them correct, and they are widely used. But if you genuinely want to remove confusion and ambiguity from English, get rid of these questions!

---

<div class="post-metadata">

**Author:** ![Ludovic](https://avatars.discourse-cdn.com/v4/letter/l/7ab992/32.png) [@Ludovic](https://boards.straightdope.com/u/Ludovic)\
**Post date:** [June 24, 2024, 10:53am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/249 "2024-06-24T10:53:53Z")

</div>

Or you could revive the old convention of using “yes/no” as unambiguous answers to these negative questions, and using “yea/nay” as unambiguous answers to the usual positive questions. However, according to Wikipedia that seemed like too much work even when it was in place, which is why I called it a convention rather than a rule:

> **[Yes and no | The Early English four-form system](https://en.wikipedia.org/wiki/Yes_and_no#The_Early_English_four-form_system)**
>
> While Modern English has a two-form system of yes and no for affirmatives and negatives, earlier forms of English had a four-form system, comprising the words yea, nay, yes, and no. Yes contradicts a negatively formulated question, No affirms it; Yea affirms a positively formulated question, Nay contradicts it.
> 1.Will they not go? — Yes, they will. |
> 2.Will they not go? — No, they will not. |
> 3.Will they go? — Yea, they will. |
> 4.Will they go? — Nay, they will not. This is illustrated by the ...

---

<div class="post-metadata">

**Author:** ![Q.Q.Switcheroo](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/q.q.switcheroo/32/5713_2.png) [@Q.Q.Switcheroo](https://boards.straightdope.com/u/Q.Q.Switcheroo)\
**Post date:** [June 24, 2024, 1:26pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/250 "2024-06-24T13:26:52Z")

</div>

> [@Left\_Hand\_of\_Dorkness](#):
>
> I was eating breakfast with my daughter, discussing plans, and she said, “So are you not going to visit that place?”
> 
> I had just taken a bite, but this was a yes/no question. I could answer it with a simple nod or shake of my head, or a thumbs up or thumbs down.

This is a major pet peeve for people with medical conditions that leave them unable to communicate except through gestures. (Imagine having to respond nonverbally to a question like “You don’t have any allergies, right?”)

---

<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 24, 2024, 2:41pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/251 "2024-06-24T14:41:20Z")

</div>

The problem of course is rooted in the questioner wanting to both deliver the question, and to assert which answer they believe _a priori_ to be correct.

**LHOD** ’s daughter is saying “I think you expressed that you aren’t going to visit that place. Please confirm my understanding.”

And **Q.Q.**'s “You don’t have any allergies, right?” is expressing “I know that most people don’t have allergies, so the answer for most people is “no”. But what is the answer for you?”

In a social sense what’s going on is them trying to structure the question in such a way that the expected answer is “yes”. Because it’s supportive to offer people questions to which they can answer “yes”, and it feels better to the questioner to have the answer come back “yes”; someone answering “no” is inherently offputting and amounts to a gentle rebuke.

In some cultures it’s an outright affront to answer “no” to an utterly unambiguous question even if “no” is the truth. Better (socially) to lie than to ever say “no”.

Language is about a lot more than Boolean logic.

---

<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 24, 2024, 3:13pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/252 "2024-06-24T15:13:18Z")

</div>

> [@solost](#):
>
> but if the word ‘literally’ loses its meaning, what word do we use when we want to convey we mean something literally?

Letterally? That is: by the letter. There seem to be religious believers who claim the Bible or the Old Testament or something is Godott’s word letter by letter and not one iota should be changed and they call themselves letteralists to make the difference (and express their superiority) with respect to the mere literalists clear.  
Apart from that – and it is only a suggestion – I disagree with the OP’s premise: I don’t think English grammar or semantics are acceptable at all. They are a mess. But I don’t hate them, I have even learned to find them endearing and funny sometimes, particularly since I learned not to care about my own mistakes. My excuses to the taliban of rules that must be often grated by my chaotic approach, it is not meant personally.

---

<div class="post-metadata">

**Author:** ![Q.Q.Switcheroo](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/q.q.switcheroo/32/5713_2.png) [@Q.Q.Switcheroo](https://boards.straightdope.com/u/Q.Q.Switcheroo)\
**Post date:** [June 24, 2024, 7:20pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/253 "2024-06-24T19:20:44Z")

</div>

One that always bugged me: “He must be spinning in his grave.” It’s meant to be a comic exaggeration of “turning over in his grave”…except that “turning over” in that context means “flopping around restlessly” (as in “tossing and turning”), not “rotating steadily around a longitudinal axis.”

---

<div class="post-metadata">

**Author:** ![Yllaria](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/yllaria/32/3452_2.png) [@Yllaria](https://boards.straightdope.com/u/Yllaria)\
**Post date:** [June 25, 2024, 12:57am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/254 "2024-06-25T00:57:30Z")

</div>

If he’s not spinning, you can’t attach him to a turbine and create electricity. (It’s been awhile since I read through **Dresden Codak**. But I remember that.)

---

<div class="post-metadata">

**Author:** ![Stoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/stoid/32/272_2.png) [@Stoid](https://boards.straightdope.com/u/Stoid)\
**Post date:** [June 26, 2024, 12:16pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/255 "2024-06-26T12:16:58Z")

</div>

At the moment I am feeling desperate to find a way to stop the race to obliterate the difference in meaning between “empathy” and “sympathy”.

A very simple example, for those who may need it in this world where the word “sympathy” is almost gone:

~I am a woman. You are a man. If someone kicks you in the testicles, I am very sympathetic.

~If you are a woman, and you tell me your D&C was painful, I would be empathetic.

A simple way of putting it is that sympathy is feeling _for_ you, empathy is feeling _with_ you. They are different and the way empathy has been taking over is driving me crazier, not getting easier.

---

<div class="post-metadata">

**Author:** ![Mama\_Zappa](https://avatars.discourse-cdn.com/v4/letter/m/71e660/32.png) [@Mama\_Zappa](https://boards.straightdope.com/u/Mama_Zappa)\
**Post date:** [June 26, 2024, 2:36pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/256 "2024-06-26T14:36:08Z")

</div>

And both “close” and “closed” are adjectives, with completely different meanings. “Close” means “nearby”, while “closed” means “not open”.

Of course, “closed” is also a verb (past participle). The library close to my house was closed by the county, so now it’s closed"

It is odd, when compared with “open”.

---

<div class="post-metadata">

**Author:** ![Moonrise](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/moonrise/32/14764_2.png) [@Moonrise](https://boards.straightdope.com/u/Moonrise)\
**Post date:** [June 26, 2024, 4:20pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/257 "2024-06-26T16:20:19Z")

</div>

I empathize with you.

---

<div class="post-metadata">

**Author:** ![Stoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/stoid/32/272_2.png) [@Stoid](https://boards.straightdope.com/u/Stoid)\
**Post date:** [June 26, 2024, 11:03pm UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/258 "2024-06-26T23:03:08Z")

</div>

Hehehe  
😂

---

<div class="post-metadata">

**Author:** ![rowrrbazzle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rowrrbazzle/32/414_2.png) [@rowrrbazzle](https://boards.straightdope.com/u/rowrrbazzle)\
**Post date:** [June 28, 2024, 5:38am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/259 "2024-06-28T05:38:32Z")

</div>

This problem cropped up on the old panel game show _What’s My Line_. Because a “no” answer gave the guest another $5, the moderator, John Daly, would’ve rephrased your “no” answer to your daughter’s question as “No, your father is not going to visit that place, yes.” To avoid the confusion, Dorothy Kilgallen would’ve phrased your daughter’s question as “Is it correct to say that you are not going to visit that place?”

---

<div class="post-metadata">

**Author:** ![rowrrbazzle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rowrrbazzle/32/414_2.png) [@rowrrbazzle](https://boards.straightdope.com/u/rowrrbazzle)\
**Post date:** [June 28, 2024, 5:52am UTC](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984/260 "2024-06-28T05:52:36Z")

</div>

You have my compassion.

[Previous page](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984.md?page=12)

[Next page](https://boards.straightdope.com/t/acceptable-english-grammar-semantics-that-you-hate/1001984.md?page=14)
