On the last updating, the keyman lexical model can have 8 candidates.
I think 8 is not enough for the future IME developing.
I want 30 candidates.
Can you add this feature on the following updating?
nyny
January 14, 2025, 5:40am
2
Hello @Cathaylab ,
You can request a new feature for the lexical model here .
Thanks.
More importantly, I see the actual request here is in regard to developing an IME/IMX - a ‘picker’ solution like those used with the Chinese and Japanese languages.
As with I want a new feature in Keyman Lexical model , this GitHub issue should be of interest:
opened 05:45AM - 19 Dec 22 UTC
common/
feat
### Is your feature request related to a problem? Please describe.
In our key… boards repository, we have a few old Web keyboards that implemented custom CJK-picker functionality. This functionality is only functional on `desktop` form-factor devices, and is thus not practical to use within Keyman for Android or Keyman for iPhone and iPad.
See:
- https://keymanweb.com/#cmn-hans,Keyboard_chinese
- https://keymanweb.com/#ko,Keyboard_korean_rr
- https://keymanweb.com/#ja,Keyboard_japanese
We've had a few recent Community forum posts highly related to this functionality, with some users and/or communities seeking to implement their own versions of this as well.
See:
- https://community.software.sil.org/t/creating-a-proper-applicable-lexical-model/7004
- https://community.software.sil.org/t/simplifying-text-menu-patterns/7013
- This one was hoping to insert a menu into the context, with the next keystroke making a selection; sort of an inlined-IMX as if in a command-line console.
Note that at their core, picker keyboards like the three existing ones listed above tend to operate based upon the following pattern, expressed roughly in Keyman language syntax:
- `<source text>` + [ `number keystroke`] > `<transformed text>`
- In a way, they are _loosely_ similar to predictive text: input text gets mapped to an output text suggestion.
- Note that `<source text>` may or may not be in the same script as the `<transformed text>`! This is a notable distinction from our existing predictive text models, which expect same-source operation with limited transformation of the text.
### Describe the solution you'd like
Desired features:
- Whatever form the IMX solution takes, it should be supported by all end-user Keyman platforms.
- The IMX should take in post-keystroke context and output 'picker suggestions' based upon said text.
- Typically, use of a number key (on desktop) should allow selection of one of the options.
- On touch... we can probably rely on something very similar to the predictive-text banner, if not that banner itself.
- We should be able to convert our existing picker keyboards to utilize the same solution.
### Describe alternatives you've considered
_No response_
### Keyman apps
- [X] Keyman for Android
- [X] Keyman for iPhone and iPad
- [X] Keyman for Linux
- [X] Keyman for macOS
- [X] Keyman for Windows
- [X] Keyman Developer
- [X] KeymanWeb