The next draft of my Metlab script has just left the building – a relief really, as the temptation is always to tinker with it some more (one of my stranger ambitions with the new draft was to bring it in dead on 90 pages – I got to 94 – good enough for the moment). I’m not even going to hazard a guess as to how many times I had to re-write the first 30 pages – this ‘making it up as you go along’ lark is not good for one’s mental health. Next time out, I’m outlining all the way.
Metlab aside, I’ve been pondering recently about subtext:
Subtext is content of a book, play, musical work, film, video game or television series which is not announced explicitly by the characters (or author) but is implicit or becomes something understood by the observer of the work as the production unfolds. Subtext can also refer to the thoughts and motives of the characters which are only covered in an aside. Subtext can also be used to imply controversial subjects without specifically alienating people from the fiction, often through use of metaphor.
That’s from Wikipedia, and is all well and good, but what happens when a subtext is so submerged it takes determined efforts and discussion from viewers to unearth it? For instance, this is from an essay by Bill Blakemore on The Shining:
The Shining is also explicitly about America's general inability to admit to the gravity of the genocide of the Indians - or, more exactly, its ability to "overlook" that genocide. Not only is the site called the Overlook Hotel with its Overlook Maze, but one of the key scenes takes place at the July 4th Ball. That date, too, has particular relevance to American Indians. That's why Kubrick made a movie in which the American audience sees signs of Indians in almost every frame, yet never really sees what the movie's about. The film's very relationship to its audience is thus part of the mirror that this movie full of mirrors holds up to the nature of its audience.
I’ve used this quote from Umberto Eco before, but it seems apt enough again here, that the novel is a machine for generating possibilities. That’s partially what I love so much about The Shining – on the surface, it’s a masterful horror film. The various subtexts, however, provide so much more – there’s even a theory (posited by David Kirkpatrick) that The Shining can be viewed within a Marshall McLuhan subtext. I’m not so sure about this as the argument is a little laboured, but even so: there’s nothing to say they’re wrong, which is part of the beauty of subtext, in that it provides an entertaining battleground for ideas.
The only problem with subtext as far as I’m concerned is that it’s incredibly difficult to submerge it adequately without it either A) sinking altogether (so that no-one notices it), or B) making a huge song and dance about it (and when that happens, it’s not really a subtext any more). Where subtext informs a theme to such an extent as it (allegedly) does in The Shining, then it can be incredibly difficult to pick apart the filmmaker’s intentions (which is always part of the fun of course). But in a script, how far do you push it? Subtext will always be submerged to a certain degree, but if it falls off a reader’s radar altogether, you could argue that you haven’t done your job. Make it too obvious, and you risk it clanking about like a gawky teenager in a suit of armour - and no-one wants that.
All of which means: I love subtext, but I find it very difficult to strike the right balance. How about you?
You’d hardly recognize Arlo Finch overseas
9 hours ago