Randy Drielinger <[email protected]> wrote: > With the risk of not being compliant with other OS's, but isn't using > file://localpath/<real_file_name.extension> (so using file://localpath/ by > default) > the solution for the original suggestion? > > This ensures not breaking anything on existing websites and is a far more > logical name for the whole workaround.
How does using a number of /'s and <ZERO> \'s increase the likelihood of compatibility with web apps which are clearly looking for \'s?
