Date   

locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Gene
 

I forgot to ask as first steps if you closed and opened both Firefox and NVDA and then if you rebooted.  those would be good to do before trying anything else.
 
Gene

-----Original Message-----
From: Gene
Sent: Tuesday, June 01, 2021 3:35 PM
Subject: Re: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
I’m using Windows 7 and NVDA beta 2021.1beta1.  I updated and I can browse properly.  When I restarted Firefox, I got this message:
Say hello to a new Firefox
Designed to get you where you want to go, faster
Streamlined toolbar and menus
Prioritize the important things so you find what you need.
Modern tabs
Neatly contain information, supporting focus and flexible movement.
Fresh icons and clearer messages
Help you find your way with a lighter touch.
 
It appears to me that sometimes when I press alt, menus don’t open properly.  but if I fool around, press escape, perhaps tab then press alt again, the menus come up properly.  I haven’t played with this enough to know if it is a problem or a quirk I experienced and if it is a problem, if I have to fool around more than one time to make the menus come up properly.
 
You may want to try firefox Portable and see what happens. 
 
Gene
-----Original Message-----
From: Jackie
Sent: Tuesday, June 01, 2021 2:59 PM
Subject: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Gene
 

I’m using Windows 7 and NVDA beta 2021.1beta1.  I updated and I can browse properly.  When I restarted Firefox, I got this message:
Say hello to a new Firefox
Designed to get you where you want to go, faster
Streamlined toolbar and menus
Prioritize the important things so you find what you need.
Modern tabs
Neatly contain information, supporting focus and flexible movement.
Fresh icons and clearer messages
Help you find your way with a lighter touch.
 
It appears to me that sometimes when I press alt, menus don’t open properly.  but if I fool around, press escape, perhaps tab then press alt again, the menus come up properly.  I haven’t played with this enough to know if it is a problem or a quirk I experienced and if it is a problem, if I have to fool around more than one time to make the menus come up properly.
 
You may want to try firefox Portable and see what happens. 
 
Gene

-----Original Message-----
From: Jackie
Sent: Tuesday, June 01, 2021 2:59 PM
Subject: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

 

This uses the proton system, you should be able to turn it off by going to about:config and disabling all refferences to proton but thats going to change.



On 2/06/2021 8:24 am, Jackie wrote:
Uh, no, it's the latest, supposedly stable, update to firefox. I was notified this morning.


Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com


On Tue, Jun 1, 2021 at 1:21 PM Gene <gsasner@...> wrote:
Isn’t that a beta or alpha version?  What happens if you downgrade, I’m not sure if you can run an earlier installer over the current installation or if you have to uninstall the current version first?  Or, you could test by running Firefox Portable and seeing if it works properly. 
 
I advise that Firefox Portable be used for various reasons I’ll explain in another message if people want to know. 
 
If you want to use alpha or beta versions, I advise having Firefox Portable on the machine as a backup.
Gene
-----Original Message-----
From: Jackie
Sent: Tuesday, June 01, 2021 2:59 PM
Subject: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Chris Smart
 

I don't know if it matters at all, but how did you answer the couple of set up questions?


It asked me something about picking a theme to use, and I chose to keep it the same as my current Windows 10 theme.



On 2021-06-01 4:24 p.m., Jackie wrote:
Uh, no, it's the latest, supposedly stable, update to firefox. I was notified this morning.


Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com


On Tue, Jun 1, 2021 at 1:21 PM Gene <gsasner@...> wrote:
Isn’t that a beta or alpha version?  What happens if you downgrade, I’m not sure if you can run an earlier installer over the current installation or if you have to uninstall the current version first?  Or, you could test by running Firefox Portable and seeing if it works properly. 
 
I advise that Firefox Portable be used for various reasons I’ll explain in another message if people want to know. 
 
If you want to use alpha or beta versions, I advise having Firefox Portable on the machine as a backup.
Gene
-----Original Message-----
From: Jackie
Sent: Tuesday, June 01, 2021 2:59 PM
Subject: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Jackie
 

Uh, no, it's the latest, supposedly stable, update to firefox. I was notified this morning.


Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com


On Tue, Jun 1, 2021 at 1:21 PM Gene <gsasner@...> wrote:
Isn’t that a beta or alpha version?  What happens if you downgrade, I’m not sure if you can run an earlier installer over the current installation or if you have to uninstall the current version first?  Or, you could test by running Firefox Portable and seeing if it works properly. 
 
I advise that Firefox Portable be used for various reasons I’ll explain in another message if people want to know. 
 
If you want to use alpha or beta versions, I advise having Firefox Portable on the machine as a backup.
Gene
-----Original Message-----
From: Jackie
Sent: Tuesday, June 01, 2021 2:59 PM
Subject: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Gene
 

I just checked and the version you updated to appears to be the production release version.  I use Firefox portable and I’m going to update now to see if I have any problems.
 
Gene

-----Original Message-----
From: Jackie
Sent: Tuesday, June 01, 2021 2:59 PM
Subject: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Jackie
 

I forgot to mention I even tried it w/the beta NVDA as a portable version. & yes, I did restart my computer as well.

Very :(.




Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Gene
 

Isn’t that a beta or alpha version?  What happens if you downgrade, I’m not sure if you can run an earlier installer over the current installation or if you have to uninstall the current version first?  Or, you could test by running Firefox Portable and seeing if it works properly. 
 
I advise that Firefox Portable be used for various reasons I’ll explain in another message if people want to know. 
 
If you want to use alpha or beta versions, I advise having Firefox Portable on the machine as a backup.
Gene

-----Original Message-----
From: Jackie
Sent: Tuesday, June 01, 2021 2:59 PM
Subject: [nvda] Updated Firefox to version 89, can no longer use w/NVDA
 
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


Dropbox 4.6 4.5 Update

Chris Smart
 

Something is malfunctioning with the latest NVDA beta, add-on notifications, and the Dropbox Add-on.


I keep getting a message that "Dropbox 4.6, 4.5" is available. When I say yes to Update it, I get an error saying 4.5 is out of date.

Is there a way to disable that particular add-on from being checked?


locked Re: Updated Firefox to version 89, can no longer use w/NVDA

Chris Smart
 

working fine here with both the latest Jaws and the current NVDA beta.



On 2021-06-01 3:59 p.m., Jackie wrote:
Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


locked Updated Firefox to version 89, can no longer use w/NVDA

Jackie
 

Subject says it all, really. Everything just says "unknown" when trying to use Firefox version 89 using Windows 10. Microsoft Windows
Version 20H2 (OS Build 19042.985).

Yes, addons of both NVDA & Firefox are now disabled, & I have refreshed Firefox. Yes, I can provide a log for interested parties. Yes, I have tried running comm registration tool. There is text on the screen, Seeing AI sees it, but NVDA does not recognize it, nor does narrator.

I'm hosed.


Re: What's the situation with Seika Braille drivers?

Lukasz Golonka
 

On Tue, 1 Jun 2021 21:23:03 +0200
"Mallard" <mallard@kimabe.eu> wrote:

Many thanks. I-m using a Seika 5/40, not 80.

I hope this works anyway.
Assuming whatever display you have used to work with 2019.2 and stopped
working after Python 3 migration the PR which I've mentioned in my
previous message is the right one.


Re: What's the situation with Seika Braille drivers?

Mallard
 

Hello,


Many thanks. I-m using a Seika 5/40, not 80.

I hope this works anyway.


I-ll do my best. I-m totally lost on Github. I get lost there, but I-ll do my best.


Thanks again. Stay safe,

Ollie

On 01/06/2021 21:01, Lukasz Golonka via groups.io wrote:
Hello,,

On Tue, 1 Jun 2021 17:56:23 +0200
"Mallard" <mallard@kimabe.eu> wrote:

the situation here is becoming pretty much unbearable. Using a Seika braille display with NVDA has become practically impossible.


The first hints I found on the drivers being worked on are from 2019. Some time ago I was told a driver was being tested... When can we expect to be able to use Seikas again?
Assuming you're using one of: Seika v3/5/80 the pull request which fixes
support for it can be found here:

https://github.com/nvaccess/nvda/pull/10961

I've asked main developers for a second look at it but it would be
better if you can join GitHub and comment on the PR - it is much more
effective when affected users are advocating themselves.


Re: What's the situation with Seika Braille drivers?

Lukasz Golonka
 

Hello,,

On Tue, 1 Jun 2021 17:56:23 +0200
"Mallard" <mallard@kimabe.eu> wrote:

the situation here is becoming pretty much unbearable. Using a Seika braille display with NVDA has become practically impossible.


The first hints I found on the drivers being worked on are from 2019. Some time ago I was told a driver was being tested... When can we expect to be able to use Seikas again?
Assuming you're using one of: Seika v3/5/80 the pull request which fixes
support for it can be found here:

https://github.com/nvaccess/nvda/pull/10961

I've asked main developers for a second look at it but it would be
better if you can join GitHub and comment on the PR - it is much more
effective when affected users are advocating themselves.

--
Regards
Lukasz


Re: Farewell, NVDA community: retiring from NVDA contributions, effective September 1, 2021

ely.r@...
 

Joseph,

This is a time when I wish I had come to know you in person. Have to say that your personality often comes through in your many notes of direction and support you have shared. Envy your move to graduate school. There was a time when I felt it would be just fine to go on accumulating degrees as it was wonderful learning and being a part of the community  that grad school seems to gather.

 

Best to you on your next adventure and thanks for all the solutions. Must sometimes your solutions arrived before I knew there was an answer I would shortly need.

Best,

Rick and General, guide dog extraordinaire

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Roger Stewart
Sent: Tuesday, June 1, 2021 10:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Farewell, NVDA community: retiring from NVDA contributions, effective September 1, 2021

 

Thank you very much for all you have done for NVDA.  Without your add ons, I'd not be able to do internet broadcasting, use Goldwave very well and many many other things I do every day are using your contributions.  I'll miss your contributions much, but you'll keep on helping me every day with what you have done.  Good luck on your future endeavors. 

 

Roger

 

 

 

 

 

 

 

 

 

 

 

 

On 5/31/2021 11:44 PM, Joseph Lee wrote:

Hi NVDA users,

Update: just submitted last NVDA pull request for now.

In order to spend more time on transitioning to graduate school, I'm retiring from NVDA code contributions, effective June 1, 2021. I'll still be around to coordinate preparing add-ons for NVDA 2021.1 stable release, and will provide leadership on add-ons community until then.

Thanks to everyone who sent encouragements, both on this thread and for the last nine years. I'm more satisfied to hear how NVDA has made a difference in a person's life, more than seeing people use what I have contributed: improved touchscreen support, Windows 10 support (search suggestions, emoji panel, clipboard history, supporting modern apps), playing sounds when suggestions appear, toggling NVDA start and exit sounds, and others I lost count. Through my add-ons, you have context-sensitive help on using controls, much better touchscreen usage experience, resource usage reporting, and the ability to keep up to date with add-ons. But these are nothing compared to contributing to getting NVDA to help you unlock your potential. I know that NVDA will make a huge difference in people's lives for years to come; the true power and market share of NVDA is not the download count but lives improved by it.

P.S. I will indeed post an update once Add-on Updater starts noticing new versions of my add-ons.

Farewell, NVDA Users community. long live NVDA, NV Access, NVDA community! Sincerely, Joseph

Joseph S. Lee Certified NVDA Expert, 2019 former Volunteer code contributor, translator, community add-ons reviewer, NonVisual Desktop Access screen reader project (June 2012 to May 2021)

 


A few questions about NVDA, eSpeak NG, and languages (non-programer)

Daniel Parker
 
Edited

[Version note: In this general query and my notes that follow, I will be referring both to NVDA 2020.4 and the most recent beta of NVDA 2021.1; if no version is specified, assume the comment applies to both.]
 
Hello all,
 
I would first like to say that I'm a newcomer to the group, and I very much appreciate the level of dedication, enthusiasm, and zeal of all the contributors who share my dream of a free screen reader which not only shows up the best in paid software, but also has possibly the best language support of any reader I've come across, and that's saying something! This question is primarily aimed at developers, but help/knowledge from anyone is very welcome.
 
I am now mostly a Mac user, but before 2017 I primarily used Windows, and still occasionally do for certain programs or, yes, viewing text in languages not supported by VoiceOver. Ever since 2016, when I was told about NVDA's rapid progress and tried it for myself, I have continually been impressed by the huge and ever-expanding list of TTS languages supported, especially through eSpeak NG. I am aware that said synthesizer is its own independent project, but I do have questions about how much modification the NVDA team, or community, does to the synthesizer's output before packaging eSpeak with a release. To preface, I have absolutely no knowledge of programing or development, and I will likely ask foolish questions and make foolish assumptions, for which I apologize.
 
[Note: I have developed some informal notes about eSpeak TTS languages, including which have translated what ASCII symbols, which have phonetic problems, etc. They will be at the bottom of this message if anyone cares.]
 
First, I have a question regarding TTS ASCII symbol translation. Some eSpeak languages have translated numbers, punctuation symbols (e.g., dot/period, comma, colon), and also symbols like the carriage return. Some languages only translate numbers but leave the English punctuation symbols. And some don't translate either. One language, Hebrew, translates only punctuation (more on Hebrew later).
 
I am American, and so I find some of NVDA's default punctuation names (dot, tick, bang, semi) a bit idiosyncratic as compared with, say, Jaws 'period, apostrophe, exclaim, semicolon'. But when dealing with the TTS languages that do not have punctuation translated, it's always the NVDA set of names. I am wondering whether or not those names originate with NVDA or eSpeak (or perhaps both), and thus whether it is the NVDA community or the eSpeak community which provides those translations. I also have this question about TTS languages like Hebrew, Japanese and Burmese which, instead of defaulting to eSpeak English for Latin-script words, spell out all Latin letters. Is that a function of how NVDA uses or packages eSpeak, or eSpeak itself?
 
Second, as I mentioned, I am no programer. However, I do have some knowledge of linguistics and phonology from having taken a few linguistics classes in university, as well as having studied as a hobby on my own time. I have found certain TTS languages with sometimes glaring phonetic problems, some of which I know I could fix easily if only I knew how to program. These include doubled phonemes which should actually be lengthened, incorrect prosody/stress, diphthongs in some languages which could be better handled, and in the case of Haitian Creole, a plainly incorrect phonemic inventory, full stop. I am aware that this is most likely under the purview of the eSpeak NG community, but this leads back to the first question about translation. While I regrettably do not speak any minority language and so cannot translate the interface, it might be possible for me to look up what  punctuation mark A or number A is called in language X and add it to the speech output. But this is where I'm unsure. If I want to help with eSpeak NG phonemics, I'm going to have to learn Speech Synthesis Markup Language (SSML) and probably also some C, which eSpeak is written in. But if any of the things I have mentioned (along with languages with scrambled letters) are controlled by NVDA, then I will likely also have to learn Python. Learning three programing languages seems like a lot for a complete beginner. If that's what it takes I'll do my best, but I want to be sure of what I need to do. I guess I'm just wondering if developers or the NVDA Team have ideas about what would be the best way to prepare myself for this work, which I am very passionate about doing, but for which I lack knowledge as yet.
 
I am also aware that eSpeak has many more TTS languages that NVDA does not include, at least according to a cursory glance at Wikipedia and Github. Is there a reason for this, or a process by which the NVDA Team or community determines which new languages are ready to be included in the next release?
 
Thank you very much in advance for your responses to these elementary questions, and for this excellent community that has worked so hard to realize our shared goal.
 
All the best,
Daniel
 
------------------
 
eSpeak NG TTS language notes
 
Numbers and punctuation translated: Arabic1, Aragonese, Bulgarian, Catalan, Czech, Danish, German, Greek, Spanish (both versions), Persian (both versions)2, Finnish, French (all versions), Gaelic (Irish), Hindi2, Hungarian, ), Armenian (West Armenian), Icelandic, Italian, Japanese, Georgian, Kannada, Korean, Kyrgyz, Lithuanian, Macedonian, Dutch, Polish, Portuguese (Brazil), Romanian, Russian (both versions), Slovak, Slovenian, Albanian, Serbian, Swedish, Tamil, Turkish, Ukrainian, Vietnamese (all versions).
 
