From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: embossing files
Date: Sun, 16 Mar 2003 21:11:29 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303162109030.8236-100000@igueths> (raw)
Hi all. How would I go about go about embossing translated files I
translated with nfbtrans? I tried catting the file to /dev/lp0 but the
Blazer didn't start embossing. Do I need to send it some handshake
sequence for it to start printing? Has anyone gotten this to work if so
how? Thanks!
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
next reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths [this message]
` Chuck Hallenbeck
` Ann Parsons
igueths
` Chuck Hallenbeck
igueths
` Igor Gueths
` Chuck Hallenbeck
Igor Gueths
` Adam Myrow
igueths
` Gregory Nowak
` Luke Davis
` Igor Gueths
` Luke Davis
` Igor Gueths
` Igor Gueths
` Adam Myrow
` Gregory Nowak
` Igor Gueths
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=Pine.LNX.4.44.0303162109030.8236-100000@igueths \
--to=igueths@attbi.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).