xrotwang
commented
7 years ago Yes, the class hierarchy shouldn't get out of hand.
Am 11.09.2017 22:19 schrieb "Johann-Mattis List" notifications@github.com:
If we stick to BIPA, we can mechanically assign the standard characters to tones. We could even expand the system by a class that lists both vocalic and tone features, following these rules:
This would drastically increase the acceptance of sounds, and computationally, separating may be automatized, and adding the tones in our potential space to all existing vowels is a no-brainer. But it needs some thinking nevertheless, whether we want to really go this way, given that we know that transcription systems usually don't follow IPA-rules here. Maybe, the way to go is the JIPA collection, where they have quite a few of these examples. Needless to say, that this would be another class: tonevowels, or vowelswithtones.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lingpy/clts/issues/24, or mute the thread https://github.com/notifications/unsubscribe-auth/AA1HKE8pEPzWIqtG9R7s-icaDLlkF0aSks5shZXmgaJpZM4PTtxN .
LinguList
If we stick to BIPA, we can mechanically assign the standard characters to tones. We could even expand the system by a class that lists both vocalic and tone features, following these rules:
This would drastically increase the acceptance of sounds, and computationally, separating may be automatized, and adding the tones in our potential space to all existing vowels is a no-brainer. But it needs some thinking nevertheless, whether we want to really go this way, given that we know that transcription systems usually don't follow IPA-rules here. Maybe, the way to go is the JIPA collection, where they have quite a few of these examples. Needless to say, that this would be another class:
tonevowels, orvowelswithtones.