ctrl-alt-backspace made the message disappear and now this window appears to
be working.
Thanks.
Chris
On Sat, 8 Sep 2007, Samuel Thibault wrote:
Hi,
Christopher Gray, le Fri 07 Sep 2007 17:11:01 -0700, a écrit :
I'm not as conversant as I need to be with Linux terminology yet. In
Ubuntu
Hi,
Christopher Gray, le Fri 07 Sep 2007 17:11:01 -0700, a écrit :
> I'm not as conversant as I need to be with Linux terminology yet. In
> Ubuntu terms, brltty operates fine when I go to a command line, console I
> believe, with alt+ctrl+f2.
alt-ctrl-f1 to f6 are the linux text console.
alt-c
Hi Samuel:
I'm not as conversant as I need to be with Linux terminology yet. In Ubuntu
terms, brltty operates fine when I go to a command line, console I believe, with
alt+ctrl+f2. It gives the error message when I go to a full screen command
prompt, alt+ctrl+f7. Hope this is of some help a
Christopher Gray, le Fri 07 Sep 2007 16:26:37 -0700, a écrit :
> It is at a command line prompt that I get this "not in text mode" error. I
> hope
> this is helpful information.
What do you mean by "at a command line prompt"? A gnome-terminal as
opposed to any other gnome widget, or something
On Sat, 8 Sep 2007, Mario Lang wrote:
> On Debian, I can just enable automatic startup of Orca for my specific user
> that I use for GNOME and everything works just fine after login, no need
> to manually start it. I guess this should actually work on Ubuntu as well.
I tried this on Ubuntu and G
Christopher Gray <[EMAIL PROTECTED]> writes:
> On Fri, 7 Sep 2007, Dave Mielke wrote:
>
>> Is this perhaps a symptom of starting brltty after the X screen reader? Maybe
>> it doesn't try to reconnect.
>
> I don't think so, but wouldn't say for certain. The reason I am doubting
> this
> is that
On Fri, 7 Sep 2007, Dave Mielke wrote:
> Is this perhaps a symptom of starting brltty after the X screen reader? Maybe
> it doesn't try to reconnect.
I don't think so, but wouldn't say for certain. The reason I am doubting this
is that the screenreader must be started by hand right now in Ubunt
Hi Mario:
I followed the Orca instructions for braille, and near the end of them a
command
is given
from Python; something about "import brltty". That command gives me no errors.
For that reason partly, I believe the answer to your question is "yes".
Also, braille is working with orca, at le
Christopher Gray <[EMAIL PROTECTED]> writes:
> I have 3.8 working now in a terminal window. However, when I go to a
> full-screen session, alt+ctrl+f7 in Ubuntu, I get the message "not in text
> mode". Is their a cure for this?
That depends if you are already logged in to GNOME or not.
I have
[quoted lines by Christopher Gray on 2007/09/07 at 15:33 -0700]
>If you're agreeable, I'll write Janina a note and I feel certain she'd work
>with
>you to resolve the problem.
Sure. I like to see problems fixed.
>It's not free, however. $40.00, US.
With ten (of thirteen) children still at
Hi Dave:
Yes, ttsynth uses IBM's viavoice. It is available from Capital Accessibility.
If you're agreeable, I'll write Janina a note and I feel certain she'd work
with
you to resolve the problem. It's not free, however. $40.00, US.
I have 3.8 working now in a terminal window. However, when
[quoted lines by Christopher Gray on 2007/09/07 at 12:53 -0700]
>I seem to have contracted a problem with speech.c. Perhaps it is caused by
>my installation of ttsynth, but I'm not sure.
What's ttsynth? Is it by any chance a descendant of IBM's older ViaVoice
synthesizer?
Brltty is trying to
Hmmm, that's interesting. In ttsynth in order to get it to make properly, I
had to link a directory that allows ttsynth_say to find eci.h. The instruction
and link command
for ttsynth is:
create a symbolic link to /opt/IBM/ibmtts/inc/eci.h in the ttsynth-say
directory: ln -sf /opt/IBM/ibm
Christopher Gray, le Fri 07 Sep 2007 12:53:00 -0700, a écrit :
> gcc -Wall -g -O2 -I. -I./../.. -I. -I../.. -D_POSIX_C_SOURCE=2
> -D_BSD_SOURCE -D_XOPEN_SOURCE=500 -DHAVE_CONFIG_H -fPIC
> '-DDRIVER_NAME=ViaVoice' '-DDRIVER_CODE=vv' '-DDRIVER_COMMENT="text to
> speech engine"' '-DDRIVER_VERSION="
Hello:
I seem to have contracted a problem with speech.c. Perhaps it is caused by my
installation of ttsynth, but I'm not sure.
Thanks for any advice.
Here is the error generated by make.
gcc -Wall -g -O2 -I. -I./../.. -I. -I../.. -D_POSIX_C_SOURCE=2 -D_BSD_SOURCE -D_XOPEN_SOURCE=500
-DHAV
15 matches
Mail list logo
