352
Views
0
CrossRef citations to date
0
Altmetric
Original Articles

Tense-lax merger: Bangla as a first language speakers’ pronunciation of English monophthongs

ORCID Icon ORCID Icon
Pages 220-241 | Received 18 Nov 2016, Accepted 25 Apr 2017, Published online: 09 Jun 2017
 

ABSTRACT

Native speakers of English naturally differentiate tense–lax vowels (e.g. /i:/ in FEAST vs. /ɪ/ in FIST) in their speech. Can the speakers of Bangla, Hindi and Japanese as a first language (L1) learning and using English as a second language (L2) maintain such contrastive vowel qualities? Hence, this study investigates L1 Bangla speakers’ pronunciation of English tense–lax vowels. Data collected from recordings of a reading passage and a set of sentences by 19 speakers are analysed using Pratt, focusing on the contrast between traditionally paired English monophthongs /i:/ vs. /ɪ/, /u:/ vs. /ʊ/, /ͻ:/ vs. /ɒ/ and /ɑ:/ vs. /ʌ/ in terms of their length and high–low/front–back articulatory qualities. The findings suggest that the participants seem not to distinguish between these paired monophthongs in terms of their high–low/front–back qualities; although they mostly demonstrate maintaining their long–short features. Besides, these paired vowels appear to contrast to some extent on gender variation.

Notes

1. ‘The Boy Who Cried Wolf’ is a suitable text for measuring formant values in English vowel production.

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.