as {{<span class="searchmatch">ja</span>-taru}}. --Lo Ximiendo (talk) 01:55, 23 September 2014 (UTC) It's been talked about before, and the responses I've read suggest that the <span class="searchmatch">JA</span> editors...
it's apparently on other parts of speech too? It occurs with both <span class="searchmatch">ja</span>-pos and <span class="searchmatch">ja</span>-<span class="searchmatch">adj</span> on kana-only na inflections, so this issue seems to span multiple...
templates and couldn't figure out what the problem was: the problem is that the <span class="searchmatch">ja</span>-<span class="searchmatch">adj</span> templates don't select the right categories. When you use the decl fields...
Done —Suzukaze-c◇◇ 09:24, 31 January 2020 (UTC) @Suzukaze-c: looks good! {{<span class="searchmatch">ja</span>-<span class="searchmatch">adj</span>-infl}} still suffers from this issue though. Hope that template will be...
question. For the latter, there should be a way to manipulate {{<span class="searchmatch">ja</span>-verb}} and {{<span class="searchmatch">ja</span>-<span class="searchmatch">adj</span>}} to allow an entry to have both modern and classical inflections...
====Conjugation==== <!-- verbs --> {{ko-conj/verb}} <!-- adjectives --> {{ko-conj/<span class="searchmatch">adj</span>}} Also, if it's OK, "alt=" for alternative forms, I often have to add the...
at 하다 (hada) before I removed them. They seem to have come directly from {{<span class="searchmatch">ja</span>-verbconj}} so they probably apply more to Japanese grammar than to Korean...