It would be even nicer if their mailer understood ASCII -- or if mail forwarders first looked it over and reformatted as necessary. BTW, XML is not equivalent to Word. Anti-MS bias is a red herring. kerry ============== > X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 > Date: Tue, 30 Mar 1999 14:47:48 +0200 > To: [EMAIL PROTECTED] > From: "Erik.Huizer" <[EMAIL PROTECTED]> > Subject: Draft Poisson minutes > Mime-Version: 1.0 > Content-Type: text/plain; charset="iso-8859-1" > X-MIME-Autoconverted: from quoted-printable to 8bit by lists.tislabs.com > id HAA21503 > Sender: [EMAIL PROTECTED] > Precedence: bulk > Content-Transfer-Encoding: quoted-printable > X-MIME-Autoconverted: from 8bit to quoted-printable by > dfw-ix8.ix.netcom.com id RAA09447 > > IETF/Minneapolis=20 > POISSON Meeting > 17 March 1999=20 > > Erik Huizer, Chair > Zita Wenzel, Recorder > > 1. Opening > > 2. RFC Series > > Revisions to the RFC Editor web site make it easier to use. A > searchable > database is available. Marshall Rose and Carl Malamud started a project > = > where > they converted RFCs to XML as source rather than ASCII. A common tool > wo= > uld > make life easier, but not Word. RFCs need to be easier to produce. > Woul= > d be > nice to have a format that supports tables and graphs. IETF is not > tryin= > g to > sell RFCs, but maintain an archive. Good reason to stick with ASCII is > f= > or > developing countries.
