[quoted lines by Rob Hudson on 2021/05/09 at 21:33 -0500]
>If I start brltty with systemctl, I get that
>"not saved"
>when exiting preferences.
>If I just start it by typing
>brltty
>at root prompt, everything works as expected.
Then it's a permissions problem for sure. To pass
Dave Mielke wrote:
> [quoted lines by Rob Hudson on 2021/05/09 at 17:36 -0500]
>
> >With which log categories do I need to start up brltty.
>
> For your case, none because we're looking for an error.
Ok, new wrinkle. If I start brltty with systemctl, I get that
"not saved"
when exiting
Hi,
Am 09.05.21 um 11:17 schrieb Dave Mielke:
[quoted lines by halim.sa...@freenet.de on 2021/05/09 at 09:41 +0200]
> For plain tty stuff with speech enabled I found some problems which
> makes things dificult for me.
Have you enabled autospeak?
yes
> When I read a man page with
Hi Didier,
> Am 09.05.2021 um 22:28 schrieb Didier Spaier :
> 1. pulseaudio is only started on demand (when an application requires it)
> 2. pulseaudio is set to use the the dmix mixer, so ends all streams go to alsa
> through via this mixer. From our /etc/pulse/default.pa:
>
> ### In Slint, we
Hi Dave,
> Am 09.05.2021 um 22:35 schrieb Dave Mielke :
>
> [quoted lines by Christian Schoepplein on 2021/05/09 at 22:04 +0200]
>
>> It would be really cool if you have another idea that could help.
>
> The AtSpi2 screen driver used to have a focus parameter which could contrain
> it to
Hello. One way around the problem with a graphical terminal
accessibility issues while
still working in a graphical environment is to use a screen reader like brltty
or Yasr in an
instance of xterm. While brltty won't give you access to the rest of the
graphical
environment, it should
Hi Dave,
> Am 09.05.2021 um 21:45 schrieb Dave Mielke :
>
> [quoted lines by Christian Schoepplein on 2021/05/09 at 21:29 +0200]
>
>> OK; then the only solution currently is to use an older brltty version if I
>> like to have a setup with speech support enabled for brltty in the Mate
>>
On Sun, May 09, 2021 at 09:08:34PM +0200, Didier Spaier wrote:
>
>I always wonder why people do in a graphical environment things more easily
>done
>in a console. Maybe just because that's what they are used to? Granted, there
>are things that can't be done in console, but typing commands in a
[quoted lines by Rob Hudson on 2021/05/09 at 17:36 -0500]
>With which log categories do I need to start up brltty.
For your case, none because we're looking for an error.
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke| 2213 Fox Crescent |
On Sun, May 09, 2021 at 11:13:03AM +0200, Samuel Thibault wrote:
>Dave Mielke, le dim. 09 mai 2021 05:03:27 -0400, a ecrit:
>> [quoted lines by halim.sa...@freenet.de on 2021/05/09 at 10:19 +0200]
>>
>> > The problem reported is not a speech only problem I think.
>>
>> Specifying
Am 09.05.2021 um 12:10 schrieb Aura Kelloniemi:
Isn't Orca's speech support for terminals better than BRLTTY's? I believe it
is more featureful, though syncing the braille display with speech output is
not possible, if Orca does the speaking.
Exactly this is the problem.
Speech and braille
Dave Mielke wrote:
> The log should contain the actual error.
With which log categories do I need to start up brltty.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general
[quoted lines by Rob Hudson on 2021/05/09 at 16:40 -0500]
>Still says
>"not saved"
>when exiting preferences.
The log should contain the actual error.
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke| 2213 Fox Crescent | WebHome:
Alexander Epaneshnikov wrote:
actually you need to change prefs file permission too.
if it doesn't help, you need to provide logs.
-rw-r--r-- 1 brltty brltty 5057 Oct 6 2020 brltty.prefs
___
This message was sent via the BRLTTY mailing list.
To post
Le 09/05/2021 à 23:24, Samuel Thibault a écrit :
Didier Spaier, le dim. 09 mai 2021 23:13:18 +0200, a ecrit:
Le 09/05/2021 à 23:09, Samuel Thibault a écrit :
Didier Spaier, le dim. 09 mai 2021 23:02:49 +0200, a ecrit:
Still, this could be an issue for audiophiles, but they can use jack.
10.05.2021 0:40, Rob Hudson пишет:
Alexander Epaneshnikov wrote:
what's happening? Permissions problem?
-rw-r--r-- 1 root root 5057 Oct 6 2020 ./lib/brltty/brltty.prefs
Thanks.
i think yes. try to change it to brltty brltty.
Still says
"not saved"
when exiting preferences.
actually you
Alexander Epaneshnikov wrote:
> what's happening? Permissions problem?
> -rw-r--r-- 1 root root 5057 Oct 6 2020 ./lib/brltty/brltty.prefs
> Thanks.
>
i think yes. try to change it to brltty brltty.
Still says
"not saved"
when exiting preferences.
___
Hi Chistian,
Le 09/05/2021 à 23:17, Christian Schoepplein a écrit :
Are the changes in /etc/pulseaudio/default.pa the only necessary changes I have
to perform on a standard Debian system, or are there other things I have to do?
If yes, I’ll try it on a fresh Debian Bullsey installation.
I am
10.05.2021 0:08, Rob Hudson пишет:
Brltty 6.3 on arch linux.
If I set hte preferences menu to
"save on exit: yes"
And then exit the preferences menu, the braille display flashes
"not saved"
what's happening? Permissions problem?
-rw-r--r-- 1 root root 5057 Oct 6 2020 ./lib/brltty/brltty.prefs
Didier Spaier, le dim. 09 mai 2021 22:58:57 +0200, a ecrit:
> Well initially I posted on linux-speakup,
> I also posted here:
> https://mail.gnome.org/archives/orca-list/2018-February/msg00143.html
linux-speakup and orca are not pulseaudio-maintainer lists.
> But you forwarded the suggestion in
Didier Spaier, le dim. 09 mai 2021 23:13:18 +0200, a ecrit:
> Le 09/05/2021 à 23:09, Samuel Thibault a écrit :
> > Didier Spaier, le dim. 09 mai 2021 23:02:49 +0200, a ecrit:
> > > Still, this could be an issue for audiophiles, but they can use jack.
> >
> > Speech-based screen reading also
Brltty 6.3 on arch linux.
If I set hte preferences menu to
"save on exit: yes"
And then exit the preferences menu, the braille display flashes
"not saved"
what's happening? Permissions problem?
-rw-r--r-- 1 root root 5057 Oct 6 2020 ./lib/brltty/brltty.prefs
Thanks.
Le 09/05/2021 à 23:09, Samuel Thibault a écrit :
Didier Spaier, le dim. 09 mai 2021 23:02:49 +0200, a ecrit:
Still, this could be an issue for audiophiles, but they can use jack.
Speech-based screen reading also requires very low latency to get snappy
feedback.
OK, then does anyone knows
Didier Spaier, le dim. 09 mai 2021 23:02:49 +0200, a ecrit:
> Still, this could be an issue for audiophiles, but they can use jack.
Speech-based screen reading also requires very low latency to get snappy
feedback.
Samuel
___
This message was sent via
Le 09/05/2021 à 22:38, Aura Kelloniemi a écrit :
On 2021-05-09 at 22:28 +0200, Didier Spaier wrote:
> ### In Slint, we want to share audio resources between speech apps that
> ### rely on alsa and other apps that rely on pulseaudio.
> load-module module-alsa-sink device=dmix
>
Dave Mielke, le dim. 09 mai 2021 16:45:26 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2021/05/09 at 22:39 +0200]
>
> >Again, the Braille part is working completely fine.
> >
> >The problem raised here is *speech* only.
>
> I'm being slow on this one. Is what's wanted, when not on a
[quoted lines by Samuel Thibault on 2021/05/09 at 22:39 +0200]
>Again, the Braille part is working completely fine.
>
>The problem raised here is *speech* only.
I'm being slow on this one. Is what's wanted, when not on a terminal window,
that Orca renders the speech but brltty renders the
Dave Mielke, le dim. 09 mai 2021 16:35:27 -0400, a ecrit:
> We didn't consider the possibility that Orca wouldn't be using that brltty's
> brlapi interface.
Again, the Braille part is working completely fine.
The problem raised here is *speech* only.
Samuel
[quoted lines by Christian Schoepplein on 2021/05/09 at 22:04 +0200]
>It would be really cool if you have another idea that could help.
The AtSpi2 screen driver used to have a focus parameter which could contrain it
to terminal windows. We dropped that parameter when brlapi priorities were
Le 09/05/2021 à 21:44, Christian Schoepplein a écrit :
The only reason I am looking for a solution to get brltty with speech support
up and running in the Mate text terminal is that I am looking for a good
altnerative to have a system with full screen reader support for the text
console and
Christian Schoepplein, le dim. 09 mai 2021 21:29:27 +0200, a ecrit:
> There are also other issues and problems with the output of brltty with
> strange behaviour for empty or very long lines or for applications like vim
> where a status line
Note that there is a longstanding bug in libvte
On 2021-05-09 at 13:03 -0400, Dave Mielke wrote:
> Okay. The bit about count actually being meanless when isArray is false
> should probably be formally documented.
+1
> Or, we could change count to something more intuitively obvious like
> arraySize.
+1
Will it then express the maximum
On 2021-05-09 at 21:08 +0200, Didier Spaier wrote:
>
> I always wonder why people do in a graphical environment things more
> easily done
> in a console. Maybe just because that's what they are used to? Granted,
> there
> are things that can't be done in console, but typing commands in a
[quoted lines by Christian Schoepplein on 2021/05/09 at 21:29 +0200]
>OK; then the only solution currently is to use an older brltty version if I
>like to have a setup with speech support enabled for brltty in the Mate
>terminal? Is this right?
Maybe. Another possibility might be to tell Orca
[quoted lines by Christian Schoepplein on 2021/05/09 at 20:59 +0200]
>When I start brltty by typing
>
>brltty -b ba -x a2:type=terminal -N
The lowercase -x option is used to select the screen driver. For example: -xa2
The uppercase -X option is used to set a screen driver parameter. For
Le 09/05/2021 à 20:41, Christian Schoepplein a écrit :
Am 09.05.2021 um 12:10 schrieb Aura Kelloniemi:
Isn't Orca's speech support for terminals better than BRLTTY's? I
believe it
is more featureful, though syncing the braille display with speech
output is
not possible, if Orca does the
[quoted lines by Samuel Thibault on 2021/05/09 at 13:01 +0200]
>Why making the difference? What is the actual benefit here? The more
>subtle we make the API, the less approchable it becomes.
True.
>Really, the original intent was a straightforward:
>
>- if isArray = False, there is just one
Dave Mielke, le dim. 09 mai 2021 05:46:00 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2021/05/09 at 11:36 +0200]
>
> >> Some bindings might wish to use a list rather than an array.
> >
> >If bindings want to return a list, fine for them, "array" is just a word
> >for the brlapi
Hi Samul,
Goodpoint :-).
Then a keyboard command for enablig/disabling that behaviour would be useful.
Regards
Halim
Am 09.05.2021 12:40 schrieb Samuel Thibault :halim.sa...@freenet.de, le dim. 09 mai 2021 12:33:30 +0200, a ecrit:
> just for understanding the reason why should brltty with a2
halim.sa...@freenet.de, le dim. 09 mai 2021 12:33:30 +0200, a ecrit:
> just for understanding the reason why should brltty with a2 screen driver
> read
> widgets outside gnome / xfce /lxde /mate terminal?
Just because it can, which can be useful in case orca crashes.
Samuel
Hi,
just for understanding the reason why should brltty with a2 screen driver read widgets outside gnome / xfce /lxde /mate terminal?
Does atspi provide information from which application the content is comming from?
I would prefer orca to read all thing ousdide terminals and brltty with a2
Hello
On 2021-05-09 at 05:46 -0400, Dave Mielke wrote:
> [quoted lines by Samuel Thibault on 2021/05/09 at 11:36 +0200]
> >> Some bindings might wish to use a list rather than an array.
> >
> >If bindings want to return a list, fine for them, "array" is just a word
> >for the brlapi
On 2021-05-09 at 11:09 +0200, Samuel Thibault
wrote:
> But as I tried to explain in my first mail but apparently completely
> failed: only makes the reading of other widgets *less* prioritized,
> and not completely ignored. For braille that's fine enough since more
> prioritized reading
[quoted lines by Samuel Thibault on 2021/05/09 at 11:36 +0200]
>> Some bindings might wish to use a list rather than an array.
>
>If bindings want to return a list, fine for them, "array" is just a word
>for the brlapi protocol, it can be expressed whichever way is fine for
>bindings.
They may
Dave Mielke, le dim. 09 mai 2021 05:24:11 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2021/05/09 at 11:04 +0200]
>
> >But for all bindings that will be returned as an array of two elements.
>
> I don't think that's a good assumption. Why should we impose constraints on
> any set of
[quoted lines by Samuel Thibault on 2021/05/09 at 11:13 +0200]
>No, please reread tryRestartTerm, it only uses the typeFlags array to
>determine the quality returned by the screen reader. If there is no text
>to read it will return SCQ_NONE indeed since it has nothing to say. But
>if there is
[quoted lines by Samuel Thibault on 2021/05/09 at 11:04 +0200]
>But for all bindings that will be returned as an array of two elements.
I don't think that's a good assumption. Why should we impose constraints on any
set of bindings that can offer a better way? For example, the Java bindings
halim.sa...@freenet.de, le dim. 09 mai 2021 10:19:06 +0200, a ecrit:
> The problem reported is not a speech only problem I think.
It is, because for the braille case only one of the two screen readers
get to show something, while for speech the two get sent to
speech-dispatcher and spoken there.
[quoted lines by halim.sa...@freenet.de on 2021/05/09 at 09:41 +0200]
> Please excuse my bad English :-(. I am new in this list.
New or not, that's an illegal apology. :-) How good or not-so-good any person's
English is isn't an issue. All are welcome and it's our pleasure to be of
whatever
Aura Kelloniemi, le dim. 09 mai 2021 10:48:28 +0300, a ecrit:
> On 2021-05-09 at 09:23 +0200, halim.sa...@freenet.de wrote:
> > Yes, brltty should talk when a user enables speech. But It should _only_
> talk in xfce/mate/gnome terminals and not when
> > using the graphical desktop.
>
> Does it
Dave Mielke, le sam. 08 mai 2021 21:03:30 -0400, a ecrit:
> I think the only thing wrong with the current data is that display size is
> marked as an array. I don't think that's right because the display size is a
> single, two-element value and we should be expecting exactly one (not zero or
>
[quoted lines by halim.sa...@freenet.de on 2021/05/09 at 09:23 +0200]
> Yes, brltty should talk when a user enables speech. But It should
> _only_ talk in xfce/mate/gnome terminals and not when using the
> graphical desktop.
I suppose that, strictly speaking, is a matter of user
Hi
On 2021-05-09 at 09:23 +0200, halim.sa...@freenet.de wrote:
> Yes, brltty should talk when a user enables speech. But It should _only_
> talk in xfce/mate/gnome terminals and not when
> using the graphical desktop.
Does it help if you set
screen-parameters a2:Type=terminal
in your
Hi,
Please excuse my bad English :-(. I am new in this list.
I use brltty last years only for braille in orca.
For plain tty stuff with speech enabled I found some problems which makes things dificult for me.
When I read a man page with info brltty stops speaking when the screen content starts to
Hi Dave,
Yes, brltty should talk when a user enables speech. But It should _only_ talk in xfce/mate/gnome terminals and not when using the graphical desktop.
On my Machine brltty 6.0 is in use in ubuntu 20.04 and that version of brltty works as described.
I think the work on a2 driver in brltty
[quoted lines by Samuel Thibault on 2021/05/08 at 20:29 +0200]
>From: Christian Schoepplein
>To: debian-accessibil...@lists.debian.org
>Subject: Problems when using brltty in the terminal
>Date: Sat, 8 May 2021 16:20:35 +0200
>
>3. Edited the file /etc/X11/Xsession.d/90xbrlapi and removed the
56 matches
Mail list logo
