JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for TEXTUALSCHOLARSHIP Archives


TEXTUALSCHOLARSHIP Archives

TEXTUALSCHOLARSHIP Archives


TEXTUALSCHOLARSHIP@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEXTUALSCHOLARSHIP Home

TEXTUALSCHOLARSHIP Home

TEXTUALSCHOLARSHIP  March 2007

TEXTUALSCHOLARSHIP March 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Texts as cultural objects

From:

John Bryant <[log in to unmask]>

Reply-To:

John Bryant <[log in to unmask]>

Date:

Thu, 22 Mar 2007 17:06:07 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (145 lines)

When it comes to using the words "text" and "object," I tend to think in
terms that Barbara's mentor Tom Tanselle offers: that is, a text is
words or wording, and hence essentially conceptual; a book or document
is an object on which a version of the text is inscribed.  Generally,
speaking texts are not objects; they are separate from the material
documents upon which they appear, or even the ink or medium in which
they are inscribed or printed.  At least that is a good place to start.

And when we look at texts in revision, or what I call revision texts, we
have an interesting condition that illustrates this conceptual notion of
text (v. material books) and which might also be worth discussing.  In
some recent articles and in my forthcoming book, Melville Unfolding, I
talk about the "invisible text of revision."  I also alluded to this at
STS last week.  When a writer revises on the page, s/he composes,
strikes out words, inserts words, and re-composes.  What is printed
finally is the last event in the revision process and that is what is
visible to us.  What is invisible to us is the revision text, which may
not be visible even on the manuscript page.

The example I used last week was in Melville's Typee MS.  At one point
in the "text" concerning sacrificial offerings we find 
"the relics of some blo [strikeout blo] recent sacrifice."  

This phrase reaches print as 
"the relics of some recent sacrifice."

But in reality (such as it is), HM first wrote "blo" with the idea of
writing "bloody sacrifice" OR "bloody recent sacrifice"

He changed his mind mid-bloody, crossed out "blo" and then went on to
finish his new image
"recent sacrifice"

I would argue that "bloody sacrifice" is a "text" that existed as a
wording in HM's mind, much like Tanselle's notion of "text" as a
conceptual not material thing.  It is an invisible text of revision in
my parlance, a wording not fully transcribed but one that clearly
existed conceptually.  And these kinds of "text" appear throughout any
rough draft manuscript.  

So these are texts that only an editor can make visible or material by
writing them out in book objects for readers who are interested in
reading a work in revision.

So is this "invisible" thing a text, or an object, or a cultural object?
 I tend to think it is the first and last of these three.  It is
cultural in the sense that any moment of revision may triggered by the
writer interacting with a culture.  When HM decides in a split second
not to write "bloody," he may be reacting to a projected audience need
or restriction; he is bending as well to his own rhetorical strategy. 
And once you have evidence of a reader response imbedded in an authorial
moment, it seems to me you have a culture to contend with.

Book history can deal with such textual cultural matters as revision. 
Revision is an authorial but also a cultural process, just like other
book related processes, like production and consumption, which, as
process, are inherently "invisible."
yrs,
John Bryant

___________
John Bryant, English Department, Hofstra University, Hempstead, NY 11549
>>> "Dan O'Donnell" <[log in to unmask]> 03/22/07 3:56 PM >>>
On Thu, 2007-22-03 at 16:57 +0000, Barbara Bordalejo wrote:
> The problem with "texts as cultural objects" is that it is very  
> vague, so much so that I feel I have to ask you what exactly do you  
> mean by it.

Well I don't mean anything exact, because I don't think it is exactly
definable: like porn, Book History is something you know when you see
it. I guess the closest I'd come to a exclusive definition is: study of
transmission, composition, and reception of texts where the primary
focus is on how these aspects of textual activity were or can be
understood historically, sociologically, or anthropologically.

> I accept, however, that the definition implied a clear delimitation.  
> That is why I liked it. Vague terms lead to confusion and to the  
> danger of creating pseudo-disciplines.

I'm not sure that's really the case: in fact, I'd argue that "What is
Book History" is a useful question only if it is being used
inclusively--i.e. to discover what it is we do that makes us think we
are doing book history--rather than exclusively--i.e. to discover what
it is the others are doing that puts them on the outside. Otherwise you
end up with those barren debates we used to have in classics class about
whether something was a dative of advantage or reference. These terms
are useful when considering inclusively all the various things a dative
can do; but less useful when you try rule exclusively whether a
particular example belong in one or the other category. I don't think
there is necessarily a sharp line that says "this is book history and
this is not."

> Now, what is that common end we are working towards? I would like to  
> be aware, so I can do my part. ;-)

The common goal is the study of texts as cultural objects. QED. ;)

> 
> 
> BB
> 
> 
> On 22 Mar 2007, at 16:29, Dan O'Donnell wrote:
> >
> >
> > Not having been at the roundtable, I can't comment directly--but it
> > seems to me the non-material definition is unfortunately limiting. I
> > prefer the study of texts as cultural objects. It seems to me that
the
> > great power of Book History in the last fifteen years or so has  
> > been the
> > way it managed to overcome aspects of the culture wars from the  
> > 1990s by
> > turning the discussion among philologists, textual scholars, and
less
> > materially oriented theorists and critics to a less zero sum
argument
> > than it once had been: now we are at least arguably working towards
a
> > common end.
> >
> > -- 
> > Daniel Paul O'Donnell, PhD
> > Chair, Text Encoding Initiative <http://www.tei-c.org/>
> > Director, Digital Medievalist Project <http:// 
> > www.digitalmedievalist.org/>
> > Associate Professor and Chair of English
> > University of Lethbridge
> > Lethbridge AB T1K 3M4
> > Vox: +1 403 329 2378
> > Fax: +1 403 382-7191
> > Homepage: http://people.uleth.ca/~daniel.odonnell/
> >
-- 
Daniel Paul O'Donnell, PhD
Chair, Text Encoding Initiative <http://www.tei-c.org/>
Director, Digital Medievalist Project
<http://www.digitalmedievalist.org/>
Associate Professor and Chair of English
University of Lethbridge
Lethbridge AB T1K 3M4
Vox: +1 403 329 2378
Fax: +1 403 382-7191
Homepage: http://people.uleth.ca/~daniel.odonnell/

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2024
February 2024
December 2023
October 2023
September 2023
August 2023
June 2023
April 2023
February 2023
January 2023
December 2022
October 2022
September 2022
July 2022
June 2022
May 2022
April 2022
March 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
July 2020
June 2020
May 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
November 2004
October 2004
September 2004
July 2004
June 2004
May 2004
March 2004
January 2004
November 2003
June 2003
March 2003
January 2003
December 2002
November 2002
September 2002
August 2002


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager