We need to get more scripts into Unicode, not more emoji.

That is — somewhat inflated — the core message of a NYT article published six 
months ago,
and never shared here (no more than so many articles about Unicode, scripts, 
and emoji).
Some 100 scripts are missing in the Standard, affecting as many as 400 million 
people worldwide.

https://www.nytimes.com/2017/10/18/magazine/how-the-appetite-for-emojis-complicates-the-effort-to-standardize-the-worlds-alphabets.html

(Just found while searching for Hanifi Rohingya script, thanks to the Wikipedia 
entry 
[trying to find out whether to include Hanifi Rohingya in beta feedback 
{closing soon}]).

On 01/04/18 08:27 Nathan Galt via Unicode wrote
> 
> I predict that these emoji will be extraordinarily popular in insults between 
> gamers on both Twitch and Discord. I’d wager, with suitable metrics 
> available, that using these for insult purposes will be the majority of all 
> accessibility-emoji use worldwide. Expected meanings:
> 
> - PERSON WITH WHITE CANE: “the person under discussion didn’t see that guy 
> who killed him/his partner/his whole team”
> - DEAF SIGN: “the person under discussion failed to notice an audio cue that 
> would have prevented his/his partner’s/his team’s death(s)”
> - PERSON IN MECHANIZED WHEELCHAIR: “the person under discussion failed to 
> properly press keys and move his mouse as he should have and his mechanical 
> failures caused his/his partner’s/his team's death(s)”
> 
> I don’t think the cultural impact of these will be as uniformly positive as 
> Apple hopes.
> 
> 
> > On Mar 26, 2018, at 9:51 AM, William_J_G Overington via Unicode  wrote:
> > 
> > I have been looking with interest at the following publication.
> > 
> > Proposal For New Accessibility Emoji
> > 
> > by Apple Inc.
> > 
> > www.unicode.org/L2/L2018/18080-accessibility-emoji.pdf
> > 
> > I am supportive of the proposal. Indeed please have more such emoji as well.
> > 
> > [snip]
> > 
> > How could the accessibility emoji in the proposal be used in practice?
> > 
> > William Overington
> > 
> > Monday 26 March 2018
> 
> 
>

Reply via email to