On Mon, 30 Sep 2013 21:49:17 +0200, Stephan Beal <sgb...@googlemail.com>
wrote:
On Mon, Sep 30, 2013 at 9:07 PM, j. van den hoff
<veedeeh...@googlemail.com>wrote:
so I think either fossil should quote any occurence of `/' when
constructing the URL (if possible -- I'm not sure if it is) or silently
replace any `/' by something else (as it already does with any blanks
which
are replaced by `+'). a `-' actually might be the best choice for
replacing
the `/'.
My personal preference would be to restrict the project name field to
only
characters which are legal in Fossil filenames (note that fossil
disallows
some which are legal in Unix but not on Windows, like ":").
yes, that would be possible. but still: at least blanks _are_ allowed in
file names, but not in the URL and are therefore replaced by `+' and I
think this is the more reasonable approach. I would argue that it's
preferable to allow free text for the project name (including blank,
slash, colon etc.) and just map all these to something valid (maybe all of
them to `+' just like it is already done for blanks) when the "tarball
URL" is constructed: after all, the project name is just the descriptive
title at the top of the web-page and it feels not right to enforce that
this title is also a "valid file name".
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