Only numbers translated: Afrikaans, Amharic, Assamese, Azerbaijani, Bashkir,, Bengali, Bishnupriya Manipuri, Bosnian, Chinese Mandarin (both versions), Welsh, Esperanto, Estonian, Basque, Gaelic (Scottish), Hakka Chinese, Hawaiian, Armenian (East Armenian),  Interlingua, Indonesian, Ido, Lojban, Greenlandic3, Konkani, Kurdish, Latin, Lingua Franca Nova, Latgalian, Latvian, Malayalam, Marathi, Malay, Maltese, Maori (as of beta version), Myanmar Burmese, Norwegian Bokmal, Nahuatl Classical, Nepali, Oromo, Oriya, Punjabi, Papiamento, Klingon, Portuguese (Portugal), Lang Belta, Pyash, Quechua, Shantaiyai, Sindhi, Sinhala, Swahili, Telugu, Thai, Setswana, Tatar, Uzbek, Urdu, Chinese (Cantonese) (both versions).
 
Only punctuation translated: Hebrew1
None translated: Cherokee, Chuvash, Guarani, Greek (Ancient), Kazakh, Nogai, Turkmen. 
 
Phonetic improvements (as of the most recent beta of 2021.1): Arabic, Maori.
 
Latin words spelled: Bashkir, Chuvash, Hebrew, Armenian (West Armenian), Japanese, Konkani, Kyrgyz, Myanmar Burmese, Shantaiyai.
 
Latin letters scrambled: Greek (Ancient)
 
Phonemic problems (pronunciations in X-Sampa; not exhaustive):
 
Arabic: vowel qualities and some consonants are not accurate. Long vowels often doubled as of 2020.4; this is better as of the most recent beta. Stress needs work.
Estonian: Lengthened phonemes doubled.
Gaelic (Irish): some. For example, 'ae' should not make the following consonant slender; 'aei' serves that purpose. 'Aei' should sound like [e:], not [e:I].
Gaelic (Scottish): some, possibly. R sounds strange in many circumstances; need to investigate.
Hawaiian: Some diphthongs could use work. The phonemic inventory may not actually reflect current spoken Hawaiian.
Haitian Creole: Major problems. No nasal vowels. Several digraphs are incorrectly pronounced. 'Ou' is pronounced [o"u] instead of [u], 'ch' is pronounced [Sh] instead of [s], 'j' is pronounced [j] instead of [Z], 'ui' is pronounced [u"i] instead of [Hi], and 'r' is pronounced [h] instead of [R] or [G]. In addition, the number 1 is incorrectly pronounced [y.o"un] instead of the correct [ju~].
Italian: minor; single 'r' between vowels could be [4] instead of [r] and everywhere else 'r' and double 'rr' might be [r] instead of [r:]. Some other phonemes like 'ff' could be lengthened, not doubled. Check raddoppiamento sintattico.
Japanese: in some cases like in the numbers, alveolar consonants before [i] are not palatalized. Lengthened consonants are incorrectly doubled.
Maltese: Some, but I do not know enough yet to fully document.
Portuguese (Portugal): 'r' except between vowels and double 'rr' could be [r] or [R] instead of [r\].
Romanian: 'r' could more distinctly be [4] or [r] rather than [r\]
Lue Saami: lengthened phonemes doubled?
Setswana: unsure about vowel qualities. Lengthened phonemes doubled.
 
Sounds for some native, latin or foreign letter names: Cherokee, Greek (ancient), Hakka Chinese, Hawaiian, Haitian Creole, Lojban, Georgian, Maori (beta), Nahuatl Classical, Quiche, Uyghur, 
 
Pronunciation of foreign letter names in the middle of words, or native letters scrambled when foreign letters appear: Cherokee, Chinese Mandarin (Latin as pinyin), Greek (Ancient), Hakka Chinese, Hawaiian, Maori (as of beta version),  Klingon, Lang Belta, Quiche, Lue Saami, Turkmen, Uyghur, Uzbek.
 
Alphabet name (e.g., Cyrillic) appended to native letters: Kyrgyz, Nogai. 
 
English letter names: Chinese Mandarin (Latin as Pinyin), Persian Pinglish, Gaelic (both versions), Kannada, Maori (new version), Malayalam, Malay, Shantaiyai, Tamil, Telugu, Setswana (some).
 
Other problems:
Cherokee: Does not recognize 'q' as a native letter; pronounces letter name in the middle of words, which is disruptive. Instead of reverting to English, words with non-Cherokee Latin letters are scrambled.
Greek (ancient): cannot pronounce names of letters and letters with diacritics (modern Greek is fully able to do this); instead, uses the sound of the letter or the encoding number for some letters with diacritics. Reads with distinct pause between words. Pronounces most Greek words fine, but no tone distinctions. Pronounces letter name of 'c' in the middle of words.
Hakka Chinese: scrambles the following Latin letters in the middle of a word: B, C, D, G, J, Q, R, W, X, Z. Some is understandable since Hakka was likely developed for the Latin orthography.
Hawaiian: Appears to be based on a Slavic-language inventory. The use of 'y' in a word is disruptive.
Lang Belta: when foreign letters appear, spells in phonetic alphabet, but maybe this is intentional?
Quechua: names for 'k' and 'q' are not distinct. May be based partially on Slavic inventory?
Tatar: does not recognize some native Cyrillic letters; uses encoding number.
 
1) Tokenization for Hebrew and Arabic is obviously a major problem. Punctuation and numbers, when translated at all, are not voweled and make no sense. Perhaps adding vowels to the specifications would solve this.
2) Persian and Hindi do not translate all punctuation. Also say a few random marks out loud, such as comma and the right parenthesis.
3) in some cases, Greenlandic uses an approximation of Danish numbers (e.g., when reading by character), but otherwise it uses its own (e.g., when reading by line).


