Multilingual typing: committed words are learned in the user history of the wrong language
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 62/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
调研方向
Start in DictionaryFacilitatorImpl, where addToUserHistory() reads currentlyPreferredDictionaryGroup before adjustConfidences() and then calls addWordToUserHistory with that group. Check unlearnFromUserHistory() as well, since it only touches the preferred group's history. Done when a German word typed after English words is stored in the de_DE history, and unlearnFromUserHistory() clears the word from every group that holds it. The reporter's groupForLearning idea is a starting point to verify, not a finished patch.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
With multilingual typing, DictionaryFacilitatorImpl.addToUserHistory() always adds the word to the user history of currentlyPreferredDictionaryGroup. It even reads that group before adjustConfidences() runs for the word:
val preferredGroup = currentlyPreferredDictionaryGroup // read here
...
adjustConfidences(suggestion, wasAutoCapitalized) // confidence changes afterwards
...
// add to history for preferred dictionary group, to avoid mixing languages in history
addWordToUserHistory(preferredGroup, ngramContextForCurrentWord, currentWord, ...)
So after a few English words, a German word, typed or picked from the suggestions, goes into the English user history. There:
- the English main dictionary doesn't know it (
mainFreq = -1), so it is stored as an invalid word and needs several uses before it's suggested; - it is scored with the English locale weight;
- the bigram (previous word → German word) is stored in the English history too.
This is the opposite of what the comment intends ("to avoid mixing languages in history"). It also means that correcting a wrongly swiped word (e.g. German "hier" that came out as English "hitter") barely helps next time.
unlearnFromUserHistory() has the same issue: it only removes the word from the preferred group's history.
Log from our build (German main, English (US) secondary, with a temporary debug line in addToUserHistory). After "the weather is good and I think that", the user types "hier":
learn 'that' -> en_US, preferred en_US, confidences [de_DE=0, en_US=8]
learn 'hier' -> de_DE, preferred en_US, confidences [de_DE=1, en_US=2]
With the current LeanType code, "hier" goes to en_US, because that group is preferred. With our fix it goes to de_DE.
Fix that works for us
Pick the history by the word's language: the preferred group if the word belongs to it (or to no language), otherwise the group whose main/apps/personal dictionary contains it:
private fun groupForLearning(word: String): DictionaryGroup {
val preferred = currentlyPreferredDictionaryGroup
if (dictionaryGroups.size == 1) return preferred
fun belongsTo(group: DictionaryGroup) = isValidWord(word, DICTIONARY_TYPES_EXCLUDING_HISTORY, group)
|| isValidWord(word.lowercase(group.locale), DICTIONARY_TYPES_EXCLUDING_HISTORY, group)
if (belongsTo(preferred)) return preferred
return dictionaryGroups.filter { it !== preferred && belongsTo(it) }.maxByOrNull { it.confidence } ?: preferred
}
Use it in addToUserHistory() (per word, after adjustConfidences()), and let unlearnFromUserHistory() remove the word from the history of all groups. I can send a PR once we've tested it a bit longer.
To Reproduce
- Languages & Layouts → German → Multilingual typing → add English (US). Main dictionaries for both, personalized suggestions on.
- Type a few English words, then a German word that is not English (e.g. "hier").
- The word is added to the English user history (visible with a debug log, or via the dictionary dump in the debug settings).
Expected behavior
Words are learned in the user history of their own language.
App version & Flavor
Found in GlassType, my fork, now based on LeanType 4.3.1 (0e673e1). The code is unchanged in current main.
Device Info
- Model: Samsung Galaxy Z Fold 3 (SM-F926B)
- OS version: Android 15
- 主要语言
- Kotlin
- 星标
- 1k
- 派生
- 59
- 平均合并
- 14 小时 9 分钟
- 30 天内合并 PR
- 56
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
LeanBitLab/LeanType 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
LeanBitLab/LeanType#760 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 62/100
LeanBitLab/LeanType#762 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 70/100
LeanBitLab/LeanType#761 ·
维护者通常 1 天内回复
-
Native crash (SIGSEGV in getSuggestionsNative) when typing with a multilingual secondary language未关闭
难度 4/5 3-5 天 新手友好度 25/100
LeanBitLab/LeanType#759 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 30/100
LeanBitLab/LeanType#757 · 4 条评论 ·
维护者通常 1 天内回复
查看 LeanBitLab/LeanType 的全部 Issue
相似的 Issue
-
bug ready-for-agent
难度 2/5 1-3 小时 新手友好度 82/100
neutraltone/settee#132 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
Kotlin/kotlinx.serialization#3311 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
partiql/partiql-lang-kotlin#1987 ·
维护者通常 3 天内回复
-
Issue: Bug
难度 2/5 1-3 小时 新手友好度 62/100
OpenAPITools/openapi-generator#25524 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
ActivityWatch/aw-android#383 · 1 条评论 ·
维护者通常 2 天内回复