nvda@nvda.groups.io

Re: wonder vs. wander

Sarah k Alawami

#50781

Actually , my mac read everything with out exaggeration or what not. It all sounded normal to me. Now if I would have taken the time to "spell" everything , I would probably notice the mistakes, but yeah.

Show quoted text

On 19 Nov 2018, at 11:28, Brian Vogel wrote:

On Mon, Nov 19, 2018 at 01:21 PM, Kwork wrote:

NVDA is saying awl words correctly, if exaggeratedly at times.
Any time you hear a speech synthesizer saying something "exaggeratedly" that should be a big, honkin' warning that something's off.

Kudos, though, on this post. It was extremely clever. I do, however, believe that one should be able to hear the difference, even in synthesized speech in the middle of a sentence, between pro deuce and produce (as but one example). There's also the question of whether we're talking produce as a verb or noun, as the stress is on the second syllable in the first instance and the first syllable in the second. That being said, the speed at which many blind individuals can understand voice output from screen readers just astounds me. I could no sooner wrap my head around speech that fast than fly to the moon using my own arms as propulsion. If you have speech produced at ear blistering (for me) speeds then the elisions between two short words and a single word with the same phonemes becomes much harder to suss out.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

~ Saul Bellow, To Jerusalem and Back

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

Joseph Lee

#50780

Hi,
Eh? That's weird. Have you tried with OneCore synthesizer too? If the new CLDR setting is checked from voice settings yet NVDA isn't reading emojis, chances are that you may have symbol level set to none or some.
Cheers,
Joseph

Show quoted text

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: Tuesday, November 20, 2018 10:23 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, just restarted with all addons disabled. Here we go with trying to enter an emoji. I could enter one, but it read the same way, 1 of 50, so I have no idea what it was. So I deleted it.

On 11/20/2018 0:26, Joseph Lee wrote:
Hi,
What you're describing is the behavior of emoji panel in Version 1803. Can you try with all add-ons turned off (from exit dialog, select restart with add-ons disabled)?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John 
Isige
Sent: Monday, November 19, 2018 10:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, let's see if this works. No, if I shift tab from most recent I get "search emoji", then continuing to shift tab I get the categories like "transportation", but if I use the arrows, it just does "1 of 250" and so on.

On 11/19/2018 22:47, hurrikennyandopo ... wrote:
Hi

I just noticed now when you are on the recent one if you shift/tab 
now it gives you the categories where now you right or left arrow to 
them then press the enter key on the one you want then shift tab or 
tab to get to the list of them. it seems to be speaking mine out correctly.

it seems like a slight modification to the tutorial.

Gene nz

On 20/11/2018 4:46 PM, John Isige wrote:
Just tested the beta, and it doesn't read emojis, at least for me, 
with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on.
This happens even with the one-core voices, which used to read more 
emojis than any other synthesizer. This happens whether the copy is 
installed or portable. Windows 10 64-bit, latest upates, not 1809 
though. Here's the log from when I try to get to an emoji to put 
into this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation INFO - core.main
(21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018,
16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main
(21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1 INFO - 
synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - 
brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10> 
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 
'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 
'NVDAObjects.NVDAObject'>, <class 
'documentBase.TextContainerObject'>, <class 
'baseObject.ScriptableObject'>, <class 
'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule:
<'windowsinternal_composableshell_experiences_textinput_inputapp'
(appName
u'windowsinternal_composableshell_experiences_textinput_inputapp',
process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0> 
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent 
link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)] UIA
className: GridViewItem UIA patterns available:
LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, 
ScrollItemPattern, SelectionItemPattern

--
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related 
material at http://www.accessibilitycentral.net Regardless of where 
you are in New Zealand if you are near one of the APNK sites you can 
use a copy of the NVDA screen reader on one of their computers. To 
find out which locations (or location) is near to you please visit 
http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA certified expert 
near you, please visit the following link 
https://certification.nvaccess.org/. The certification page contains 
the official list of NVDA certified individuals from around the 
world, who have sat and successfully passed the NVDA expert exam.

Re: continues in beta

Joseph Lee

#50779

Hi,
Okay, can you do the following for me please:
1. Close Settings app.
2. Restart NVDA with debug logging enabled (from exit dialog).
3. Open Settings app. NVDA should announce gibberish at this point.
4. Close Settings app, then open NVDA log viewer (NVDA+F1), copy everything, and paste the entire log as a private email to me.

Cheers,
Jsoeph

Show quoted text

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Tuesday, November 20, 2018 10:33 AM
To: nvda@nvda.groups.io
Subject: [nvda] continues in beta

With the last release of NVDA when you open up the settings menu NVDA reads what I call trash.  This issue still remains with the 2018-4 beta 1.
It is saying something like
C equals microsoft windows
O equals Microsoft corporation
L equals readman
F equals Washington
c equals us windows

continues in beta

Don H

#50778

With the last release of NVDA when you open up the settings menu NVDA reads what I call trash.  This issue still remains with the 2018-4 beta 1.
It is saying something like
C equals microsoft windows
O equals Microsoft corporation
L equals readman
F equals Washington
c equals us windows

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

John Isige

#50777

OK, just restarted with all addons disabled. Here we go with trying to enter an emoji. I could enter one, but it read the same way, 1 of 50, so I have no idea what it was. So I deleted it.

Show quoted text

On 11/20/2018 0:26, Joseph Lee wrote:
Hi,
What you're describing is the behavior of emoji panel in Version 1803. Can you try with all add-ons turned off (from exit dialog, select restart with add-ons disabled)?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: Monday, November 19, 2018 10:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, let's see if this works. No, if I shift tab from most recent I get "search emoji", then continuing to shift tab I get the categories like "transportation", but if I use the arrows, it just does "1 of 250" and so on.

On 11/19/2018 22:47, hurrikennyandopo ... wrote:
Hi

I just noticed now when you are on the recent one if you shift/tab now
it gives you the categories where now you right or left arrow to them
then press the enter key on the one you want then shift tab or tab to
get to the list of them. it seems to be speaking mine out correctly.

it seems like a slight modification to the tutorial.

Gene nz

On 20/11/2018 4:46 PM, John Isige wrote:
Just tested the beta, and it doesn't read emojis, at least for me,
with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on.
This happens even with the one-core voices, which used to read more
emojis than any other synthesizer. This happens whether the copy is
installed or portable. Windows 10 64-bit, latest upates, not 1809
though. Here's the log from when I try to get to an emoji to put into
this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation INFO - core.main
(21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018,
16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main
(21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1 INFO -
synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO -
brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10> Python
class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class
'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class
'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule:
<'windowsinternal_composableshell_experiences_textinput_inputapp'
(appName
u'windowsinternal_composableshell_experiences_textinput_inputapp',
process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0>
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent
link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)] UIA
className: GridViewItem UIA patterns available:
LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern,
ScrollItemPattern, SelectionItemPattern

--
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related
material at http://www.accessibilitycentral.net Regardless of where
you are in New Zealand if you are near one of the APNK sites you can
use a copy of the NVDA screen reader on one of their computers. To
find out which locations (or location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA certified expert
near you, please visit the following link
https://certification.nvaccess.org/. The certification page contains
the official list of NVDA certified individuals from around the world,
who have sat and successfully passed the NVDA expert exam.

Re: New registration atscounts in assembla

Ján Kulik

#50776

I do not know, I'm probably off, my invitation was gone, and if I register or I'm wrong?

Re: New registration atscounts in assembla

Iván Novegil

#50775

Has your email address been invited to the team? I don't see any recent invitation to that address...

If you have one, try to sign up again by clicking the link on it, or if this doesn't work contact Assembla support, they usually help.

Otherwise, insist through the translations mailing list to the other Slovak translators, they should be who send the invitation.

Regards.

Iván Novegil Cancelas
Editor
ivan.novegil@...

Comunidad hispanohablante de NVDA | Proyecto NVDA.es
- www.NVDA.es
- @nvda_es

Usuario do NVDA en galego

***Note que a anterior mensaxe e/ou os seus adxuntos pode conter información privada ou confidencial. O emprego da información desta mensaxe e/ou dos seus adxuntos está reservado ao ámbito privado do destinatario agás autorización do remitente. Se recibiu esta mensaxe por erro comuníqueo por esta mesma vía e destrúa a mensaxe.***

O 20/11/2018 á(s) 17:59, Ján Kulik escribiu:

Show quoted text

hi all, I need to advise you on Friday I wanted to sign up for Assembla.com to work with NVDA add-on translation. Unfortunately, he does not want to sign up for assemblages because I was sure I entered all the details and when I entered the organizational domain http://subversion.assembla.com/svn/screenReaderTranslations, I'm writing that the domain must consist of some numbers and I do not know what. How did you register? I tried everything I could, it did not work.

THNK

New registration atscounts in assembla

Ján Kulik

#50774

hi all, I need to advise you on Friday I wanted to sign up for Assembla.com to work with NVDA add-on translation. Unfortunately, he does not want to sign up for assemblages because I was sure I entered all the details and when I entered the organizational domain http://subversion.assembla.com/svn/screenReaderTranslations, I'm writing that the domain must consist of some numbers and I do not know what. How did you register? I tried everything I could, it did not work.

THNK

Re: Excel reads numeric cells in column E as exponents rather than cell value

Matthew Horspool

#50773

Hi Quentin,

Doing something with how the string is formatted would do wonders for me! I'm a long time JAWS user and technically minded, but I still cannot come to terms with how NVDA "gabbles" out all of its information in one go. Perhaps I've got too used to my creature comforts, but having differentiation between things like this is such a big deal for me that I simply cannot switch to NVDA full-time. If it was improved I would consider a switch much more viable.

Inserting a comma between the cell data and its coordinates would be a good step in the right direction. Could the same be done, please, for table cell coordinates generally, table header information, access keys in menus, the name of a menu and the first control in that menu, etc?

It is only a quick fix though. Longer term, you could do worse than to implement something akin to the JAWS model, e.g. by introducing a message voice which could read coordinates, access keys and suchlike. If this is set differently, a pause will occur naturally as the voice changes. If it's set the same, pauses could be eliminated for those who like the way NVDA does things currently.

Even longer term, something like the Speech and Sounds Manager would be simply fantastic! I have perfect pitch and so, in JAWS, I currently have heading level 1 play a note C, heading level 2 play a D, level 3 an E and so on. Switching to NVDA which must report to heading and its level in speech, because what else is it supposed to do other than not report it at all, feels very sluggish. I also have sounds for buttons, radio buttons, combo and list boxes, tree views and so on and some of this can be replicated in an add-on, but not as neatly. I heard somewhere about something nicknamed "Speech Refactor" which might make some of this stuff possible? Where are we with that?

Thanks,

Matthew

Show quoted text

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: 19 November 2018 23:14
To: nvda@nvda.groups.io
Subject: Re: [nvda] Excel reads numeric cells in column E as exponents rather than cell value

Rick,

Well spotted, and interesting pickup. This is exactly why NVDA itself doesn't try to interpret information, but simply present it as it is displayed. Many synthesizers do try to interpret data, which is where you end up with St being read as "street" when it is actually used in the context of "saint" or dr for Doctor instead of drive.

In this case, it is processing the whole string (value and cell coordinates) as one piece of information: 1.24E4 is read as the scientific formatted number "1.24 times 10 to the power of 4". If the value was in the cell above it is read as "1.24 times 10 cubed" or in E2 as "1.24 times 10 squared". It is interesting to note that this affects the OneCore voices, and even then only some of them. On my system, I have ten OneCore voices. Of those:

- David, Zira and Mark interpret the coordinates as you encountered

- George, Catherine, Hazel, Susan, Linda, Richard or James, simply read it as it should be read: 1.24 E4

I just checked and of the David, Hazel and Zira Microsoft Speech API version 5 voices I have, David reads it as a scientific number, but Hazel and Zira both read 1.24 E4.

I will raise this with Microsoft and look to see if we can do anything with how we format the string, maybe we can put a comma in-between the pieces of information.

On Mon, Nov 19, 2018 at 9:47 PM Rick <softwarethatworks@...> wrote:

Hello NVDA List:

The other day I was reading an Excel spreadsheet sent to me by a colleague. It had numeric values in column E. When reading these cells with Microsoft One Core voices (I am using Microsoft David) the cell name was read as an exponent to the power of 10. For instance, if the value 1.24 was present in cell E4, the speech produced, “1.24 time 10 to the power of 4” rather than 1.24 E4. This does not happen when using Espeak voices or SAPI 5 voices. Note, if the number in the cell is the result of a formula and not a direct value, the phrase, “has formula” is inserted between the number and the cell name, so it works as expected (i.e. 1.24 has formula E4).

Note: This does not happen using Narrator, since Narrator reads the cell name first.

I am running the latest released copy of NVDA, Office 365 desktop apps and Windows 10 Professional.

Rick

--

Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

Re: problem with NVDA and libre office

The Gamages

#50772

Hello,

To read the alignment in Libre office Writer,

Press alt then right arrow to the format menu,

Arrow down to “ alignment” and right arrow to the sub menu.

Now up and down arrow, some will say “selected” but the one that says “checked” will be the current alignment.

Best Regards, Jim.

Show quoted text

From: Ashley Wayne
Sent: 20 November 2018 03:02
To: nvda@nvda.groups.io
Subject: Re: [nvda] problem with NVDA and libre office

Hi thank you, I did not realize that. Well, at least I wasn't missing

something obvious.

On 11/19/2018 7:16 PM, zahra wrote:

> hi.

> both openoffice and libreoffice dont support reporting alignment for

> nvda screen reader.

> i am not sure about jaws and libreoffice compatibility with jaws, but

> i am sure that you cant read alignment information when using

> libreoffice or openoffice.

>

> On 11/20/18, Ashley Wayne <a.r.wayne2008@...> wrote:

>> Hi all,

>>

>> I cannot seem to get NVDA to announce the alignment of text in libre

>> office writer, such as left or centered. I will have alignment checked

>> under the document formatting section of preferences but still nothing.

>> NVDA key plus F will read other attributes like font type or size but

>> still not alignment. When I go to other applications with text, like

>> websites for example, NVDA will then read alignment information. What

>> am I missing here? Thank you so much for any help.

>>

>> Ashley

>>

>> ---

>> This email has been checked for viruses by AVG.

>> https://www.avg.com

>>

>

audio ducking

Isaac <bigikemusic@...>

#50771

Hi, is there a way to change how fast audio ducks and how fast it resumes normal volume, I don't like the two or three second delay in ducking?

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

Joseph Lee

#50770

Hi,
What you're describing is the behavior of emoji panel in Version 1803. Can you try with all add-ons turned off (from exit dialog, select restart with add-ons disabled)?
Cheers,
Joseph

Show quoted text

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: Monday, November 19, 2018 10:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, let's see if this works. No, if I shift tab from most recent I get "search emoji", then continuing to shift tab I get the categories like "transportation", but if I use the arrows, it just does "1 of 250" and so on.

On 11/19/2018 22:47, hurrikennyandopo ... wrote:

Hi

I just noticed now when you are on the recent one if you shift/tab now 
it gives you the categories where now you right or left arrow to them 
then press the enter key on the one you want then shift tab or tab to 
get to the list of them. it seems to be speaking mine out correctly.

it seems like a slight modification to the tutorial.

Gene nz

On 20/11/2018 4:46 PM, John Isige wrote:
Just tested the beta, and it doesn't read emojis, at least for me, 
with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on.
This happens even with the one-core voices, which used to read more 
emojis than any other synthesizer. This happens whether the copy is 
installed or portable. Windows 10 64-bit, latest upates, not 1809 
though. Here's the log from when I try to get to an emoji to put into 
this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation INFO - core.main 
(21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018,
16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main 
(21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1 INFO - 
synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - 
brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10> Python 
class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 
'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 
'NVDAObjects.NVDAObject'>, <class 
'documentBase.TextContainerObject'>, <class 
'baseObject.ScriptableObject'>, <class 
'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule: 
<'windowsinternal_composableshell_experiences_textinput_inputapp' 
(appName
u'windowsinternal_composableshell_experiences_textinput_inputapp',
process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0> 
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent 
link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)] UIA 
className: GridViewItem UIA patterns available: 
LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, 
ScrollItemPattern, SelectionItemPattern

--
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related 
material at http://www.accessibilitycentral.net Regardless of where 
you are in New Zealand if you are near one of the APNK sites you can 
use a copy of the NVDA screen reader on one of their computers. To 
find out which locations (or location) is near to you please visit 
http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA certified expert 
near you, please visit the following link 
https://certification.nvaccess.org/. The certification page contains 
the official list of NVDA certified individuals from around the world, 
who have sat and successfully passed the NVDA expert exam.

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

John Isige

#50769

OK, let's see if this works. No, if I shift tab from most recent I get "search emoji", then continuing to shift tab I get the categories like "transportation", but if I use the arrows, it just does "1 of 250" and so on.

Show quoted text

On 11/19/2018 22:47, hurrikennyandopo ... wrote:

Hi


I just noticed now when you are on the recent one if you shift/tab now it gives you the categories where now you right or left arrow to them then press the enter key on the one you want then shift tab or tab to get to the list of them. it seems to be speaking mine out correctly.


it seems like a slight modification to the tutorial.


Gene nz


On 20/11/2018 4:46 PM, John Isige wrote:
Just tested the beta, and it doesn't read emojis, at least for me, with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on. This happens even with the one-core voices, which used to read more emojis than any other synthesizer. This happens whether the copy is installed or portable. Windows 10 64-bit, latest upates, not 1809 though. Here's the log from when I try to get to an emoji to put into this message in Thunderbird.


INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation
INFO - core.main (21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10>
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule: <'windowsinternal_composableshell_experiences_textinput_inputapp' (appName u'windowsinternal_composableshell_experiences_textinput_inputapp', process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0>
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)]
UIA className: GridViewItem
UIA patterns available: LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, ScrollItemPattern, SelectionItemPattern



-- 
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

John Isige

#50768

It was checked yes. So let's see if unchecking it helps. Nope, but how
about re-checking it? That doesn't help either. Restarting? Nope. But I
get some sort of error when restarting, but it doesn't show up in the
log. I can post that, if you can tell me where to find it. Also, when I
restarted while in Thunderbird, but not when minimized to the desktop, I
got this error:


ERROR - eventHandler.executeEvent (00:04:32.400):
error executing event: gainFocus on
<baseObject.Dynamic_EditableTextWithAutoSelectDetectionBrokenFocusedStateDocumentEditorMozillaIAccessible
object at 0x056023F0> with extra args of {}
Traceback (most recent call last):
  File "eventHandler.pyo", line 155, in executeEvent
  File "eventHandler.pyo", line 92, in __init__
  File "eventHandler.pyo", line 100, in next
  File
"C:\Users\khomus\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py",
line 426, in event_gainFocus
  File "eventHandler.pyo", line 100, in next
  File
"C:\Users\khomus\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\__init__.py",
line 267, in event_gainFocus
  File "eventHandler.pyo", line 100, in next
  File "appModules\thunderbird.pyo", line 28, in event_gainFocus
  File "eventHandler.pyo", line 100, in next
  File "NVDAObjects\behaviors.pyo", line 169, in event_gainFocus
  File "NVDAObjects\__init__.pyo", line 961, in event_gainFocus
  File "NVDAObjects\__init__.pyo", line 849, in reportFocus
  File "speech.pyo", line 416, in speakObject
  File "documentBase.pyo", line 24, in makeTextInfo
  File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 87, in __init__
  File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 204, in
_findContentDescendant
LookupError: Object has no text descendants

Show quoted text

On 11/19/2018 21:58, Joseph Lee wrote:
Hi,
Press Control+NVDA+V and see if the new "Include Unicode Consortium data (including emoji) when processing characters and symbols" checkbox is checked.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: Monday, November 19, 2018 7:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

Just tested the beta, and it doesn't read emojis, at least for me, with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on. This happens even with the one-core voices, which used to read more emojis than any other synthesizer. This happens whether the copy is installed or portable. Windows 10 64-bit, latest upates, not 1809 though. Here's the log from when I try to get to an emoji to put into this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation INFO - core.main (21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main (21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10> Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>,
<class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule:
<'windowsinternal_composableshell_experiences_textinput_inputapp'
(appName
u'windowsinternal_composableshell_experiences_textinput_inputapp',
process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0> UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)] UIA className: GridViewItem UIA patterns available: LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, ScrollItemPattern, SelectionItemPattern

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

hurrikennyandopo ...

#50767

Hi

Will mention it. Yep that is the version i am running of Windows 1809.

Gene nz

Show quoted text

On 20/11/2018 5:49 PM, Joseph Lee wrote:

Hi,

Be sure to mention that this change is for Version 1809 and later, as Version 1803 still uses older tab method for switching between categories.

Cheers,

Joseph

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Monday, November 19, 2018 8:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

Hi

I just noticed now when you are on the recent one if you shift/tab now it gives you the categories where now you right or left arrow to them then press the enter key on the one you want then shift tab or tab to get to the list of them. it seems to be speaking mine out correctly.

it seems like a slight modification to the tutorial.

Gene nz

On 20/11/2018 4:46 PM, John Isige wrote:

Just tested the beta, and it doesn't read emojis, at least for me, with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on. This happens even with the one-core voices, which used to read more emojis than any other synthesizer. This happens whether the copy is installed or portable. Windows 10 64-bit, latest upates, not 1809 though. Here's the log from when I try to get to an emoji to put into this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation
INFO - core.main (21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10>
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule: <'windowsinternal_composableshell_experiences_textinput_inputapp' (appName u'windowsinternal_composableshell_experiences_textinput_inputapp', process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0>
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)]
UIA className: GridViewItem
UIA patterns available: LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, ScrollItemPattern, SelectionItemPattern

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

Joseph Lee

#50766

Hi,

Be sure to mention that this change is for Version 1809 and later, as Version 1803 still uses older tab method for switching between categories.

Cheers,

Joseph

Show quoted text

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Monday, November 19, 2018 8:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

Hi

I just noticed now when you are on the recent one if you shift/tab now it gives you the categories where now you right or left arrow to them then press the enter key on the one you want then shift tab or tab to get to the list of them. it seems to be speaking mine out correctly.

it seems like a slight modification to the tutorial.

Gene nz

On 20/11/2018 4:46 PM, John Isige wrote:

Just tested the beta, and it doesn't read emojis, at least for me, with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on. This happens even with the one-core voices, which used to read more emojis than any other synthesizer. This happens whether the copy is installed or portable. Windows 10 64-bit, latest upates, not 1809 though. Here's the log from when I try to get to an emoji to put into this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation
INFO - core.main (21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10>
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule: <'windowsinternal_composableshell_experiences_textinput_inputapp' (appName u'windowsinternal_composableshell_experiences_textinput_inputapp', process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0>
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)]
UIA className: GridViewItem
UIA patterns available: LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, ScrollItemPattern, SelectionItemPattern

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

hurrikennyandopo ...

#50765

Hi

I just noticed now when you are on the recent one if you shift/tab now it gives you the categories where now you right or left arrow to them then press the enter key on the one you want then shift tab or tab to get to the list of them. it seems to be speaking mine out correctly.

it seems like a slight modification to the tutorial.

Gene nz

Show quoted text

On 20/11/2018 4:46 PM, John Isige wrote:

Just tested the beta, and it doesn't read emojis, at least for me, with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on. This happens even with the one-core voices, which used to read more emojis than any other synthesizer. This happens whether the copy is installed or portable. Windows 10 64-bit, latest upates, not 1809 though. Here's the log from when I try to get to an emoji to put into this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation
INFO - core.main (21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10>
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule: <'windowsinternal_composableshell_experiences_textinput_inputapp' (appName u'windowsinternal_composableshell_experiences_textinput_inputapp', process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0>
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)]
UIA className: GridViewItem
UIA patterns available: LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, ScrollItemPattern, SelectionItemPattern

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

Ccleaner for half off

Travis Siegel <tsiegel@...>

#50764

For those who are interested, there is a special running at the moment, you can purchase Ccleaner for 50 percent off if you purchase from an affiliate link.  I just happen to have one of those on softcon.com, so if you're on the fence, or thought it was too expensive, then drop by softcon.com, and click on the ccleaner link, and obtain either the pro or the pro plus for half it's original price.  Of course, if you're not interested, then just ignore this message, that works too.

Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

Joseph Lee

#50763

Hi,
Press Control+NVDA+V and see if the new "Include Unicode Consortium data (including emoji) when processing characters and symbols" checkbox is checked.
Cheers,
Joseph

Show quoted text

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: Monday, November 19, 2018 7:46 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

Just tested the beta, and it doesn't read emojis, at least for me, with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on. This happens even with the one-core voices, which used to read more emojis than any other synthesizer. This happens whether the copy is installed or portable. Windows 10 64-bit, latest upates, not 1809 though. Here's the log from when I try to get to an emoji to put into this message in Thunderbird.

INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation INFO - core.main (21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main (21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10> Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>,
<class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule: 
<'windowsinternal_composableshell_experiences_textinput_inputapp' 
(appName
u'windowsinternal_composableshell_experiences_textinput_inputapp',
process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0> UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)] UIA className: GridViewItem UIA patterns available: LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, ScrollItemPattern, SelectionItemPattern

NVDA 2018.4-Beta 1 doesn't read emojis for me.

John Isige

#50762

Just tested the beta, and it doesn't read emojis, at least for me, with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on. This happens even with the one-core voices, which used to read more emojis than any other synthesizer. This happens whether the copy is installed or portable. Windows 10 64-bit, latest upates, not 1809 though. Here's the log from when I try to get to an emoji to put into this message in Thunderbird.


INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation
INFO - core.main (21:37:01.523):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10>
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule: <'windowsinternal_composableshell_experiences_textinput_inputapp' (appName u'windowsinternal_composableshell_experiences_textinput_inputapp', process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0>
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)]
UIA className: GridViewItem
UIA patterns available: LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern, ScrollItemPattern, SelectionItemPattern