sci.lang.japan FAQ / 1. Writing / 1.1. and

1.1.1. How did and originate?

毛/无
州 ?
Table 1: The parent of the characters

The earliest written form of Japanese was phonetic, but based on used for their pronunciation rather than meaning. This system is known as man'yougana (万葉仮名) (see 1.3.10. What is ). The two kana alphabets, katakana (片仮名) and hiragana (平仮名), began as simplifications of this complicated system.

Each and character is a simplification of one of the .The are based on a stylized form of the character using or cursive calligraphy. See 1.3.9.3. Handwritten styles. , fragment or partial , are based on parts of the , often written in the cursive style.

In the past, took more than one form for each "sound". Since 1900, they have been standardized to unique forms, and the variant forms only live on as hentaigana (変体仮名).

On the right are two tables of the parent of each kana. Some sources differ somewhat from this. These tables are in the order (see 1.1.5. What is the origin of the kana ordering?), using the (see 1.3.8. Can Japanese be written right to left?) writing style.

There is some controversy about some of the characters' origins, resulting in discrepancies between sources.

? May be from 尓/爾 万/末
州 ?
慧/恵流/礼
Table 2: The parent of each character.

The katakana themselves predate the existence of the syllabic nasal sound which is now represented by ん. This sound came into being around the year 1,000 A.D., after the katakana had already been created, and so originally there was no equivalent katakana. According to Seeley's book on the Japanese writing system, (ン) did not originate from any particular kanji. However, other sources state that it originates from the 尓/爾 (these are both forms of the same .) The origin of the katakana character for is also unknown, since it appears fully formed in the earliest documents available.

Acknowledgements

Thanks to Jim Breen and Kouji Ueshiba for more information.


sci.lang.japan FAQ / 1. Writing / 1.1. and

Copyright © 1994-2010 Ben Bullock

If you have questions, corrections, or comments, please contact Ben Bullock or use the discussion forum / Privacy

This site powered by: NearlyFreeSpeech.NET