On 5/28/2014 11:58, Stephan Beal wrote:
On Wed, May 28, 2014 at 7:51 PM, Warren Young <[email protected]
<mailto:[email protected]>> wrote:

    I don't see that there is ambiguity here at all.

Ah, correct. The onus is on the one creating the link to do the escaping.

...which does mean it is *partly* Fossil's problem, but only insofar as it creates links itself, as when generating HTML from Markdown and Wiki sources.

In Markdown, if I give it the text "[the foo page](foo++)", it mustn't molest my + signs.

If instead I refer to the foo++ Wiki article from another Wiki article and Fossil chooses to generate an HTML page containing a URL using query it must URL-escape the + signs (...?name=foo%2b%2b), knowing that Fossil (or the SCGI proxy) will be decoding them.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to