RE: LDML Keyboard Descriptions and Normalisation

From: Andrew Glass via Unicode <unicode_at_unicode.org>
Date: Tue, 3 Sep 2019 18:03:18 +0000

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.

Cheers,

Andrew

-----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.

Richard.
Received on Tue Sep 03 2019 - 13:03:59 CDT

This archive was generated by hypermail 2.2.0 : Tue Sep 03 2019 - 13:04:00 CDT