home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Dream 44
/
Amiga_Dream_44.iso
/
RiscPc
/
Utils
/
man_nroff.tgz
/
man_tar
/
!man.ReadME
< prev
Wrap
Text File
|
1995-10-07
|
3KB
|
98 lines
CAWF a.k.a. NROFF
-----------------
This is a quick and dirty port of 'cawf' that came from Simtel20
This implements an 'nroff' and 'man' function that runs under RISCOS.
Two invocations are possible
Once the filer has seen !man then any files in the !man.1 directory
can be read by typing
man subject
Or double clicking any file of type ManPages (100)
The man pages are in subdirectory '1'
CHANGING FILE TYPE USED
-----------------------
If you want to alter the file type, the !sprites file and the !boot
file need changing to refer to the correct file type.
To change to file type XXX
The Boot file is :
set Cawf$path <obey$dir>.
iconsprites cawf:!Sprites
set alias$man run cawf:man %*0
set file$type_100 ManPages
set alias$@RunType_100 taskwindow -quit "cawf:cawf -man -dNONE %%0"
Change the two 100's i to XXX n this file
and rename the sprites file_100 and small_100 to file_XXX and small_XXX
in !Sprites.
OTHER USES
----------
The 'nroff' program itself is called 'cawf' (see the cawf ManPages file)
and can be invoked independently.
Then it will also format to 1st word plus files
(this prints via Acorn drivers )
cawf -man -dacorn manfile > printer:
Or:
cawf -man -dacorn manfile > FWP_file
Will produce bold and underline in a FirstWord Plus File (for e.g. Ovation)
Look in cawf:lib.device/cf on how to add devices
CREDITS
-------
For RISCOS port:
Mike James <mike@hamble.demon.co.uk>
Thats me. Full of Pouilly-FumΘ and happy for it.
For cawf:
/*
* Copyright (c) 1991 Purdue University Research Foundation,
* West Lafayette, Indiana 47907. All rights reserved.
*
* Written by Victor A. Abell <abe@mace.cc.purdue.edu>, Purdue
* University Computing Center. Not derived from licensed software;
* derived from awf(1) by Henry Spencer of the University of Toronto.
*
* Permission is granted to anyone to use this software for any
* purpose on any computer system, and to alter it and redistribute
* it freely, subject to the following restrictions:
*
* 1. The author is not responsible for any consequences of use of
* this software, even if they arise from flaws in it.
*
* 2. The origin of this software must not be misrepresented, either
* by explicit claim or by omission. Credits must appear in the
* documentation.
*
* 3. Altered versions must be plainly marked as such, and must not
* be misrepresented as being the original software. Credits must
* appear in the documentation.
*
* 4. This notice may not be removed or altered.