jmdict/jmdict.go

261 lines
11 KiB
Go
Raw Normal View History

2016-07-30 17:33:36 +00:00
package jmdict
2016-08-07 00:43:26 +00:00
import "io"
type Jmdict struct {
// Entries consist of kanji elements, reading elements,
// general information and sense elements. Each entry must have at
// least one reading element and one sense element. Others are optional.
Entries []JmdictEntry `xml:"entry"`
}
type JmdictEntry struct {
2016-07-31 00:30:45 +00:00
// A unique numeric sequence number for each entry
Sequence int `xml:"ent_seq"`
// The kanji element, or in its absence, the reading element, is
// the defining component of each entry.
// The overwhelming majority of entries will have a single kanji
// element associated with a word in Japanese. Where there are
// multiple kanji elements within an entry, they will be orthographical
// variants of the same word, either using variations in okurigana, or
// alternative and equivalent kanji. Common "mis-spellings" may be
// included, provided they are associated with appropriate information
// fields. Synonyms are not included; they may be indicated in the
// cross-reference field associated with the sense element.
2016-08-07 00:43:26 +00:00
Kanji []JmdictKanji `xml:"k_ele"`
2016-07-31 00:30:45 +00:00
// The reading element typically contains the valid readings
// of the word(s) in the kanji element using modern kanadzukai.
// Where there are multiple reading elements, they will typically be
// alternative readings of the kanji element. In the absence of a
// kanji element, i.e. in the case of a word or phrase written
// entirely in kana, these elements will define the entry.
2016-08-07 00:43:26 +00:00
Readings []JmdictReading `xml:"r_ele"`
2016-07-31 00:30:45 +00:00
// The sense element will record the translational equivalent
// of the Japanese word, plus other related information. Where there
// are several distinctly different meanings of the word, multiple
// sense elements will be employed.
2016-08-07 00:43:26 +00:00
Sense []JmdictSense `xml:"sense"`
2016-07-31 00:30:45 +00:00
}
2016-08-07 00:43:26 +00:00
type JmdictKanji struct {
2016-07-30 17:33:36 +00:00
// This element will contain a word or short phrase in Japanese
// which is written using at least one non-kana character (usually kanji,
// but can be other characters). The valid characters are
// kanji, kana, related characters such as chouon and kurikaeshi, and
// in exceptional cases, letters from other alphabets.
Expression string `xml:"keb"`
// This is a coded information field related specifically to the
// orthography of the keb, and will typically indicate some unusual
// aspect, such as okurigana irregularity.
Information []string `xml:"ke_inf"`
// This and the equivalent re_pri field are provided to record
// information about the relative priority of the entry, and consist
// of codes indicating the word appears in various references which
// can be taken as an indication of the frequency with which the word
// is used. This field is intended for use either by applications which
// want to concentrate on entries of a particular priority, or to
// generate subset files.
// The current values in this field are:
// - news1/2: appears in the "wordfreq" file compiled by Alexandre Girardi
// from the Mainichi Shimbun. (See the Monash ftp archive for a copy.)
// Words in the first 12,000 in that file are marked "news1" and words
// in the second 12,000 are marked "news2".
// - ichi1/2: appears in the "Ichimango goi bunruishuu", Senmon Kyouiku
// Publishing, Tokyo, 1998. (The entries marked "ichi2" were
// demoted from ichi1 because they were observed to have low
// frequencies in the WWW and newspapers.)
// - spec1 and spec2: a small number of words use this marker when they
// are detected as being common, but are not included in other lists.
// - gai1/2: common loanwords, based on the wordfreq file.
// - nfxx: this is an indicator of frequency-of-use ranking in the
// wordfreq file. "xx" is the number of the set of 500 words in which
// the entry can be found, with "01" assigned to the first 500, "02"
// to the second, and so on. (The entries with news1, ichi1, spec1 and
// gai1 values are marked with a "(P)" in the EDICT and EDICT2
// files.)
// The reason both the kanji and reading elements are tagged is because
// on occasions a priority is only associated with a particular
// kanji/reading pair.
2016-08-02 03:24:50 +00:00
Priorities []string `xml:"ke_pri"`
2016-07-30 17:33:36 +00:00
}
2016-08-07 00:43:26 +00:00
type JmdictReading struct {
2016-07-30 17:33:36 +00:00
// This element content is restricted to kana and related
// characters such as chouon and kurikaeshi. Kana usage will be
// consistent between the keb and reb elements; e.g. if the keb
// contains katakana, so too will the reb.
Reading string `xml:"reb"`
// This element, which will usually have a null value, indicates
// that the reb, while associated with the keb, cannot be regarded
// as a true reading of the kanji. It is typically used for words
// such as foreign place names, gairaigo which can be in kanji or
// katakana, etc.
NoKanji *string `xml:"re_nokanji"`
// This element is used to indicate when the reading only applies
// to a subset of the keb elements in the entry. In its absence, all
// readings apply to all kanji elements. The contents of this element
// must exactly match those of one of the keb elements.
Restrictions []string `xml:"re_restr"`
// General coded information pertaining to the specific reading.
// Typically it will be used to indicate some unusual aspect of
// the reading.
Information []string `xml:"re_inf"`
// See the comment on ke_pri above.
2016-08-02 03:24:50 +00:00
Priorities []string `xml:"re_pri"`
2016-07-30 17:33:36 +00:00
}
2016-08-07 00:43:26 +00:00
type JmdictSource struct {
2016-07-30 17:33:36 +00:00
Content string `xml:",chardata"`
// The xml:lang attribute defines the language(s) from which
// a loanword is drawn. It will be coded using the three-letter language
// code from the ISO 639-2 standard. When absent, the value "eng" (i.e.
// English) is the default value. The bibliographic (B) codes are used.
2016-08-07 01:13:19 +00:00
Language *string `xml:"lang,attr"`
2016-07-30 17:33:36 +00:00
// The ls_type attribute indicates whether the lsource element
// fully or partially describes the source word or phrase of the
// loanword. If absent, it will have the implied value of "full".
// Otherwise it will contain "part".
2016-08-07 01:13:19 +00:00
Type *string `xml:"ls_type,attr"`
2016-07-30 17:33:36 +00:00
// The ls_wasei attribute indicates that the Japanese word
// has been constructed from words in the source language, and
// not from an actual phrase in that language. Most commonly used to
// indicate "waseieigo".
Wasei string `xml:"ls_wasei,attr"`
}
2016-08-07 00:43:26 +00:00
type JmdictGlossary struct {
2016-07-30 17:33:36 +00:00
Content string `xml:",chardata"`
// The xml:lang attribute defines the target language of the
// gloss. It will be coded using the three-letter language code from
// the ISO 639 standard. When absent, the value "eng" (i.e. English)
// is the default value.
2016-08-07 01:13:19 +00:00
Language *string `xml:"lang,attr"`
2016-07-30 17:33:36 +00:00
// The g_gend attribute defines the gender of the gloss (typically
// a noun in the target language. When absent, the gender is either
// not relevant or has yet to be provided.
2016-08-07 01:13:19 +00:00
Gender *string `xml:"g_gend"`
// g_type attribute added in jmdict Rev 1.09
// At present the values used are "lit", "fig", "expl" and "tm". It is
// proposed to add a "descr" value to indicate a gloss which is a
// description of the Japanese term rather than a translation or an
2022-07-04 03:41:16 +00:00
// explanation of the meaning.
Type *string `xml:"g_type,attr"`
2016-07-30 17:33:36 +00:00
}
2016-08-07 00:43:26 +00:00
type JmdictSense struct {
2016-07-30 17:33:36 +00:00
// These elements, if present, indicate that the sense is restricted
// to the lexeme represented by the keb and/or reb.
2016-08-01 03:36:45 +00:00
RestrictedKanji []string `xml:"stagk"`
RestrictedReadings []string `xml:"stagr"`
2016-07-30 17:33:36 +00:00
// This element is used to indicate a cross-reference to another
// entry with a similar or related meaning or sense. The content of
// this element is typically a keb or reb element in another entry. In some
// cases a keb will be followed by a reb and/or a sense number to provide
// a precise target for the cross-reference. Where this happens, a JIS
// "centre-dot" (0x2126) is placed between the components of the
// cross-reference.
References []string `xml:"xref"`
// This element is used to indicate another entry which is an
// antonym of the current entry/sense. The content of this element
// must exactly match that of a keb or reb element in another entry.
Antonyms []string `xml:"ant"`
// Part-of-speech information about the entry/sense. Should use
// appropriate entity codes. In general where there are multiple senses
// in an entry, the part-of-speech of an earlier sense will apply to
// later senses unless there is a new part-of-speech indicated.
2016-08-02 03:24:50 +00:00
PartsOfSpeech []string `xml:"pos"`
2016-07-30 17:33:36 +00:00
// Information about the field of application of the entry/sense.
// When absent, general application is implied. Entity coding for
// specific fields of application.
2016-07-31 23:10:17 +00:00
Fields []string `xml:"field"`
2016-07-30 17:33:36 +00:00
// This element is used for other relevant information about
// the entry/sense. As with part-of-speech, information will usually
// apply to several senses.
Misc []string `xml:"misc"`
// This element records the information about the source
// language(s) of a loan-word/gairaigo. If the source language is other
// than English, the language is indicated by the xml:lang attribute.
// The element value (if any) is the source word or phrase.
2016-08-07 00:43:26 +00:00
SourceLanguages []JmdictSource `xml:"lsource"`
2016-07-30 17:33:36 +00:00
// For words specifically associated with regional dialects in
// Japanese, the entity code for that dialect, e.g. ksb for Kansaiben.
2016-08-02 03:24:50 +00:00
Dialects []string `xml:"dial"`
2016-07-30 17:33:36 +00:00
// The sense-information elements provided for additional
// information to be recorded about a sense. Typical usage would
// be to indicate such things as level of currency of a sense, the
// regional variations, etc.
Information []string `xml:"s_inf"`
// Within each sense will be one or more "glosses", i.e.
// target-language words or phrases which are equivalents to the
// Japanese word. This element would normally be present, however it
// may be omitted in entries which are purely for a cross-reference.
2016-08-07 00:43:26 +00:00
Glossary []JmdictGlossary `xml:"gloss"`
// Some JMdict entries can contain 0 or more examples
Examples []JmdictExample `xml:"example"`
}
type JmdictExample struct {
// Each example has a Srce element that indicates the source of the example
// the source is typically the Tatoeba Project
Srce JmdictExampleSource `xml:"ex_srce"`
// The term associated with this example
Text string `xml:"ex_text"`
// Contains the Example sentences
Sentences []JmdictExampleSentence `xml:"ex_sent"`
}
type JmdictExampleSource struct {
// The id of the example for the source
ID string `xml:",chardata"`
// The source type (i.e. 'tat' for tatoeba)
SrcType string `xml:"exsrc_type,attr"`
}
type JmdictExampleSentence struct {
// The language of the example sentence
Lang string `xml:"lang,attr"`
// The example sentence text
Text string `xml:",chardata"`
2016-07-30 17:33:36 +00:00
}
2016-08-07 00:43:26 +00:00
func LoadJmdict(reader io.Reader) (Jmdict, map[string]string, error) {
var dict Jmdict
entities, err := parseDict(reader, &dict, true)
return dict, entities, err
}
2016-07-31 01:04:49 +00:00
2016-08-07 00:43:26 +00:00
func LoadJmdictNoTransform(reader io.Reader) (Jmdict, map[string]string, error) {
var dict Jmdict
entities, err := parseDict(reader, &dict, false)
return dict, entities, err
2016-07-30 17:33:36 +00:00
}