Take the 2-minute tour ×
Japanese Language Stack Exchange is a question and answer site for students, teachers, and linguists wanting to discuss the finer points of the Japanese language. It's 100% free, no registration required.

why is it that some 形容動詞 accepts の after it while some only accepts な after it?


の only: 普通、大勢

な or の: 初心、特別、特殊

Is there a way for us to tell if a 形容動詞 needs a の or な particle after it.. or is it just by brute force memory?

Btw my second question is that if a 形容動詞 accepts both の and な after it, is it true that usually we will use the な, even though の is grammatically correct too?

share|improve this question
which 形容動詞 accepts の after it? –  Lukman Jun 10 '11 at 3:46
see my edited question and tsuyoshi's comment on the answer at japanese.stackexchange.com/questions/892/… –  Pacerier Jun 10 '11 at 6:38
Just in case, I said 特別の can be used, but I did not say anything about 特殊の. Off the top of my head, 特殊の sounds strange to me, but I will not rule out the possibility that it is used in some contexts. –  Tsuyoshi Ito Jun 10 '11 at 15:06
add comment

2 Answers

up vote 9 down vote accepted

I'm not sure if there's a real answer to that. At least not something that will help you learn which is which. Some 形容動詞 take な, some take の, and some take both. How did that happen? That's quite simple.

All 形容動詞 are in fact a special class of nouns. In academic English material, they are often called "adjectival nouns" or even "descriptive nouns", to emphasize the fact that they're nouns. So how do you use a noun to describe another noun? Since Classical Japanese we had two main methods of doing that:

  1. Using the the copula (ADJであるNOUN)
  2. Using the genitive relation particle (ADJのNOUN)

In Classical Japanese, the copula was なり, and for genitive relation we also had が besides の, but it probably worked more or less the same. In the modern language, the copula なり went out of use and was replaced by だ in all forms except for the positive present form, where な (which comes from なり) remains in use.

The inconsistency is mainly there, in the positive present form, since in other forms (past or negative), the copula is used always. That's because you just cannot use の in other forms, since it's not copula and therefore does not conjugate, so you have to replace it with forms of the modern copula だ. な, on the other hand, can be said to be a copula, but it conjugates like だ in all other forms, so in these forms all adjectival nouns behave the same.

But still, why do is the choice of の, な or both in the present-positive form is so inconsistent? That's just how languages tend to work, chaotically. When you have two possible ways of forming an adjective (with a copula and with a genitive particle), people use both, and both forms come into what linguists call 'a competition'. There are several possible resolutions to a competition, such as one of the forms dying in favor of the other, or each form grabbing a different meaning. In this case, we have a complementary distribution, where some adjectival nouns settled take な, some settled for の, and for a good measure of irregularity some settled for both.

share|improve this answer
So な comes from an obsolete copula? Fascinating! –  Amanda S Jun 10 '11 at 7:24
wow! who put this answer onto wikipedia? : en.wikipedia.org/wiki/… –  Pacerier Aug 29 '11 at 14:20
add comment

I think you might be referring to the の found after an na-adjective word when it is used the predicate of a clause.

3.このクラブはきれいの花クラブと言います。(This club is called "The Pretty Flowers Club")

1 and 2 are the basic sentence patterns. Does the sentence in question look like the 3rd example?

If the question is clarified, then this answer might not answer the intended question.

share|improve this answer
nop i'm not talking about these cases.. btw きれい is a な only 形容動詞 –  Pacerier Jun 10 '11 at 6:41
see my edited question.. –  Pacerier Jun 10 '11 at 6:41
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.