-
Notifications
You must be signed in to change notification settings - Fork 5
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
Ambiguous f. (forma or filius) needs a warning #57
Comments
created by @dimus at https://gitlab.com/gogna/gnparser/-/issues/43 mentioned in issue #63 |
created by @dimus at https://gitlab.com/gogna/gnparser/-/issues/44 closed |
created by @dimus at https://gitlab.com/gogna/gnparser/-/issues/45 I am closing this ticket again, and opening a new one about changing |
created by @gdower at https://gitlab.com/gogna/gnparser/-/issues/46 Yuri thinks keeping I can also easily just convert |
created by @dimus at https://gitlab.com/gogna/gnparser/-/issues/47 reopened |
created by @dimus at https://gitlab.com/gogna/gnparser/-/issues/48 I decided not to go with I guess one thing we can do is to keep forma as |
created by @gdower at https://gitlab.com/gogna/gnparser/-/issues/49 @dimus, instead of standardizing forma to an fm. abbreviation, Yuri suggests that gnparser should disambiguate the rank to forma, because the fm. abbreviation is seldom used and may not be recognized. Paddy suggests using form, which might be a reasonable compromise. |
created by @dimus at https://gitlab.com/gogna/gnparser/-/issues/57
Sometimes it is impossible to say just by looking at a name-string, if
f.
in it belongs to an author asfilius
(son of) or it belongs to the following epithet and designates its rank asforma
:We decided that we create less damage, if we associate
f.
with author as filius, than potentially creating a wrong rank for the infraspecific epithet. However we do not explicitly say that there is an ambiguous situation. We need to create a new level 2 warning "Ambiguous f. (forma or filius)" for such occasions.The text was updated successfully, but these errors were encountered: