LDML Keyboard Descriptions and Normalisation

Andrew Glass via Unicode unicode at unicode.org
Tue Sep 3 13:03:18 CDT 2019

Hi Richard,

This is a good point. A keyboard that is doing transforms should specify which type of normalization it has been designed to do. I've filed a ticket to track this.



-----Original Message-----
From: Unicode <unicode-bounces at unicode.org> On Behalf Of Richard Wordingham via Unicode
Sent: 02 September 2019 19:07
To: unicode at unicode.org
Subject: LDML Keyboard Descriptions and Normalisation

I'm getting conflicting indications about how the LDML keyboard description handles issues of canonical equivalence.  I have one simple question which some people may be able to answer.

Is the keyboard specification intended to distinguish between keyboards that generally output:

(a) NFC text;
(b) NFD text; or
(c) Deliberately unnormalised texts?

For example, when documenting my own keyboards, I would want to distinguish between a keyboard that went to great trouble to output text in precomposed characters as opposed to one that took the easy route of outputting text in fully decomposed characters.  For a Tibetan keyboard, it would matter whether contractions were compatible with the USE (so generally *not* NFC or NFD) or in NFC or NFD.


More information about the Unicode mailing list