Invalid bracketing

windows doesn't allow special chars in file names. or at least, most special chars.
Care to be specific for once instead of dancing around on the stage of ambiguity as usual? Try changing a file name so that it includes ! or # or $ or % in Windows and I think you'll find they are accepted. I guess those are not on your "most" list?

I'm saying NO special characters or spaces should EVER be in file names, so what are you contributing to this discussion by waffling, let along quoting me?
 
I'm saying NO special characters or spaces should EVER be in file names, so what are you contributing to this discussion by waffling, let along quoting me?
so i see that I'm getting the usual heat from the specificity players here. I've already gotten a word tonight about staying "on topic". It reminds me of my boss at my government job. He's scared $hitless of other people and the world in general, and as a result, he obsesses over keeping all of us "on task" for the entire time we're on the clock. He's about the worst boss I've ever had, and I've worked for some pretty bad engineers that actually worked in my field! I've always thought that this culture kick of constantly keeping busy is a direct result of peoples' fears about the sustainability of capitalism that arose when the system was taken into foreign countries that were overcrowded.

But to satisfy your request sir, here's what I found:

ACCEPTED:
Code:
=> !
=> @
=> #
=> $
=> %
=> ^
=> &
=> (
=> )
=> +
=> ;
=> []
=> {}
NOT ACCEPTED
Code:
=> /
=> \
=> *
=> :
=> ?
=> " (double quote)
=> <
=> >
=> | (pipe)
is that good enough? I might have missed a few...
 
Actually, not entirely true, Adam. Windows allows a lot of special characters depending on exactly how you created the file. Ran into that with the Navy. However, ordinary parsing will not allow use of the specials. For instance, some third-party FTP packages could create some horrific names that required some extensive but delicate renaming because the command-line parser for RENAME would get... pi$$y.
 
ok Richard. I get it. But I won't carry on with regard to asking what you mean by "not entirely true", because I literally tested every one of those with windows 10 to satisfy the previous man. We've hijacked enough threads together in our time here. Let's move right on over to the cooler to continue this if you want to. Have a good night, sir. =)
 
My point is that NORMALLY you would be right, but to completely answer the question, you would have to ask exactly how the files were created and more specifically by what app. That's all.
 

Users who are viewing this thread

Back
Top Bottom