Skip to content

SaveliiLukash/kanji-frequency

 
 

Repository files navigation

Kanji frequency

Statistical data of kanji usage frequencies was collected by processing textual data from various sources. You can find these files in the data directory:

File Total # of kanji Description Date
aozora.json ~51.5M Fiction and non-fiction books from Aozora Bunko May 2015
news.json ~10.3M Online news articles from various sources June 2015
twitter.json ~10.0M Twitter messages collected by a bot June 2015
wikipedia.json ~784.6M Japanese Wikipedia dump May 2015

See detailed descriptions below.

Format

Each file contain an array of arrays (rows). Each row contains three fields:

  1. (string) Kanji itself. "all" is a special case in the first row.
  2. (integer) How many times it was found in the analyzed data set. For "all" it is a total number of kanji, including repetitions.
  3. (float) Fraction of total amount of data this character represents. For "all" it is 1 (i.e. 100%).

Aozora

  • Sources: Aozora Bunko
  • Result: aozora.json
  • Total # of scanned texts: 12905
  • Total # of kanji collected: ~51.5M
  • Date collected: May 2015
  • Processing method: Pages were scanned as plain text, ignoring HTML structure, since they contain very little extra content.

Known issues

http://vtrm.net/japanese/kanji-frequency/en points out:

Some kanji radicals or elements which are usually not used on their own gathered relatively high rankings. One would expect such elements not to occur at all, or nearly so. For example, in Shpika’s list, 廴, a radical not used on its own, is stated to occur 1595 times and is ranked 2294th most common kanji. The explanation is simple: when a kanji outside the JIS X 0208 set appears in a text, the Aozora Bunko policy is to break it out into simpler parts. By instance, 𢌞 (it may not be displayed correctly if you don’t have a suitable font installed) is written ※[#「廴+囘」、第4水準2-12-11], where 廴+囘 is the kanji decomposition and 第4水準2-12-11 is the JIS X 0213 code point.

News

  • Sources:
  • Result: news.json
  • Total # of kanji collected: ~10.3M
  • Total # of scanned texts:
    • asahi - 19392
    • mainichi - 6449
    • saga-s - 61671
    • yomiuri - 1978
  • Date collected: June 2015
  • Processing method: Samples include articles published between June 2014 and June 2015, more samples from 2015. Only article titles, subtitles, main text body and image captions were scanned. Everything else was ignored: menus, publication dates, comments, ads, links to related articles, etc. Weather forecasts and area-specific news were not included.

Twitter

  • Sources: Twitter via Streaming API
  • Result: twitter.json
  • Total # of scanned texts: unknown
  • Total # of kanji collected: ~10.0M
  • Date collected: June 2015
  • Processing method: Messages were collected within about 1 week from Twitter's Streaming API v1 using a bot. Only message text bodies were scanned, authors' names and other data ignored. You can find specific details in the bot's source code, at commit e82cf7c (the exact version used to collect the data).

Known issues

Twitter dataset contains a lot of kanji used primarily in emoji:

  • ( ^ω^)个 (umbrella/flower?)
  • U^皿^U (grin/teeth, mustache?)
  • ( ’ω’)旦~~ (cup)
  • (╯°益°)╯ (rage face)
  • (oT-T)尸 (flag)
  • and probably many more

Also, the "笑" character is #1 simply bause it is used as a generic "smiley face". Yet technically, it's not an emoji because it's used for its meaning, as opposed to the examples above that are used only for their shapes.

Wikipedia

  • Sources: Japanese Wikipedia via Wikipedia dump (see jawiki bot)
  • Result: wikipedia.json
  • Total # of scanned texts: unknown
  • Total # of kanji collected: ~784.6M
  • Date collected: May 2015 (dump date is 2015-05-12)
  • Processing method: Dump included only current versions of pages and articles, without previous revisions or any other history of editing. Dump was scanned as plain text, ignoring XML and wiki markup structure.

Known issues

Since XML structure and wiki markup was ignored, thus this dataset is potentially noisy. This needs further investigation. Proper parsing was not implemented simply because it is too difficult (need to parse both XML and wiki markup).

Alternative datasets

License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

About

Kanji usage frequency data collected from various sources

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 45.5%
  • HTML 37.0%
  • Less 12.8%
  • CoffeeScript 4.2%
  • Shell 0.5%