Re: Problem with filenames containing spaces
  By: Oli to Rob Swindell on Thu Jan 20 2022 11:30 pm

 > Rob wrote (2022-01-20):
 >
 >  >> And it's only a problem with filenames that contains a whitespace
 >  >> character.
 >  RS> It's also a problem for filenames that contain any other "unsafe"
 >  RS> characters that "SHOULD" (according to FTS-1026) be escaped.
 >
 > You mean like 0x00 to 0x1F (control chars) and backslash (0x53)? How often
 > do you use these in filenames? ;)

Preferably, never, but I'm not in control of what characters are used in filenames received BinkP, the sender is.

Ideally, the BinkP spec would have been even *more* restrictive in the filename characters allowed (escaped or not), because filenames with colons, semicolons, asterisks, question marks and vertical-bars (pipes) are *not* what I would call "safe", yet they're expressly allowed as "safe" in the spec. :-(
-- 
                                            digital man (rob)

Synchronet "Real Fact" #81:
Vertrauen has had the FidoNet node number 1:103/705 since 1992
Norco, CA WX: 76.0øF, 23.0% humidity, 3 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux