-
Notifications
You must be signed in to change notification settings - Fork 632
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
常见问题 #133
Comments
补充一个FAQ: |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Closed
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This was referenced May 5, 2023
Closed
Closed
Closed
This comment was marked as duplicate.
This comment was marked as duplicate.
Closed
This comment was marked as resolved.
This comment was marked as resolved.
Closed
Closed
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
Repository owner
locked and limited conversation to collaborators
Sep 26, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
⚙️修改配置
直接修改
直接在文件上修改,这样修改也简单,适合初次尝试。
补丁
以打补丁的方式来覆盖原配置的选项,不修改仓库中已有的文件,这样可放心全量拉取更新,通过 plum 或 git pull 时不用担心由于更新文件导致自定义的配置被覆盖。
❓常见问题
xx 字打不出来 / xx 读音没有
可能为生僻字,请尝试开启大字表。若确实为常用字(如常见于人名、物品名、术语),请 PR 或在 #666 补充。
部分候选项变成豆腐块、方块、问号
系统缺少相关字体导致。请尝试下载或更换显示字体。
关于部分生僻字,参考 #841 的推荐。
Windows 10 平台部分 Emoji 用系统默认字体无法显示,请尝试下载 Noto Color Emoji 或用 Windows 11 Emoji 字体替换。
配置出错
如果缩进错误,或用了 Tab,可能部署时并不会报错,而是自动加载默认配置。
如果发现方案选单里是朙月拼音,打的是繁体,那可能是配置有问题,Rime 自动加载了默认配置,检查一下修改过的地方。
配置错误也可能导致
default.yaml
文件被移入trash/
目录,你需要移动回来,改好后重新部署,然后可以直接删除trash/
目录。中英文、大小写切换
Shift 是否切换中英,切换时的行为等等,参考
default.yaml
中ascii_composer
下的详细注释。修改标点符号映射
默认反引号没有改成间隔号,有需要可以输入「点」和「间隔号」。
标点符号相关配置在
default.yaml
中定义,再在多个方案中引用。皮肤横向竖向排列
皮肤配置不通用,要参考各前端自己的配置方式。
小狼毫由
style/horizontal
属性决定:鼠须管的
horizontal
属性已经弃用,在squirrel.yaml
皮肤的选项中使用以下两个属性:style
的高。鼠须管效果展示:
自定义短语
自定义短语用 Tab 分割词汇、编码、权重。
custom_phrase.txt
中是我自己的习惯,仅供参考,这个每个人的习惯都不一样,可以换成自己的。可以新建一个文件,并在方案的
custom_phrase/user_dict:
下指定使用哪个文件。台湾繁体
默认 OpenCC 的选项
traditionalize/opencc_config: s2t.json
是香港繁体。台湾繁体有以下两种方式供参考,先修改为
s2tw.json
:(因为不知道什么原因,
s2tw.json
选项并没有真正转换为台湾繁体,所以又补了一个t2tw.json
)(librime 1.10 已修复,新版本不再需要折腾了。)
颜文字
没有加入颜文字 #462,少数颜文字可以直接用 OpenCC 或自定义短语实现,常用的用户可以参考 #463。
Linux (iBus & Fcitx & Fcitx5)系统无候选 / Lua 无法引入 / 雾凇拼音候选后出现拼音注释等
输入
rq
(双拼是date
),如若没有出现当前日期,则表示 Lua 没有成功加载,您就可能遇到上述问题。请确保你已经正确安装了 librime 包,并以插件或其他形式安装了其依赖包 librime-lua(部分发行版——特别是红帽系——需要手动安装);如果仍存在问题,或者你无法判断是否达成此条件,请:
fcitx-rimeAppImage 和 Flatpak 可以确保没有依赖问题。
请参考: #840
添加或修改 Lua
做好自己的 Lua 放在
lua/
文件夹内,使用新版 librime-lua 引入模块的方式,不用修改rime.lua
:比如想将自己修改后的
new_date_translator.lua
替换掉date_translator
:日志中的常见 WARNING
WARNING 日志仅为警告,一般可以忽视。ERROR 文件若有日志,则需要留神。
这是因为 melt_eng 和 radical_pinyin 引用了自身的节点,RIME build 时认为这可能会导致引用了一个未编译完成的文件,因而抛出警告。无视即可。
因为某些词典有重复的条目,build 时 RIME 认为这可能会造成编码和权重的覆写,因而抛出警告,无视即可。
⌨️双拼
双拼的自定义短语文件默认为
custom_phrase_double.txt
,需要手动创建。英文方案
melt_eng.schema.yaml
中有一些不通用的派生规则,默认启用的是全拼的。部件拆字方案
radical_pinyin.schema.yaml
的反查和辅码,有一些不通用的派生规则,默认启用的是全拼的。双拼是显示全拼编码还是双拼编码?比如小鹤双拼输入
zz
时,是显示zz
还是zou
,默认是转换为全拼编码。translator
下的preedit_format
属性会影响输入框和 Shift+回车 时的显示,删除这部分就不转换。双拼的补丁示例
除直接修改外,也可以打补丁,可以直接用 plum 自动打补丁,也可以手写,下面以小鹤双拼方案
double_pinyin_flypy.schema.yaml
为例。melt_eng.custom.yaml
修改英文派生规则:radical_pinyin.custom.yaml
修改反查及辅码派生规则:double_pinyin_flypy.custom.yaml
:全拼双拼混输
参考:https://dvel.me/posts/rime-full-pinyin-double-pinyin-mixed-input/
The text was updated successfully, but these errors were encountered: