Download - Pnronline.com.au
Download - Pnronline.com.au
Download - Pnronline.com.au
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
words<br />
Duh Vinci<br />
A<br />
paper I edited recently for AAPG<br />
regularly used the wrong words. For<br />
example, High density sources have<br />
been interpreted as Miocene reefs, amplified<br />
by underlying Oligocene intrusives.<br />
(In the interests of not too blatantly fingering<br />
the <strong>au</strong>thor, I have modified this and other<br />
examples slightly from the original, retaining<br />
the errors but changing the setting.)<br />
Are the high-density bodies properly described<br />
as ‘sources’? The context is that they are<br />
the ‘source’ of the positive Bouguer Gravity<br />
anomalies. Underlying dense intrusive material<br />
was interpreted as also contributing to the<br />
gravity highs. So, it was the gravity highs that<br />
were amplified, not the Miocene reefs.<br />
I do sense an increase in this type of error in<br />
the geological papers I’ve edited over the past<br />
few years. Is this the geoscientific <strong>com</strong>munity’s<br />
drift into Amglish, the ‘language’ I discussed last<br />
month, with its dumbing-down loss of precision<br />
and a lack of any care at the loss; indeed, a<br />
cheering at the freedom of close-enough will<br />
do, and appl<strong>au</strong>ding this as far more politically<br />
correct for our times than the elitist notion of<br />
speaking properly. I hope not.<br />
By co-incidence, I was browsing through past items<br />
in a favourite blog, Language Log, when I came<br />
across posts by Geoffrey K. Pullum criticising the<br />
writing in Dan Brown’s novel The Da Vinci Code.<br />
One of his posts offered an excellent example of<br />
imprecision. (May 1, 2004, The Dan Brown Code)<br />
Pullum quoted from the first page of the novel,<br />
as terrified Louvre curator Jacques S<strong>au</strong>nière<br />
flees from his attacker.<br />
A voice spoke, chillingly close. "Do not move."<br />
On his hands and knees, the curator froze, turning<br />
his head slowly. Only fifteen feet away, outside<br />
the sealed gate, the mountainous silhouette of<br />
his attacker stared through the iron bars. He was<br />
broad and tall, with ghost-pale skin and thinning<br />
white hair. His irises were pink with dark red pupils.<br />
Pullum then listed the errors and imprecisions<br />
– what he, being precise, called infelicities and I<br />
quote him almost directly below.<br />
1. A voice doesn't speak — a person speaks; a<br />
voice is what a person speaks with.<br />
2. ‘Chillingly close’ would be right in your<br />
ear, whereas this voice is fifteen feet away<br />
behind the thundering gate.<br />
3. It was the fall of the gate that made a thunderlike<br />
noise; the gate itself wasn’t thundering.<br />
4. The curator cannot slowly turn his head<br />
if he has frozen; freezing (as a voluntary<br />
human action) means temporarily ceasing<br />
all muscular movements.<br />
5. A silhouette does not stare! A silhouette is a<br />
shadow.<br />
6. If the curator can see the man's pale sk in,<br />
thinning hair, iris colour, and red pupils (all<br />
at fifteen feet), the man cannot possibly be<br />
in silhouette.<br />
Perhaps we can call such errors duhvincis.<br />
It is important for <strong>au</strong>thors to read closely what<br />
they have written. This is especially true for<br />
younger <strong>au</strong>thors, many of whose schooling<br />
had a less rigorous approach, shall we say, to<br />
grammar and writing than was the case for<br />
older Pesapersons.<br />
I have touched before on this need for very<br />
careful reading of what has been written before<br />
it is passed onto editors or managers and the<br />
like. It is a point that needs regular restating. It is<br />
too easy to simply glance across the words and<br />
sit back with a Nobel-winners smile, confident<br />
that the words say exactly what was meant.<br />
Consider these sentences from recent papers:<br />
••<br />
‘When lake level rose and spilled into an<br />
adjacent basin …’<br />
••<br />
‘The overfilled lake model occurs when<br />
the rate of supply of sediment and water<br />
exceeds the potential ac<strong>com</strong>modation.’<br />
••<br />
‘The top surface of the lower unit reflects<br />
the thickness changes of this sequence.’<br />
••<br />
‘The main objective was to interpret<br />
basement structure within the data.’<br />
••<br />
‘The contract deadline was not achieved<br />
bec<strong>au</strong>se of the timely negotiations<br />
necessitated by the contractor.’<br />
The meaning is clear enough in most cases but<br />
the words do not say what the writer meant to<br />
be saying.<br />
••<br />
Lake levels can’t spill. ‘When lake levels rise<br />
and the water spills into …’<br />
••<br />
Models don’t occur, in the real-world sense<br />
used here. (Plus I have always had a struggle<br />
ac<strong>com</strong>modating ‘ac<strong>com</strong>modation space’ as<br />
a necessary term – though several geologist<br />
friends I admire greatly, and whose skills<br />
exceed mine, are enthusiastic supporters and<br />
users of the term; so it might be me. But, in<br />
this case, is it the potential ac<strong>com</strong>modation<br />
that is being exceeded? Or is it the actual<br />
ac<strong>com</strong>modation? And, while I’m being picky,<br />
shouldn’t it be ‘ac<strong>com</strong>modation space’.)<br />
••<br />
The isopach reflects (shows?) the changing<br />
thickness of the sequence; the top (upper?)<br />
surface does not. (I can hear the ho wls<br />
that, given a smooth lower surface for the<br />
sequence, the top surface would reflect the<br />
thickness changes. Fair enough. If that was<br />
the case, the sentence is acceptable. But it<br />
has to be read in context and that decision<br />
made by the writer.)<br />
••<br />
There is no ‘basement structure within the<br />
data’; …from the data? …using the data.<br />
Maybe … use the data to interpret …<br />
••<br />
The negotiations weren’t timely; they<br />
were time-consuming. ‘Required’ by the<br />
contractor would be better.<br />
As several of these examples show, a <strong>com</strong>mon<br />
problem is the imprecise use of a term in relation<br />
to the action being discussed; the lake level<br />
‘spilling’ or the model ‘occurring’. Sometimes it is<br />
just poor expression and needs more work.<br />
Confronted by these confused sentences, an<br />
experienced editor or manager will begin to<br />
look very closely at the technical details. If<br />
a writer can’t put down what he means in a<br />
simple and clear way, it might be revealing<br />
that he doesn’t have a clear and simple<br />
understanding of what he (or she) is saying.<br />
I have cited Hemingway many times in this<br />
column, most <strong>com</strong>monly his declaration that<br />
when you know something well (as opposed<br />
to knowing about it – a distinction one of my<br />
mentors was very fond of ), you know what you<br />
can leave out and still get the message thr ough<br />
clearly. When you don’t know well enough<br />
what you’re writing about, it shows.<br />
On which note, let me remind younger<br />
Pesapersons that the Papa in my August column,<br />
A Reminder from Papa, was not me being all<br />
fatherly. That was Hemingway's popular nickname,<br />
given him, not surprisingly, by his children, and<br />
adopted quite widely by his friends and admirers<br />
later in his life and after his death.<br />
All the best for the New Year. Enjoy the<br />
Christmas season. If it all gets too much, read<br />
the first few pages of The Da Vinci Code and<br />
have a bloody good l<strong>au</strong>gh. Try not to think too<br />
much about the money he made writing that<br />
badly about something so ridiculous. And let’s<br />
have less duhvincis in our writing in 2013.<br />
Peter Purcell <br />
56 | PESA News Resources | December 2012 / January 2013