> Do you also document this, as well as that "\" (which is a valid character in
> unix paths) must be inserted as "\\"?
"\" is not allowed in \href, that was the bug. This is independent if it is valid in some case or
not. Unix-paths use "/" not "\" as far as I know. Note that \href takes only URI paths.
And "\" cannot be inserted as "\\" because this is a line break.
> In general, I do not like much automatic conversions like this, but I don't
> have a better idea.
I had 3 choices:
1. when the user presses "\", nothing is inserted
2. when the user presses "\", a "/" appears
3. when the user presses "\", he gets the "\" as expected
The most intuitive one is 3. Because then you can use the paths as you normally do in your OS and
what you get is always the right thing.
Note that this only affects the Url field, in the Name field you can use "\", this is translated in
the background to \textbacklash as we also do for normal text.
regards Uwe
