02.07.2013 Views

A/UX® Programmer's Reference Sections

A/UX® Programmer's Reference Sections

A/UX® Programmer's Reference Sections

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

nterm(5) nterm(5)<br />

NAME<br />

nterm- terminal driving tables for nroff<br />

DESCRIPTION<br />

nroff(l) uses driving tables to customize its output for various<br />

types of output devices, such as printing terminals, special word<br />

processing terminals (such as Diablo, Qume, or NEC Spinwriter<br />

mechanisms), or special output filter programs. These driving<br />

tables are written as ASCII files, and are installed in<br />

/usr / lib/nterm/tab. name, where name is the name for<br />

that terminal type as given in term(5).<br />

1<br />

The first line of a driving table should contain the name of the terminal:<br />

simply a string with no embedded white space. "white<br />

space" means any combination of spaces, tabs and new lines. The<br />

next part of the driver table is structured as follows:<br />

bset [integer] (not supported in all versions of nroff)<br />

breset [integer] (not supported in all versions of nroff)<br />

Hor [integer]<br />

Vert [integer]<br />

Newline [integer]<br />

Char [integer]<br />

Em [integer]<br />

Halfline [integer]<br />

Adj [integer]<br />

twini t [character-string]<br />

twrest [character-string]<br />

t wnl [character-string]<br />

hI r [character-string]<br />

hlf [character-string]<br />

fIr [character-string]<br />

bdon [character-string]<br />

bdoff [character-string]<br />

i ton [character-string]<br />

i toff [character-string]<br />

ploton [character-string]<br />

plotoff [character-string]<br />

up [character-string]<br />

down [character-string]<br />

right [character-string]<br />

left [character-string]<br />

February, 1990<br />

Revision C

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!