TIP: Click on subject to list as thread! ANSI
echo: allfix_help
to: Jerry Schwartz
from: Ken Johnson
date: 2010-11-29 10:26:38
subject: File Names

Hello Jerry.

25 Nov 10 09:21, you wrote to me:

KJ> Hello, Ken...
KJ>
KJ> I have one issue that needs to be considered: file names (at least in the
KJ> Windows/DOS versions) are always upshifted.
KJ>
KJ> I'm not sure how this should be handled. Windows file names are
KJ> case-insensitive (unless you use the Posix API), but *nix file names are
KJ> case-sensitive.
KJ>
KJ> Preserving the case of the file name would mean that
"file1" and "File1"
KJ> are two different files to a *nix system, but are the same file to a
KJ> Windows system.
KJ>
KJ> At first blush I think that preserving the existing convention (always
KJ> upshift) is the best way to keep things straight.
KJ>
KJ> Regards,
KJ>
KJ> Jerry Schwartz
KJ>
KJ> mailto:jerryschwartz{at}comfortable.com
KJ> http://www.writebynight.com
KJ>
KJ> --- Msged/NT 6.0.1

Yes, the filenameing convention is one of the priorities that I am looking at.
I was originally thinking of changing all names to lower, as this would be
easier to deal with when porting to Linux. Windows would handle it, and DOS
makes everything upper, so when reading in the filenames, would just
process them as if they are lower. Have  a bit of testing still to do here
before I do the commit of it.


Ken

--- GEcho/32 1.20/Pro
KJ> * Origin: Write by Night (1:142/928)
* Origin: Northern Nevada Net - Reno, NV USA - net213.rail-city.net (1:213/0)
SEEN-BY: 10/1 11/200 203 331 14/250 400 34/999 120/228 123/500 128/2 187
SEEN-BY: 138/146 140/1 222/2 226/0 230/150 250/1 306 261/20 38 100 1381 1404
SEEN-BY: 261/1411 1418 266/1413 280/1027 320/119 396/45 633/104 260 267 285
SEEN-BY: 690/682 712/848 800/432 801/161 189 5030/1256
@PATH: 213/0 10/1 261/38 633/260 267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.