Saturday, November 27, 2010

might didn't

A few weeks ago I caught myself saying "might didn't". When it came out I was confused, and assumed, like my cohorts, that it was a speech error. But the next day I did a bit of google searching, and realized that in fact "might didn't" is a construction associated with the use of double modals, and that perhaps I was successfully integrating double modals into my grammar.

One example: "Great Tools For YouTube And Online Music Streaming You Might Didn't Know Of"

In standard English this would be "Great Tools...You Might Not Have Known Of", or hypercorrect "...Of Which You Might Not Have Known". The "might didn't" construction indicates to me that syntacticians are missing the boat if they claim double modals are merely lexicalied constructions inserted whole into T. "Did" isn't a modal, and there are clear syntactic parallels between "might could" and "might did". What we need is a theory of grammar for double modal dialects that correctly accounts for the pattern of usage, not a theory that best fits standard dialects and half-heartedly accounts for certain superficial aspects of double modal grammars. Personally, I'm interested in a proper syntactic account of double modals because I'm all for accurate description of minority languages and dialects, but I have a feeling that such dialects could also reveal important things about what might could be a part of Universal Grammar.

Saturday, November 20, 2010

past participles

Many verbs in English have three basic forms: a present tense form, which consists of the bare stem (plus -s in 3rd person singular), a past tense form (usually -ed), and a past participle form (often irregular, but quite a few end with -en). Notice I say "many" and not even "most", much less "all". There are infamous examples of verbs like lie/lay/laid vs. lay/laid/lain, which have three distinct forms but overlap in two of them, or teach/taught/taught, which has an irregular past tense and identical past participial form. The participial form appears in perfect constructions such as "I had just gotten to work when the boss walked in" or passives like "The wine was drunk in less than an hour". However, since many such participles are rarely if ever used, some people are uncomfortable using some of them, or simply unaware that a separate form exists. (Test yourself: I have swum, or I have swam? Swum is the historical past participle.) While I am somewhat of a past participle enthusiast, I rarely really notice the substitution of the simple past with verbs like "swim" and "drink". The ones that do strike me as odd are those that I perceive as common, which is why constructions like "was began" catch my ear. "Begin" is significantly more common than "swim", as evidence by the 106,952 hits for "began" in COCA versus the 2,069 for "swam". Likewise, "begun" gets 19,007 hits while "swum" only gets 186. And note that the "begin" to "swim" ratio is twice as high in the participial form than in the past. I think it's for this reason that constructions like "was began" strike me as odder than mere "had swam". COCA gets 26 hits for "had began" versus 4,865 for "had begun", and 3 for "had swam" versus 59 for "had swum". In other words, the past-for-participle substitution rate for "swim" is an order of magnitude higher than for "begin" (.5% for "begin", 5% for "swim"). At this point in the evening I'm not about to embark on a frequency analysis journey, but my guess would be you'd find similar patterns for many other verbs: past-for-participle substitution rates rise as raw usage frequency decreases.

Saturday, November 13, 2010

pre-fixed menu

I saw a nice example of an eggcorn the other day, advertising a "pre-fixed" menu. This is of course referring to the phenomenon of a "prix fixe" menu, where restaurants offer a multi-course meal for a set price (typically one that's cheaper than expected). Even though I don't speak French, I've always thought this phrase was fairly transparent: as an English-speaker, I'm familiar with the fact that French adjectives (like most other Romance languages) have adjectives after the noun -- we even have some traces of it in English, e.g., Attorney-General. And if you know that much, it's not a big stretch from prix fixe --> price fixed --> fixed price. But for someone who's only ever heard the phrase pronounced, the similarity might not be as obvious: /ˌpriːˈfɪks/. This certainly does sound almost identical to a standard pronunciation of "pre-fixed". And since prix fixe menus have a price that's already set, the semantic notion of a menu being "pre-fixed" makes sense as well. Phonetic similarity + semantic compositionality = the perfect scenario for eggcorn formation.

Just for fun, some examples that I found online:
http://www.afridom.net/lesouk-harem/menu.html
http://www.thespot-restaurant.com/party.html
http://www.clarksbarandgrill.com/Menu/Dockside-Grill-pre-Fixed-Menu.htm

Saturday, October 30, 2010

N N N N N N

Just a quick post before I get back to reading Seth Cable's recent article on Tlingit and Q particles. Last month CNN ran an article called "Titanic 100th cruises spark buzz, debate". Even before looking at the content of the article, I understood the basic gist of this headline: there are going to be cruises on the 100th anniversary of the Titanic's sinking, and these cruises are sparking buzz and debate. However, I find it amazing that I was easily able to understand what seems like it should have been a crash blossom. The headline is a string of six words that could almost all be nouns or verbs. Titanic and 100th can only be nouns, but the other four words could go either way. The anniversary is cruising some area called a spark buzz? Without the comma there would be been even more possible permutations.

Saturday, October 23, 2010

Let's see if we can't do that

Last week Vicki Hartley wrote to ask me about "the use of a negative construction when a positive construction is simpler". One example is "I'll see if I can't do that". Strangely, this sentence means essentially the same thing as "I'll see if I can do that". Another example she asked about was, e.g., "I don't have but three students", to mean "I have only three students". The way I see it, these are two separate constructions, though there is an underlying theme.

In the first, you're saying that you'll try the opposite of what you intend. I told Vicki that I saw this as similar to what goes on in the scientific method -- we'll start with our hypothesis and try to disprove it; hopefully we'll fail. Logically, this seems to make sense, since either way the result is the same: you find out whether or not you're able to do something. On the other hand, as a speaker, I wonder if this "scientific method" approach is really what's going on here. To me "I'll see if I can't do that" really doesn't mean "I'm going to attempt to not do that". To me I can't find any semantic difference in "see if I can't" versus "see if I can". Pragmatically there are differences -- the redundant negative version seems to presuppose that there will be some difficulty associated with the course of action, hence the negative. On the other hand, it seems to also presuppose that the course of action will result in a positive outcome. To me, telling a sopping wet child "let's see if we can't find you some dry clothes" would be infelicitous if it were my child at my house. I could only felicitously say that to my child's friend at my house, where there would be no reason to expect to find them dry clothes that fit properly. (An aside: I picked this example because I associate "let's see if we can't..." with a parent talking to a child -- not sure if this is relevant to the discussion at hand.) However, I'll also say it implies that I'm relatively sure of a positive outcome (finding dry clothes that fit). If I say "let's see if we can find you some dry clothes" I don't get quite the same expectation; there's more tolerance for the negative outcome "oh well, I guess not".

The second construction is a slightly different version of the redundant negative. For me, "I don't have but three students" is slightly marked, but fully grammatical, whereas "I have but three students" sounds archaic almost to the point of ungrammaticality. So we have the following, which all entail having three students:

1) I have three students.
2) I have only three students.
3) I have but three students.
4) ?I have but only three students.
5) I don't have but three students.

