I’ve split this topic out from https://community.software.sil.org/t/issue-with-holem-vs-holem-for-waw-with-the-sil-hebrew-keyboard/5164 in order to separate the keyboard design discussion from a potential issue with Keyman.
This topic is about potential difference in behaviour between Windows and macOS. The original topic continues the keyboard design issue.
@martinacc wrote originally:
I have an issue with Holem vs Holem for Waw with the SIL Hebrew keyboard.
Normally, typing “O” will output Holem, and typing “Shift + O” will output Holem for Waw.
I wish this mapping is consistent. However, the combination with Waw messes it up.
When I type “Waw” followed by “O”, it automatically turns into “Waw + Holem for Waw”.
I need to first type “O”, then “Waw” in order to output “Holem Waw”.
This is not how I normally type. I used to use the SBL Hebrew keyboard, and typing “O” always outputs “Holem”, even after “Waw”. I’ve always instructed my students to first time “Waw” then “Holem” for “Holem Waw”. Now, I will have to tell them NEVER to do it for “Holem Waw”. It is very important, because if students type “Holem for Waw”, their answers will be marked as incorrect by the online grading system.
Is it possible to prevent the automatic transformation?
to make it worse, the auto transformation issue happens to the Mac version only. The windows version does not have this issue. So there is in consistency.
PS: I switched from the SBL Hebrew keyboard to Keyman, because the SBL Hebrew keyboard is inconsistent on the presentation of Shin and Sin. On Mac, the unicode value for Shin is
\uFB2Aand on Windows it is
\u05E9\u05C1. Keyman is consistent on the presentation of Shin and Sin. But now, the “Holem” → “Holem for Waw” issue with the Mac version of Keyman is worse than the Sin/Shin issue with the SBL Hebrew keyboard in my work, I may have to painfully switch back to the SBL keyboard.
So, again, is there any way to prevent this automatic transformation of “Holem” to “Holem for Waw” after Waw on Mac?
… see original topic for more discussions …
Okay, I’ve tested some more this morning. I had a test version of Keyman installed on my mac last week, and it turns out I was seeing anomolous behaviour with that. Installing 14.0.280, I see the expected behaviour on macOS for sample key combinations do (gives
U+05D3 U+05B9) and wo (gives
U+05D5 U+05BA). This matches what I see for Windows.
So if you are seeing something different on Windows and macOS, we need to try and figure out why. Can we start off again with you trying those two sequences on both platforms and documenting what is being produced? Note the OS version, Keyman version and keyboard version in both cases. Use a basic app such as TextEdit on mac and Notepad on Windows, so we can be sure that there are no application interactions.