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

Morpheus parsing llt-tokenized texts #7

Open
LFDM opened this issue Feb 11, 2014 · 1 comment
Open

Morpheus parsing llt-tokenized texts #7

LFDM opened this issue Feb 11, 2014 · 1 comment

Comments

@LFDM
Copy link

LFDM commented Feb 11, 2014

People can request to markup enclicits (the Pisa guys who'd like to annotate some Seneca already did), in most cases this comes down to a hyphen, e.g. arma virumque becomes arma virum -que. I think this makes a lot of sense, especially with other cases, such as an enclitic ne, because without marking them as split up, there would be no chance to disambiguate an enclitic -ne from the 'real' ne (used for negations etc.)

However, Morpheus doesn't really know what to do with the hyphen - -c and -que remain unidentified entirely, -ne is said to be a form of neo1 etc.

@gregorycrane
Copy link

Morpheus needs to be fed individual tokens, so you need to pre-process
things and feed it only "virum". It won't recognize the enclitics, so
handle them as exceptions.

On 2/11/14, 9:11 AM, Gernot Höflechner wrote:

People can request to markup enclicits (the Pisa guys who'd like to
annotate some Seneca already did), in most cases this comes down to a
hyphen, e.g. |arma virumque| becomes |arma virum -que|. I think this
makes a lot of sense, especially with other cases, such as an enclitic
|ne|, because without marking them as split up, there would be no
chance to disambiguate an enclitic |-ne| from the 'real' |ne| (used
for negations etc.)

However, Morpheus doesn't really know what to do with the hyphen -
|-c| and |-que| remain unidentified entirely, |-ne| is said to be a
form of |neo1| etc.


Reply to this email directly or view it on GitHub
#7.

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