Subject: Re: W2K/XP fncase
From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To: djgpp-workers AT delorie DOT com
Cc: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
In-Reply-To: <Pine.SUN.3.91.1011015104328.23336A-100000@is>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1011015104328 DOT 23336A-100000 AT is>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.15.99+cvs.2001.10.05.05.19 (Preview Release)
Date: 15 Oct 2001 13:14:25 +0200
Message-Id: <1003144468.28450.5.camel@bender.falconsoft.be>
Mime-Version: 1.0
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Mon, 2001-10-15 at 10:46, Eli Zaretskii wrote:
> 
> > Which does not call any buggy Windows interrupts.  It would not consider
> > names with lower case or +,;=[] as DOS83, or any with multiple periods, or 
> > leading periods.
> 
> What about blanks?  We shouldn't downcase file names with blanks, I
> think.

I'd also vote for not downcasing files without extension.  My main gripe
with the current FNCASE=n situation is that is downcases names like
BUGS, COPYING, README, INSTALL, etc.  I'm not sure if there are many
such files on a typical DOS system where downcasing _would_ be good
thing.