Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!gem.mps.ohio-state.edu!unix.cis.pitt.edu!brutus.cs.uiuc.edu!uakari.primate.wisc.edu!xanth!mcnc!thorin!prins.cs.unc.edu!prins
From: prins@prins.cs.unc.edu (Jan Prins)
Newsgroups: comp.lang.apl
Subject: Re: X11 for APL
Message-ID: <10815@thorin.cs.unc.edu>
Date: 29 Nov 89 22:30:11 GMT
References: <2789@water.waterloo.edu>
Sender: news@thorin.cs.unc.edu
Reply-To: prins@prins.cs.unc.edu (Jan Prins)
Organization: UNC Chapel Hill Computer Science Department
Lines: 18

AT UNC we use STSC's APL*PLUS/UNX interpreter which supports a large
variety of terminal types via flexible input and output mappings.

STSC supplied us with X11 APL fonts that can be used with xterm and a
suitably arranged output mapping to yield an APL window.  The plain MIT
X11R3 xterm actually requires two fonts (-fn and -fb) to support all the
APL characters and overstrikes (recall quad-AV has 256 elements); 
DECwindows supports 8-bit character codes and hence dxterm can be used 
with a single font and a simpler mapping.

With this arrangement any workstation running X can host an APL window 
even though the interpreter, in general, runs on a different machine.

Regards,

Jan Prins (prins@cs.unc.edu)
Dept. of Computer Science
UNC Chapel Hill