Jump to ContentJump to Main Navigation
The George Gershwin Reader$
Users without a subscription are not able to see the full content.

Robert Wyatt and John Andrew Johnson

Print publication date: 2007

Print ISBN-13: 9780195327113

Published to Oxford Scholarship Online: October 2011

DOI: 10.1093/acprof:oso/9780195327113.001.0001

Show Summary Details
Page of

PRINTED FROM OXFORD SCHOLARSHIP ONLINE (www.oxfordscholarship.com). (c) Copyright Oxford University Press, 2019. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a monograph in OSO for personal use (for details see www.oxfordscholarship.com/page/privacy-policy).date: 20 February 2019

George Gershwin and DuBose Heyward: Selected Correspondence (1932–1934)

George Gershwin and DuBose Heyward: Selected Correspondence (1932–1934)

Chapter:
54 George Gershwin and DuBose Heyward: Selected Correspondence (1932–1934)
Source:
The George Gershwin Reader
Author(s):

Robert Wyatt

John Andrew Johnson

Publisher:
Oxford University Press
DOI:10.1093/acprof:oso/9780195327113.003.0054

This chapter the presents the text of selected correspondence between George Gershwin and DuBose Heyward during the period from 1932 to 1934. There are missing portions in the correspondence between Gershwin and Heyward concerning their project to turn the latter's novel Porgy into an opera because of their in-person meetings and telephone conversations. However, the eleven letters presented here provide important insights into their long-distance working relationship.

Keywords:   George Gershwin, DuBose Heyward, Porgy, novel, opera, correspondence, letters

Oxford Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs , and if you can't find the answer there, please contact us .