From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: Other accessible terminal emulation
Date: Mon, 19 Nov 2018 19:18:18 +0100 [thread overview]
Message-ID: <9996e7f8-2882-0ed0-e6e0-18a0cd96fb57@linux-a11y.org> (raw)
In-Reply-To: <CAO2sX30-Ee+C7SCsstu5own+DxZPYtomDcgsGk_gR0C_1Y_dSg@mail.gmail.com>
Howdy,
> Also, previous messages in this thread would suggest it works just as
> well in a Terminal Emulator as from the terminal itse
yea exactly. Fenrir provides "drivers" to provide different backends
(speech, braille (WIP), input, sound, remote and screen)
currently i implement 2 different screen drivers.
1. vcsaDriver: uses /dev/vcsa[1-x] as information source to provide
information on the screen. this just works for real TTY terminal with an
existing VCSA device
2. ptyDriver: uses pty, fork, and pyte to stand as "man in the middle"
(like yasr did but in a lot more advanced state). so it spawns an
terminal and captures any input you did and watches to the output of
its child process, processing it and pass it through.
i suggest to use XTERM or another inaccessible terminal emulator to my
users, because they don't conflict with orca at all (input (shortcuts)
and output).
> built-in support for Unicode(arguably of limited use for
fenrir provides Unicode support as well for any language form just the
beginning (on VCSA and PTY).
> No idea why Fenrir is named after the Wolf from Norse mythology,
hehe because i m a rebel ;). Just kidding. the naming was strom_dragons
idea ;).
sadly i m not a good software deployer, so i just provide packages for
ArchLinux (since i use it). I also see some debian packages ( i never
tested or tried them, currenlty).
But fenrir runs also without any installation just from git, (the
dependencies are needed of course).
so if anyone is good in deploying software for different distros with
setup.py or similar, just tell me :).
cheers chrys
Am 19.11.18 um 18:30 schrieb Linux for blind general discussion:
> Fenrir is a text-mode, userspace screen reader written in Python. I
> haven't used it myself, but its gaining popularity as an alternative
> to espeakup. The two biggest pros I've heard is that, as a user space
> application, it doesn't require a kernel module(espeakup requires the
> speakup kernel module) and should thus be easier to setup on distros
> that don't ship staging modules in their default kernels(speakup has
> been trapped in staging for years and has little chance of graduating
> to kernel main short of a complete rewrite as I understand it) and
> built-in support for Unicode(arguably of limited use for
> English-speaking users, but could be vital to those whose native
> language uses a non-Latin Alphabet).
>
> Also, previous messages in this thread would suggest it works just as
> well in a Terminal Emulator as from the terminal itself, which I don't
> believe I've heard suggest of espeakup or SBL, the latter which I use
> for terminal speech myself(I only run X for Firefox, so I can't
> comment on the question of Terminal Emulators).
>
> No idea why Fenrir is named after the Wolf from Norse mythology,
> especially since its traditional to name screen readers after marine
> animals and this is the only screen reader I know of with a non-marine
> animal-based name.
>
> On 11/19/18, Linux for blind general discussion <blinux-list@redhat.com> wrote:
>> What is fenrir?
>>
>> On 11/19/18, Linux for blind general discussion <blinux-list@redhat.com>
>> wrote:
>>> Howdy,
>>>
>>> gnome-terminal works as well.
>>>
>>> you also can use fenrir to make an terminal emulator accessible by
>>> starting it with:
>>> fenrir -e (for using escape sequence shortcuts)
>>> sudo fenrir -E (using evdev, can only run once)
>>>
>>> cheers chrys
>>> Zitat von Linux for blind general discussion <blinux-list@redhat.com>:
>>>
>>>> Is there any other accessible terminal emulators besides using mate
>>>> terminal in a window manager?
>>>>
>>>> _______________________________________________
>>>> Blinux-list mailing list
>>>> Blinux-list@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9996e7f8-2882-0ed0-e6e0-18a0cd96fb57@linux-a11y.org \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).