Re: L2/18-181

2018-05-16 Thread Richard Wordingham via Unicode
On Thu, 17 May 2018 01:24:09 +0100 Michael Everson via Unicode wrote: > It sounds to me like a fault in the keyboard software, which could be > fixed by the people who own and maintain that software. We had this discussion a few years ago. See

Re: L2/18-181

2018-05-16 Thread Richard Wordingham via Unicode
On Wed, 16 May 2018 17:41:12 -0500 Anshuman Pandey via Unicode wrote: > > 3. Keyboard design is more difficult because consonants like ক্ষ > > are encoded as conjunct forms instead of atomic characters. > > Ignorant question on my part: is it difficult to use character >

Re: L2/18-181

2018-05-16 Thread Michael Everson via Unicode
It sounds to me like a fault in the keyboard software, which could be fixed by the people who own and maintain that software. > On 17 May 2018, at 01:20, Richard Wordingham via Unicode > wrote: > > On Thu, 17 May 2018 00:34:35 +0100 > Michael Everson via Unicode

Re: L2/18-181

2018-05-16 Thread Richard Wordingham via Unicode
On Thu, 17 May 2018 00:34:35 +0100 Michael Everson via Unicode wrote: > This is not a fault of the encoding. > > > On 16 May 2018, at 23:01, Richard Wordingham via Unicode > > wrote: > > > > I think simple Windows keyboards have a limit of 4 16-bit

Re: L2/18-181

2018-05-16 Thread Michael Everson via Unicode
And Icelandic. And Irish. And so on. > On 16 May 2018, at 23:41, Anshuman Pandey via Unicode > wrote: > >> 2. Collation is different between the Assamese and Bengali languages, >> and code point order should reflect collation order. > > The same issue applies to

Re: L2/18-181

2018-05-16 Thread Michael Everson via Unicode
This is not a fault of the encoding. > On 16 May 2018, at 23:01, Richard Wordingham via Unicode > wrote: > > I think simple Windows keyboards have a limit of 4 16-bit code units; > for an Indic SMP script, one couldn't map to a single key, as it > would require 6 code

Fwd: L2/18-181

2018-05-16 Thread Anshuman Pandey via Unicode
> On May 16, 2018, at 3:46 PM, Doug Ewell via Unicode > wrote: > > http://www.unicode.org/L2/L2018/18181-n4947-assamese.pdf > > This is a fascinating proposal to disunify the Assamese script from > Bengali on the following bases: ‘Fascinating’ is a not a term I’d use for

Re: L2/18-181

2018-05-16 Thread Richard Wordingham via Unicode
On Wed, 16 May 2018 13:46:22 -0700 Doug Ewell via Unicode wrote: > http://www.unicode.org/L2/L2018/18181-n4947-assamese.pdf > > This is a fascinating proposal to disunify the Assamese script from > Bengali on the following bases: > 3. Keyboard design is more difficult

Re: Choosing the Set of Renderable Strings

2018-05-16 Thread Richard Wordingham via Unicode
On Wed, 16 May 2018 05:23:08 -0800 James Kass via Unicode wrote: > Note that although the proposal gave canonical combining class > zero to both the tone marks and the vowel signs, the on-line Unicode > data gives canonical combining class 230 to the tone marks. There were

L2/18-181

2018-05-16 Thread Doug Ewell via Unicode
http://www.unicode.org/L2/L2018/18181-n4947-assamese.pdf This is a fascinating proposal to disunify the Assamese script from Bengali on the following bases: 1. The identity of Assamese as a script distinct from Bengali is in jeopardy. 2. Collation is different between the Assamese and Bengali

Re: preliminary proposal: New Unicode characters for Arabic music half-flat and half-sharp symbols

2018-05-16 Thread Hans Åberg via Unicode
> On 16 May 2018, at 09:42, Hans Åberg via Unicode wrote: > >> On 16 May 2018, at 00:48, Ken Whistler via Unicode >> wrote: >> >>> A proposal should also show evidence of usage and glyph variations. >> >> And should probably refer to the

Re: Choosing the Set of Renderable Strings

2018-05-16 Thread James Kass via Unicode
In response to Richard Wordingham, Sorry I can't answer many of your questions. Hoping someone who can does. Note that although the proposal gave canonical combining class zero to both the tone marks and the vowel signs, the on-line Unicode data gives canonical combining class 230 to the tone

Re: preliminary proposal: New Unicode characters for Arabic music half-flat and half-sharp symbols

2018-05-16 Thread Johnny Farraj via Unicode
Hi Garth, You are right, I sent a similar posting to the list 3 years ago. at that time I was hoping get help from some of the more experienced members on the list to write a proposal. this is a very specialized job and it could take me months to figure out the process and learn the language. But

Re: preliminary proposal: New Unicode characters for Arabic music half-flat and half-sharp symbols

2018-05-16 Thread Hans Åberg via Unicode
> On 16 May 2018, at 00:48, Ken Whistler via Unicode > wrote: > > On 5/15/2018 2:46 PM, Markus Scherer via Unicode wrote: >> I am proposing the addition of 2 new characters to the Musical Symbols table: >> >> - the half-flat sign (lowers a note by a quarter tone) >> -