> 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?
What should I document? With my patch can insert "\" and you get "\" in the URL and the name field.
So everything is as expected.
I don't see a difference to the treatment of "#" in normal text where "#" becomes "\#" as LaTeX-code
but you get "#" in the output.
>> (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.
You can use such strange paths as they are now with my patch. As it is, surely a bit rash, in trunk,
I would like when you could give it a try and report back when there are still problems I was not
aware of, because I don't have access to Unix.
When there is no remaining problem, this should go in.
---
> the difference is that entering problematic path is not bug of lyx per
> se, but the users fault, which is not supposed to be fixed.
I don't agree. When the user enters text, LyX has to take care that the LaTeX code is correct,
that's our aim. I simply forgot to handle "\" in URLs and fixed this now. Other characters like "#"
etc. are already handled.
> what you call "fixing" is like if you want automatically fix wrong TeX code
entered into ERT.
The hyperlink inset is not ERT! It works the same as e.g. the index inset and our other insets. Also
in indexes LyX has to take care about special characters, so I don't understand why hyperlink should
act different.
regards Uwe
