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

 
Output of file : FONTFILT.MAN contained in archive : CAWF.ZIP


FONTFILT(1) Unix Programmer's Manual FONTFILT(1)


BNBABMBE
fontfilt - font filter for cawf

BSBYBNBOBPBSBIBS
BfBoBnBtBfBiBlBt [ B-Bc IcIoInIfIiIg ] [ B-Bd IdIeIvIiIcIe ] [ B-Bf IfIoInIt ] [ B-Bh ] [ IfIiIlIe(Is) ]

BDBEBSBCBRBIBPBTBIBOBN
IFIoInItIfIiIlIt enhances IcIaIwIf(1) output with device-specific control sequences
that select fonts and display bold and italic characters. (The IcIaIwIf B-BfBe
option must be used to identify bold and italic characters.)

BOBPBTBIBOBNBS
IFIoInItIfIiIlIt options select the configuration file, the device, the font and
the input source.

B-Bc IcIoInIfIiIg
specifies the name of the configuration file. (See the BDBEBVBIBCBEBS BABNBD
BFBOBNBTBS and BCBOBNBFBIBGBUBRBABTBIBOBN BFBIBLBE sections for more information.)

B-Bd IdIeIvIiIcIe
specifies the printer output device. The default is the name of the
last device in the configuration file, usually ``ansi''.

B-Bf IfIoInIt
specifies the desired printer font name. The default is device
specific.

B-Bh requests a usage information display (help) that includes a list of
the devices and fonts that are supported.

IfIiIlIe(Is)
specify the paths to IcIaIwIf output files.

BDBEBVBIBCBEBS BABNBD BFBOBNBTBS
The devices and fonts that IfIoInItIfIiIlIt supports are defined in a
configuration file. The default configuration file is named IfIoInItIfIiIlIt.IcIf
and is located in Ic:/IsIyIs/IlIiIb/IcIaIwIf (the author's MS-DOS environment
default).

The IfIoInItIfIiIlIt.IcIf configuration file of this distribution defines the
following devices and fonts. Use the B-Bh option to see the definitions of
your active configuration file. (The first font named in the following
listing and in the B-Bh display is the default for the device.)

ansi ANSI terminal display
(ANSI.SYS driver required for MS-DOS)
Italic: Underscore
Fonts: none

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






May, 1991 1



FONTFILT(1) Unix Programmer's Manual FONTFILT(1)


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

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

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

vgamono VGA monochrome monitor for MS-DOS
(ANSI.SYS driver required for MS-DOS)
Italic: Reverse-video
Fonts: none

BEBXBABMBPBLBEBS
The IcIaIwIf invocation must use its B-BfBe option. The following example
selects the 12 CPI Prestige font on a Panasonic KX-P1180 printer.

cawf -fe -man cawf.1 | fontfilt -d kxp1180 -f p12

The following example selects the 12 CPI Letter Gothic font on an HP
LaserJet III printer.

cawf -fe -man cawf.1 > lj3.tmp
fontfilt -dlj3 -flg12 lj3.tmp > lpt1:

BCBOBNBFBIBGBUBRBABTBIBOBN BFBIBLBE
IFIoInItIfIiIlIt searches for its configuration file in Ic:/IsIyIs/IlIiIb/IcIaIwIf (the
author's MS-DOS environment default). This default can be overridden by
the CAWFLIB environment variable, or changed in the source code.

The configuration file has a simple format that conforms to the following
rules.

1. Lines that begin with a pound sign (`#') a space or are zero in
length are ignored.

2. Lines that begin with an alphabetic character name a device.

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


May, 1991 2



FONTFILT(1) Unix Programmer's Manual FONTFILT(1)


by a single character defining the type of definition, followed by
an equal sign (`=').

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.)

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.)

The first font definition for a device is assumed to be the default
font for the device.

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).

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'.

# 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


BSBEBE BABLBSBO
bsfilt(1), cawf(1) and nroff(1).

BDBIBABGBNBOBSBTBIBCBS
Diagnostic messages are delivered to the standard error file.

BHBIBSBTBOBRBY
IFIoInItIfIiIlIt was written by Vic Abell, . Chet
Creider had the idea for it and provided some
device-specific prototypes, adapted from the IrIo work of Ted A. Campbell.
(Campbell's IrIo is based on ROFF4.)







May, 1991 3



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

  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/