{"query":"import rime dictionary","results":[{"title":"Chinese, Japanese & Korean","heading":"Dictionaries made for fcitx5, Rime or Sogou","section":"Languages","url":"https://wmkeyboard.pages.dev/languages/cjk/#dictionaries-made-for-fcitx5-rime-or-sogou","markdown":"https://wmkeyboard.pages.dev/languages/cjk.md","score":22.39,"text":"Most Chinese dictionary projects on GitHub are built for the desktop input methods, and many ship two files per release: a `.dict` for fcitx5 and a `.dict.yaml` for Rime. Take the `.dict.yaml`. It is the Rime format from the list above, so it imports as it is: pick **Chinese**, open **Custom dictionaries** and import the file.\n\nSogou's own `.scel` cell dictionaries import directly too, from Custom dictionaries or by opening the file with WM Keyboard; the import names them as a Chinese list.\n\nfcitx5's `.dict` is compiled, and the keyboard can't read it: it is libime's binary dictionary. Look for the Rime file or the `.scel` files in the same release, or convert the project's source text instead.\n\nEach file can be at most 32 MB. That rules out the whole-corpus builds, such as [fcitx5-pinyin-sougou-dict](https://github.com/blackteahamburger/fcitx5-pinyin-sougou-dict), whose `sougou.dict.yaml` is over 400 MB: the import refuses it, and splitting it wouldn't help, because the keyboard reads every list into memory when it builds the Chinese table. That project's release also carries `sougou_dict.tar.gz`, the raw Sogou cell dictionaries it was built from. Unpack it and import the `.scel` files for the topics you actually type, such as computing, place names or medicine. A few thematic lists of a few megabytes each give most of the benefit and load fast."},{"title":"Importing from other keyboards","heading":"Input methods: .cin, Rime and m17n","section":"Reference","url":"https://wmkeyboard.pages.dev/reference/importing-other-keyboards/#input-methods-cin-rime-and-m17n","markdown":"https://wmkeyboard.pages.dev/reference/importing-other-keyboards.md","score":22.12,"text":"- **A `.cin` table** is one file. Each code types the entries listed for it, and the suggestion strip offers them as you type, an exact code first and then the codes that start with what you typed. The keys show the caps the table names in `%keyname`, so a Cangjie table puts 日月金 on the keys and an Array table its 1- 2⇡ positions. Keys the table uses besides letters, such as Array's `, . / ;` or Boshiamy's `[ ] '`, get a key each.\n- **A Rime schema** needs the `.schema.yaml`, the `.dict.yaml` it names, every table that dictionary imports, any shared file its rules come from, such as `pinyin.yaml` or `zhuyin.yaml`, and the word list the dictionary ranks by: `essay.txt` from rime-essay, or the file its `vocabulary:` line names (`essay-cantonese.txt` for rime-cantonese). Without the word list the import still works, but most dictionaries state no counts of their own, so every character ranks the same, and a pinyin dictionary has few phrases: Rime builds them from that list, and so does this app. The confirm dialog names any of these files that were not picked. A schema that converts syllables (Rime's `script_translator`: pinyin, Jyutping, Wugniu, Zhuyin on terra_pinyin) converts whole phrases with the same decoder as the built-in Chinese layouts, prefix commit and learned picks included. A code schema (`table_translator`: Cangjie 5, Array 30, Wubi 86) works like a `.cin` table. The schema's spelling rules (`speller/algebra`) are applied when you import, so tone-free and abbreviated spellings and the schema's own keys for Zhuyin work as they do in Rime. A dictionary picked without a schema works too, with no spelling rules."},{"title":"Chinese, Japanese & Korean","heading":"The RIME engine","section":"Languages","url":"https://wmkeyboard.pages.dev/languages/cjk/#the-rime-engine","markdown":"https://wmkeyboard.pages.dev/languages/cjk.md","score":20.75,"text":"**Learning.** RIME learns into its own user dictionary when you pick a candidate, and it learns whole phrases: picking 你好 and then 世界 for `nihaoshijie` teaches it 你好世界. Like the rest of the keyboard's learning, it learns nothing in incognito or a password field. **Delete RIME data** removes the compiled schemas, your imported ones and everything RIME learned; the downloaded packs stay and compile again.\n\n**Before the first unlock.** RIME's schemas and its user dictionary sit in the app's credential-protected storage, with your other learned words, so on a phone that has restarted and not been unlocked yet, Chinese types on the built-in engine. RIME takes over again after you unlock."},{"title":"Key layouts","heading":"Managing your layouts","section":"Reference","url":"https://wmkeyboard.pages.dev/reference/settings/keymaps/#managing-your-layouts","markdown":"https://wmkeyboard.pages.dev/reference/settings/keymaps.md","score":19.15,"text":"- **Import from another keyboard**: a second ungrouped row directly below it, for a layout from another keyboard: FlorisBoard or HeliBoard (`.json` or `.txt`), FUTO (`.yaml`), Samsung Keyboard (`.kcf`) or Multiling O (layout text or a settings export). Subtitle: \"Read a layout file from FlorisBoard, HeliBoard, FUTO, Samsung Keyboard (Keys Cafe) or Multiling O.\" A Multiling O settings export with more than one layout in it opens one dialog that lists them and imports them all, each in the language it was made for. See [Importing from other keyboards](https://wmkeyboard.pages.dev/reference/importing-other-keyboards/) for what survives the conversion.\n- **Import an input method**: a third row below it, for another input method's own data files: a `.cin` table (gcin, OpenVanilla), a Rime schema with its `.dict.yaml` dictionaries, or an m17n `.mim` file. Subtitle: \"Read a .cin table, a Rime schema with its dictionaries, or an m17n .mim file. Pick all the files the method needs at the same time.\" The picker takes several files at once. The result is a layout that types through the method, with a confirm dialog and a **Language** row like the one above. See [Input methods](https://wmkeyboard.pages.dev/reference/importing-other-keyboards/#input-methods-cin-rime-and-m17n).\n- **Built in**: the enabled shipped layouts, only shown at all once at least one is on."},{"title":"Backup & restore","heading":"Moving to a new phone","section":"Privacy & security","url":"https://wmkeyboard.pages.dev/privacy/backup/#moving-to-a-new-phone","markdown":"https://wmkeyboard.pages.dev/privacy/backup.md","score":18.29,"text":"A backup carries your own RIME words and imported RIME schemas with your personal dictionary, along with which word you picked for each reading on the built-in Chinese and Japanese boards, but nothing that was downloaded. RIME's compiled files stay out too, since RIME builds them again by itself. If the new phone may not reach GitHub, where downloads come from, press **Save downloaded files** on the Backup screen first. It writes one zip with your word lists, RIME's packs, voice and AI models and feature libraries. **Restore downloaded files** on the next phone puts them back. A library goes back in only if its checksum matches what that version of the keyboard expects, so use the same version on both phones. If you restore a backup without those files, the message that follows says how many feature libraries are missing and opens [the page that lists them](https://wmkeyboard.pages.dev/privacy/offline/#feature-libraries).\n\nThemes, sticker packs, icon packs, custom word lists and your own vocabulary\nlists all *replace* rather than merge on import. Restore onto a phone that\nalready has its own customizations in those categories and they're discarded\nin favor of what's in the file. Do this on a fresh install where you can, or\ngo in expecting the overwrite."}]}