Subject:	Re: W2K/XP fncase [was Re: New perl package]
From:	Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To:	djgpp-workers AT delorie DOT com
In-Reply-To:	<2561-Fri12Oct2001083139+0200-eliz@is.elta.co.il>
References:	<10110120257 DOT AA19829 AT clio DOT rice DOT edu>
	<2561-Fri12Oct2001083139+0200-eliz AT is DOT elta DOT co DOT il>
X-Mailer:	Evolution/0.15.99+cvs.2001.10.05.05.19 (Preview Release)
Date:	12 Oct 2001 09:37:46 +0200
Message-Id:	<1002872267.31951.8.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

On Fri, 2001-10-12 at 08:31, Eli Zaretskii wrote:
> > From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> > Date: Thu, 11 Oct 2001 21:57:29 -0500 (CDT)
> > 
> > W2K:
> > short: TEST. long: test
> > short: _67C0CVS. long: _.CVS
> > Fixpath: c:/test/_.CVS
> 
> Good God!

Was this on a FAT32 or NTFS filesystem (the 'c:' suggests the latter)?
Since NTFS does not store a short name, that might make a difference.
Also, what do you get for actual long names?

  touch averylongfilename1 averylongfilename2 averylongfilename3
  fixpath averylongfilename1 averylongfilename2 averylongfilename3

> If we cannot find a way to fix this, I agree that we should simply
> bypass those calls on XP and behave as if FNCASE were set to y.

Fair enough - after all, the only reason we have FNCASE at all is to
avoid seeing DOS names as all-uppercase, right?  And XP users are
unlikely to have many FAT32 partitions where that problem could show up.

- Raw text -