Fixes for CLDR 19169 #5253
Fixes for CLDR 19169 #5253
Conversation
|
We should probably have some guidance/policy on when to use codepoints (possibly with comments) and when to use characters themselves, these are difficult to review just in code. |
As usual, it depends on fonts, layout engines, RTL status, etc as to which is easier. Tool wise, we could have something like cldrmodify which automatically enforces such a policy. The simplest policy is of course to leave it to author's discretion. |
| <key id="K" output="\u{10A11}\m{A}" /> | ||
| <key id="q" output="\u{10A11}\m{A}" /> | ||
| <key id="Q" output="\u{10A11}\m{A}" /> | ||
| <key id="Q" output="\u{10A11}\m{A}" /> <!--intentional duplicate --> |
There was a problem hiding this comment.
Perhaps something such as "q and Q produce the same output"?
For that matter, why not just use the same key in two spots in the layout?
| <layers formId="us"> | ||
| <layer modifiers="none"> | ||
| <row keys="grave 1 2 3 4 5 6 7 8 9 0 barabove equal"/> | ||
| <row keys="q w e r t y u i o p open-square close-square backslash"/> |
CLDR-19169
ALLOW_MANY_COMMITS=true
These keyboard updates implement refinements for new LDML layouts for Sanskrit, Tibetan, and Gandhari including introducing backspace transforms and better use of set/uset.