Hi Richard, I agree that there is some work to be done to ensure correct display of Tai Tham. That work may involve changes to USE in a future update. We will have a panel on Universal Shaping at the upcoming IUC conference. That will be a good opportunity for a discussion between implementers and font developers. If you are able to attend that would be great. If not, we can certainly go through the proposed changes you have sent.
Cheers, Andrew -----Original Message----- From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of Richard Wordingham Sent: Friday, May 8, 2015 9:50 AM To: unicode@unicode.org Subject: Re: Script / font support in Windows 10 On Fri, 8 May 2015 14:15:55 +0000 Peter Constable <peter...@microsoft.com> wrote: > I think this is the right public link: > > https://msdn.microsoft.com/en-us/goglobal/bb688099.aspx Does this confirm the intention of Microsoft that at some stage the Universal Shaping Engine (USE) in Windows 10 will support the Tai Tham script? In February we discovered that the USE didn't support syllable-final SAKOT+consonant - the commonest and eponymous use of U+1A60 TAI THAM SIGN SAKOT, which may well be the commonest character in the Tai Tham script. For example, we can't write the name of the city of 'Chiang Rai' in the Tai Tham script using the USE. Richard.
