From npn@sirius.att.com Thu Mar 21 18:47:04 1991
Received: from att.att.com by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA12633; Thu, 21 Mar 91 18:47:04 +0100
Message-Id: <9103211747.AA12633@dkuug.dk>
From: npn@sirius.att.com
Date: Thu, 21 Mar 91 10:49 EST
Original-From: sirius!npn (Nils-Peter Nelson +1 908 582 6078)
To: ath@prosys.se, dberry@cs.technion.ac.il, guy@auspex.com, heimir@rhi.hi.is,
        i18n@dkuug.dk, lee@sq.com, petern@uel.co.uk, ra@intsys.no,
        rcd@ico.isc.com, sommar@enea.se, staff@cadlab.sublink.org,
        steve@sol.yorku.ca, yfcw14@castle.ed.ac.uk, zvr@theseas.ntua.gr
Subject: troff support for Latin 1
X-Charset: ASCII
X-Char-Esc: 29

Dear International Correspondent:
You have been kind enough to answer previous postings
concerning Latin 1 and troff. Perhaps we can help each
other further.
We are ready to test out DWB 3.2 code, which includes
Latin 1 support. We accept input either as 8 bit
ISO 8859-1, or as escaped 7 bit ASCII. The 7 bit escapes
are new to troff, but based on the VT200 compose code
sequences I am told are most commonly used. For example,
the British Pound sign can be represented by 8 bit hex A3,
by the simulated VT200 sequence \(L- or by the old troff
convention \(ps.
I have written two small C programs which will convert
between 8 bit and 7 bit representations, so that 8 bit
files can be mailed without mangling, or resorting to
binary tricks.
If you are interested I propose the following:
1. tell me you are interested
2. I will mail you the C programs
3. You can mail back ASCII versions of 8 bit troff files
4. I will stream through troff | dpost and mail back
PostScript output.
5. You print the PostScript and tell me if it looks
like what you expect.

If you are not interested please tell me as well so
I can remove you from this mailing list.
Hyphenation is still poor on non-English text, so
beware this may not be camera-ready copy.
	Nils-Peter Nelson
	npn@mhpo.att.com