ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Grammar
Date: Mon, 26 Jul 2010 20:20:32 +0000	[thread overview]
Message-ID: <AANLkTi=SQZp-fi1QfchP-pw_E9UgpSF1=T7_T6Q2drW4@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi==mCxuGP+oTd78gVMea37eW0Hn1bbj8OE1O--n@mail.gmail.com>

On Mon, Jul 26, 2010 at 4:23 PM, Richard Stephens
<richard.stephens@converteam.com> wrote:
>> On 26-7-2010 11:48, John Haltiwanger wrote:
>>
>>> It seems the most successful/widely adopted form is to vary from 'he'
>>> to 'she' (so that in one sentence you use one, in the next another).
>>> Some authors even change the gender within a sentence. This method was
>>> adopted because 'one' (the "real" correct unisex pronoun) is just too
>>> awkward for extended use. The morphographic he/she/he/she method reads
>>> surprisingly well.
>>
>> maybe male authors could use he and female authors could use she
>> consistently (or we could get accustomed to 'it')
>>
>> Hans
>>
>
> The trend that I have noticed (and which trips off the tongue most easily
> for British english-speakers) is to use the plural 'they' in place of the
> singular pronoun 'he' or 'she'. This avoids having to choose! For purists,
> it rankles, but then we have to accept that the language will change.
> Personally, for serious writing, I use the rather cumbersome, but
> grammatically correct, 'he or she'. I personally don't like 'he/she'. The
> use of 'one' as a pronoun in British english is pretty much dead and sounds
> very stilted to us - only the Queen and old school masters still use it!
> Using 'it' is not an option.
> Best regards,
> Richard

The best thing about switching the pronouns between uses (so, not even
on a sentence basis--in case that is how my first explanation was
perceives--but on the 'usage' of a pronoun. So, generally restricted
to a paragraph) is that you are making the explicit ('he or she')
implicit. You demonstrate that it is equally normal for one to occur
in the place of another in the current of your explanation, without
being cumbersome to speak within any given sentence (unless one is
uncomfortable with the subject noun of a given sentence being
feminine, of course).

The solution of sticking to your own gender is complicated by the
historical-and-ongoing trend to male dominance in academia. The
problematic of the gendered pronoun emerges as male voices normalize
the male as the subject of discourse. In this way Hans' solution would
only perpetuate the issue at hand, which is that feminine pronouns
appear as an "other" when all you ever see is male pronouns. It's
invocation is, simply by virtue of its disparity in appearance, an
edge case. Language has deep roots in the mind such that a linguistic
framing of something as Other can and in fact does 'other' the subject
at which the framing is directed. Some theorists, both male and
female, take it to the position of only using feminine pronouns in
their examples that require third-person. Others change it within
individual sentences in a more extreme demonstration of juxtaposition.

Personally, I find it a sign of forward-thinking when pronouns are
'neutralized' through this juxtaposition of possibility (ie both are
shown to fit equally the examples provided). Perhaps it is simply the
times I grew up in, but reading a man only ever writing 'he' implies a
crucial non-existence of concern re: the subject in the writer's mind.
I don't throw out their theory as a result of it, but it is certainly
something I note.

Then again, I'm a fringe member of a fringe discipline (new media), so
perhaps what I can do/what is expected linguistically is irrelevant
for the majority.

> Converteam UK Ltd. Registration Number: 5571739 and Converteam Ltd.
> Registration Number: 2416188 Registered in England and Wales. Registered
> office: Boughton Road, Rugby, Warwickshire, CV21 1BU.
>
> CONFIDENTIALITY : This e-mail and any attachments are confidential and may
> be privileged.
> If you are not a named recipient, please notify the sender immediately and
> do not disclose the contents to another person, use it for any purpose or
> store or copy the information in any medium.
>
> http://www.converteam.com
>
> Please consider the environment before printing this e-mail.
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
>
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-07-26 20:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 16:23 Grammar Richard Stephens
2010-07-26 20:20 ` John Haltiwanger [this message]
2010-07-26 20:48   ` Grammar Khaled Hosny
2010-07-26 21:25   ` Grammar Hans Hagen
2010-07-27  8:47   ` Grammar Marcin Borkowski
2010-07-27 13:06     ` Grammar John Haltiwanger
2010-07-27 13:17       ` Grammar Hans Hagen
2010-07-27 13:24         ` Grammar luigi scarso
2010-07-27 13:26         ` Grammar Procházka Lukáš
2010-07-27 13:38           ` Grammar Taco Hoekwater
2010-07-27 15:16           ` Grammar Matija Šuklje
2010-07-27 15:28             ` Grammar Arthur Reutenauer
2010-07-27 15:38               ` Grammar Matija Šuklje
2010-07-27 13:31       ` Grammar Arthur Reutenauer
2010-07-27 14:12         ` Grammar John Haltiwanger
2010-07-27 15:04           ` Grammar Arthur Reutenauer
2010-07-27 14:10       ` Grammar David Rogers
2010-07-27 14:15         ` Grammar Hans Hagen
2010-07-27 16:33           ` Grammar David Rogers
2010-07-27 16:59             ` Grammar Matija Šuklje
2010-07-27 17:03               ` Grammar Taco Hoekwater
2010-07-27 15:27       ` Grammar Matija Šuklje
2010-07-27 17:08         ` Grammar John Haltiwanger
2010-07-27 23:10         ` Grammar Marcin Borkowski
2010-07-27 23:40           ` Grammar Hans Hagen
2010-07-28  9:28           ` Grammar Henning Hraban Ramm
2010-07-28 13:14             ` Grammar Alain Delmotte
2010-07-27 22:57       ` Grammar Marcin Borkowski
2010-07-28  5:00         ` Grammar David Rogers
2010-07-28 12:45           ` Grammar Marcin Borkowski
2010-07-28  9:29         ` Grammar John Haltiwanger
2010-07-28  9:39           ` Grammar Thomas A. Schmitz
2010-07-28 13:00             ` Grammar Marcin Borkowski
2010-07-28 13:12           ` Grammar Marcin Borkowski
  -- strict thread matches above, loose matches on Subject: below --
2010-07-24 22:50 Semantic data in ConTeXt? Matija Šuklje
2010-07-25 21:33 ` Matija Šuklje
2010-07-25 23:47   ` Grammar (was: Semantic data in ConTeXt?) David Rogers
2010-07-26  8:23     ` Matija Šuklje
2010-07-26  9:48       ` John Haltiwanger
2010-07-26 10:06         ` Grammar Hans Hagen
2010-07-26 10:20           ` Grammar luigi scarso
2010-07-26 11:56             ` Grammar Matija Šuklje
2010-07-26 12:38               ` Grammar Hans Hagen
2010-07-26 19:33               ` Grammar Martin Schröder
2010-07-26 20:44                 ` Grammar Matija Šuklje
2010-07-27 16:53         ` Grammar (was: Semantic data in ConTeXt?) Rory Molinari
2010-07-27 23:12           ` Marcin Borkowski
2010-07-28  0:00             ` Grammar Hans Hagen
2010-07-28  9:33               ` Grammar John Haltiwanger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=SQZp-fi1QfchP-pw_E9UgpSF1=T7_T6Q2drW4@mail.gmail.com' \
    --to=john.haltiwanger@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).