I have a question mark by (4) because I'm not sure if I like it or not. I
think I don't, but it doesn't seem totally wrong. And then we have the
following, which all entail NOT having three students:

6) I don't have three students.
7) I don't have only three students.
8) *I don't have but only three students.

I'm pretty sure (8) is bad, but if it's not, I think it would mean the
positive, not the negative.

My guess is that we should treat this second construction as parallel to the first one. Despite my archaic interpretation of "I have but three students", this was definitely fine in earlier versions of English, and my guess is that many people would find it unremarkable even today. Thus "I don't have but three students" is essentially the same phenomenon as "Let's see if we can't do that". One avenue of research that might prove useful is semantic research on some of the North American languages. Salishan languages have suffixes that create a "managed to" reading (non-control transitivizers, for those in the know). Navajo has an adversative reading that indicates that a proposition is counter to expectation. Blackfoot (an unrelated language) has the same thing (which coincidentally is also the affix for "please"). This might be what we're seeing in English: variation based on presuppositions of the speaker's ability to bring into being some desired or discussed resultant state.

Saturday, October 9, 2010

new Clarion blog post on writing systems

If you're interested in writing systems, check out my post this week for the Clarion Foundation blog: Writing Systems. As an amateur writer, I sometimes wax a little authorial on these posts, but if you've found them too fiction-oriented so far, know that I'm intending future posts to be more strictly linguistic in nature.

Saturday, September 25, 2010

"the written word"

I was interested to see the headline "LOL -- 'Webspeak' invades Oxford dictionary" on CNN this week. The article is little more than a blurb about some new additions to the Oxford American Dictionary, but I was struck by the first line: "Are years of e-mails, text messaging and status updates finally affecting the written word?" When I read that I did a bit of a double-take, as you might be doing right now. "Hold on a sec," you might think, "aren't ALL of those things written words?" This usage takes to the extreme the idea that "the written word" as a set phrase is somehow not compositional; it doesn't literally mean "a corpus of written materials in contemporary usage", but rather some lofty edifice culled from esteemed writers and curmudgeonly literary critics. While I acknowledge that "the written word" is a semi-idiom in many dialects of American English, I would never use it quite as idiomatically as in this article -- literally juxtaposing a huge corpus of written material with the ethereal ideal of "the written word".

Despite this opening line, the article isn't critical at all of this move by the OAD. The author in fact notes that "It is nice to see Oxford attempting to get with the times" by including expressions that many of us see every day. Lexicographers are often remarkably descriptive, despite the tendency for prescription among those who use their products regularly. However, the author does fear that this will make difficult times for English teachers, as students back up their usage of TTYL and LMAO in academic writing with dictionary citations. I can certainly see English teachers cowering in terror, even though this seems to me ridiculous. As long as we talk about what is appropriate rather than correct, there's no need to fear descriptivism. For instance, I rail against those who teach that it is "incorrect" to use "which" in restrictive relative clauses, or that it is "ungrammatical" to use double modals. On the other hand, in some contexts there are reasons for teaching that it is inappropriate to use these in academic papers (although frankly I'm always against the claim that "which" should be only used for nonrestrictive relative clauses).

The problem with the absolutist view of English is that it isn't absolute. If you try to teach students that "which" should only be used for nonrestrictive relative clauses, you don't have anywhere to turn. The dictionary won't tell you this, esteemed authors don't show this usage, even the venerable old Strunk didn't keep his whichs and thats complementary (though when White came along he added the rule and edited all of Strunk's examples to make them fit the rule). Too often what people think of as "correct" grammar is simply bits and pieces of inconsistent jargon they've internalized from many different, often conflicting, sources. What students need to be taught is that academic writing is a formal style with strict rules. It's not that double modals are wrong, it's that double modals are frowned upon in academic writing. And that's a reason not to use them in such contexts if you want to get a job.