Yes, it is a really old keyboard, but I think we do have source (currently in a private keyman-keyboards-internal repo, Chinese-Japanese-Korean KMW folder, not in the public repo). See also https://github.com/keymanapp/keyboards/pull/64 for a Windows equivalent which also needs work.
A few notes:
It depends on a database backend which is still running on legacy infrastructure.
The source that we do have would take some time to organise and publish; it’s not well organised and needs careful preparation.
Great article! The feedback on gaps in the documentation is appreciated (you can also add issues for documentation or even submit pull requests at keymanapp/help.keyman.com). I’ll get the rest of the Keyman team to read it too; they may have ideas for you.
I especially appreciate the documentation link as the number of different keyman related repos is a little hard to sort through at first. As I learn more about the engine and my thoughts coalesce, I think I’ll try submitting improvements through pull requests.
This is the second time I’ve tried to pull a big tool that is not an Angular-friendly NPM package into my project, and both times it’s been a bit of a struggle. So yes, there is definitely room for improvement on how I’m handling the images, fonts, and CSS (and I have much to learn). This was just the first configuration that I could get to actually work.
I’ll share a link to our production app later on when my keyboard addition reaches the surface.
Understood. NPM is on our roadmap … but it’s not a small project and we definitely have a lot of room for improvement ourselves. For example, the CSS in KeymanWeb is ancient and desperately needs rewriting (preferably in .scss).
I look forward to seeing the production app in the future!
Thanks for the clear and detailed bug report I may have a crack at some of these on my return to Australia in a few days; the mobile support is probably a bigger thing because they’ve never been supported on mobile, but the other issues are certainly easily fixable.