Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE ( (c) Oxford University Press, 2015. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Handbooks Online for personal use (for details see Privacy Policy).

date: 20 January 2017

Abstract and Keywords

The chapter firstly deals with Saussure, then with the scholars most directly influenced by Saussure’s linguistic thought, the schools of Geneva, Prague, and Copenhagen, and finally with other European linguists essentially independent from it, but who are nevertheless labeled as “structuralist”: the Frenchmen Guillaume and Tesnière, and the London school. Saussure’s views are summarized by means of his four classical “dichotomies” (langue vs. parole, synchrony vs. diachrony, signifiant vs. signifié, associative vs. syntagmatic relations). They were differently developed by Saussure’s followers: the Geneva school (Bally, at least) and the Prague school choose a functionalist approach. The Prague school also aimed at overcoming the synchrony/diachrony dichotomy, especially in the domain of phonology, where its most important contributions lie (by Trubetzkoy, Jakobson, and Martinet). On the other hand, the Copenhagen school (whose leader was Hjelmslev) adopted a strictly formal approach. Guillaume’s and Tesnière’s approaches differ from those of the just mentioned schools by focusing on syntax rather than on morphology and phonology. The London school (especially its leader, Firth) worked out a particular approach to phonology (“prosodic phonology”).

Keywords: Saussure’s dichotomies, Prague school, Copenhagen school, Tesnière, London school

Access to the complete content on Oxford Handbooks Online requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can''t find the answer there, please contact us.