Liste des Groupes | Revenir à cu programmer |
2) Spaces in filenames are pretty much a necessity from the end-userOS/2 also had the "display file name" approach for invalid file names.
POV (but see below). Yes, it makes things hard for us on the admin
side of the game. I have always thought that the right answer is
to have both - a short name that is usable for the admin side of
the game and a long label that the user can work with. There are
two solutions of this nature that I like:
a) The "Extend a name" idea. Where you have short names at the
filesystem level, but then have a database linked to that
that allows the user to think that long, descriptive
filenames are supported.
A long long time ago, there was a DOS product called
"Extend a name" that did this. Also, 4DOS (and later
versions) does this.
b) The way VFAT does it (and NTFS emulates) - where, for anyIn fact both variants caused at least as much problems as they solved.
file with a long name, there is an 8.3 filename (usually
with weird characters in the filename) as well, and either
filename is usable by programs. This is one place where I
think Windows really gets it right (and Unix could learn
from it).
Les messages affichés proviennent d'usenet.