when trying to read emoticons with any synthesizer with cldr data processing enabled, these were not read

[zstanecic]

Steps to reproduce:

1. Type the text with emoticons
2. try to read it with any synthesizer, language or voice of the synthesizer,
   note, this bug also affects espeak,
3. try to read emoticon symbols with arrow keys, and using the review cursor commands.
   note that emoticons symbols are not readable by word and when reading whole text

Actual behavior:

emoticons are not read with cld data enabled

Expected behavior:

emoticons should be read

System configuration:

windows 10 1809 17763

NVDA Installed/portable/running from source:

installed

NVDA version:

latest alpha, alpha-16149,e713f614

Windows version:

10.0.17763 /1809

Name and version of other software in use when reproducing the issue:

n/a not applicable

Other information about your system:

Other questions:

Does the issue still occur after restarting your PC?

yes

Have you tried any other versions of NVDA?

no, and not applicable, as this is the new feature recently included

[LeonarddeR]

Note that the CLDR data does not contain emoticon descriptions, only emoji descriptions.

• Emoticons include :D, :), and ;)
• Emoji include 👍🏻, 😂, and ❤

[zstanecic]

Hi, When i say emoticons, i mean emojies, From: Leonard de Ruijter <notifications@github.com> Sent: Tuesday, October 9, 2018 1:35 PM To: nvaccess/nvda <nvda@noreply.github.com> Cc: zstanecic <zvonimirek222@yandex.com>; Author <author@noreply.github.com> Subject: Re: [nvaccess/nvda] when trying to read emoticons with any synthesizer with cldr data processing enabled, these were not read (#8826) Note that the CLDR data does not contain emoticon descriptions, only emoji descriptions. * Emoticons include :D, :), and ;) * Emoji include 👍🏻, 😂, and ❤ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8826 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AKohk0YM5u-4uFf-afTxn_04cL5g8Rqmks5ujInMgaJpZM4XMB3E> . <https://github.com/notifications/beacon/AKohk6lxj8tFGH8eSOZk7DQD7MAgC1T3ks5ujInMgaJpZM4XMB3E.gif>

[LeonarddeR]

A quick talk with @zstanecic revealed that he was using speech at the none symbol level, and in this case, emojis won't be read.
We might want to document this.

[LeonarddeR]

Given the request we have received, I think it makes sense to do the following:

1. Speak emoji at the none level as well, which basically means that they're always spoken
2. Add a script/gesture to disable/enable emoji processing. I propose shift+NVDA+p.