Peter Davis peter@pdavis.cx writes:
On Tuesday 28 January 2003 01:31, Peter Davis wrote:
The only thing that could remove the limitation would be to use some
additional encoding, such as Base64 or C-style escaping.
On Tuesday 28 January 2003 01:41, Julian Reschke wrote:
Maybe I'm missing something, but if filenames/pathnames are stored as
file URLs anyway, this wouldn't be an issue at all. URLs do not contain
control characters, after all...
Yes, URL escaping would solve the problem. (/me slaps head.)
Unfortunately, entry names aren't stored as URLs -- there is a separate
url attribute for that.
Heh...this was the first route I was going to take yesterday, but
dismissed it because technically speaking, the name refers to an
on-disk path (which can differ from the basename of the URL for
switched files and directories).
As such, I'm +0 on using URI-escaping on the name= attribute. It
would be a much smaller change (would only touch two functions in
libsvn_wc/entries.c -- write_entry and svn_wc__atts_to_entry). I
dunno, what do others think? Are we blurring any correctness lines
just to allow some certifiable whackos the chance to store formfeed
characters in their filenames? Quite honestly, the newline support is
enough of a stretch (and one that we decided we would *not* support in
code portions like the svn:ignore property values).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:22:00 2006