cloudpilot-emu VS nvda

Also of interest: CloudpilotEmu - Palm emulator in your browser

https://cloudpilot-emu.github.io/

When I installed it and could play Vexed again... ahh, the happiness!

You can run the original Palm version in a browser with CloudpilotEmu. Works great on my phone when I just have to scratch the itch. https://cloudpilot-emu.github.io/

And you can use it online as well https://cloudpilot-emu.github.io/

I've never seen a good major one TBH. The best PWA I've ever used, however, is this Palm OS emulator:

https://cloudpilot-emu.github.io/

There's Worldle for Palm OS, for example: https://github.com/RobbieNesmith/PalmWordle

POSE has also been ported to WASM recently, which means it runs on both Android and iOS as a PWA: https://github.com/cloudpilot-emu/cloudpilot-emu

I came across this recently if anyone is interested, in browser emulator with all the roms: https://cloudpilot-emu.github.io/

CloudpilotEmu is a web-based emulator for PalmOS. It emulates dragonball based devices and supports PalmOS up to version 4.x. CloudpilotEmu is based on the original POSE emulator.

After some brief research it seems the issue you're seeing may be a known bug in at least some versions/release of espeak-ng.

Here's some potentially related links if you'd like to dig deeper:

* "questions about mandarin data packet #1044": https://github.com/espeak-ng/espeak-ng/issues/1044

* "ESpeak NJ-1.51’s Mandarin pronunciation is corrupted #12952": https://github.com/nvaccess/nvda/issues/12952

* "The pronunciation of Mandarin Chinese using ESpeak NJ in NVDA is not normal #1028": https://github.com/espeak-ng/espeak-ng/issues/1028

* "When espeak-ng translates Chinese (cmn), IPA tone symbols are not output correctly #305": https://github.com/rhasspy/piper/issues/305

* "Please default ESpeak NG's voice role to 'Chinese (Mandarin, latin as Pinyin)' for Chinese to fix #12952 #13572": https://github.com/nvaccess/nvda/issues/13572

* "Cmn voice not correctly translated #1370": https://github.com/espeak-ng/espeak-ng/issues/1370

NOTE: There is an accessibility bug in Safari and NVDA where labels are not properly associated to Form-Associated Custom Elements for screen readers. They are read fine with VoiceOver in Chromium browsers (Chrome, Edger, Brave, etc.) and Firefox on Mac and MS Narrator and JAWS on Windows. As a workaround, you can continue including your labels within your elements.

If that doesn't meet your need, I would encourage you to file an issue on our issue tracker at: https://github.com/nvaccess/nvda/issues

We don't have a huge number of users relying on touch, and we know NVDA could be improved in this area, so we are always keen for feedback. The best place is to file an issue at: https://github.com/nvaccess/nvda/issues (Happy to have discussion here, but just in case I miss it, and in any case someone will still need to create an issue for any action items eventually).

If you think this is an issue with NVDA, you can open an issue on Github.

It's getting better. We originally didn't have any contact with anyone from the LO community to try to get any help from their side. But in recent years we've had support from a couple of LO developers and community members and support for LO is improving. As always though, if you use it and encounter any issues with NVDA, please do report them to us either in a message or email, or create an issue on our GitHub page: https://github.com/nvaccess/nvda/issues If it is a LibreOffice issue (rather than NVDA) then they also have an issue tracker: https://bugs.documentfoundation.org/ And often it is hard to tell, so feel free to report it to us and we can ensure it gets reported with LO as well (or vice-versa).

Even if you can't contribute to the code itself, this level of technical knowledge of the issue would definitely be worth writing up in an issue on https://github.com/nvaccess/nvda/issues

And there's still a lot of work for the third-party tools to do, too.

https://github.com/nvaccess/nvda/issues/5186#issuecomment-20...

https://bugzilla.mozilla.org/show_bug.cgi?id=381888

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

I read somewhere that screen readers look for a flashing vertical line, to detect the caret position in systems that don't expose it via the OS's APIs. I can't find a reference for that right now, though.

Coming in late and without much new info I'm afraid. Good question though. I must admit, I'm not sure if we considered this situation. The one thing I can suggest, is if you are interested in the functionality, is creating an issue on our GitHub tracker here: https://github.com/nvaccess/nvda/issues

- If you are confident you've found a bug and would like to report it, we have a GitHub page here: https://github.com/nvaccess/nvda/issues