Summary and Keywords
Definition of the copula as a discrete grammatical category is problematic. It is the semantically unmarked copulas (simple equivalents of the English verb ‘to be’) which deserve most attention in a comparison of the Romance languages; they have a typically suppletive historical morphology and are often the result of the grammaticalization of full lexical verbs, the point at which true unmarked copular status is achieved being sometimes difficult to identify. The unmarked copulas of the Ibero-Romance languages (Spanish, Portuguese, and Catalan) have the most complex distribution and have proved the most difficult to account for synchronically.
The situation in the early 21st century is the consequence of a progressive encroachment of the reflexes of Latin stare and other verbs on the functions of Latin esse (reference is made to the Classical Latin form esse for convenience; however, the Romance paradigms must be taken to derive from a Vulgar Latin form *essĕre, into which other verbs, notably sedēre ‘to sit’ in the case of the Ibero-Romance languages, were suppletively incorporated). The contrastive study of the development of cognate copular verbs in closely related languages needs closer attention in regard to the identification of the parameters of copula choice with adjectival complements.
Keywords: copulas, auxiliaries, grammaticalization, syntax, pragmatics, etymology, contrastive linguistics, being, becoming
Access to the complete content on Oxford Research Encyclopedia of Linguistics 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. If you are a student or academic complete our librarian recommendation form to recommend the Oxford Research Encyclopedias to your librarians for an institutional free trial.
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.
