26.11.2012 Views

Phi-features and the Modular Architecture of - UMR 7023 - CNRS

Phi-features and the Modular Architecture of - UMR 7023 - CNRS

Phi-features and the Modular Architecture of - UMR 7023 - CNRS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

258<br />

a. me/*se: I am <strong>the</strong> only person who complains about me.<br />

b. me/se: I am <strong>the</strong> only person who complains about himself.<br />

(French, Morin 1978: 342f.)<br />

Interpretatively <strong>the</strong> simplest solution might be for fake indexicals to get <strong>the</strong>ir<br />

1 st /2 nd persons <strong>features</strong> outside <strong>the</strong> syntax-interpretation computation, at PF, but it<br />

requires long-distance phi-<strong>features</strong> transmission at PF (Kratzer 2009, Heim 2008).<br />

The PCC demonstrates that fake indexicals are in fact [+person] in syntax, not<br />

only PF, because <strong>the</strong>y license PCC repairs in French (397) (cf. section 4.4).<br />

(397) Il n'y a que moi qui trouve personne<br />

a. pour me leur présenter/vendre.<br />

b. pour me présenter/vendre à eux.<br />

to me.A <strong>the</strong>m.D introduce/sell to <strong>the</strong>m<br />

I am <strong>the</strong> only one who finds no one to introduce/sell me.A *<strong>the</strong>m.D /<br />

to <strong>the</strong>m. (O<strong>the</strong>rsi do find someone to introduce/sell me/<strong>the</strong>mi to <strong>the</strong>m.)<br />

(French)<br />

The [+person] specification <strong>of</strong> fake indexicals in (397) only suggests PF phitransmission<br />

is not <strong>the</strong> right solution. The literature develops ways to interpret<br />

bound 1 st /2 nd person pronouns appropriately, as well as proposals for <strong>the</strong>m to be<br />

eliminated by a syntactic relationship (Schlenker 2005, Maier 2006, Heim 2008).<br />

The fake 3 rd person reading <strong>of</strong> 1 st /2 nd person pronouns is not available in examples<br />

like (366), repeated below (cf. Heim 2008). In (366) 3 rd person pronouns have<br />

<strong>the</strong> speaker/addressee among <strong>the</strong>ir values, although ordinarily only 1 st /2 nd person<br />

pronouns do so. Sauerl<strong>and</strong> (2008) proposes that 3 rd person pronouns do not have<br />

any person restriction, <strong>and</strong> derives <strong>the</strong> distribution <strong>of</strong> uses from <strong>the</strong> principle <strong>of</strong><br />

Maximize Presuppositions in (398). The principle requires <strong>the</strong> use <strong>of</strong> 1 st /2 nd person<br />

pronouns whenever <strong>the</strong>ir value meets <strong>the</strong>ir lexical presupposition in (362) <strong>of</strong> referring<br />

to <strong>the</strong> speaker/addressee. Since in (366), <strong>the</strong> bound pronouns take on both<br />

speaker <strong>and</strong> non-speaker values, this presuppositions cannot be met. Then Maximize<br />

Presuppositions allows 3 rd person.<br />

(366) Eachi <strong>of</strong> usj evaluates herselfi/<strong>the</strong>mselvesi/*ourselvesi/j<br />

(398) Maximize Presuppositions (consequence <strong>of</strong>): The <strong>features</strong> that appear on<br />

a pronoun are chosen so as to maximize <strong>the</strong> presupposition <strong>the</strong>y express,<br />

as long as no presupposition failure is triggered.<br />

(Schlenker 2005; cf. Heim 2001, 2008, Sauerl<strong>and</strong> 2008)<br />

Maximize Presuppositions might be expected to interact in an interesting way<br />

with <strong>the</strong> Person Case Constraint. It governs <strong>the</strong> choice between LFs with more or<br />

less specified pronouns according to <strong>the</strong>ir presupposition failure. We might expect<br />

<strong>the</strong> Person Case Constraint to matter for it. It prohibits [+person] pronouns in cer-

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

Saved successfully!

Ooh no, something went wrong!