What's the situation with Seika Braille drivers?

Mallard
 

Hello all,


the situation here is becoming pretty much unbearable. Using a Seika braille display with NVDA has become practically impossible.


The first hints I found on the drivers being worked on are from 2019. Some time ago I was told a driver was being tested... When can we expect to be able to use Seikas again?


Thanks.

Ciao,

Ollie


Re: Farewell, NVDA community: retiring from NVDA contributions, effective September 1, 2021

Roger Stewart
 

Thank you very much for all you have done for NVDA.  Without your add ons, I'd not be able to do internet broadcasting, use Goldwave very well and many many other things I do every day are using your contributions.  I'll miss your contributions much, but you'll keep on helping me every day with what you have done.  Good luck on your future endeavors. 

Roger












On 5/31/2021 11:44 PM, Joseph Lee wrote:

Hi NVDA users,

Update: just submitted last NVDA pull request for now.

In order to spend more time on transitioning to graduate school, I'm retiring from NVDA code contributions, effective June 1, 2021. I'll still be around to coordinate preparing add-ons for NVDA 2021.1 stable release, and will provide leadership on add-ons community until then.

Thanks to everyone who sent encouragements, both on this thread and for the last nine years. I'm more satisfied to hear how NVDA has made a difference in a person's life, more than seeing people use what I have contributed: improved touchscreen support, Windows 10 support (search suggestions, emoji panel, clipboard history, supporting modern apps), playing sounds when suggestions appear, toggling NVDA start and exit sounds, and others I lost count. Through my add-ons, you have context-sensitive help on using controls, much better touchscreen usage experience, resource usage reporting, and the ability to keep up to date with add-ons. But these are nothing compared to contributing to getting NVDA to help you unlock your potential. I know that NVDA will make a huge difference in people's lives for years to come; the true power and market share of NVDA is not the download count but lives improved by it.

