Received: by nummer-3.proteosys id <01C19443.A98CA42C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:47 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.A98CA42C" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: L3 suggestion: different file extension Date: Tue, 28 Apr 1992 13:36:02 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "Mailing list for the LaTeX3 project" To: "Rainer M. Schoepf" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 697 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.A98CA42C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >>> more important to me: will i be able to have blank >>> spaces in the names of my documents (file names to you)? >>> i resent having to type that stupid underscore. On VM/CMS, you always could! ------_=_NextPart_001_01C19443.A98CA42C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: L3 suggestion: different file extension

>>> more important to me: will i be able to = have blank
>>> spaces in the names of my documents = (file names to you)?
>>> i resent having to type that stupid = underscore.

On VM/CMS, you always could!

------_=_NextPart_001_01C19443.A98CA42C--