Category : Word Processors
Archive   : CAWF.ZIP
Filename : FONTFILT.1

 
Output of file : FONTFILT.1 contained in archive : CAWF.ZIP
.\" manual page for fontfilt(1)
.TH FONTFILT 1 "May, 1991"
.SH NAME
fontfilt \- font filter for cawf
.SH SYNOPSIS
.B fontfilt
[
.BI \-c " config
] [
.BI \-d " device
] [
.BI \-f " font
] [
.B \-h
] [
.I file(s)
]
.SH DESCRIPTION
.I Fontfilt
enhances
.IR cawf (1)
output with device\-specific control sequences that select
fonts and display bold and italic characters.
(The
.I cawf
.B \-fe
option must be used to identify bold and italic characters.)
.SH OPTIONS
.I Fontfilt
options select the configuration file, the device, the font and the
input source.
.TP
.BI \-c " config
specifies the name of the configuration file.
(See the
.B "DEVICES AND FONTS
and
.B "CONFIGURATION FILE
sections for more information.)
.TP
.BI \-d " device
specifies the printer output device.
The default is the name of the last device in the configuration
file, usually ``ansi''.
.TP
.BI \-f " font
specifies the desired printer font name.
The default is device specific.
.TP
.BI \-h
requests a usage information display (help) that includes a list of
the devices and fonts that are supported.
.TP
.I file(s)
specify the paths to
.I cawf
output files.
.SH DEVICES AND FONTS
The devices and fonts that
.I fontfilt
supports are defined in a configuration file.
The default configuration file is named
.I fontfilt.cf
and is located in \fIc:/sys/lib/cawf\fR (the author's MS\-DOS
environment default).
.LP
The
.I fontfilt.cf
configuration file of this distribution defines the following devices
and fonts.
Use the
.B \-h
option to see the definitions of your active configuration file.
(The first font named in the following listing and in the
.B \-h
display is the default for the device.)
.LP
.ta \w'kxp1180'u+3n +\w'Italic:'u+3n +\w'bps10'u+6n
.nf
.ne 4
ansi ANSI terminal display
(ANSI.SYS driver required for MS\-DOS)
Italic: Underscore
Fonts: none

.ne 3
epson dot matrix printer in Epson FX-86e/FX-800 mode
Bold: Double-strike
Fonts: none

.ne 4
ibmppds IBM Personal Printer Data Stream (PPDS) protocol
Bold: Double-strike
Italic: Underline
Fonts: none

.ne 10
kxp1180 Panasonic KX\-P1180 dot matrix printer in PGM mode
Bold: Emphasized
Fonts: c10 10 Characters Per Inch (CPI) Courier
c12 12 CPI Courier
bps10 10 CPI Bold PS
bps12 12 CPI Bold PS
p10 10 CPI Prestige
p12 12 CPI Prestige
ss10 10 CPI Sans Serif
ss12 12 CPI Sans Serif

.ne 6
lj3 HP LaserJet III
Fonts: c10 10 point, 12 Characters Per Inch (CPI)
Courier
c12ibm 12 point, 10 CPI Courier, IBM\-PC
Symbol Set
lg12 12 point, 12 CPI Letter Gothic

.ne 4
vgamono VGA monochrome monitor for MS\-DOS
(ANSI.SYS driver required for MS\-DOS)
Italic: Reverse-video
Fonts: none
.SH EXAMPLES
The
.I cawf
invocation must use its
.B \-fe
option.
The following example selects the 12 CPI Prestige font on a
Panasonic KX-P1180 printer.
.IP
cawf -fe -man cawf.1 | fontfilt -d kxp1180 -f p12
.LP
The following example selects the 12 CPI Letter Gothic font on an
HP LaserJet III printer.
.IP
cawf -fe -man cawf.1 > lj3.tmp
.br
fontfilt -dlj3 -flg12 lj3.tmp > lpt1:
.SH CONFIGURATION FILE
.I Fontfilt
searches for its configuration file in \fIc:/sys/lib/cawf\fR (the
author's MS\-DOS environment default).
This default can be overridden by the CAWFLIB environment variable,
or changed in the source code.
.LP
The configuration file has a simple format that conforms to the
following rules.
.TP
1.
Lines that begin with a pound sign (`#') a space or are zero in length
are ignored.
.TP
2.
Lines that begin with an alphabetic character name a device.
.TP
3.
Device lines may be followed by lines that define the device escape
control sequences for bold, italic and Roman characters, or font
definitions.
These definition lines must begin with a TAB, followed by a single
character defining the type of definition, followed by an equal
sign (`=').
.TP
4.
The bold, italic and Roman definition types are `b', `i' and `r'.
An equal sign follows the single type character, and the device
escape control sequence follows it.
(See rule 6 for a description of the encoding of the control
sequence.)
.TP
5.
The font definition type is `f'.
It's followed by an equal sign, the name of the font (it must not
include an equal sign); another equal sign, terminating the font
name; and after the second equal sign, the device control sequence
to make the font active.
(See rule 6 for a description of the encoding of the control
sequence.)
.IP
The first font definition for a device is assumed to be the default
font for the device.
.TP
6.
All characters following the equal sign up to the terminal end\-of\-line
character are part of an escape control sequence.
The sequence may contain any printable ASCII characters.
Non\-printable characters can be encoded in octal with the `\\nnn'
form, or in hexadecimal with the `\\xnn' form.
The special code, `\\E' or `\\e' represents the ESC control character,
octal 033 (hexadecimal 1b).
.LP
Here's an example showing the definition for the HP LaserJet III.
All of its non\-printable characters are ESC's; the first is coded with
the octal form (`\\033'); the second, with `\\E'; the rest, with the
hexadecimal form `\\x1b'.
.DS
# HP LaserJet III

lj3
b=\\033(s7B
i=\\E(s1S
r=\\x1b(s0B\\x1b(s0S
f=c10=\x1b&l0O\x1b(8U\x1b(s0p12h10v0s0b3T
f=c12ibm=\x1b&l0O\x1b(10U\x1b(s0p10.00h12.0v0s0b3T
f=lg12=\x1b&l0O\x1b(8U\x1b(s12h12v0s0b6T
.DE
.SH SEE ALSO
bsfilt(1), cawf(1) and nroff(1).
.SH DIAGNOSTICS
Diagnostic messages are delivered to the standard error file.
.SH HISTORY
.I Fontfilt
was written by Vic Abell, .
Chet Creider had the idea for it and provided
some device\-specific prototypes, adapted from the
.I ro
work of Ted A. Campbell.
(Campbell's
.I ro
is based on ROFF4.)


  3 Responses to “Category : Word Processors
Archive   : CAWF.ZIP
Filename : FONTFILT.1

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/