{"query":"import rime dictionary","results":[{"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.92,"text":"- **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. Its dictionary's `encoder` rules are applied as Rime's own compiler applies them: a phrase the dictionary lists without a code, and every phrase of the word list it names, gets the code its formula spells from its characters' codes (Wubi 86 types 中国 as `khlg`, the first two letters of each), skipping the codes its `exclude_patterns` rule out. 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":"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.5,"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":"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.23,"text":"**Traditional characters** and **Regional wording** work here too: they switch on the matching filter inside the schema (Simplified, Traditional, Taiwan or Hong Kong forms), so a candidate is converted before the keyboard measures how much of your reading it covers. Cantonese stays in Traditional, as the built-in Jyutping dictionary is.\n\n**Words on the keys.** On the Pinyin layout, candidates float over the key that carries on their reading, read from the spelling RIME shows for each one, so a schema that shows no spelling floats none. After a commit, the words from what comes next float over the key that starts them, which needs the Chinese dictionary pack as well.\n\n**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.3,"text":"- **Another keyboard** (in the Import a layout sheet): 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- **Input method** (in the Import a layout sheet): 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":"Importing from other keyboards","heading":"What can be imported","section":"Reference","url":"https://wmkeyboard.pages.dev/reference/importing-other-keyboards/#what-can-be-imported","markdown":"https://wmkeyboard.pages.dev/reference/importing-other-keyboards.md","score":17.67,"text":"| `.schema.yaml` with its `.dict.yaml` files | Rime (Weasel, Squirrel, Trime, fcitx5-rime) | A layout that types the schema |\n| `.mim` | m17n (ibus-m17n, fcitx5-m17n): ITRANS, InScript, Tamil99 and the other Indic methods | A layout whose rules write the text as you type |\n| jquery.ime rule file (`.js`, or Indic Keyboard's `.xml`) | Wikipedia's input methods, Indic Keyboard: several hundred methods for languages across the world | A layout whose rules write the text as you type |\n| Colour theme text | HeliBoard, LeanType | One theme, from a file or from the clipboard |\n| `OK_Settings_Begin` theme text or a theme link | Multiling O Keyboard | One theme, from a file or from the clipboard |\n| `kinetica_backup_….txt` backup | Kinetica 2.2 and later | A list of everything inside to pick from: see [Whole backups](#whole-backups). The **Kinetica** button on the themes screen takes its theme alone |\n| `.clinktheme` | Clink (iOS) | One theme, with a dark and a light look when it switched with the phone |\n| `.clinklayout` | Clink (iOS) | A custom layout of its letter rows |\n| `.zip` theme | Gboard, the Rboard community | One theme, with a look each for key borders on and off |\n| `.zip` or `.pack` theme pack | Rboard | Any or all of the themes inside, each its own theme |\n| `.keyman-touch-layout` | Keyman | A custom layout, without the keyboard's rules |\n| `.kmp` package | Keyman | A custom layout and its typing rules |\n| `.combined` word list | HeliBoard, LeanType, FUTO, any AOSP keyboard | A custom dictionary |\n| `.dict` dictionary | HeliBoard, LeanType, FUTO, OpenBoard, GApps | A custom dictionary |"}]}