Obviously I don't know when to give up & go to sleep, 'cause I skimmed yet -more- essays/arguments in
mannazone ('The Administration' comm) & I don't want to go into specifics, but it made me think about authorial intent in a slightly different way.
The thing is, really, that it's a double-edged sword, isn't it? What I mean is, it is both necessary to understanding (illuminating?) some basic plot-points or developments when utilized in key/minimum amounts and completely poisonous when used to explain away a reader's genuine reactions to what actually did happen. Like, you can use a known case of 'intent' to debunk what I'd call a 'transformative theory'-- one that takes canon and makes it a metaphor for something else, some external symbology. A good example of this is the things Harry/Hermione shippers found in book 3 to support canon H/Hr: those things were just contrary to the point of the given scenes, and you can call upon authorial intent as support of this argument. However, you can only use it to disprove actual conclusions from specific incidents: you can't disprove subtext or ambiguous cues (whether used for H/Hr, Sirius/Remus or even Harry/Draco subtext).
In other words, you can't say 'seeing' Sirius/Remus isn't a valid emotional response to canon cues; you -can- say it's not actually canon. Does that make sense?
Somehow this seems even more important when the author is actually there to argue with you; when they get involved and interact with fandom.
There's a limit there-- you can say what you intended (as the writer), but you can't dictate beyond what the writing itself shows. If, in fact, the writing didn't follow your precise outlined ideas (the meta!story in the writer's head), then it may be bad writing, or it may be the nature of writing itself, but it's not like the meta!story therefore overwrites the actual story experienced by a given reader.
A big part of this is simply a game of definitions; when it comes to talking about a character's emotions especially, we're walking on extremely shaky ground. One person's 'love' isn't another person's 'love'; what the writer may see as 'unacceptable' and 'indicative of moral failure' (or a diagnosable psychiatric disorder), the reader may see as 'tragic' and indicative of a wounded heart that needs healing. Also, what's 'obviously just a sexual thing' for the writer -and- a reader must necessarily be overridden if it's not for the characters as they perceive themselves. Is the reader wrong & the writer right? Vice versa?
The answer has to be "neither", of course: regarding their own emotions, the character is right (and sometimes, if it's ambiguous and/or the character's confused, there is simply no answer). You cannot dictate meta-questions of a story's reality-- the sort of stuff that in actual reality, people would argue about because it's subjective. (Ie, 'did he really love her?'-- what possible consensus could there be in any situation like this? He did if he thinks he did, period; he did if he acts like he did also, to a large extent, yes, but then this is in the realm of 'reader's perception of subtext'.)
I'm especially impatient with any attempt by the author to project into a future they hadn't actually written; I won't accept 'he feels like X' or 'X is likely to happen' if this hasn't been shown yet. This is simply ridiculous-- the writer doesn't own every possible permutation of the future for the characters in their universe! I'm sure this is actually why some writers hate fanfic, because they think if they stop people from writing it, they'll actually stop them from thinking it. Uh-uh, no go. People perceive half-formed futures as soon as they have their idiosyncratic reactions to a given character's actions/emotions/etc; in terms of unstated consequences, a given reader will believe what makes sense to them based on life experience-- and this is a necessary part of reading, of bonding with fiction. It is that bit of self-projection that draws one into the world & the characters, that tugs them ever so slightly out of the author's head and into the reader's!
My issue, really, is that I'm perfectly happy with ambiguity. I love it that I can't really -know- that Brian's in love with Justin in QaF (though I think he is, in his own way) or whether Toreth 'more than just needs' Warrick (though I think he does, in his own way). Both of these are self-centered bastards with long-suffering caring boyfriends, and I admit there may be -some- wish-fulfillment in my wanting to look at the bright side as a reader-- but in both cases the romance becomes flat and utterly boring if you categorically answer 'no' (as the writers have in both instances, though the circumstances aren't the same).
What I'm trying to say is, 'Authorial Intent' is useful for understanding, but it cannot-- should not-- attempt to penetrate a reader's heart. In theory, I can accept 'this isn't love'-- objectively, things remain ambiguous. In terms of my own reaction, though, there is no ambiguity-- the bells ring, the numbers add up, my alarms go off-- bingo! I can shout it from the rooftops! I embrace subjectivity, since as a reader, it's become my story and in a very real sense these are my characters 'cause they also live in my head, so. This doesn't mean 'in my head', Draco Malfoy 'really' turns into this svelte angel who wears leather pants (or someone who's about to whisper sweet nothings anytime soon)-- y'know, because he's just... not like that. However, yes, my Draco Malfoy can be obsessed and in denial; my Toreth can be also. Yes. Oh yes. I can make this work with canon, okay.
So bite it. HE'S IN LOVE. :P
The thing is, really, that it's a double-edged sword, isn't it? What I mean is, it is both necessary to understanding (illuminating?) some basic plot-points or developments when utilized in key/minimum amounts and completely poisonous when used to explain away a reader's genuine reactions to what actually did happen. Like, you can use a known case of 'intent' to debunk what I'd call a 'transformative theory'-- one that takes canon and makes it a metaphor for something else, some external symbology. A good example of this is the things Harry/Hermione shippers found in book 3 to support canon H/Hr: those things were just contrary to the point of the given scenes, and you can call upon authorial intent as support of this argument. However, you can only use it to disprove actual conclusions from specific incidents: you can't disprove subtext or ambiguous cues (whether used for H/Hr, Sirius/Remus or even Harry/Draco subtext).
In other words, you can't say 'seeing' Sirius/Remus isn't a valid emotional response to canon cues; you -can- say it's not actually canon. Does that make sense?
Somehow this seems even more important when the author is actually there to argue with you; when they get involved and interact with fandom.
There's a limit there-- you can say what you intended (as the writer), but you can't dictate beyond what the writing itself shows. If, in fact, the writing didn't follow your precise outlined ideas (the meta!story in the writer's head), then it may be bad writing, or it may be the nature of writing itself, but it's not like the meta!story therefore overwrites the actual story experienced by a given reader.
A big part of this is simply a game of definitions; when it comes to talking about a character's emotions especially, we're walking on extremely shaky ground. One person's 'love' isn't another person's 'love'; what the writer may see as 'unacceptable' and 'indicative of moral failure' (or a diagnosable psychiatric disorder), the reader may see as 'tragic' and indicative of a wounded heart that needs healing. Also, what's 'obviously just a sexual thing' for the writer -and- a reader must necessarily be overridden if it's not for the characters as they perceive themselves. Is the reader wrong & the writer right? Vice versa?
The answer has to be "neither", of course: regarding their own emotions, the character is right (and sometimes, if it's ambiguous and/or the character's confused, there is simply no answer). You cannot dictate meta-questions of a story's reality-- the sort of stuff that in actual reality, people would argue about because it's subjective. (Ie, 'did he really love her?'-- what possible consensus could there be in any situation like this? He did if he thinks he did, period; he did if he acts like he did also, to a large extent, yes, but then this is in the realm of 'reader's perception of subtext'.)
I'm especially impatient with any attempt by the author to project into a future they hadn't actually written; I won't accept 'he feels like X' or 'X is likely to happen' if this hasn't been shown yet. This is simply ridiculous-- the writer doesn't own every possible permutation of the future for the characters in their universe! I'm sure this is actually why some writers hate fanfic, because they think if they stop people from writing it, they'll actually stop them from thinking it. Uh-uh, no go. People perceive half-formed futures as soon as they have their idiosyncratic reactions to a given character's actions/emotions/etc; in terms of unstated consequences, a given reader will believe what makes sense to them based on life experience-- and this is a necessary part of reading, of bonding with fiction. It is that bit of self-projection that draws one into the world & the characters, that tugs them ever so slightly out of the author's head and into the reader's!
My issue, really, is that I'm perfectly happy with ambiguity. I love it that I can't really -know- that Brian's in love with Justin in QaF (though I think he is, in his own way) or whether Toreth 'more than just needs' Warrick (though I think he does, in his own way). Both of these are self-centered bastards with long-suffering caring boyfriends, and I admit there may be -some- wish-fulfillment in my wanting to look at the bright side as a reader-- but in both cases the romance becomes flat and utterly boring if you categorically answer 'no' (as the writers have in both instances, though the circumstances aren't the same).
What I'm trying to say is, 'Authorial Intent' is useful for understanding, but it cannot-- should not-- attempt to penetrate a reader's heart. In theory, I can accept 'this isn't love'-- objectively, things remain ambiguous. In terms of my own reaction, though, there is no ambiguity-- the bells ring, the numbers add up, my alarms go off-- bingo! I can shout it from the rooftops! I embrace subjectivity, since as a reader, it's become my story and in a very real sense these are my characters 'cause they also live in my head, so. This doesn't mean 'in my head', Draco Malfoy 'really' turns into this svelte angel who wears leather pants (or someone who's about to whisper sweet nothings anytime soon)-- y'know, because he's just... not like that. However, yes, my Draco Malfoy can be obsessed and in denial; my Toreth can be also. Yes. Oh yes. I can make this work with canon, okay.
So bite it. HE'S IN LOVE. :P
Re: heh!
Date: 2006-12-04 07:56 am (UTC)They may be claiming that the author is promoting a definition of love in the story? I don't know, I wasn't able to follow this. But, since the true debate is not over what is there, but what it should be called, it's not really a text issue.
Re: heh!
Date: 2006-12-04 08:03 am (UTC)If in fact the author -was- promoting a definition of love (judging from the central relationship and how it works), it would be the unhealthy/selfish love type, haha, that's the most silly part of it.