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

Words and Syllables #64

Open
HallowXIII opened this issue Aug 2, 2015 · 3 comments
Open

Words and Syllables #64

HallowXIII opened this issue Aug 2, 2015 · 3 comments

Comments

@HallowXIII
Copy link

The SCA does not currently handle suprasegmentals internally. While it is possible to hack together rules approaching this, it would be better to represent words as sequences of syllables, each of which can be specified for suprasegmental features.

Syllables themselves should be sequences of segments, with the syllable being aware of the type and position of elements within it -- along the lines of public Segment getNucleus().

The initial iterations of this feature will require syllable breaks to be explicitly specified in the lexicon and should be made strictly optional. A future integration as the default system will require an intelligent segmenter.

@HallowXIII HallowXIII self-assigned this Aug 2, 2015
@samanthamccabe
Copy link
Owner

Think this is quite feasible. All data are stored in Sequence objects, which could be enhanced to have a "syllable" tier representing which segments belong to which syllables.

Requiring the user's lexicon to reflect syllable boundaries is excellent at this point, since a lot of people may not need them, and it reduces the burden on us. We'd still need a way to indicate the nucleus.

When a user uses whatever command to enable syllables, they might also provide a series of syllable patterns (using regular expressions). The SCA could use these to determine what segment or segments represent the nucleus. If they were using features, this might be a little easier.

@HallowXIII
Copy link
Author

PyLaut use(s?/d) features everywhere, so what we did there was just check for [+syllabic] and arrange the consonants around that -- would probably mesh nicely with syllable patterns.

@samanthamccabe
Copy link
Owner

Well, for better or worse, Haedus is feature-system-agnostic. I'm sure there's some reasonably simple way of doing it.

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

No branches or pull requests

2 participants