Separated by a Common Language

I've been to two conferences in the past two weeks, presenting studies on British and American use of the word please. It was a blog post here that inspired this new research direction: three years ago I posted about whether one says please when ordering in restaurants (click that link for lots of discussion!). If you read the comments at that post, you'll see Americans saying things like 

Please winds up feeling impolite with people that you don't have the right to order around, ie anyone other than your children.

and British commenters saying things like 

not saying please makes it sound like a lord giving an order to his butler

--that is, Americans saying please sounds bossy and Brits saying 'you have to say please, or else you'll sound bossy'. The conference papers will turn into one or two journal articles (eventually!). In the meantime, the two studies brought up so many little factoids about please that I could do at least a half a dozen blog posts on them. Let's start with one and see how I go.

This one comes from the work I'm doing with Rachele De Felice of the Survey of English Usage at University College London and that we presented at the Corpus Linguistics 2015 conference. We're looking at requests (1,350 of them in total) in two corpora of corporate emails, one from a British company that will remain anonymous, and the other from an American company you might have heard of. We found, as others have in other data, that twice as many British requests as American ones include please. What's more, in British English please is particularly often used in requests that do not involve much of an imposition--things like please don't hesitate to call if you need assistance, please note that tomorrow is a holiday or please accept our congratulations. They have the form of an imperative sentence (do this!), but the recipient is not actually asked to do much of anything; instead, they're offered something (help, information, congratulations).

This brings us to one of the types of please-imperatives found in the email data: please find attached and its relatives please find enclosed and please find below. There were 20 of these in the British data and two in the American data — all of them with please. So, not only do we have far fewer American please find attached's, we don't have any please-less find attached's. Surely British corporate emailers don't attach documents 10 times more often as American ones do?

The mystery of the missing find attached's is solved when we consider that this is another case where the "command" isn't really much of a command at all. There's no need to boss around the other person to go about finding things, since the sentence is just communicating "I have attached a document for you". In fact, it would be just plain weird to put this into another request form like Could you please find the document attached? or I would be very grateful if you would find the document attached. This underscores that please find attached is not much of a request at all. It is instead a set phrase in imperative form that does a not-very-requesty job.

We found that American business people are actively discouraged from using this set phrase. Here is what the Oxford Dictionary of American Usage and Style by Bryan A. Garner has to say (highlighting added):





Garner goes on to cite sources from the 19th century onward (all of them American) that agree that please find enclosed is a horrible business-ism that should be avoided. My small forays into (the possibly smaller genre of) British business writing advice has not turned up anything at all about this phrase. (Let me know if you know of any advice in either direction.)

Whatever you think of please find attached, it creates problems for our comparative speech-act research. If we look at British imperatives in our email data and say "84% have please, while only 43% of American imperatives do", it looks like maybe the Americans are bossier--ordering people around without saying please. But that might not be the best way to look at it.

Another way to look at it is: British emailers often only say please because they've put messages into command form that American emailers might put into a declarative sentence. The imperative could be seen as more imperious (or at least officious) than putting the same message into a declarative sentence.

And with that, I'll leave you with a British please sign that Peter Austin posted in the week of our presentation:

	GB our	GB or	US or	US our
hono(u)r	10376	2985	17145	2437
humo(u)r	8903	1632	10461	1560
neighbo(u)r	5364	1029	8128	1037
odo(u)r	673	276	1224	119
tumo(u)r	2546	658	2269	244
vigo(u)r	910	201	745	197
totals	=28772	=6781	=39972	=5594
'foreign' rate	19%		12%

In other words,  19% of the -o(u)r words I searched for in the GB corpus had the AmE -or spelling and 12% of the US -o(u)r words had -our spellings. A few of these may just be by people who can't spell or who are putting on airs by using another spelling system, but they're probably a very few. The percentages for the individual words range from 8.9% (tumo(u)r) to 20.9% (vigo(u)r) for the US data and 15.5% (humo(u)r) to 29.1% (odo(u)r) for the GB data. It's important to use a number of words because the data will be skewed if it's just a word that American use more than British people (or vice versa), regardless of spelling. We can see that happening a bit with odo(u)r.

(I'd originally included colo(u)r in the list, which made the total difference more stark: 24% to 14%. I took it out because I suspected that the use of color in HTML coding might be skewing the result.)

So this can lead us to the hypotheses:

About 12% of US blog data is not written by Americans.
About 19% of UK blog data is written by people using American English spelling.

We cannot say that about 12% of the US data were written by British people, or even that 81% of the British data were written by British people, since -our spellings are used in the rest of the anglophone world. Half of the vigours written on British sites might have been written by Australians or Canadians, for all we know. The -or is more a marker of Americanness than -our is a marker of Britishness. But we also can't say that the people spelling -or are Americans, we can only assume they are people whose education in English spelling used American English standards. So, half of the -or spellings might have been written by people in the Phillipines (where American spelling is used). It's unlikely that it's that many, but I've phrased the hypotheses to allow for these possibilities.

Why is the number of American spellings on British sites larger than the number of British spellings on American sites? Well, it might just be because there are nearly five times as many Americans on the internet than there are Brits. (The US has 86.9% internet penetration on a population of around 318 million, so that's over 276 million internet users. The UK has 89.8% penetration in a population of about 63 million, so that's nearly 57 million internet users. Source.) Of course, there are a lot more countries involved here (and I'm not going to go do all that adding-up at the moment), but that's a reasonable step toward(s) explaining the difference, and one that doesn't involve running around screaming 'the sky is falling on British English'!

So, what this means is that if we look for differences between American and British Englishes on GloWBE and see that a form that's used in Britain is used 10% as much in America, we can't conclude that the Britishism is gaining traction in the US, because there's a fair likelihood that the people who used the Britishism weren't American. If we see one with 40% use in the US, however, we can aver that it's well on its way to being established there.

Anyhow, I'm glad I decided to explain that all in a blog post, as it makes it clearer in my mind for explaining it in about 10 seconds as I fly by that slide in my presentation next week. If you see any flaws in my thinking or math(s), please let me know!

In other news (aka shameless self-promotion):
The Odditorium people have made a podcast of my Catalyst Club talk about little words (especially the). It's a bit odd without the visuals, but they do call themselves 'oddpodcast', after all.



I'm speaking at two conferences in the next two weeks, plus have a few public speaking engagements in the future. Follow the links for more info. If you're nearby, come say (orig. AmE in this form) hello!

23 July (with Rachele de Felice): The politics of please in British and American English. Corpus Linguistics conference, University of Lancaster.

31 July Separated by a Common Politeness Marker: please in British and American English. International Pragmatics Association Conference, Antwerp.  
17 Sept How America Saved the English Language.  The Bedford Culture Club (Horsham, W Sussex). 

Further ahead, titles yet to be confirmed:
27 Sept  Sunday Assembly Brighton.  
27 Nov (Thanksgiving dinner--a day late)  English-Speaking Union, Chichester.

Yesterday, The Syntactician was asking me questions about semantic terminology in relation to particular uses of the verb know, as one does. And so, as one does, I looked for know in the indices of various books about verbs that I have, hoping to find a term that would suit her particular purposes. In doing so, I came across something that was completely new to me in F. R. Palmer's A linguistic study of the English verb (1965):

In case you can't read the photo, it says that you can 'help someone do something' or you can 'help someone to do something'.  So far, so familiar to me.

But then it goes on to say that know has the same pattern with  

(1)  Have you ever known them come on time?

and

(2)  Have you ever known them to come on time?

Now, if I have ever seen sentences of type (1) in the wild, I must have assumed them to have typos, because if I want to know someone/thing + verb, I must have the the to-infinitive form of the verb. Yes to (2), no to (1). Absolutely, no question.

So, I turned to the (English) Syntactician, who said that yes, (1) is good in her BrE, "but old-fashioned". I then went onto Twitter to proclaim my ignorance/learning/disbelief, and many English people (many of whom are probably not terribly old-fashioned) replied to say "Yes, that's fine. I can say that."  No US people replied to say they could say it, and now that I look in Algeo's British or American English?, I see that he records this as a British form.

Palmer hasn't mentioned the big restriction on this, however. Algeo does, but I learned the restriction  the hard way: by tweeting "Can you really know someone do something?" The answer there is 'no'--British English speakers can only use the to-less version in the perfect aspect (the 'have/had verbed' forms). So:

• General (BrE or AmE) perfect: I have known them to frequent dark alleys.
• BrE-only perfect:   I have known them frequent dark alleys.
• General English present:  I know them to frequent dark alleys.
• Nobody's English present:  *I know them frequent dark alleys.

 
(Overly academic side point. Skip this unless can name at least two theories of grammar!
I'm wondering how you get a [say, Chomskyan] theory of grammar to account for a complementation structure that is particular to a certain aspect of a certain verb. Maybe all theories are now so lexical that it's  possible--though you'd have to treat known and know as different lexical items, I guess. Would be easier to account for in a Construction Grammar, but still seems like a very heavy--or at least fiddly--cognitive load for a language to bear. If you know about such things, let me know in the comments, please!)

I should also say a bit about that help (to). As I said above, both of these are fine in AmE and BrE:

(3)   I helped them escape.


(4)  I helped them to escape.

 ...but what's interesting for us is that AmE prefers (3) [in 75% of the cases in the Brown corpus] and BrE prefers (4) [73% of the cases in the LOB corpus] (both figures from Algeo, p. 228).



And that, my friends, is how you write a blog post of less than 1000 words. When was the last time you had known me do that?  :)

A while ago, I wrote about a difference in AmE and BrE use of street and road, in that in BrE it's more natural to cross the road and in AmE (certainly in a town or city) it's more common to cross the street. (I've also written about in/on the street, so see that post for more on that.) That's common-noun usage, but what about the proper names of vehicular paths?

There's no question that some ways of designating paths are more common in one country or the other. I've never seen a road named [Something] Trail or [Something] Boulevard in the UK (though see the comments for some counterexamples), and in the US there aren't as many Crescents or (BrE) Closes (pronounced with a /s/, not a /z/). But a problem for making generali{z/s}ations about such things is that the naming of streets or roads varies a lot on the local level in both countries, with different names based on regional differences, urban/rural differences, and terrain differences.

The other day Damien Hall (tweeting as @EvrydayLg) pointed out:

Struck since long B4 I lived there by US habit of omitting eg St, Rd in addresses. We don't.

He hypothesi{z/s}ed that it might be because street is more common in the US and therefore the default. But I don't think that's why. Instead, Americans are happy to say things like

go up Main and take the first right onto Union

...because in most cases that will be an unambiguous statement, since there will typically only be one thoroughfare called Main (Street) and one called Union (maybe Avenue) in a town. I often send packages to a friend who lives in Tennessee. I've never bothered to find out if she lives on Woodland Street or Woodland Lane because I only need to put '140 Woodland' (and the city, state and, if I'm nice, the zip code) on the package and it gets there. As you can see from this (AmE) yard sale sign, the practice of not saying street or road is common. (Where there is more than one with the same name, you'll hear the street/road/lane/whatever more regularly.)

(Side note on codes: Five-digit US zip codes only say which town or which part of a city the address is in, unlike six-or-seven-letter/number UK post codes, which generally indicate the town/part-of-city in the first half (letter-letter+1- or 2-digit number) and which street or part-of-street in the second half (number-letter-letter). Nine-digit US zip codes, called ZIP+4, are a more recent addition* that do indicate street, but which I don't actually use. I couldn't tell you what mine is at the US address I use. 
*It says how old I am that I consider something from 1983 a 'recent addition'. )

'Street'-less street names are so unambiguous that most Americans would immediately recogni{z/s}e that the film title State and Main refers to a corner in a town--mostly likely in the cent{er/re} of the town, since those are common street names in American towns and because we refer to (AmE) intersections or the corners at those intersections in that way. 

(I'm sure I've mentioned before that Main Street is a likely street to have in a town as the main street. It is also metaphorically used to refer to 'the inhabitants of small US towns considered as having a narrow-minded or materialistic worldview' (AHD5). So, politicians might worry about 'what will fly on Main Street'. The High Street is the proverbial main street in a British town (it may or may not be named High Street) and is used metaphorically to refer to the commercial market--i.e. 'what will fly on the high street' is what the masses are likely to want to buy.)

British roads need the street or road (etc.) because little is unambiguous when it comes to British road names.

Take my former (more common in AmE) neighbo(u)rhood as an example:
There is a Buckingham Road, which meets Buckingham Place. Buckingham Street runs parallel to Buckingham Road, but doesn't meet Buckingham Place because halfway through it changes its name to Clifton Street. Off the map are Clifton Road, Clifton Hill, Clifton Street, Clifton Place and Clifton Terrace. But we don't need to leave this map to see that there's also a West Hill Street, West Hill Road and West Hill Place. I also feel bad for the people who live on the parallel Albert Road and Alfred Road who probably get each other's (AmE) mail/(BrE) post all the time.

Once I found an unconscious man on Buckingham Place.  Except I didn't know which Buckingham it was. The ambulance people were (BrE) well (orig. AmE) pissed off at me.

If that weren't bad enough, I now live on a road that shares its entire name with another road in the same city. When I tell taxis where to take me I have to say "X Street, off Y Road". We always tell plumbers and such which one to go to (we even give them our post code) and then when they don't show up, we text them to say "no, it's the other one".

A famous exception to the 'one pathway per name' rule in the US is New York City, which has both a 3rd Street and a 3rd Avenue. Except that it doesn't really have a '3rd Street', since you need to put East or West in front of it in order for the house number to be meaningful--so if someone says they live on East 5th, you know it's East 5th Street. In New York and the US more generally Avenue is often abbreviated in speech (as well as writing) to its first syllable (written as Ave. or Av.). 

And so onto the Easts and Wests. In the US, you can reasonably expect that East Main Street and West Main Street are the same thoroughfare, but that house numbering starts from the where they join (or divide, depending how you think of it). East Main Street will run to the east from that (AmE) intersection/(BrE) junction.

In some cities they put the compass-points after the name and that can mean something different. In Washington, DC, it indicates quadrant of the city that that part of the road is in. So, 7th Street NW and 7th Street SW are one long road that runs north/south, but the parts of it in different quadrants of the city. On the other side of the capitol building, the street numbering starts over, and so 7th Street SE and 7th Street NE run parallel to the other 7th Street NW/SW.

So, the other day, I had to find Brunswick Street East in Hove (UK). Somehow (¡Apple Maps!) I ended up on Brunswick Street West. I knew that Brunswick Street East would not be a continuation of West (after all, the road was running north-south), but I hoped it would be the next street eastward. It was not. At least it was eastward. (I hadn't been willing to trust even that.) But I did get to see Brunswick Place, Brunswick Square and Brunswick Terrace in my explorations.

Finding street names is its own challenge. In the US, street signs tend to be affixed to poles at the corners of roads. At some big intersections, they may hang over the road on the wires that hold the (AmE) stop lights/(BrE/AmE) traffic lights. In the UK, they tend to be on buildings or walls near the end of the road. This may require some searching since some are high and some are low. Here's one of my favo(u)rites from Brighton:






House-numbering, of course, is another nightmare. In the US, it's pretty predictable that even numbers will be on one side of the road and odd ones on the other. In the UK, it might be that way (though you've no guarantee that 92 will be across the street from 93--it might be many houses further down). Another UK way is to have consecutive numbering up one side of the road (1, 2, 3, 4,...) to wherever the road ends and then down the other side, so that, say, 52 and 53 may be across the road from one another, but 1 will be across the road from 104. Another way it might be is that the name of the road on one side is different from the name on the other side--so, for example, the people at 15 Vernon Terrace in Brighton live across from the people at 17 Montpelier Crescent. (And Vernon Terrace only lasts for one (AmE) block, after which its name changes and house numbers re-start twice before you get to the sea, which has pleasantly few thoroughfare names.)

I've talked about differences in house numbering on Numberphile, so (BrE) have a look at the video if you are (orig. AmE) nerdy enough want to hear more about house-numbering: