Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postvocalic aspiration in Urarina #141

Closed
MuffinLinwist opened this issue Feb 28, 2024 · 4 comments
Closed

Postvocalic aspiration in Urarina #141

MuffinLinwist opened this issue Feb 28, 2024 · 4 comments

Comments

@MuffinLinwist
Copy link

MuffinLinwist commented Feb 28, 2024

Converting the northernperu dataset into CLDF, I run into some CLTS sound class errors. Urarina faces processes of postvocalic aspiration in between syllables since the language does not accept consonants on coda position (Olawsky 2006, pp. 40-1). The solution adopted so far is to transcribe it in the ortho-profile as:

Grapheme IPA
!aʰ/a
!iʰ/i
!uʰ/u

This strategy deletes the information. The grammar mentions that this phenomenon is optional (pp. 41). It appears, however, often throughout the dataset.

On the other hand, tanscribing it as iʰtʃ i ʰtʃ does not quite reflect the insertion of /h/ after vowels. Below, I copy some of the CLTS errors I get:

ID LANGUAGE CONCEPT FORM SEGMENTS
Urarina-102_near-1 Urarina 102_near iʰtʃũṹ i <<ʰ>> tʃ u ∼ !ṹ/u ∼
Urarina-106_nose-1 Urarina 106_nose aʰs̪í a <<ʰ>> s !í/I
Urarina-112_toplay-1 Urarina 112_toplay n̪ẽʰkuat̪ihján̪ãã n e ∼ <<ʰ>> k u a t i h j !á/a n a ∼ a ∼

@LinguList or @xrotwang, how can we better represent this aspiration?

@MuffinLinwist MuffinLinwist changed the title Postvocalic aspiration in Urartian Postvocalic aspiration in Urarina Mar 11, 2024
@LinguList
Copy link
Contributor

Is there a problem in representing aspiration on vowels as "breathy"?

@LinguList
Copy link
Contributor

Check here. This is allowed, just not the superscript h.

@FredericBlum
Copy link

@MuffinLinwist Have you adopted this solution for Urarina? Would be nice to have this solved for the NP-release. You can then just close this issue

@MuffinLinwist
Copy link
Author

Yes, thanks @LinguList for the response. I'm closing the issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants