Date   

Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

Don H
 

So I have to ask the question why change to the new python if it has the potential of messing things up?

On 8/26/2018 1:14 PM, Joseph Lee wrote:
Hi,
When I call espeak_Initialize when initializing Espeak from NVDA, I get an exception and Espeak can’t find phonetics table from a specific location. I will need to investigate this further, as being able to get at least one synthesizer running in Python 3 mode is a crucial milestone I hope to achieve soon.
Cheers,
Joseph
*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Reece H. Dunn
*Sent:* Sunday, August 26, 2018 10:26 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3
On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:
Hi all,
For the last few hours, there has been a thread regarding
incompatibility of some add-ons and NVDA 2018.3, with some folks
claiming that speech synthesizers are not compatible. This
information is mostly false, and this may have been driven by
confusion regarding wxPython 4 versus Python 3.
wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version
4.0.3, a necessary milestone for the eventual migration to Python 3.
If an add-on uses attributes that are not found in newer wxPython
releases, they won’t load. Likewise, an add-on that exclusively uses
wxPython 4 material won’t work in older NVDA releases. At least some
GUI elements of speech synthesizer drivers are affected, and that’s
the reason why there has been an uproar regarding an important
add-on. Regarding speech synthesizer drivers and GUI issues, they
produce minor warnings, but apart from that, they are usable (but
not forever).
Python 3: Python is a programming language. Therefore, moving from
one version of a programming language to the next can be
challenging, especially if it introduces incompatible syntax and
throws away old internal assumptions. Python 2 to 3 migration will
go through both issues and much more, and research suggests that
many NVDA features and add-ons will be affected, including some
synthesizers the community uses (sorry, Espeak, you’re included in
this mix). Specifically, due to prevalence of Unicode, it’ll take
some time to come up with routines that will work with text
formatted as Unicode and other encodings, and unfortunately, some
speech synthesizers will insist on using ANSI format strings when in
fact Python 3 wants to read and write Unicode (Espeak is a notable
case).
What is the issue/are the issues regarding espeak (I have experience converting Python 2 to 3 code)?
Are you referring to espeak wanting UTF-8 (which is like/compatible with ANSI/ASCII strings), or issues with the way the NVDA espeak binding is written?
NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings. Espeak supports UTF-8 and UTF-16, but not UTF-32.
Kind regards,
Reece
In regards to add-ons, any add-on that deals with text processing
are affected (speech synthesizers, for example). Also, if they use
Python standard library (various Python modules), they need to take
note of differences between Python 2 and 3, especially in regards to
module and function renames (_winreg versus winreg, the former with
an underscore and the latter without).
A more general overview of what will it take to move NVDA to Python
3 can be found at:
https://github.com/nvaccess/nvda/issues/7105
Cheers,
Joseph


Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,

When I call espeak_Initialize when initializing Espeak from NVDA, I get an exception and Espeak can’t find phonetics table from a specific location. I will need to investigate this further, as being able to get at least one synthesizer running in Python 3 mode is a crucial milestone I hope to achieve soon.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Reece H. Dunn
Sent: Sunday, August 26, 2018 10:26 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:

Hi all,

 

For the last few hours, there has been a thread regarding incompatibility of some add-ons and NVDA 2018.3, with some folks claiming that speech synthesizers are not compatible. This information is mostly false, and this may have been driven by confusion regarding wxPython 4 versus Python 3.

 

wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version 4.0.3, a necessary milestone for the eventual migration to Python 3. If an add-on uses attributes that are not found in newer wxPython releases, they won’t load. Likewise, an add-on that exclusively uses wxPython 4 material won’t work in older NVDA releases. At least some GUI elements of speech synthesizer drivers are affected, and that’s the reason why there has been an uproar regarding an important add-on. Regarding speech synthesizer drivers and GUI issues, they produce minor warnings, but apart from that, they are usable (but not forever).

 

Python 3: Python is a programming language. Therefore, moving from one version of a programming language to the next can be challenging, especially if it introduces incompatible syntax and throws away old internal assumptions. Python 2 to 3 migration will go through both issues and much more, and research suggests that many NVDA features and add-ons will be affected, including some synthesizers the community uses (sorry, Espeak, you’re included in this mix). Specifically, due to prevalence of Unicode, it’ll take some time to come up with routines that will work with text formatted as Unicode and other encodings, and unfortunately, some speech synthesizers will insist on using ANSI format strings when in fact Python 3 wants to read and write Unicode (Espeak is a notable case).

What is the issue/are the issues regarding espeak (I have experience converting Python 2 to 3 code)?

Are you referring to espeak wanting UTF-8 (which is like/compatible with ANSI/ASCII strings), or issues with the way the NVDA espeak binding is written?

NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings. Espeak supports UTF-8 and UTF-16, but not UTF-32.

Kind regards,
Reece

In regards to add-ons, any add-on that deals with text processing are affected (speech synthesizers, for example). Also, if they use Python standard library (various Python modules), they need to take note of differences between Python 2 and 3, especially in regards to module and function renames (_winreg versus winreg, the former with an underscore and the latter without).

 

A more general overview of what will it take to move NVDA to Python 3 can be found at:

https://github.com/nvaccess/nvda/issues/7105

 

Cheers,

Joseph


Re: Free Synthesizers

Jackie
 

Then Brian V's response was right on the money, wherever the money went lol.

On 8/26/18, kelby carlson <kelbycarlson@gmail.com> wrote:
Windows 10 unfortunately.
On Aug 26, 2018, at 1:09 PM, Jackie <abletec@gmail.com> wrote:

What version of Windows do you run, Kelby?

On 8/26/18, Brian Vogel <britechguy@gmail.com> wrote:
MS SAPI 5 and One Core.

--

Brian *-* Windows 10 Home, 64-Bit, Version 1803, Build 17134

The psychology of adultery has been falsified by conventional
morals,
which assume, in monogamous countries, that attraction to one person
cannot
co-exist with a serious affection for another. Everybody knows that this
is
untrue. . .

~ Bertrand Russell




--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com




--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com


Re: Free Synthesizers

kelby carlson
 

Windows 10 unfortunately.

On Aug 26, 2018, at 1:09 PM, Jackie <abletec@gmail.com> wrote:

What version of Windows do you run, Kelby?

On 8/26/18, Brian Vogel <britechguy@gmail.com> wrote:
MS SAPI 5 and One Core.

--

Brian *-* Windows 10 Home, 64-Bit, Version 1803, Build 17134

The psychology of adultery has been falsified by conventional morals,
which assume, in monogamous countries, that attraction to one person cannot
co-exist with a serious affection for another. Everybody knows that this is
untrue. . .

~ Bertrand Russell




--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com



Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

Reece H. Dunn
 

On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:

Hi all,

 

For the last few hours, there has been a thread regarding incompatibility of some add-ons and NVDA 2018.3, with some folks claiming that speech synthesizers are not compatible. This information is mostly false, and this may have been driven by confusion regarding wxPython 4 versus Python 3.

 

wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version 4.0.3, a necessary milestone for the eventual migration to Python 3. If an add-on uses attributes that are not found in newer wxPython releases, they won’t load. Likewise, an add-on that exclusively uses wxPython 4 material won’t work in older NVDA releases. At least some GUI elements of speech synthesizer drivers are affected, and that’s the reason why there has been an uproar regarding an important add-on. Regarding speech synthesizer drivers and GUI issues, they produce minor warnings, but apart from that, they are usable (but not forever).

 

Python 3: Python is a programming language. Therefore, moving from one version of a programming language to the next can be challenging, especially if it introduces incompatible syntax and throws away old internal assumptions. Python 2 to 3 migration will go through both issues and much more, and research suggests that many NVDA features and add-ons will be affected, including some synthesizers the community uses (sorry, Espeak, you’re included in this mix). Specifically, due to prevalence of Unicode, it’ll take some time to come up with routines that will work with text formatted as Unicode and other encodings, and unfortunately, some speech synthesizers will insist on using ANSI format strings when in fact Python 3 wants to read and write Unicode (Espeak is a notable case).

What is the issue/are the issues regarding espeak (I have experience converting Python 2 to 3 code)?

Are you referring to espeak wanting UTF-8 (which is like/compatible with ANSI/ASCII strings), or issues with the way the NVDA espeak binding is written?

NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings. Espeak supports UTF-8 and UTF-16, but not UTF-32.

Kind regards,
Reece

In regards to add-ons, any add-on that deals with text processing are affected (speech synthesizers, for example). Also, if they use Python standard library (various Python modules), they need to take note of differences between Python 2 and 3, especially in regards to module and function renames (_winreg versus winreg, the former with an underscore and the latter without).

 

A more general overview of what will it take to move NVDA to Python 3 can be found at:

https://github.com/nvaccess/nvda/issues/7105

 

Cheers,

Joseph


Re: Favourite add-ons

Ralf Kefferpuetz
 

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gerardo Corripio
Sent: Sonntag, 26. August 2018 17:47
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

And the one called Total Commander enhanced


El 26/08/2018 a las 10:44 a.m., Rosemarie Chavarria escribió:
Hi, Ralph,

How does this add-on work and what does it do?

Rosemarie



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ralf Kefferpuetz
Sent: Tuesday, August 21, 2018 11:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Hi Gary,

It is one of my developed addons.
You can get it here:
https://github.com/Novalis7747/Outlook-enhanced/raw/master/outlook-0.9.nvda-addon

cheers,
Ralf
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Bowers
Sent: Dienstag, 21. August 2018 18:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Ralph - Thanks for your list. Where can I see Outlook enhanced?

Gary

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ralf Kefferpuetz
Sent: Tuesday, August 21, 2018 9:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Hello,



My top 12 addOns are:

Application Dictionary

Golden cursor

IdentNav

Input lock

Instant translate

Notepad++

Outlook enhanced

Remote support

SentenceNav

Sonos for Sonos desktop

Speech history

Total Commander enhanced



Best regards,

Ralf



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sociohack AC
Sent: Dienstag, 21. August 2018 15:37
To: nvda@nvda.groups.io
Subject: [nvda] Favourite add-ons



What are the most useful add-ons for you people?
--
Regards,
Sociohack












--
Gera
Enviado desde Thunderbird what does it do, or for what program is it used for on the computer?


Re: Free Synthesizers

Jackie
 

What version of Windows do you run, Kelby?

On 8/26/18, Brian Vogel <britechguy@gmail.com> wrote:
MS SAPI 5 and One Core.

--

Brian *-* Windows 10 Home, 64-Bit, Version 1803, Build 17134

    The psychology of adultery has been falsified by conventional morals,
which assume, in monogamous countries, that attraction to one person cannot
co-exist with a serious affection for another.  Everybody knows that this is
untrue. . .

           ~ Bertrand Russell



--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Sarah k Alawami
 

I have to agree. I’ve seen this behavior with one of the devs wiht a lot of his programs, the qube anybody, and the thing he did for pandora for windows? Yeah. So frankly I’m not surprised


I do agree this should be a part of nvda’s core and if we don’t use it, we don’t have to. And eah this dev has broken other things with gpl with his apps as well, so again, not surprised. Good apps but horable bedside manners?

Take care

On 26 Aug 2018, at 4:48, Noah Carver via Groups.Io wrote:

This is not the official server. Someone studied the connection between remote and the official server and developed an unofficial server so that others could host NVDA remote.  I’ve written to the creators of this addon via email regarding the violations of GPL, however it appears that the creators of this addon don’t care. Therefore, I feel it would be in the interest of both NVAccess and the community at large for NVAccess to take possession of all code associated with the remote addon and incorporate it into NVDA core.

On Aug 26, 2018, at 05:45, dingpengyu <dingpengyu06@...> wrote:


Re: Free Synthesizers

 

MS SAPI 5 and One Core.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    The psychology of adultery has been falsified by conventional morals, which assume, in monogamous countries, that attraction to one person cannot co-exist with a serious affection for another.  Everybody knows that this is untrue. . .

           ~ Bertrand Russell

 

 


Free Synthesizers

kelby carlson
 

What are some free synthesizers available for NVDA besides Espeak? I know that things should be fine for awhile, but I want some alternatives and can't really afford to pay for anything at the moment unfortunately.


Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,

Clarification: NVDA 2018.3 will continue to be powered by Python 2.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Sunday, August 26, 2018 9:07 AM
To: nvda@groups.io
Subject: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi all,

 

For the last few hours, there has been a thread regarding incompatibility of some add-ons and NVDA 2018.3, with some folks claiming that speech synthesizers are not compatible. This information is mostly false, and this may have been driven by confusion regarding wxPython 4 versus Python 3.

 

wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version 4.0.3, a necessary milestone for the eventual migration to Python 3. If an add-on uses attributes that are not found in newer wxPython releases, they won’t load. Likewise, an add-on that exclusively uses wxPython 4 material won’t work in older NVDA releases. At least some GUI elements of speech synthesizer drivers are affected, and that’s the reason why there has been an uproar regarding an important add-on. Regarding speech synthesizer drivers and GUI issues, they produce minor warnings, but apart from that, they are usable (but not forever).

 

Python 3: Python is a programming language. Therefore, moving from one version of a programming language to the next can be challenging, especially if it introduces incompatible syntax and throws away old internal assumptions. Python 2 to 3 migration will go through both issues and much more, and research suggests that many NVDA features and add-ons will be affected, including some synthesizers the community uses (sorry, Espeak, you’re included in this mix). Specifically, due to prevalence of Unicode, it’ll take some time to come up with routines that will work with text formatted as Unicode and other encodings, and unfortunately, some speech synthesizers will insist on using ANSI format strings when in fact Python 3 wants to read and write Unicode (Espeak is a notable case).

 

In regards to add-ons, any add-on that deals with text processing are affected (speech synthesizers, for example). Also, if they use Python standard library (various Python modules), they need to take note of differences between Python 2 and 3, especially in regards to module and function renames (_winreg versus winreg, the former with an underscore and the latter without).

 

A more general overview of what will it take to move NVDA to Python 3 can be found at:

https://github.com/nvaccess/nvda/issues/7105

 

Cheers,

Joseph


NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi all,

 

For the last few hours, there has been a thread regarding incompatibility of some add-ons and NVDA 2018.3, with some folks claiming that speech synthesizers are not compatible. This information is mostly false, and this may have been driven by confusion regarding wxPython 4 versus Python 3.

 

wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version 4.0.3, a necessary milestone for the eventual migration to Python 3. If an add-on uses attributes that are not found in newer wxPython releases, they won’t load. Likewise, an add-on that exclusively uses wxPython 4 material won’t work in older NVDA releases. At least some GUI elements of speech synthesizer drivers are affected, and that’s the reason why there has been an uproar regarding an important add-on. Regarding speech synthesizer drivers and GUI issues, they produce minor warnings, but apart from that, they are usable (but not forever).

 

Python 3: Python is a programming language. Therefore, moving from one version of a programming language to the next can be challenging, especially if it introduces incompatible syntax and throws away old internal assumptions. Python 2 to 3 migration will go through both issues and much more, and research suggests that many NVDA features and add-ons will be affected, including some synthesizers the community uses (sorry, Espeak, you’re included in this mix). Specifically, due to prevalence of Unicode, it’ll take some time to come up with routines that will work with text formatted as Unicode and other encodings, and unfortunately, some speech synthesizers will insist on using ANSI format strings when in fact Python 3 wants to read and write Unicode (Espeak is a notable case).

 

In regards to add-ons, any add-on that deals with text processing are affected (speech synthesizers, for example). Also, if they use Python standard library (various Python modules), they need to take note of differences between Python 2 and 3, especially in regards to module and function renames (_winreg versus winreg, the former with an underscore and the latter without).

 

A more general overview of what will it take to move NVDA to Python 3 can be found at:

https://github.com/nvaccess/nvda/issues/7105

 

Cheers,

Joseph


Re: Favourite add-ons

Gerardo Corripio
 

And the one called Total Commander enhanced

El 26/08/2018 a las 10:44 a.m., Rosemarie Chavarria escribió:
Hi, Ralph,

How does this add-on work and what does it do?

Rosemarie



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ralf Kefferpuetz
Sent: Tuesday, August 21, 2018 11:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Hi Gary,

It is one of my developed addons.
You can get it here:
https://github.com/Novalis7747/Outlook-enhanced/raw/master/outlook-0.9.nvda-addon

cheers,
Ralf
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Bowers
Sent: Dienstag, 21. August 2018 18:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Ralph - Thanks for your list. Where can I see Outlook enhanced?

Gary

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ralf Kefferpuetz
Sent: Tuesday, August 21, 2018 9:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Hello,


My top 12 addOns are:

Application Dictionary

Golden cursor

IdentNav

Input lock

Instant translate

Notepad++

Outlook enhanced

Remote support

SentenceNav

Sonos for Sonos desktop

Speech history

Total Commander enhanced


Best regards,

Ralf


From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sociohack AC
Sent: Dienstag, 21. August 2018 15:37
To: nvda@nvda.groups.io
Subject: [nvda] Favourite add-ons


What are the most useful add-ons for you people?
--
Regards,
Sociohack











--
Gera
Enviado desde Thunderbird what does it do, or for what program is it used for on the computer?


Re: Favourite add-ons

Rosemarie Chavarria
 

Hi, Ralph,

How does this add-on work and what does it do?

Rosemarie

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ralf Kefferpuetz
Sent: Tuesday, August 21, 2018 11:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Hi Gary,

It is one of my developed addons.
You can get it here:
https://github.com/Novalis7747/Outlook-enhanced/raw/master/outlook-0.9.nvda-addon

cheers,
Ralf
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Bowers
Sent: Dienstag, 21. August 2018 18:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Ralph - Thanks for your list. Where can I see Outlook enhanced?

Gary

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ralf Kefferpuetz
Sent: Tuesday, August 21, 2018 9:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Favourite add-ons

Hello,



My top 12 addOns are:

Application Dictionary

Golden cursor

IdentNav

Input lock

Instant translate

Notepad++

Outlook enhanced

Remote support

SentenceNav

Sonos for Sonos desktop

Speech history

Total Commander enhanced



Best regards,

Ralf



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sociohack AC
Sent: Dienstag, 21. August 2018 15:37
To: nvda@nvda.groups.io
Subject: [nvda] Favourite add-ons



What are the most useful add-ons for you people?
--
Regards,
Sociohack


Re: off topic windows live mail - desperate

 

I guess the first question is what font is she using?

The defaults under WLM tend to work "out of the box".

I am suspecting this is actually something utterly independent of WLM, as I've encountered instances of printers with a character set mind of their own on a couple of occasions over the decades.  My first test is to see if the printer behaves similarly from other programs, such as Notepad or Word.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    The psychology of adultery has been falsified by conventional morals, which assume, in monogamous countries, that attraction to one person cannot co-exist with a serious affection for another.  Everybody knows that this is untrue. . .

           ~ Bertrand Russell

 

 


Re: Future of speech synth add ons

 

Hi,
There are minor issues with Vocalizer add-on in regards to GUI, but apart from that, it works as advertised.
I'll address the "real" issue in the next post.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Abbie Taylor
Sent: Sunday, August 26, 2018 7:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Future of speech synth add ons

I also use Vocalizer from Code Factory, so it looks like I, too, will have to find another synthesizer when the new NVDA update comes out. How can I get more One-Core voices? The only options I see in the preferences are David, Zera, and Mark.

Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com http://www.abbiejohnsontaylor.com abbietaylor945@gmail.com Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm

--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@gmail.com


Re: Screen Reader under DOS

JM Casey <crystallogic@...>
 

There's a version of DosBox that some people made, called Talking Dos Box. It comes with a few screen-readers and one of them is jAWS for Dos. I haven't tried it at all, though.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arno Schuh
Sent: August 26, 2018 5:12 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Screen Reader under DOS

Hi,

