Linguistics Stack Exchange is a question and answer site for professional linguists and others with an interest in linguistic research and theory. It only takes a minute to sign up.
Sign up to join this community
in this following paper , if we go to page no- 126 we will find a table with all acoustic features of all german Phonemes.
http://pub.uni-bielefeld.de/luur/download?func=downloadFile&recordOId=2302713&fileOId=2302716
can you kindly refer to any link or documentations where i can get the list of the similar features for english Phonemes.
Thank you.
The acoustic features are independent of the language used. Thus, phones that are common between German and English have the same features. Also, the features are typically based on their details from the IPA charts. The phones listed on that page are in X-SAMPA.
For a discussion of the feature-based model, you can check out the Virtual Linguistics Campus videos:
You can also find:
You can work out how the features map to the IPA consonant and vowel tables, then apply that to the phonemes from English not present in German.
You may need to define the feature set differently, as phoneme features are typically defined in a minimal way to express the phones in a given language, and may not accurately model the IPA. For example, the document defines ç as a mix of consonant and vowel terminology (high fricative) instead of consonant terminology (palatal fricative) -- this is because it uses coronal for s (alveolar) and palatal for ʃ (post-alveolar).
How you define the set of features depends on what information you want to preserve, and what information you want to ignore. It also depends on how many languages you want to support using the model.
If you want a feature set that covers the majority of IPA phonemes, you may want to look at Appendix A (feature abbreviations) of Evan Kirshenbaum's ASCII-IPA at http://www.kirshenbaum.net/IPA/faq.html. I am using an extension of this in my Cainteoir Engine application to support all IPA phonemes:
The features are stored as either binary or enumerated value features defined in https://github.com/rhdunn/cainteoir-engine/blob/master/src/include/cainteoir/phoneme.hpp -- for example, voiced is a binary feature, but place of articulation is an enumerated value.
The list of 3-letter feature codes is defined in https://github.com/rhdunn/cainteoir-engine/blob/master/src/libcainteoir/phoneme/phoneme.cpp.
The feature codes I am using are Kirshenbaum's features, with the following extensions/modifications:
alp -- alveolo-palatalcon -- consonant (implicit if vwl is not listed; used for querying features)epg -- epiglottalsib -- sibilantlbp -- labio-palatalnsy -- non-syllabic diacritic (for diphthongs)tie -- tiebar (this phone is tied to the next phone, for affricates and other co-articulated phones)orl -- Kirshenbaum intended this for oral stop ({orl,stp}) vs nasal stop ({nas,stp}), but uses {stp} and {nas} for these instead, treating stp as a plosive, therefore I am ignoring it.I also have additional features for missing diacritics, intonation, tones, stress and length. This allows me to encode the entire IPA code chart.
I don't have features for things like sonorants, liquids or glides (as used to describe some english phonemes in the SAMPA for English chart at http://www.phon.ucl.ac.uk/home/sampa/english.htm) as the IPA nomenclature covers these and I haven't encountered a situation where the additional features are useful.
The Kirshenbaum feature model differs from the other models as it labels each value with a 3 letter code. Thus, it will assign 2 features to a single binary feature (e.g. vcd for +voice and vls for -voice). I prefer the Kirshenbaum approach as the user-visible model as it is easier to implement (e.g. when processing phoneme set definitions) and allows the internal representation to be changed easier (so you don't have to modify anything using the feature labels).
