Mail Archives: djgpp/2003/06/25/23:52:56
> From: "deckerben" <bdeck AT lycos DOT co DOT uk>
> Newsgroups: comp.os.msdos.djgpp
> Date: Wed, 25 Jun 2003 20:42:56 +0200
>
> "Eli Zaretskii" <eliz AT elta DOT co DOT il> wrote in message
> news:2593-Wed25Jun2003075056+0300-eliz AT elta DOT co DOT il...
> > > From: "deckerben" <bdeck AT lycos DOT co DOT uk>
> > > Newsgroups: comp.os.msdos.djgpp
> > > Date: Tue, 24 Jun 2003 23:34:01 +0200
> > This is not the default because in most situations the behavior you
> > see now is what users want, especially if they have files that come
> > from DOS (where _all_ directory entries are in UPPERCASE).
>
> I really understand the DOS issue. But this would not be true under NT
> systems, where true filename cases are reported correctly.
I meant DOS filenames under Windows, not under DOS. So your case is
included.
> Fooling with this causes problems.
Making FNCASE=y the default causes problems as well, although in
different places. Windows users generally expect to see case
insensitivity in handling file names, and FNCASE=y makes a huge step
away from that.
> I am recommending all NT-based PythonD users to set FNCASE=y.
Beware: FNCASE=y might be required for _building_ PythonD, but if it
is not required for _using_ it, you might get your users into more
trouble than you wish.
- Raw text -