Wow. All I wanted was supporting arguments to choose a naming convention here at the office. Given that 99% of the lusers are ignoratti, the space is here to stay. So I can now see based on the above arguments, that actually it is historically developer’s fault for not making the use of space in filename easier for programmers to work with.
All those back up scripts, etc. need to be hand coded to handle space names. Why? Because developers were so callous(sp?) as to select the language-text space char as the code separator. Should actually be some other funky (read non-printing) thinggy like chr(9) A Tabb for anyone?
Go figure, we always blame the luser, when they do the most natural thing. In this case lusers are correct, and OS/dev languages are incorrect, they should find a diffrent ‘standard’ to using the space (maybe keyboards should have to ‘space’ bars eh? One for ‘text’ space and oine for ‘code’ space - hey my new invention for the Unicode world!!!