Hi Robin,
No one is suggesting this as a specification name. And yes, I will continue to
argue that as long as desktop operating systems allow the creation of filenames
with spaces, that is what most users will do. Not that web documents should have
spaces or underscores in the filename, but that users, when creating files on
their desktop, will create documents with spaces in the filename since it makes
them more legible. The filename itself is indicating placeholders for a date.
Now someone could gently suggest to Bob Beims or whoever created the template
that using DD-MM-YYYY or some other pattern might be more appropriate, but it
*does* make sense given the intent of the filename.
When we roll out a system that *prevents* documents with spaces (or other bad
characters) in filenames, we will also *educate* users as to why they can't have
spaces in filenames, and how to create patterns that - while eliminating spaces
- also create meaningful filenames. You could start that education process now,
but as long as Kavi doesn't enforce it, it won't make a difference. You have to
time the education to the actual restriction for it to have the desired impact.
Mary
>
