[net.text] neqn and diablo solution

dfh@scirtp.UUCP (David F. Hinnant) (06/14/86)

 Thanks to all who responded to my problem concerning neqn and the 
diablo 630.  First, the correct way to do what I want to do is to use
the 450 terminal description:

  (1)	neqn foo.mm | nroff -T450 | lpr

My problem is that under our version of UNIX (INTERACTIVE Systems
"IN/ix"), the diablo printer spooler mechanism "knows" about the default
Teletype escape sequences and converts them automagicly to diablo
escape sequences.  This means that normally when I say:

  (2)	neqn foo.mm | nroff | lpr

I get reasonable output on the diablo (super and sub scripts), but no
simulated greek characters.

Because the diablo printer driver "back end" "knows" about the old
Teletype 37 (I think that's the right number), it somehow munges the 
diablo escape sequences I get by (1), and I get nonsense for output.

Options I considered:

  a) Use a different "back end" driver.

I read the INtext documentation and couldn't easily see how to turn off
the Teletype translation.

  b) Hook the printer up to a spare port and send the file directly
without using a "back end".

This is easier said than done.  The 630 is set for EOB/ACK 
protocol which the "back end" uses.  Changing the dip switches to
start/stop is no easy task, and I would have to do it every time I want
to generate output, and then change them back. The switches are on the
main circuit board, well hidden from easy access.

My appeal:

Can someone at INTERACTIVE or someone who uses IN/ix tell me how to tell
the "back end" driver NOT to try to interpret the control codes in the
print file to Teletype codes, but let them go on by?  This way I could
have a different "back end" option and use the existing printer/back end
configuration.


-- 
				David Hinnant
				SCI Systems, Inc.
				...{decvax, akgua}!mcnc!rti-sel!scirtp!dfh