Environment:
Keyman for Windows 17.0.329 (latest stable release)
Yiddish Pasekh keyboard (yi-001) Package version 2.0 Yiddish Pasekh keyboard
Windows 11 Pro Version 10.0.22635 Build 22635
Lenovo X1 Carbon notebook PC
After working normally for years, I can’t type a yud (י) character using the mapped “y” key on my physical keyboard or clicking the “y” on the on-screen keyboard (so it’s not a hardware issue with my physical keyboard). Both produce a Roman character “y” when pressed. I haven’t noticed any other keyboard issues.
I’m using the latest version of both the Keyman client and the Yiddish Pasekh keyboard.
I was on the penultimate version of the yiddish_pasekh.bmp when this started happening; I updated to the newest version in hopes that it would fix the issue.
I believe that this is a defect in either the latest version of Keyman or, less likely, in the Yiddish Pasekh keyboard map since the defect occurs in the latest two versions of the keyboard.
That’s no good! I can verify using the keyboard online gives the y output. We’ll definitely take a look. I know we did make changes to the keyboard, but we tried not to make breaking changes.
This morning I checked for, found, and installed the updates to both the Keyman Windows client (now 17.0.330) and the Yiddish Pasekh keyboard (now 2.0.1).
I am happy to report that with these updates the keyboard works perfectly again; the issue with the y/yud mapping is resolved.
THANK YOU, Lorna and everyone else involved in this break/fix.
I’m a heavy (daily) user of the Yiddish Pasekh kb so I’d be a good alpha or beta tester for YP kb updates. I use the physical keyboard > the onscreen one but if I find an issue with the former I then try to reproduce it with the latter to see if it’s a hardware problem or something else.
