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

improper segmentation in aa data #8

Closed
LinguList opened this issue Dec 30, 2017 · 1 comment
Closed

improper segmentation in aa data #8

LinguList opened this issue Dec 30, 2017 · 1 comment

Comments

@LinguList
Copy link
Collaborator

we have some cases where the segmentation failed, since before using ipa2tokens, the spaces were not converted to "_", which is the usual way to use the function. Note that ipa2tokens splits as a default on white-space, which has advantages when using the function internally, but requires to remove whitespace by replacing by either nothing or by the underscore prior to initial segmentation.

I estimate that there are about 20 errors in the data (judging on eyeballing), and we can tolerate it, but it is important, in case you apply ipa2tokens in the future, that you keep in mind how the function works. I might add an additional comment to lingpy.org, but I think that basically the description is exhaustive enough already. The best way to prepare data anyway is to use orthography profiles. This is how we arrived at the segmentation of PN data and also ST data. But it requires, of course, more user-input than using lingpy for the segmentation task...

@LinguList
Copy link
Collaborator Author

If you agree that we leave these 20-odd errors as is, please feel free to just close this issue.

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

2 participants