P.S. I will indeed post an update once Add-on Updater starts noticing new versions of my add-ons.

Farewell, NVDA Users community. long live NVDA, NV Access, NVDA community! Sincerely, Joseph

Joseph S. Lee Certified NVDA Expert, 2019 former Volunteer code contributor, translator, community add-ons reviewer, NonVisual Desktop Access screen reader project (June 2012 to May 2021)



Re: Farewell, NVDA community: retiring from NVDA contributions, effective September 1, 2021

Kelly, Kathleen
 

Thank you so much for all your help. Good luck in graduate school. 


From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of Joseph Lee via groups.io <joseph.lee22590@...>
Sent: Tuesday, June 1, 2021 12:44 AM
To: nvda@nvda.groups.io <nvda@nvda.groups.io>
Subject: Re: [nvda] Farewell, NVDA community: retiring from NVDA contributions, effective September 1, 2021
 
WARNING: This email originated from outside of USF. Do NOT click links or attachments unless you recognize the sender and know the content is safe.

Hi NVDA users,

Update: just submitted last NVDA pull request for now.

In order to spend more time on transitioning to graduate school, I'm retiring from NVDA code contributions, effective June 1, 2021. I'll still be around to coordinate preparing add-ons for NVDA 2021.1 stable release, and will provide leadership on add-ons community until then.

