InterTrac links don't work correctly with quoting for spaces

[anonymous]

I've only tried this with the milestone link since it is the only example I can try in my current projects. If I do something like the following (of course the milestone name is fictitious):

[t:milestone:"0.10.4 release" Milestone]

I don't see the expected

Milestone

but instead see

release' Milestone

for the link. Also, the URL shows /intertrac/milestone:"0.10.4 at the end. I assume the unpaired " will probably confuse the link interpreter. We are running with *.compat set to false and all Trac projects are running the same Trac version (0.10.3). The space escape also fails with single quotes. The single or double quote escaping for spaces works just fine for links when not used in an intertrac context (i.e. [milestone:"0.10.4 release" Milestone]

[Christian Boos]

Currently, the syntax for quoting is strict:

[prefix:"target with spaces" label(with spaces as well)]

The prefix should not contain ":" itself.

So your example should be rewritten:

[t:"milestone:0.10.4 release" Milestone]

However, I agree that what you came with seems to be intuitive for InterTrac links (i.e. use the "normal" quoted Trac link milestone:"0.10.4 release", then prepend the InterTrac prefix), so I'll give it a try.

[simon@…]

I ran across this problem in Trac 0.11 when using the source browser. I wanted to refer to a requirements document in another trac instance. The document has a space in the file name. It turns out that I have to use double quoting to make it work. I.e.

[prefix:'source:"path with a space"']

I think that is a teeny bit to clunky.

[Christian Boos]

You're right, I assumed prefix:"source:path with a space" would work but it doesn't, double quoting is needed right now.

There's also the <prefix:source:"path with a space"> alternative which comes with #7386.

[Christian Boos]

This is also fixed by r9284 (and r9297 so that the example given in this description works), so I'm closing as duplicate of #4865.