JMdict root object

Important concepts:

  • "Kanji" and "kana" versions of words are not always equivalent to "spellings" and "readings" correspondingly. Some words are kana-only. You should treat "kanji" and "kana" as different ways of spelling, although when kanji versions are present, kana versions are indeed "readings" for those
  • Some kana versions only apply to particular kanji versions, i.e. different spellings of the same word can be read in different ways. You'll see the appliesToKanji field being filled with a particular version in such cases
  • "Sense" in JMdict refers to translations along with some other information. Sometimes, some "senses" only apply to some particular kanji/kana versions of a word, that's why you'll see fields appliesToKanji and appliesToKana. In JMnedict, translations are simply called "translations," there are no "senses"

Hierarchy

Properties

commonOnly: boolean

true if this file contains only common kana/kanji versions

dictDate: string

Creation date of JMdict file, as it appears in a comment with format "JMdict created: YYYY-MM-DD" in the original XML file header

dictRevisions: string[]

Revisions of JMdict file, as they appear in comments in the original XML file header. These only contain actual version (e.g., "1.08"), not a full comment. Original comments also mention changes made, but this is omitted in the resulting JSON files

languages: string[]

List of languages in this files

tags: {
    [tag: Tag]: string;
}

Tags: parts of speech, names of dialects, fields of application, etc. All those things are expressed as XML entities in the original file. Keys of this object are tags per se, and values are descriptions, slightly modified from the original file

Type declaration

  • [tag: Tag]: string
version: string

Semantic version of this project (not the dictionary itself). For the dictionary revisions, see dictRevisions field below

See

https://semver.org/

words: JMdictWord[]

List of dictionary entries/words

Generated using TypeDoc