{"id":1340,"date":"2021-06-15T10:05:29","date_gmt":"2021-06-15T09:05:29","guid":{"rendered":"http:\/\/hb5.50e.myftpupload.com\/?p=4"},"modified":"2025-12-19T02:29:53","modified_gmt":"2025-12-19T01:29:53","slug":"english-speaking-advice-for-foreigners-and-americans","status":"publish","type":"post","link":"https:\/\/earlywithdrawal.net\/tolton\/2021\/06\/15\/english-speaking-advice-for-foreigners-and-americans\/","title":{"rendered":"English-speaking advice for foreigners and Americans"},"content":{"rendered":"\n
\"\"<\/figure><\/div>\n\n\n\n

Foreigners often find themselves persisting in certain grammatical errors, and the reason is the most dreadful one: native speakers are setting the example. <\/p>\n\n\n\n

There is certainly an argument to be made for the evolution of language: it is going to change, and change comes from the streets. However, there is no argument for devolution<\/em> of language, that is, making it less usable.<\/p>\n\n\n\n

Might-May<\/p>\n\n\n\n

The minister may choose his successor<\/code><\/p>\n\n\n\n

is ambiguous in modern English. Does it mean that the law allows the minister to choose his successor? Or does it mean that the minister is considering choosing his successor? Tragically, English is equipped for this problem: might<\/em> and may<\/em>. <\/p>\n\n\n\n

John and Susan may marry<\/code><\/p>\n\n\n\n

means they got state approval or permission from their parents.<\/p>\n\n\n\n

John and Susan might marry<\/code><\/p>\n\n\n\n

means they are uncertain about it, but it is possible.<\/p>\n\n\n\n

There is no cost to making the distinction; everyone either understands it or will not notice it.
<\/p>\n\n\n\n

\n\n\n\n

Should-Ought<\/p>\n\n\n\n

Should<\/em> is a marker of the subjunctive, as in<\/p>\n\n\n\n

Should you be late, you'll miss your chance.<\/code><\/p>\n\n\n\n

There is some irreal condition (hasn’t happened and might not happen) which would have consequences. Thus,<\/p>\n\n\n\n

I fear John should be late<\/p>\n\n\n\n

and not<\/p>\n\n\n\n

I fear John will be late.<\/s><\/code><\/p>\n\n\n\n

<\/p>\n\n\n\n

The subjunctive appears in expressions of will:<\/p>\n\n\n\n

Long live the king<\/code><\/p>\n\n\n\n

as opposed to<\/p>\n\n\n\n

Long lives the king<\/s><\/code><\/p>\n\n\n\n

<\/p>\n\n\n\n

I insist that he wear a tie<\/code><\/p>\n\n\n\n

instead of<\/p>\n\n\n\n

I insist that he wears a tie<\/s><\/code><\/p>\n\n\n\n

Therefore, when someone tells you,<\/p>\n\n\n\n

You should lose some weight<\/code><\/p>\n\n\n\n

It means, let it be such that you lose weight.<\/p>\n\n\n\n

When someone says<\/p>\n\n\n\n

You ought to lose some weight<\/code><\/p>\n\n\n\n

It means there is a compelling reason for you to lose weight, perhaps the threat of coronary disease.<\/p>\n\n\n\n

Many times, these implicit orders are given precisely because there is a compelling reason, and therein lies the confusion. However, there are situations in which the distinction is manifest. When someone says,<\/p>\n\n\n\n

You ought to smell smoke from the car<\/code><\/p>\n\n\n\n

it means, there is a compelling reason for you to smell smoke, like the fact that there is<\/em> smoke, and if you don’t, there might be something wrong with your sense of smell. When someone says,<\/p>\n\n\n\n

You should smell smoke from the car<\/code><\/p>\n\n\n\n

It means, please go smell the smoke coming from the car (maybe you can identify the source).<\/p>\n\n\n\n

Admittedly, should<\/em> and ought<\/em> are confounded most of the time, and ought<\/em> is the loser. However, this is no reason to cast away the cases where there is a difference: the speaker may not even think clearly in these cases. The mental tool is not there. The speaker is impoverished in the worst place one may be poor.<\/p>\n\n\n\n

\n\n\n\n

Will-Shall<\/h2>\n\n\n\n

There are two auxiliaries to express future action, and in common practice, they are used more or less interchangeably, with the exception that shall<\/em> feels more old-fashioned.<\/p>\n\n\n\n

Devolution! There is a difference. Consider<\/p>\n\n\n\n

I will this union be everlasting.<\/code><\/p>\n\n\n\n

Will <\/em>can be used as a verb. Compare to the German will. Ich will singen<\/em> means I want to sing<\/em>. <\/p>\n\n\n\n

The following is a statement about the present, not the future:<\/p>\n\n\n\n

I tried to help her, but she will not have it.<\/code><\/p>\n\n\n\n

This is a statement about what she wants now, which might affect the future. She might be compelled to accept help, although she will not have it. So when you say<\/p>\n\n\n\n

I will be late.<\/code><\/p>\n\n\n\n

it means something like, Sarah hosts such boring parties, I want to arrive late, and that is what is going to happen. Whereas<\/p>\n\n\n\n

I shall be late<\/code><\/p>\n\n\n\n

means something like, my car has a flat tire. <\/p>\n\n\n\n

<\/div>\n\n\n\n

It is important to remember: in any future dystopia, possibility and permission (might-may) shall be confounded. Possibility is not your concern. Permission is. <\/p>\n\n\n\n

Volition and condition (will-shall) shall be confounded. What you want has no effect on the future. The distinction is herewith obliterated.<\/p>\n\n\n\n

The loss of might-may, should-ought, <\/em>and will-shall<\/em> is actual, real-life, newspeak<\/strong>. It is a simplification of language which eliminates concepts which otherwise make ruling harder. <\/p>\n\n\n\n

<\/p>\n\n\n\n

\n\n\n\n

Its – It’s<\/p>\n\n\n\n

I love its color.<\/code><\/p>\n\n\n\n

and not<\/p>\n\n\n\n

I love it's color.<\/s><\/code><\/p>\n\n\n\n

Obviously, the apostrophe is used on nouns, as in<\/p>\n\n\n\n

I love the car's color<\/code>.<\/p>\n\n\n\n

But no one writes<\/p>\n\n\n\n

I love her's hair color<\/s><\/code>.<\/p>\n\n\n\n

Similarly, there is no my’s<\/s>, no your’s<\/s>, no their’s<\/s>, and no our’s.<\/s> These are possessive pronouns. They are specifically designed for the task. They don’t need any help.<\/p>\n\n\n\n

This example is not a devolution of language, since it doesn’t make the language less useful. But it is a decidedly weird complication. It is an exception to the way all other pronouns are treated; it provides no special meaning. It seems to be part of an internet dialect (see ad below) which does not understand the use of apostrophes in general and therefore places them randomly where they are orthographically possible.<\/p>\n\n\n\n

\"\"
Who would have predicted this?<\/figcaption><\/figure>\n\n\n\n
\n\n\n\n

Try<\/p>\n\n\n\n

I'm going to try and get it done.<\/code><\/p>\n\n\n\n

You’re going to try to do what while you’re getting it done? <\/p>\n\n\n\n

Oh, get it done? Does that mean you’re going to try to get it done and get it done? Why not simply say,<\/p>\n\n\n\n

I'm going to try to get it done<\/code>.<\/p>\n\n\n\n

The reason to maintain the distinction between and<\/em> and to<\/em> is that there are uses where the difference is meaningful:<\/p>\n\n\n\n

I tried and spoke up<\/code><\/p>\n\n\n\n

I tried to speak up<\/code><\/p>\n\n\n\n

One means I did and the other implies I didn’t. Conclusion: and<\/em> and to<\/em> are not synonyms. This is a devolution.<\/p>\n\n\n\n

\n\n\n\n

I could care less<\/h2>\n\n\n\n

if<\/p>\n\n\n\n

I could care less<\/code><\/p>\n\n\n\n

means<\/p>\n\n\n\n

I couldn't care less<\/code><\/p>\n\n\n\n

say<\/p>\n\n\n\n

I couldn't care less<\/code><\/p>\n\n\n\n

\n\n\n\n

Do as you please<\/h2>\n\n\n\n

I will do as I please<\/code><\/p>\n\n\n\n

Great. Whom, exactly? Me? Awesome! Please e-mail me for instructions. If you want to please yourself, say,<\/p>\n\n\n\n

I will do as I am pleased<\/code><\/p>\n\n\n\n

or<\/p>\n\n\n

\u00a0<\/p>\n

I will do as best pleases me<\/code><\/p>\n

<\/p>\n

<\/p>\n

\n

\u00a0<\/p>\n

<\/p>\n

Lie-Lay<\/h2>\n

<\/p>\n

<\/p>\n

There is confusion about the verb lie<\/em> because the present-tense transitive form lay<\/em> looks like the past-tense intransitive form. Here is how it goes:<\/p>\n

<\/p>\n

<\/p>\n

I lie on the bed right now<\/code><\/p>\n

<\/p>\n

<\/p>\n

I lay on the bed yesterday<\/code><\/p>\n

<\/p>\n

<\/p>\n

I lay the book on the bed right now<\/code><\/p>\n

<\/p>\n

<\/p>\n

I laid the book on the bed yesterday<\/code><\/p>\n

<\/p>\n

<\/p>\n

There is no I lay on the bed right now<\/s>. Don’t give up. There is no readed<\/s><\/em> and there is no putted<\/s><\/em>. There are plenty of examples like this. You can do it!<\/p>\n

<\/p>\n

<\/p>\n

\u00a0<\/p>\n

<\/p>","protected":false},"excerpt":{"rendered":"

Foreigners often find themselves persisting in certain grammatical errors, and the reason is the most dreadful one: native speakers are setting the example.<\/p>\n","protected":false},"author":1,"featured_media":3487,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[116,115],"_links":{"self":[{"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/posts\/1340"}],"collection":[{"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/comments?post=1340"}],"version-history":[{"count":30,"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/posts\/1340\/revisions"}],"predecessor-version":[{"id":4681,"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/posts\/1340\/revisions\/4681"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/media\/3487"}],"wp:attachment":[{"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/media?parent=1340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/categories?post=1340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/earlywithdrawal.net\/tolton\/wp-json\/wp\/v2\/tags?post=1340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}