|
On 11/12/2019 12:32 PM,
[email protected] via Unicode wrote:
> Just because you can write something that is a very detailed specification doesn't mean that it is, or ever should be, a standard. Just because a select group of people engages in communication about the arcane details of a proposed specification it doesn't mean that the outcome will benefit some entirely different and larger group communicate better. There's too much of the "might possibly" about this; and it is quite different from the early days of Unicode itself, where there was a groundswell of pent-up demand for a solution to the fragmented character encoding landscape; the discussions quickly became about the best way to do that, and about how to ensure that the result would be supported. The current effort starts from an unrelated problem (Unicode not wanting to administer emoji applications) and in my analysis, seriously puts the cart before the horse. A./ |
- New Public Review on QID emoji [email protected] via Unicode
- Re: New Public Review on QID em... [email protected] via Unicode
- Re: New Public Review on QI... Ken Whistler via Unicode
- RE: New Public Review o... Peter Constable via Unicode
- Re: New Public Revi... Asmus Freytag via Unicode
- Re: New Public... [email protected] via Unicode
- Re: New Pu... Asmus Freytag via Unicode
- Re: Ne... [email protected] via Unicode
- Re: Ne... Asmus Freytag via Unicode
- Re: Ne... James Kass via Unicode
- Re: Ne... [email protected] via Unicode
- RE: New Public Revi... [email protected] via Unicode

