Welcome to the speakup community. On Fri, Jan 31, 2020 at 02:29:35PM -0700, geek@xxxxxxxxxxxxxxxx wrote: > 1. Is Speakup the same thing as Espeakup? I tried "sudo apt-get install > speakup" and it suggested replacing it with "espeakup". I know what eSpeak > is, and I've used it many times in my own projects, but are they the same > thing? They both need each other to work, but they're not the same thing. Speakup is the screen reader in the linux kernel, while espeakup is a connector between the speakup screen reader, and the espeak text to speech engine. > > 2. I'm also a developer, and I'm a big fan of building terminal apps. But > my terminal apps have use eSpeak to talk, and also use a code library called > ncurses to create a decent interface for users with some vision. I know > ASCII art in general should always be either avoided or optional, but I'd > like what I build to be accessible to everyone, including people with some > vision. Anyway, in my troubleshooting earlier, I ran dpkg-config > something-or-other and got what looked like a colorful screen with a message > box. Speakup/Espeakup was still rambling on about something previously > printed to the screen, but when I pressed the down arrow, it spoke the > currently selected option. This is awesome! But I'm interested in learning > how to make my projects compatible with Speakup. I'm sure it's more than > just not linking to eSpeak (lol). How did it know which bit of text on the > screen was selected? > As far as I understand it, when you press down arrow, a different option is highlighted. So, speakup spoke or more precisely sent the newly highlighted text to /dev/softsynth, which got picked up by espeakup, which sent it to espeak for speech output. Speakup is part of the linux kernel, so is able to intercept what is sent to the video card for output. If you want a more technical answer, then someone else will have to jump in, or just try reading through the speakup code I suppose. As far as making programs accessible for speakup users, I'd say a simple command line interface is probably best, that's just my view, and it probably isn't shared by everyone here. > 3. I'd like to get involved. I know C and Git well, currently learning GDB > and Makefiles (I got the basics though), but definitely capable of > contributing. I don't know much about the kernel, but I'd like to learn. > I'm also fluent in Spanish, so I'd like to translate the user's guide (which > I'm still reading) into Spanish. How would I get started? Apart from > reading the user guide I mean - still working on that. Speakup is in the staging part of the linux kernel. So, you probably want to follow the guidelines for submitting a patch found at: <https://www.kernel.org/doc/html/latest/process/submitting-patches.html#submittingpatches> If that's a bit much to follow, then you could probably post your translation here for others to review, and one of the speakup developers could probably generate and submit the patch on your behalf. If I'm wrong on any of the above, someone will likely step in and correct me. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-manager@xxxxxx _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
