01.02.2015 Views

Presuppositions and Pronouns - Nijmegen Centre for Semantics

Presuppositions and Pronouns - Nijmegen Centre for Semantics

Presuppositions and Pronouns - Nijmegen Centre for Semantics

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

28 <strong>Presuppositions</strong> <strong>and</strong> <strong>Pronouns</strong><br />

(62)) [most x: professor x][the x ] Y: Y Yare Coca Cola shares owned by x]<br />

(x sold Y)<br />

This mayor may not be a possible reading of (61a), but it certainly does not<br />

represent the interpretation we want to have, since (61a) might be true, while<br />

(62) would be false, if it weren't the case that most professors owned Coca<br />

Cola shares. The same holds, mutatis mut<strong>and</strong>is, <strong>for</strong> (61b, c).<br />

These observations will suffice to discredit the notion that projection<br />

phenomena can be accounted <strong>for</strong> in terms of scope. The reason <strong>for</strong> this is<br />

that presupposition projection is a pragmatic phenomenon, whereas scope<br />

taking is much more of a surface phenomenon. If we speak about an<br />

expression ex a in terms of scope, we are referring to some a-sized unit, i.e. a<br />

itself or some semantic entitity corresponding with a, such as a's oc's correlate at<br />

LF or its interpretation in a given model. Although in some frameworks this<br />

is only a metaphor, the guiding intuition is that a's scope is determined by<br />

moving a about. If, on the other h<strong>and</strong>, we speak of a presupposition triggered<br />

by ex, a, the metaphor is a completely different one, the idea being, rather, that<br />

ex a requires us to check that some piece of in<strong>for</strong>mation is given. This<br />

distinction is perhaps most evident in expressions that have scope <strong>and</strong> trigger<br />

presuppositions at the same time, like quantified NPs. An NP such as most<br />

flowers, <strong>for</strong> example, takes scope with respect to other parts of the sentence<br />

in which it occurs, while at the same time it triggers a presupposition, viz.<br />

that some collection of flowers is contextually given.<br />

The distinction between scope taking <strong>and</strong> presupposition projection is<br />

obscured by the un<strong>for</strong>tunate circumstance that definite NPs, which have<br />

always been the presuppositional expressions par excellence, happen to have<br />

the special property that their descriptive contents coincide with the<br />

presuppositions they induce. On the presuppositional account of definitess<br />

that I advocate, a definite like the banana induces the presupposition that<br />

some banana is given in the discourse context, <strong>and</strong> to a first approximation<br />

that is all there is to say about the content of the banana. In general, the<br />

content of an expression divides into an asserted <strong>and</strong> a presupposed part.<br />

Definites are special in that the asserted part is empty. Consequently, unless<br />

the presupposition triggered by a definite NP a is blocked, which will rarely<br />

happen, it will seem as if a itself had taken wide scope, but this is an illusion,<br />

as we have seen, because definite NPs aren't scope-bearing expressions.<br />

Although it wasn't the main purpose of this section to argue against<br />

Russell's theory of descriptions, I would like to conclude with a remark on<br />

this theory's theory'S remarkable staying power. I will make my point by way of a<br />

simile. My little niece has developed her own theory about the evolution of<br />

<strong>for</strong>efingers.1 177 It is not a very complex theory; in fact I can summarize it in<br />

seven words: <strong>for</strong>efingers have evolved <strong>for</strong> pointing at things. My niece<br />

plural definites.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!