くるな is a derivation. な is attaching to the verb くる. There are
derivations beyond just inflection. A "no inflection" tag doesn't say
much about exactly what kinds of derivation are forbidden, let alone
what kinds of inflection, for more r asons than just the fact that the
line between inflections and compounds is very fuzzy in Japanese.
What inflections are forbidden-in-practice is governed exactly by the
specific word that is being tagged. "No inflection" assumes that any
word that might get tagged with it, within a given part of speech, has
the same kinds of restrictions for what kinds of derivations are not
allowed.
Also, by far the most common form for かっこいい here is かっこよすぎる, the
form expected of it being an i-adjective. More common than かっこよさすぎる by
orders of magnitude. Even かっこいすぎる, which is almost certainly a
corruption, is more common than かっこよさすぎる. Compounds that end in word
X don't necessarily have the same distribution of derivations as word X
itself.
This is actually a very good example of why a "no inflection" tag
wouldn't be useful to tell very much about what kinds of restrictions
there are on the derivations the word can actually take in practice.
Exactly what it means for nontrivial derivations would always be
different from word to word.
On 2018/06/12 1:07, Marcus Richert superbrightfuture@*********
[edict-jmdict] wrote:
> A [noinfl]/[noconj] tag would not be applied to something like くるな,
which is only tagged as "expl" in the database, which isn't a PoS that
inflects/conjugates.
くるな is a derivation. な is attaching to the verb くる. There are
derivations beyond just inflection. A "no inflection" tag doesn't say
much about exactly what kinds of derivation are forbidden, let alone
what kinds of inflection, for more reasons than just the fact that the
line between inflections and compounds is very fuzzy in Japanese.
What inflections are forbidden-in-practice is governed exactly by the
specific word that is being tagged. "No inflection" assumes that any
word that might get tagged with it, within a given part of speech, has
the same kinds of restrictions for what kinds of derivations are not
allowed.
> かっこいいすぎる is not correct Japanese - it'd be "かっこよさすぎる", and
this is precisely the information we're trying to convey with noinfl,
that いい doesn't inflect - only よい does. (and the -さ- in the middle of
it is why we need a special PoS for よい and ない)
It might be proscribed (I don't know), but natives use it on purpose
without correcting themselves. If I deconjugate 食べすぎる then I'm
definitely going to want to deconjugate かっこいいすぎる as well. (This doesn't
mean that I'm displaying かっこいいすぎる as an example of how to conjugate
かっこいい to すぎる, my dictionary doesn't generate conjugations, it only
parses them.)
Also, by far the most common form for かっこいい here is かっこよすぎる, the
form expected of it being an i-adjective. More common than かっこよさすぎる by
orders of magnitude. Even かっこいすぎる, which is almost certainly a
corruption, is more common than かっこよさすぎる. Compounds that end in word
X don't necessarily have the same distribution of derivations as word X
itself.
This is actually a very good example of why a "no inflection" tag
wouldn't be useful to tell very much about what kinds of restrictions
there are on the derivations the word can actually take in practice.
Exactly what it means for nontrivial derivations would always be
different from word to word.
A good dictionary application would end up with special cases for
everything marked with "no inflection" if it wants its handling of
inflections to be robust.
You could use such a tag to prevent an application from generating a
conjugation table, but replacing a special word class with a normal one
and adding "no inflection" wouldn't really be appropriate for
applications that don't deal with conjugations that way. It doesn't tell
a deconjugator what it needs to know to handle the word in a robust manner.
- Follow-Ups:
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Marcus Richert <superbrightfuture@*********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: René Malenfant <rene_malenfant@***********>
- References:
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: s mcgraw <smcg6347@***********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: René Malenfant <rene_malenfant@***********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: s mcgraw <smcg6347@***********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Marcus Richert <superbrightfuture@*********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: s mcgraw <smcg6347@***********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Marcus Richert <superbrightfuture@*********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: s mcgraw <smcg6347@***********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Jim Breen <jimbreen@*********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Jim Breen <jimbreen@*********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Jim Breen <jimbreen@*********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: s mcgraw <smcg6347@***********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Marcus Richert <superbrightfuture@*********>
- Re: [edict-jmdict] adj-i/adj-ix issues
- From: Alexander Nadeau <wareya@*********>
- Prev by Date: Re: [edict-jmdict] adj-i/adj-ix issues
- Next by Date: Re: [edict-jmdict] adj-i/adj-ix issues
- Previous by thread: Re: [edict-jmdict] adj-i/adj-ix issues
- Next by thread: Re: [edict-jmdict] adj-i/adj-ix issues
- Index(es):