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

Problems with Latin supines #22

Open
lucascdz opened this issue May 24, 2021 · 1 comment
Open

Problems with Latin supines #22

lucascdz opened this issue May 24, 2021 · 1 comment

Comments

@lucascdz
Copy link

lucascdz commented May 24, 2021

Hi everybody,

I think I found a problem on Morpheus interpretation of Latin supines.

The list of probable morphosyntactic properties we get when we ask for information about e.g. "pastum" (from "Phaedrus' Aesopiae 2.4.14) includes a 'noun sg supine neut nom' (encoded n-s-u-nn-) option, while "pastu" is analysed as 'noun sg supine neut dat' (encoded n-s-u-nd-).

However, despite some historical issues, supines are usually classified as "non-finite verbal forms" in most of latin grammars (including Pinkster 2015: 64), being the so-called first supine (-um) an accusative case, the second (-u) an ablative case.

So I'm wondering if it would be better to change both analysis: the first one to "verb supine accusative" (v---u--a-) and the second to "verb supine ablative" (v---u--b-).

Since the same result is observed when using the Latin Word Study Tool (Perseus Hopper) as well as Arethusa tool (Perseids platform), it seems to be systemic.

Thank you for your time and apologies for my intermediate english skills.

Best regards,
Lucas

@lucascdz lucascdz changed the title Incorrect interpretation of Latin supines Problems with Latin supines May 25, 2021
@lcerrato
Copy link
Contributor

@lucascdz
Thank you for opening this issue.
There is currently no editor working on the morphological tools. We know there are improvements needed to the Latin tool and this issue will remain open as we move forward with the next phase of Perseus.

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