Sivar
16th December 2004, 21:18
Older versions of AutoGK supported commas in the input directory and file names, but more current versions do not. This is absolutely maddening when trying to encode a series like Babylon 5 which has a number of episodes with commas such as "The Long, Twilight Struggle" and "Rumors, Bargains, and Lies"
A comma is a perfectly valid character both in Windows and Unix filesystems (as are square brackets, which are also mysteriously banned), so I do not see why they are considered invalid, especially when they worked fine before.
Is there a way to edit the "invalid character list" short of using a hex editor?
A comma is a perfectly valid character both in Windows and Unix filesystems (as are square brackets, which are also mysteriously banned), so I do not see why they are considered invalid, especially when they worked fine before.
Is there a way to edit the "invalid character list" short of using a hex editor?