>> When there is no remaining problem, this should go in.
>
> I agree.
There was still a problem: I escaped the "#" character in the URL field to "\#". But this was wrong,
in the URL field is mustn't be escaped, but in the name field. We got yesterday a bug report on the
lyx-users list about th
Uwe Stöhr wrote:
> 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.
I tested it, and it actuall
> 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.
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,
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, s
On Thu, 15 Jan 2009, Uwe Stöhr wrote:
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 norma
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
On Wed, Jan 14, 2009 at 02:37:42AM +0100, Uwe Stöhr wrote:
> http://www.lyx.org/trac/changeset/28141 fixes
> http://bugzilla.lyx.org/show_bug.cgi?id=5686. Now "\" characters in the
> url field are translated in the background to "/". So one can insert path
> to files as you like - Windows or Uni
On Wed, 14 Jan 2009, Uwe Stöhr wrote:
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
Just curious... do you mean 'presses'? And if so, what happens when you
paste a URI?
I'm not sure it
On Wed, 14 Jan 2009, Jürgen Spitzmüller wrote:
Uwe Stöhr wrote:
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-p
Uwe Stöhr wrote:
> > 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 kno
> 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 U
Jürgen Spitzmüller wrote:
> > The result, e.g.
> > file:C:/file.txt
> > is handled correctly by Firefox and Internet Explorer.
> >
> > OK for branch too?
>
> Do you also document this, as well as that "\" (which is a valid character in
> unix paths) must be inserted as "\\"?
shouldn't be this co
Uwe Stöhr wrote:
> http://www.lyx.org/trac/changeset/28141 fixes
> http://bugzilla.lyx.org/show_bug.cgi?id=5686. Now "\" characters in the url
> field are translated in the background to "/". So one can insert path to
> files as you like - Windows or Unix style.
> The result, e.g.
> file:C:/file.tx
http://www.lyx.org/trac/changeset/28141 fixes http://bugzilla.lyx.org/show_bug.cgi?id=5686. Now "\"
characters in the url field are translated in the background to "/". So one can insert path to files
as you like - Windows or Unix style.
The result, e.g.
file:C:/file.txt
is handled correctly by
15 matches
Mail list logo