Thanks to everyone who sent encouragements, both on this thread and for the last nine years. I'm more satisfied to hear how NVDA has made a difference in a person's life, more than seeing people use what I have contributed: improved touchscreen support, Windows 10 support (search suggestions, emoji panel, clipboard history, supporting modern apps), playing sounds when suggestions appear, toggling NVDA start and exit sounds, and others I lost count. Through my add-ons, you have context-sensitive help on using controls, much better touchscreen usage experience, resource usage reporting, and the ability to keep up to date with add-ons. But these are nothing compared to contributing to getting NVDA to help you unlock your potential. I know that NVDA will make a huge difference in people's lives for years to come; the true power and market share of NVDA is not the download count but lives improved by it.

P.S. I will indeed post an update once Add-on Updater starts noticing new versions of my add-ons.

Farewell, NVDA Users community. long live NVDA, NV Access, NVDA community! Sincerely, Joseph

Joseph S. Lee Certified NVDA Expert, 2019 former Volunteer code contributor, translator, community add-ons reviewer, NonVisual Desktop Access screen reader project (June 2012 to May 2021)


Re: Farewell, NVDA community: retiring from NVDA contributions, effective September 1, 2021

Rui Fontes
 

Joseph, in spite of our differences in some aspects, I have learned a lot with you!

So, in my personal name and in name of NVDA portuguese community, many, many thanks for all your work!


Rui Fontes

NVDA portuguese team


Às 05:44 de 01/06/2021, Joseph Lee escreveu:

[Edited Message Follows]

Hi NVDA users,

Update: just submitted last NVDA pull request for now.

In order to spend more time on transitioning to graduate school, I'm retiring from NVDA code contributions, effective June 1, 2021. I'll still be around to coordinate preparing add-ons for NVDA 2021.1 stable release, and will provide leadership on add-ons community until then.

Thanks to everyone who sent encouragements, both on this thread and for the last nine years. I'm more satisfied to hear how NVDA has made a difference in a person's life, more than seeing people use what I have contributed: improved touchscreen support, Windows 10 support (search suggestions, emoji panel, clipboard history, supporting modern apps), playing sounds when suggestions appear, toggling NVDA start and exit sounds, and others I lost count. Through my add-ons, you have context-sensitive help on using controls, much better touchscreen usage experience, resource usage reporting, and the ability to keep up to date with add-ons. But these are nothing compared to contributing to getting NVDA to help you unlock your potential. I know that NVDA will make a huge difference in people's lives for years to come; the true power and market share of NVDA is not the download count but lives improved by it.

P.S. I will indeed post an update once Add-on Updater starts noticing new versions of my add-ons.

Farewell, NVDA Users community. long live NVDA, NV Access, NVDA community!

Sincerely,

Joseph

Joseph S. Lee

Certified NVDA Expert, 2019

former Volunteer code contributor, translator, community add-ons reviewer, NonVisual Desktop Access screen reader project (June 2012 to May 2021)

2081 - 2100 of 86618