Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3DE63BB9.CF3B4557@phekda.freeserve.co.uk>
Date: Thu, 28 Nov 2002 15:52:25 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Updates to readme.1st for 2.04, revision 2 [PATCH]
References: <200211280826 DOT JAA11739 AT lws256 DOT lu DOT erisoft DOT se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Martin Stromberg wrote:
> 
> > +A 'long file name' or 'long directory name' has path components that
> > +are longer than 8 characters in the portion before the extension
> > +and longer than 3 characters in the extension.  A long file name may
> > +also have multiple extensions and contain some characters that are
> > +invalid in short file names (e.g.: spaces).
> 
> The point was that it won't take much more space to really list the
> invalid ones: "+,;=[]" which is six characters. Compare this with
> "e.g.: spaces" which is eleven.

Space isn't a problem. My point was that this may be too much information for
the user. But I will change "spaces" to the characters you have listed.

> Plus I just remembered that spaces are valid in SFN! So at least that
> must be changed.

Yes, you are quite right. (I just read the section on long file names in the
Microsoft Platform SDK.)

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]