|
|
"Leythos" <void@xxxxxxxxxxx> wrote in message
news:wJKDf.86521$PY6.35388@xxxxxxxxxxxxxxxxxxxxxxxxx
> In article <ecGJILmJGHA.1388@xxxxxxxxxxxxxxxxxxxx>, I.can@xxxxxxx
> says...
> >
> > "Leythos" <void@xxxxxxxxxxx> wrote in message
> > news:SsIDf.52789$tK4.23599@xxxxxxxxxxxxxxxxxxxxxxxxx
> > > In article <Xns975C524545F1D6AD265@xxxxxxxxxxxxxxx>, w_masters@dummy-
> > > entry.com says...
> > > > I have this secret habit! :-)
> > > >
> > > > I often like to put a space at the end of the name of a file to make
> > > > it more legible. I prefer the look with the space put in.
> > > >
> > > > For example:
> > > >
> > > > CPA Improvement Plan.pdf
> > > > CPA Improvement Plan .pdf
> > > >
> > > > Are there any problems you can foresee I might encounter if I do
> > > > this?
> > >
> > > I've always found the long standing rule about NOT using spaces or
> > > special characters to be a good one to follow.
> > >
> > > When you want to run some utilities or some applications, they will
have
> > > issues with spaces or special characters.
> > >
> > > Suppose you want to provide a link to your file, now you need to
enclose
> > > the entire path/file in quotes or it will give an error when they
click
> > > on the link.
> > >
> > > MS Office XP will barf on files that have special characters in their
> > > name.
> > >
> > > A general rule is to use the underscore _ character in place of a
space,
> > > but never leave space/special characters in file names.
> > >
> > > Don't forget, you may be working with people that have older systems
or
> > > non-windows systems at some point and then all bets are off if you
don't
> > > use standard file naming conventions.
> >
> > Could you be a little more specific here and name an
> > older or non-Windows system that is
> > a) still in use (i.e. less than 10 years old) and
> > b) cannot cope with embedded spaces
> >
> > I would also be interested in your definition of
> > "standard file naming conventions". Is it the 8.3
> > definition? If so, do you recommend to the OP
> > to avoid using file names that have more than
> > 8 characters?
>
> Letters, numbers, underscore, no spaces or special characters, under 253
> characters in length.
>
> Try opening files across platforms with spaces in the file names.
This is your own private "Standard file naming convention".
It does not exist elsewhere.
I note that you could not think of a current platform that would
have a problem with embedded spaces in file names. Nor can I,
so why warn the OP? It's a non-issue.
|
|