I am running Windows 10 on my desktop, the most recent version of Keyman. I am attempting to install a keyboard ( this is the link - americanfutharch.kmp - Google Drive )
I can download the keyboard KMP just fine. When I attempt to install, Keyman says that the keyboard has been installed but it never displays.
Any ideas anyone? I have done the usual reboot, disable AV and firewall, etc. Nothing seems to work. Works fine on my Apple devices.
I also downloaded and installed the file with no errors, but no keyboard shows up.
Without seeing the source, I cannot say for sure, but I suspect that there hasn’t been a language associated with the keyboard. The language should be set in the .kps file.
Having the source would help, but here are some things that I found when looking in (compiled) .kmp file. I don’t know if any of them would cause the problem you are seeing.
The language tag being used is ‘usa-Runr-US’, however ‘usa’ is for the Usarufa language of Papua New Guinea, so that is inappropriate. IIUC this is being used to write (American) English, so I think ‘en-Runr’ would be more appropriate.
When this package was made, the .kmp file was included in the list of files to include in the package. That is, the .kmp file includes itself (or at least a previous version of itself), thus doubling the size of the file.
If you’d like me to take a look, can you put your source files in a location where I can access them?
Thank you both for taking a look - unfortunately, I don’t have access to the source files as I am not the developer (and not yet familiar with the Keyman Developer (though I am working on it). This is a relatively new and small project so the support is currently limited. I have reached out to the person who commissioned the keyboard and they hope to have resolved soon. Thank you again.
Yes, the keyboard package is broken because it has a slightly smaller copy of americanfutharch.kmp embedded inside it – and what’s more that nesting continues multiple levels deep – I haven’t fully extracted this, but going by file sizes, there may be 20 or more levels of nesting. This would be why Keyman for Windows is struggling with it – it’s installing the nested package over the original one.
Nested packages are a little-used feature that Keyman for Windows has had for many years; Keyman implementations on Linux and macOS don’t support nested packages.
As to how this happened, my guess is that the .kps (package source) file includes a reference to the .kmp file in the build folder of the project, and so each time it’s built, it gets another layer deeper. The easy fix is to remove the .kmp file from the .kps file listing.
I went ahead and listed this as a possible future safeguard we could add to Keyman Developer in the future at #13109.