the only screenreaders I surely know that run under DOS used external devices to speak.
I never run Jaws for DOS, but probably JfD was able to use a build-in soundcard to speech. In the past Jaws for DOS was available for free from the download area (of HJ, not sure if it still was available from FS and todays distributer).
If you try to setup such an old screenreader on a modern computer I suppose the biggest problem would be the soundcard. As said before, I never used Jaws for DOS, and so I don't know if Jaws requires a specific type of soundcards.
I remember that some screenreaders for DOS I tested in DOS times needs i. e.
soundcards from creative Labs like SoundBlaster Pro (the TalkingBlaster screenreader comes to mind).
Soundcards from other manifactures at last have to run in a legacy mode that comes close to the SB specifications.

Greetings

Arno

Am Sonntag, 26. August 2018 02:06 schrieb Howard Traxler
<howard@traxlerenterprises.com>:

I'm going to build a DOS machine and will, of course, need it to talk
and possibly display in Braille. I'm wondering if NVDA will run under
DOS? I think I'll probably use DOS version 6.22. If not, I do have
others here that will run.

Thanks.
Howard


Re: Future of speech synth add ons

 

On Sun, Aug 26, 2018 at 10:07 PM, Antony Stone wrote:
Thank you very much both for the testing and the comprehensive report.

I especially appreciate that you quote the specific version numbers of all
relevant software.

Regards,


Antony.

On Sunday 26 August 2018 at 16:48:59, Supanut Leepaisomboon wrote:

Update: I finally managed to get Windows 10 up and running in my virtual
machine, with NVDA 2018.3 beta 3. I tried to install both Tifflotecnia and
Codefactory synth drivers, and it seems that they continue to function
normally. I am able to activate the Codefactory demo and have eloquence
working. So...the conclusion that I can draw from my brief tests is that,
both the Tifflotecnia and Codefactory drivers should continue to work with
NVDA 2018.3, but looking into the future when NVDA switches to Python 3 I
can't confirm that they will continue to work. Note the versions I used
for testing are: 3.0.13 for Tifflotecnia driver, and 1.0 for Codefactory
driver (both are the latest versions available).
--
Anything that improbable is effectively impossible.

- Murray Gell-Mann, Nobel Prizewinner in Physics

Please reply to the list;
please *don't* CC me.

You're welcome. If someone could test whether they are able to activate their Codefactory licenses with NVDA 2018.3 beta 3 installed that would be great, as I do not have a license for Codefactory so can't test the activation part myself.


Re: Future of speech synth add ons

 

so it  looks like I, too, will have to find  another synthesizer when the new NVDA update comes out
Well you do not exactly have to go look for new synths, until the switch to Python 3 is fully completed. As I mentioned in my last post, Codefactory continues to work under NVDA 2018.3 beta 3.
How can I
get more One-Core voices? The only options I see in the preferences are David, Zera, and Mark.
You can do that in the settings app, just add a language (make sure that you check the tts box when adding a language) and new voices should be added (although I do not know how to add additional voices for, say, American English).


Re: Future of speech synth add ons

Antony Stone
 

Thank you very much both for the testing and the comprehensive report.

I especially appreciate that you quote the specific version numbers of all
relevant software.

Regards,


Antony.

On Sunday 26 August 2018 at 16:48:59, Supanut Leepaisomboon wrote:

Update: I finally managed to get Windows 10 up and running in my virtual
machine, with NVDA 2018.3 beta 3. I tried to install both Tifflotecnia and
Codefactory synth drivers, and it seems that they continue to function
normally. I am able to activate the Codefactory demo and have eloquence
working. So...the conclusion that I can draw from my brief tests is that,
both the Tifflotecnia and Codefactory drivers should continue to work with
NVDA 2018.3, but looking into the future when NVDA switches to Python 3 I
can't confirm that they will continue to work. Note the versions I used
for testing are: 3.0.13 for Tifflotecnia driver, and 1.0 for Codefactory
driver (both are the latest versions available).
--
Anything that improbable is effectively impossible.

- Murray Gell-Mann, Nobel Prizewinner in Physics

Please reply to the list;
please *don't* CC me.