[2303_missing_js] Update some of the keyboards in this issue

[LornaSIL]

Partially addresses #2303

@mcdurdin I did not address:

gff_amh_7.kps
gff_amh_powerpack_7.kps
gff_ethiopic_7.kps

because those are deprecated.
How do you want that handled? Or maybe you should not be testing deprecated keyboards?

[dyacob]

Did Keyman 7 produce JS files? I think it only created desktop keyboards, no web or mobile. So they may not really be "missing" in a sense. The packages were just not maintained to target platforms that came later -which in turn is handled by the successor projects that deprecate these.

[mcdurdin]

Did Keyman 7 produce JS files? I think it only created desktop keyboards, no web or mobile. So they may not really be "missing" in a sense. The packages were just not maintained to target platforms that came later -which in turn is handled by the successor projects that deprecate these.

The reason these keyboards were flagged is because their &TARGETS system store included mobile, e.g.:

keyboards/release/gff/gff_amh_7/source/gff_amh_7.kmn

Line 100 in ca4b1ec

store(&TARGETS) 'any windows'

[mcdurdin]

I note that gff_gurage_and_amharic has an override for platformsupport in its keyboard_info:

keyboards/release/packages/gff_gurage_and_amharic/gff_gurage_and_amharic.keyboard_info

Lines 28 to 32 in 59c44e8

	"platformSupport": {
	"windows": "full",
	"macos": "full",
	"linux": "full"
	}

This means it still won't be offered on touch platforms

[dyacob]

This was the original intent, that it be desktop only. GFF Gurage does have a touch layout, but it really only works in the Keyman App at this time since the Android and Apple system fonts do not yet support the Gurage letters added to Unicode 14. The KM app can load its own font. Android 14 should finally include a Noto Ethiopic font update with the 28 extra letters. Apple is still dragging its feet.

So the override would eventually be removed. Can platformSupport include a minimal version of Android or iOS? A way to specify Android >= 14 , iOS >= 18.3 would be helpful when the system font updates arrive.

Checking the .keyboard_info 1.0 Specification there doesn't appear to be support for this, but it would be good to add to the KeyboardPlatformInfo object at some point.

[DavidLRowe]

@dyacob @mcdurdin Does any of this discussion need to be moved to a new issue so that it can be acted upon?

[mcdurdin]

@dyacob @mcdurdin Does any of this discussion need to be moved to a new issue so that it can be acted upon?

I think it's all good now. There's a follow-up, related, issue regarding .keyboard_info files and inconsistent platform support data that may illuminate a little in #2311.

[mcdurdin]

Can platformSupport include a minimal version of Android or iOS? A way to specify Android >= 14 , iOS >= 18.3 would be helpful when the system font updates arrive.

Checking the .keyboard_info 1.0 Specification there doesn't appear to be support for this, but it would be good to add to the KeyboardPlatformInfo object at some point.

This would be a "nice to have" which I will track in work around the package metadata formats in keymanapp/keyman#9351. No promises at this point! I will note that it's actually really hard to maintain this level of version metadata.