Hebrew keyboards to consider updating with remapping

[LornaSIL]

Hebrew keyboards to consider updating with remapping:

store(&DISPLAYMAP) '../../../shared/fonts/kbd/kbdhebr/KbdHebr.json'

• https://keyman.com/keyboards/sil_hebrew_legacy
• https://keyman.com/keyboards/basic_kbdhebl3
• https://keyman.com/keyboards/basic_kbdheb
• https://keyman.com/keyboards/galaxie_hebrew_mnemonic
• https://keyman.com/keyboards/galaxie_hebrew_positional
• https://keyman.com/keyboards/alephwithbeth
• https://keyman.com/keyboards/yiddish_pasekh

The problem with the galaxie keyboards is that they are also part of a package and as far as I know we can't use this workaround in Keyman Dev 16.0 (packages still require v16.0 structure).

Keyboard	Platform	Add/Remove	Level
galaxie_greek_hebrew_mnemonic	macos	add	full
galaxie_greek_hebrew_positional	mobileWeb	add	full
galaxie_hebrew_positional	mobileWeb	remove	full

[mcdurdin]

The problem with the galaxie keyboards is that they are also part of a package and as far as I know we can't use this workaround in Keyman Dev 16.0 (packages projects still require v16.0 structure).

The v16 project structure still works with v17 Developer. There is no requirement to upgrade the project file format, just a recommendation, where possible. So that should not be a blocker to using the v17 compiler to leverage the &displayMap functionality.

[LornaSIL]

One thing I didn't do when I updated sil_hebrew.kvks was to remove U+25cc from the .kvks file. I think I should do that. Is that correct @darcywong00 or @mcdurdin?

I looked at khmer_angkor and it doesn't seem to have U+25cc in the .kvks file.

These are the steps @DavidLRowe suggested as documentation:

• HISTORY.md - include new version number, and description:
• LICENSE.md - update date if needed

Update keyboard to use special OSK font for better display

• xyz.kmn

  • Update version number;
  • add store(&DISPLAYMAP) '../../..shared/fonts/kbd/kbdxxxx/KbdXxxx.json' (this file will be compiled into the .kmx so doesn't need including in the .kps)

• xyz.kvks

  • set to use KbdXxxx font (in "encoding" "fontname" element).
  • remove any U+25cc codes that were originally added to improve legibility

• xyz.kps

  • add ../../../shared/fonts/kbd/kbdxxxx/KbdXxxx.ttf to list of fonts
  • set Keyboard font to use the KbdXxxx font (used for OSK)

• Needed only for the first keyboard using the Xxxx script: in release/shared/fonts/kbd/kbdxxxx/ folder, add KbdXxxx.json and KbdXxxx.ttf

  • Should document the development process somewhere. I think it's documented, just need to find it.