From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fax problem
Date: Sat, 2 Jun 2001 12:58:13 -0400 [thread overview]
Message-ID: <20010602165814.EC2EB199E4@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
I'm currently using:
# convert to g3
g3files=()
a=1
for(i in $infiles){
switch(`{file <$infiles(1)}){
case *:*g3* *:*fax*
g3files=($g3files $i)
case *:*postscript
gs -dSAFER '-sDEVICE=dfaxlow' '-sOUTPUTFILE='$tmp'.'$#a'.%03d' -dNOPAUSE -dQUIET $i quit.ps
g3files=($g3files $tmp.$#a.*)
case *
lp -dstdout $i > $tmpps
gs -dSAFER '-sDEVICE=dfaxlow' '-sOUTPUTFILE='$tmp'.'$#a'.%03d' -dNOPAUSE -dQUIET $tmpps quit.ps
g3files=($g3files $tmp.$#a.*)
}
a=($a $a)
}
[-- Attachment #2: Type: message/rfc822, Size: 2177 bytes --]
From: Richard Miller <miller@hamnavoe.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fax problem
Date: Sat, 2 Jun 2001 14:57:59 0100
Message-ID: <E156Bx3-000L0O-0K@tele-post-20.mail.demon.net>
If we're going to fix fax, we might as well also handle the general
case of faxing multiple files of different type. How about replacing
the switch(`{file $infiles(1)}) statement -- which only checks the type
of the first file -- with something like this:
# convert to g3
g3files=()
ntmp=1
for (infile in $infiles) {
otmp=$tmp.$ntmp
ntmp=`{echo $ntmp+1 | hoc}
switch(`{file <$infile}){
case *g3* *fax*
g3files=($g3files $infile)
case postscript
gs -dSAFER '-sDEVICE=dfaxlow' '-sOUTPUTFILE='$otmp.'.%03d' -dNOPAUSE -d QUIET $infile quit.ps
g3files=($g3files $otmp.*)
case *
lp -dstdout $infile > $tmpps
gs -dSAFER '-sDEVICE=dfaxlow' '-sOUTPUTFILE='$otmp'.%03d' -dNOPAUSE -dQUIET $tmpps quit.ps
g3files=($g3files $otmp.*)
}
}
-- Richard
next reply other threads:[~2001-06-02 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 16:58 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-02 13:57 Richard Miller
2001-06-01 13:09 Richard Miller
2001-05-31 22:43 William Staniewicz
2001-05-31 21:07 presotto
2001-05-31 21:06 Russ Cox
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=20010602165814.EC2EB199E4@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).