2026-04-28 - 2026-07-28
Overview
5 Issues closed from 1 user
Closed
#87 Add kanjivg data to sqlite db
Closed
#23 word search: fuzzy kana search
Closed
#109 Give higher score if kana matches search term
Closed
#93 Vendor custom SQLite build with tamerye enabled
Closed
#108 All constant radicals should exist in the database
9 Issues created by 1 user
Opened
#106 Switch to the XML-NG version of JMDict (once it releases)
Opened
#107 Create mini versions of the database to be used for testing
Opened
#108 All constant radicals should exist in the database
Opened
#109 Give higher score if kana matches search term
Opened
#110 Move kanjivg to datasources repo
Opened
#111 word search: transliterate romaji search terms
Opened
#112 Store KanjiVG_PathGroup fields original, position, radical, part in separate tables
Opened
#113 Merge KanjiVG_StrokeNumber into KanjiVG_Path in database
Opened
#114 word search: trim number prefixes off counters
16 Unresolved Conversations
Open
#90
Support wildcards in word search
Open
#54
Split out Kanji/Reading element's readingDoesNotMatchKanji/news/ichi/spec/gai/nf into separate tables
Open
#88
Add 漢検 level ratings to kanji
Open
#56
Validate input before using it in FTS5 queries
Open
#37
Word search: support mixed input (kanji, kana, romaji)
Open
#104
Add 放送禁止用語 tags
Open
#58
Add an option to only ingest a subset of data for development speed
Open
#83
Cache lemmatization results
Open
#51
Measure time taken during substeps of data ingestion
Open
#40
Word search: optimize word regrouping
Open
#9
Add progress bars while creating the database
Open
#66
Use INTEGER for JMdict_JLPTTag.jlptLevel
Open
#68
Use integer enum for KANJIDIC_Codepoint.type
Open
#99
Disable constraints causing sqlite autoindex creation when compiling for production usage
Open
#103
Get rid of JMdict_SenseGlossary_byPhrase index for production use
Open
#105
Register commit hash for 'datasources' repo