ftp.nice.ch/pub/next/text/rtf/RTF.1.10.s.tar.gz#/rtf/rtf2troff

Imakefile
 
Makefile
 
README
 
dwbtroff-map
 
groff-map
 
nwidth.trf
 
rtf2groff.sh
[View rtf2groff.sh] 
rtf2troff.c
[View rtf2troff.c] 
rtf2troff.h
[View rtf2troff.h] 
trf-flush.c
[View trf-flush.c] 
trf-mac.c
[View trf-mac.c] 
trf-nwid.c
[View trf-nwid.c] 
trf-stack.c
[View trf-stack.c] 
trf-table.c
[View trf-table.c] 
trf-unix.c
[View trf-unix.c] 
trf-writer.c
[View trf-writer.c] 
troff-man-map
 
troff-map
 
troff-me-map
 
troff-mm-map
 
troff-ms-map
 
troff-symbol-map
 
xroff-map
 

README

Output sequences in output maps are subject to uppercasing.  However, it's
assumes that sequences beginning with \ need to be left as is.  This means
that if a sequence begins with something other than \ and needs to be left
as is, rewrite it to begin with \&.

It's probably easiest to begin a new map for a troff version by copying
and modifying an existing one.  To test your output sequences, prepend
".nf" to your map, run it through your troff, and examine the result.
This will show you quickly which entries are okay and which are not.  Some
sequences will print correctly, others may disappear from the output (so
they're incorrect), and others may print incorrectly (incorrect also).

You should also test for missing entries by generating some RTF strikes
in the util directory.  Run them through rtf2troff and look at the result,
e.g.,:

	% rtf2troff ../util/ansi.rtf > junk

Look through junk for instances of ``[[name]]''. ``name'' shows you
which standard character has no entry in your output map.

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.