On Thu, Jul 10, 2008 at 10:45 AM, Bryan Tong Minh bryan.tongminh@gmail.com wrote:
Regardless of it being allowed or not, it sound like a bad idea to me to allow ?*| in filenames.
By that logic, shouldn't we ban ();!$ and so on for being shell characters as well? If people want to move files around manually, and want to use a command line instead of a GUI or a (non-shell) script, they can be careful with their escaping. But as Brion says, the plan is to eventually move to hash-based filenames anyway.
Uh... ok... so basically MediaWiki installations having com1.png files are not platform compatible?
Apparently, yeah . . . Unix's "everything but / or null" seems a lot more convenient here. Although it's kind of a pain when you get some unprintable binary gibberish for a filename by mistake. :)