From: Buddy Brannan <davros@ycardz.com>
To: speakup@braille.uwo.ca
Subject: Re: Web Braille
Date: Fri, 31 May 2002 10:57:41 -0400 [thread overview]
Message-ID: <20020531145741.GA32248@kb5elv> (raw)
In-Reply-To: <Pine.LNX.4.44.0205311005500.1445-100000@toccata.rednote.net>
Here's the relevant section from the NFBTrans readme:
Unzip nfbtrans into an empty directory. From the unix shell type
mv MAKEFILE Makefile
Then enter
make lowercase
This is necessary because the program files were zipped in MSDOS and the
file names are in upper case when unzipped in unix. Files specifically for
the MSDOS version are also removed at this time.
Compile nfbtrans by entering make target where target is ultrix, linux,
sunos, djgpp, or aix. You will have to add the target for your machine to
makefile if it is not one of these. The termcap entry in
the LIB= statement may need to be removed in linux. When the compile is
successful, copy nfbtrans to usually /usr/local/bin and set permissions
usually chmod 755 nfbtrans. Copy nfbtrans.cnf, back.tab, english.dic, spell.dat
and braille.tab to /usr/local/lib. Edit nfbtrans.cnf and change options if
necessary.
You may have to change permissions on the files you've copied into
/usr/local/lib. I recall having some sort of problem the first time I
set up NFBTrans, but I can't remember the nature of them. Anyway, it
works great under Linux.
--
Buddy Brannan, KB5ELV/3 | I choose you to take up all of my time.
Email: davros@ycardz.com | I choose you because you're funny and kind
| I want easy people from now on.
| --the Nields
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Steve Holmes
` Ryan Mann
` Igor Gueths
` Buddy Brannan
` Cheryl Homiak
` jwantz
` Janina Sajka
` Buddy Brannan [this message]
` Steve Holmes
` Cheryl Homiak
` Ed Barnes
` Buddy Brannan
` Steve Holmes
` Cheryl Homiak
` Saqib Shaikh
` Steve Holmes
` Ann Parsons
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=20020531145741.GA32248@kb5elv \
--to=davros@ycardz.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).