Open mcdurdin opened 4 weeks ago
mcdurdin
commented
4 weeks ago I wonder also about the bundle packages (e.g. galaxie_greek_hebrew_mnemonic) if there may be a separate issue to tackle here? It seems like we are adding support for web platforms but the bundled name will not be available in web.
This probably needs to be tackled on the compiler side. A little more nuance may be needed to exclude web platforms from multi-keyboard packages. See keymanapp/keyman#11645.
LornaSIL
commented
1 week ago Can you explain more what you would like? If we look at aramaic_hebrew, the .kmn has
store(&TARGETS) 'web desktop'and there is no mobile-specific layout.
The .kps does include the .js file which is presumably why it claims to support android, ios, mobileWeb.
So, in your table above it says "remove", but it says level is "full". I'm not sure what that means. Should I remove the .js from the .kps or should I add a mobile layout?
Some keyboards are listed with different platform support. Keyman Developer 16 did not always report this consistently, as it 'guessed' on mobile keyboards when a .js was being produced. Also, a few keyboards had inconsistent information in their .keyboard_info, e.g. kbdsn1. v17 is more consistent on matching the &TARGETS store. These 122 keyboards are impacted:
We may want to update the &TARGETS store in some of these keyboards to make them available on these removed platforms, as a separate project.
I wonder also about the bundle packages (e.g. galaxie_greek_hebrew_mnemonic) if there may be a separate issue to tackle here? It seems like we are adding support for web platforms but the bundled name will not be available in web.
Originally posted by @mcdurdin in https://github.com/keymanapp/keyboards/issues/2423#issuecomment-2143620424