ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel
  • »
  • Education and Science»
  • Linguistics

PHONOLOGY: A Description of English Vowels Provided by H. Giegerich and How It Differs from that by A.C. Gimson

Updated on March 16, 2017

PHONOLOGY: A Description of English Vowels Provided by H. Giegerich and How It Differs from that by A.C. Gimson

Introduction

Giegerich’s description of the English vowels takes a different approach from the traditional approach to vowel description adopted by Daniel Jones and A. C. Gimson. This difference is believed to result from a quest by phoneticians to find the best way to represent language sounds, showing that there is currently no particular fixed presentation of the way phonetic symbols should be written or described. This attempt to employ an adequate mode of phonemic description as propounded by H. Giegerich is called theory of distinctive features.

Reference Accents

Geigerich emphasizes the relationship in the vowel realization of three specific accents: Received Pronunciation (RP), Southern Scottish English (SSE) and General American English (GA) which he refers to as reference accents and none of the three is necessarily considered the best accent.

Gimson also discusses the variation between the three accents and other accents but as standard regional accents. He does not appear to share in Geigerich’s intention to strike a balance among the three varieties. He presents them only as different accents comparable to the RP, and the RP is probably still presented as the more prestigious variety.

Binary description

Giegerich, in his theory of distinctive features seeks to fully and economically express the phonemic contrasts of a language using the binary labeling presented as [+X] and [-X]. The presentation is done in the following way:

Phoneme A Phoneme B Phoneme C Phoneme D

+X +X -X -X

+Y -Y +Y -Y

where X and Y represent phonetic qualities of the phonemes of a language.

This theory also presents features that can be generally used in every area of phonemic descriptions, not one that will either describe vowels only, and probably required a different specification of feature description for consonants. Phonemes should be described in a way that will accurately show the particular phoneme as distinct from other phonemes in a very economical and manageable manner.

He introduces the use of binary features but observes that the binarity of feature may not efficiently distinguish sounds in every phonological environment; thus, he examines the use of phonemic and phonetic characteristics of phonemes, where the binary feature specification falls under phonetic characteristics of phonemes. He describes phonemes in terms of contrastive function, descriptive function and classificatory function. Below is the mode of description adopted by Giegerich.

i I u ʊ e ε o ^ ɑ a ɔ ɒ

[Consonantal] - - - - - - - - - - - -

[Sonorant] + + + + + + + + + + + +

[Continuant] + + + + + + + + + + + +­­

[Back] - - + + - - + + + - + +

[High] + + + + - - - - - - - -

[Low] - - - - - - - - + + + +

[Round] - - + + - - + - - - + +

[Tense] - - + - + - + - + - + -


Redundancy rule

The redundancy rule by Giegerich is in other words called the rule that predicts a redundant phonological feature from nonredundant ones. This implies that some features discussed by Gimson can be said to be redundant, therefore quite less important. He explains that tense vowels are usually long. In that situation, if a phoneme is described as tense, there is no use mentioning that it is long. He shows this in the following way:

  1. [+tense] [+ long]
  2. [- tense] [- long]

The arrows imply that a tense vowel is equally long and a non-tense (lax) is equally not long. That is to say that if /i/ is described as [ + tense], then predictably, it is long.

In his defence of this argument, he explains that

  1. It is difficult to define “long” and “short” than it is to define tenseness in absolute terms.
  2. Listeners don’t necessarily use it to distinguish the two phonemes.
  3. Not one of the three reference accents has such a distinction.

/i/ bee bead bean beat

/I/ - bid bin bit

He observes that it is quite acceptable that the /i/ in bead, bean, and beat is longer than /I/ in bid, bin and bit in the other of their pairing - up and down. However, /i/ in bee is realised as longer than the one in bead which is in turn longer than the one in bean. In the same manner, the /I/ in bid is longer than the one in bin which is in turn longer than the one in bit. He explains that the long vowel /i/ in beat is shorter than the /I/ in bin.

The use of +/- signs to indicate the presence or absence of a feature in a phoneme is essential to achieve the redundancy avoidance intention which is equally economical. For instance, [+ Tense] and [+ High] automatically mean [- Lax] and [- Low] respectively, so that there is no need to include the four features at the same time when specifying the features of a particular phoneme.




Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: "https://hubpages.com/privacy-policy#gdpr"

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)