automated nfbtrans; was Re: Continuous speaker beep (fwd)

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

 



Sorry; I've been replying to the wrong message and my nfbtrans comments
were going out as "continuous beep" comments.
Must be time to quit!!!
so here's the latest under the right subject heading.

-- 
Cheryl

---------- Forwarded message ----------
Date: Sun, 7 Sep 2003 13:59:56 -0500 (CDT)
From: Cheryl Homiak <chomiak@xxxxxxxxxxxxx>
To: speakup <speakup at braille.uwo.ca>
Subject: Re: Continuous speaker beep

Ok, found a much simpler way to do this, not using expect. Oh well, but I
did learn a lot playing around with expect.
The only drawback is that I haven't found a way from the command line or
the nfbtrans.cnf file to have a wild card for the output file; you can use
*.brf for your input file but all those files will be written together to
one *.txt file.
So I did the following:

(1) added or edited the following in /usr/local/lib/nfbtrans.cnf

# set translation mode to back-translate by default
tm=3
# automatic  .txt output file for .brf input file
on=2
# eliminates prompt for a file being overwritten
ow=1
# stops most progress output;  shows current output file
qm=1

Then I ran the following short script:

for i in *.brf
do
nfbtrans $i
done
exit 0


-- 
Cheryl




[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux