-
Notifications
You must be signed in to change notification settings - Fork 667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dict]对话串中多处英文权重过高 #524
Comments
rime_ice.schema.yaml
在这里加 单词,就会去第二个候选 |
而且要改的不止这一个,实际上是所有的方案里对应的这个都要改,但是包装成custom又会覆盖用户为了保证更新没有冲突自己加的custom,情况就是这么蛋疼 |
去掉英文输入吧😂 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
不写死在 Lua 里是方便打补丁,补丁里你可以自定义或继承追加: patch:
# 自定义:
reduce_english_filter/words: [my, words]
# 追加:
reduce_english_filter/words/+: [my, words]
# 清零:
reduce_english_filter/words: [] |
我发问题出来更多是希望所有之后使用这个方案的人都不再遇到同样的问题,我自己倒是能理解这些配置,感谢回复 |
我支持原方案的设计,不用做修改。 |
改词库这个我还在犹豫,我可能确实更适合你说的这种方案 |
英文词典的权重感觉确实有问题,开启的话,打到某些词的时候会有点不顺,但完全停用的话也是不怎么方便 有些词的权重让人捉摸不透。比如输入'nas’('那是')会蹦出[Network Attached Storage](自定义词组里没有这个词)。 |
这是个脚本 bug。那个 lua 只降低了完全匹配候选的排行,没有考虑到这种情境。可以新开个 issue |
少了个空格判断。 |
不用谢,禁了吧,再见。 |
我认为是你其他词库的权重写得过高,我使用原版配置输入Mac 的时候,首选项就是Mac |
双拼开启简拼 |
* github/main: (24 commits) dict: 完成同义多音字注音 close iDvel#353 dict: 添加 "明不明显" (iDvel#529) feat: reduce_english_filter.lua 增加一键全降低 fix: 完善所有双拼 i?ong 键位的正则 dict: 日常更新 fix: reduce_english_filter.lua 处理有空格的单词 iDvel#524 conf: 双拼默认不启用简拼 iDvel#508 dict: 日常更新 close iDvel#522 feat: 英文方案增加 `#` jing 和 `+` jia 的派生 dict: 日常更新 close iDvel#520 fix: reduce_english_filter.lua 可识别含单引号的单词 close iDvel#519 dict: 「皮妙」→「皮秒」 close iDvel#517 dict: 日常更新 iDvel#457 close iDvel#516 添加一些英文缩写 close iDvel#512 fix: en_spacer.lua 处理含单引号的单词 close iDvel#513 conf: 双拼默认不启用简拼 iDvel#508 fix: reduce_english_filter.lua 不处理非英文单词 fix iDvel#505 dict: 日常更新; close iDvel#502 feat: 完善九宫格 dict: 日常更新; close iDvel#493 feat: en_spacer.lua 英文词条上屏自动添加空格 (iDvel#496) ...
如图
The text was updated successfully, but these errors were encountered: