--opJtzjQTFsWo+cga
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

"Martin S. Weber" <Ephaeton@gmx.net> wrote:
> On Fri, Mar 10, 2006 at 10:35:41AM +0100, Martin Husemann wrote:
> > On Fri, Mar 10, 2006 at 10:33:17AM +0100, Hubert Feyrer wrote:
> > > 1) what formats do you have in mind, and how would you watch them (for
> > >    non-text formats) with tools in the base system
>=20
> Isn't the source of the guide the xml-panacea in the meantime ?
> Spit out some *roff output out of the xml source which can be=20
> rendered by the base text tools to more-or-less/text output, then.

Yes XML->*roff is what we want here.  Does anybody here have experience
with generating *roff from XML?  I know it's possible, just not sure how
well a structured document like the Guide translates to *roff.

-Jan

--=20
If you are undertaking anything substantial, C is the only reasonable choice
of programming language.
	-- UNIX User's Supplementary Documents

--opJtzjQTFsWo+cga
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFEEfbHfFtkr68iakwRAsOZAKDRr1L/ZiM8ftbA7cV0Z6DYCyI+pACZAXe+
XpC8XGh5QLQpRpmf6pmaVKY=
=PIs2
-----END PGP SIGNATURE-----

--opJtzjQTFsWo+cga--