Hello, one of our scientists tried to sync files with a colon in the filename. This failed with an "Invalid characters" comment in the sync log. I know that colons were a no-no in file paths on Mac operating systems before MacOS X as the colon was used as a path separator. However, as far as I know, this is history and the colon (much as a bunch of other "special" characters including "!", "&", "?" or, in particular " " which I would not use in my own work) traditionally makes life unnecessarily difficult when scripting on Unix - but it is technically possible to use on all modern file systems (though, again, probably not advisable). But maybe there is a technical reason to forbid colons in file names that I am not aware of?
Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleueler Str. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 E-Mail: [email protected] http://www.nf.mpg.de
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
