public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Whapples <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Features after users guide publication
Date: Sun, 04 Mar 2007 10:27:31 +0000	[thread overview]
Message-ID: <BAY103-DAV58E209C2146B8A4D252748E850@phx.gbl> (raw)
Message-ID: <1173003851.2904.45.camel@layla> (raw)
In-Reply-To: <001001c75e07$45a45c90$0301a8c0@cleverson>

I will answer your questions amongst the questions in your original
message (read on).
On Sat, 2007-03-03 at 23:41 -0300, Cleverson wrote:
> Hello all
> 
> I've read at speech-dispatcher docs that Speakup has a "read all" command, 
> but I didn't find any mention about this in the Speakup users guide.
> 
> In addition, when I press the keypad * while using Speakup, there is four 
> options rather than the two mentioned in the users guide, "cursoring on" and 
> "cursoring off".
> The other two highlight tracking, tries to follow the highlight and speak that, while the other read window allows you to define a rectangle "window" which speakup will monitor and speak changes (eg. if a program has a bar showing the current selected item's name, then use this to get the selected item's name spoken). The different settings work well for different programs.

> So I ask:
> 
> 1. In case Speakup users guide is really out of date, how do I proceed to 
> get Speakup current version and read its change log? My distro is Gentoo.
> Well the user guide is up to date for the current release version, but as the next answer will tell you, you may be using a later version still. I don't know where gentoo will put that documentation, hopefully someone will be able to anser that.

> 2. There are some features I would like to suggest, but perhaps it's better 
> to first update my Speakup and get aware of its current status. Is Speakup 
> still in development?
> Yes it is still in development, continual development, but as you are able to use the very latest development code, then try it. This will probably mean you will need to use the standard kernel source rather than the gentoo kernel source (as I remember even their vanilla kernel source which is meant to be it before any modifications seemed to be slightly different preventing speakup patching from CVS). I can't remember how you tell gentoo that you will manage a package yourself as it has been some time since I have used gentoo.

> Many thanks for infos
> 
> Cleverson
> 
> "Be realistic; ask for the impossible." 
> 
> 
>       
> _______________________________________________________ 
> Yahoo! Mail - Sempre a melhor opção para você! 
> Experimente já e veja as novidades. 
> http://br.yahoo.com/mailbeta/tudonovo/
>  
> 
> 
> 




  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cleverson
     [not found] ` <1173003851.2904.45.camel@layla>
   ` Michael Whapples [this message]
     ` Cleverson
     [not found]       ` <1173031866.2904.93.camel@layla>
         ` Michael Whapples
           ` Zachary Kline
     [not found]             ` <1173048155.2904.108.camel@layla>
               ` Michael Whapples
 ` Gene Collins
   ` Zachary Kline
     ` Cleverson
     ` Gene Collins
       ` Erik Heil

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=BAY103-DAV58E209C2146B8A4D252748E850@phx.gbl \
    --to=mwhapples@aim.com \
    --cc=speakup@braille.uwo.ca \
    /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).