public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Christian Schoepplein <mail@schoeppi.net>
To: blinux-list@redhat.com
Subject: Re: Comparing Brltty and Suse
Date: Wed, 26 Jun 2002 17:21:32 +0200	[thread overview]
Message-ID: <20020626152132.GA1241@athlon.bliz> (raw)
In-Reply-To: <Pine.LNX.4.44.0206260819270.17416-100000@Jumbo>

Hello!

On Mit, Jun 26, 2002 at 08:21:35 -0500, John J. Boyer wrote:
> Ok. So let's have a comparison of brltty and suse from people who have 
> tried both. I have never had to set attributes for a particular program, 
> so I wondeer if this feature is really very useful.
> John

I Think this feature is very usefull! Rreading out the attributes of a 
screen and pipe them into programm that can handel them and react 
in some way brings up a higher flexibility. Suse-Blinux reads out for 
example the color or a underlined part on the screen and in a profile you 
can tell the screenreader, what to do with this things. That makes it very 
easy to work with programms like mc or the configurationstool of SuSE 
called yast2, you can underline links in a browser or take a look at a 
statusline and when it changes it comes up on the brailledisplay. 
Attributes are also good for the speechoutput. Only the "interesting" 
things on the screen are outputet of the speechsynth.

Best regards,
Schoeppi

-- 
Christian Schoepplein    | http://www.lily-rockt.de
mail@schoeppi.net        | http://www.lavish.de




  parent reply	other threads:[~ UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John J. Boyer
 ` Nath
   ` Mario Lang
     ` Boris DAIX
       ` Dave Mielke
         ` Boris DAIX
       ` Mario Lang
         ` Boris DAIX
     ` Nath
       ` Mario Lang
 ` Christian Schoepplein [this message]
   ` John J. Boyer

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=20020626152132.GA1241@athlon.bliz \
    --to=mail@schoeppi.net \
    --cc=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).