RE: LDML Keyboard Descriptions and Normalisation

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 On Behalf Of Richard Wordingham via Unicode Sent: 02

RE: Rendering Sanskrit Medial Sequences -vy- and -ry- in Myanmar

Hi Vinodh, The order of medials in Myanmar clusters is constrained by UTN #11. So yes, you do need to follow the preferred order for Myanmar even if the sequence does not match phonetic order. Is it the case the representation is ဒျွ ဒျြ matches the visual

RE: What is the time frame for USE shapers to provide support for CV+C ?

n 8/7/2019 1:39 PM, Andrew Glass via Unicode wrote: That's correct, the Microsoft implementation of USE spec does not normalize as part of the shaping process. Why? Because the ccc system for non-Latin scripts is not a good mechanism for handling complex requirements for these writing systems and

RE: What is the time frame for USE shapers to provide support for CV+C ?

support for CV+C ? What about text that must exist normalized for other purposes? Domain names must be normalized to NFC, for example. Will such strings display correctly if passed to USE? A./ On 8/7/2019 1:39 PM, Andrew Glass via Unicode wrote: That's correct, the Microsoft implementation

RE: What is the time frame for USE shapers to provide support for CV+C ?

is the time frame for USE shapers to provide support for CV+C ? On Tue, 14 May 2019 03:08:04 +0100 Richard Wordingham via Unicode wrote: > On Tue, 14 May 2019 00:58:07 + > Andrew Glass via Unicode wrote: > > > Here is the essence of the initial changes needed to support CV+C. >

RE: Lao Sign Pali Virama and vowels above

Hi Richard, This is because the sequences include U+0EBA which was added in Unicode 12.0. Edge has not updated for Unicode 12 at this time. Cheers, Andrew -Original Message- From: Unicode On Behalf Of Richard Wordingham via Unicode Sent: Monday, May 20, 2019 3:21 PM To:

RE: What is the time frame for USE shapers to provide support for CV+C ?

Here is the essence of the initial changes needed to support CV+C. Open to feedback. * Create new SAKOT class SAKOT (Sk) based on UISC = Invisible_Stacker * Reduced HALANT class Now only HALANT (H) based on UISC = Virama * Updated Standard cluster mode [< R | CS >] < B | GB > [VS]

RE: Tamil Brahmi Short Mid Vowels

Subject: Re: Tamil Brahmi Short Mid Vowels On Wed, 29 Aug 2018 21:42:57 + Andrew Glass via Unicode wrote: > Thank you Richard and Shriramana for bringing up this interesting > problem. > > I agree we need to fix this. I don’t want to fix this with a font hack > or change to US

RE: Tamil Brahmi Short Mid Vowels

Thank you Richard and Shriramana for bringing up this interesting problem. I agree we need to fix this. I don’t want to fix this with a font hack or change to USE cluster rules or properties. I think the right place to fix this is in the encoding. This might be either a new character for Tamil

RE: Word_Break for Hieroglyphs

We’ve made a lot of progress on Hieroglyphs this year with the addition of the quadrat forming controls (thanks again to everyone involved in that effort and in the preceding 13 documents). I like to think that that part of the model is no longer in flux. Certainly, there is more work to be