chore: improve targets for various keyboards with v17 about keyboards HOT 5 OPEN

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.

from keyboards.

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?

from keyboards.

Sorry for the long delay on this.

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?

In an ideal world we update the keyboards to include full mobile support. But in the meantime, we have two options: (a) add mobile to &targets so that users can still install the desktop-style keyboard and we keep consistent metadata, or (b) remove the .js from the package. I am not sure which is best.

from keyboards.

@mcdurdin kbdsn1 - this keyboard is deprecated. Do we really want to make changes to it?

from keyboards.

@mcdurdin kbdsn1 - this keyboard is deprecated. Do we really want to make changes to it?

Nope, sorry I missed that it was deprecated in my audit.

from keyboards.