Linux for blind general discussion
blinux-list at redhat.com
Mon Oct 10 18:47:18 UTC 2022
Yes fenrir is also included in Slint 15.0, thanks Jude for the remainder.
Le 10/10/2022 à 20:10, Linux for blind general discussion a écrit :
> You forgot fenrir.
> Jude <jdashiel at panix dot com>
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> On Mon, 10 Oct 2022, Linux for blind general discussion wrote:
>> So neither tdsr nor yasr will land in Slint 15.0...
>> ... which already includes speech-dispatcher, espeakup, speechd-up, speechd-el,
>> emacspeak, brltty, and of course orca so can be used on the console as in
>> graphical environments (main included are MATE and LXQt) and switch back and
>> forth between console and graphical without losing speech.
>> I would be glad to anyone testing the slint-15.0 release candidate 2, ISO
>> available here:
>> Please read first:
>> If you like it you will not have to reinstall when the "official release" ISO
>> will be available in a very few days. On the other hand if major bugs are found
>> I will provide another ISO, else, just update the installed packages to pravide
>> fixes will be enough.
>> Didier Spaier
>> Le 10/10/2022 ? 18:30, Linux for blind general discussion a ?crit :
>>> Tdsr is in fact much like YASR in functionality from what I can tell, with the
>>> exception that it appears there is no way to change what voice it uses without
>>> editing your speech-dispatcher configuration. I didn't find any mention of an
>>> exception dictionary either, which was included in YASR as I recall, though it
>>> has been a very long time since I used that. That said, I see no advantage to
>>> using it if you already have Speakup running. I also don't see any advantage to
>>> running Speakup and Fenrir at the same time, and the primary advantage of Fenrir
>>> over Speakup, aside from spell check and other useful features, is simply that a
>>> kernel update won't even temporarily break your screen reader as I have seen
>>> happen, though such breakage does occur rather infrequently. That said, running
>>> entirely independent of the kernel does offer better portability, and also means
>>> that the screen reader can be updated independently of the kernel, which IMO is
>>> always a good thing(tm).
>> Blinux-list mailing list
>> Blinux-list at redhat.com
> Blinux-list mailing list
> Blinux-list at redhat.com
More information about the Blinux-list