Uwe Stöhr wrote: > > I don't like the concept. Better teach the users about proper use > > instead of "fixing" it behind their backs. > > I don't understand your concerns. I listed the 3 possibilities to fix this > and why I have chosen the one I implemented. There is not other way to fix > this, see also the last sentence of this mail. We also do this all the > time: When you enter a "#" in normal text, it becomes in the background a > "\#". The same is here, when you enter a "\" it becomes in the background > now a "%5C% - valid LaTeX.
Well, this points again to my initial question (which you haven't answered yet): Do you also document this, as well as how "\" (which is a valid character in unix paths) must be inserted? > > /home/juergen/test\test/somefile.pdf is valid on Unix. How am I supposed > to > enter such a path? > > \href has nothing to do with paths of OSes. It follows the definitions of > URLs. So everything you can enter in this field is an URL, not a file path. > When you use the option that a URL is a path to a file it is still an URL > and therefore the resulting link will open the file via a URL browser and > not the usual file explorer. > > (Just for my interest: is /home/juergen/test\test/somefile.pdf equivalent > to /home/juergen/test\test\somefile.pdf ?) No. In the given case, I simply have a subfolder called "test\test". Not that I'm really using such stupid names, but it's possible, and we have to take it into account. Jürgen
