Re: [orca-list] Continual reading problem



As an in-the-meantime workaround, is there any chance you could locally
do a find and replace to convert the newlines to spaces? Mind you, I'm
not saying we shouldn't see if there's a good solution I can put in
Orca. Just that you seem to have a possibly unique and definitely
annoying problem, and a timely fix seems desirable.

On Mon, 2022-01-17 at 18:33 +0100, Vojtech šmiro via orca-list wrote:
OK, bud what about books with enters after words, not spaces? I
cannot 
read with this.

Vojta.

Dne 17. 01. 22 v 16:49 Milton napsal(a):
Hi,

I like the way Orca is currently reading, I clearly can hear when
Orca 
reads a list.

Milton

Op 17-01-2022 om 15:13 schreef Joanmarie Diggs:
Hi Vojta, all.

I can confirm what you're seeing. I did a quick test in Gedit.

What Orca does is ask the app/toolkit for the current sentence,
then
the next, then the next, etc. Gtk (and possibly other toolkits)
is
treating a newline as a sentence end. I can see how that would be
annoying. However, just ignoring what Gtk (and possibly others)
report
as a sentence might lead to undesired SayAll behavior elsewhere.
For
instance, what if the text is not a book, but list of items, one
per
line? If  Orca combined all that into a single SayAll sentence,
it
might sound like gibberish. So we need to find a way to reliably
identify when a newline character is a sentence boundary versus
when it
isn't -- despite what the app or toolkit tells us.

Suggestions welcomed.
--joanie

On Sat, 2022-01-15 at 13:56 +0100, Vojtech šmiro via orca-list
wrote:
Hello,

by sentence.

Best regards

Vojta.

Dne 15. 01. 22 v 13:37 Joanmarie Diggs napsal(a):
Are you doing say all by line or by sentence (in your Orca
prefs)?
--joanie

On Sat, 2022-01-15 at 12:33 +0100, Vojtech šmiro via orca-
list
wrote:
Hello,

I have the following problem with continual reading of some
texts.

I am registered in library for the visually impaired
persons.
There
are
scanned books from volunteers, but some books have problem.
Some
words
are divided not by space, but by enter key. I will write
you
example.

Begin of the example
This is a test. In this test I will
show you, how are books
wrote.
End of the example

Windows users don't have problems with this. But Orca makes
really
long
space, when is enter key after words, not space. Please, is
some
way
to
repair it? Windows screenreaders ignores enters and don't
do that
long
space during reading.

Thanks a lot.

Best regards

Vojta.
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation:
https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html

_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: 
https://help.gnome.org/users/gnome-help/stable/a11y.html

_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]