keymanapp / keymanapp/keyman

bug(developer): import of Windows keyboard does not precisely match deadkey behaviour

Open
#5,551 2 comments 0 reactions 0 assignees View on GitHub
bug developer/
Dominant language
Pascal
Stars
534
Forks
143
Avg merge
2d 10h
Merged PRs (30d)
113

Description

**Describe the bug**

On a Windows keyboard, if a deadkey is not matched on the next key, then the default character for the deadkey is emitted, along with that next key's output. When importing into Keyman, we lose that behaviour -- we only get the default character with spacebar.

https://github.com/keymanapp/keyboards/pull/1612 shows one potential resolution:

One way to do this may be to use `notany` to generate a default result for `U+0441`:

```
dk(0441) notany(dkf0441) > U+0441 context(2)
```

And similarly for the other combinations.

We need to analyse this further before implementing.

**To Reproduce**

1. Import the kbdrum "Russian - Mnemonic" Windows keyboard in Keyman Developer
2. Typing sd gives д instead of expected сд.

---

**Keyman Developer:**
- OS: N/A
- Keyman Developer version: 14.0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.