On 1/16/2012 2:01 AM, Stefan Küng wrote:
>
> Not just TSVN. All svn clients that use the svn library do not.
> While the svn server behaves as much as DAV server as it can, there
> are some differences. And svn clients first check svn properties for
> validity in svn before they can be set. Your property is a valid DAV
> property, but not a valid svn property. You might be able to set that
> property with non-official clients, but that doesn't make them valid.
OK, that makes sense, but that still leaves the question: what is it
about this property that makes it invalid? Here's the property here in
case it got lost in the thread:
http·3a·2f·2fpurl.org·2fdc·2felements·2f1.1·2ftitle
> svn properties must be utf8 encoded. And that's mentioned in every doc
> about svn properties.
Well, that's interesting, because I assumed that TortoiseSVN would do
the UTF-8 encoding for me automatically for property names. After all,
it does the UTF-8 encoding automatically for property values, right?
I note that, once I store these properties using SVN+WebDAV or SVNKit,
TortoiseSVN *reads* them just fine---isn't that odd?
And lastly, I tried the UTF-8 encoded version of the property on
TortoiseSVN, and that didn't work either:
http·3a·2f·2fpurl.org·2fdc·2felements·2f1.1·2ftitle
>> I imagine that this problem ultimately lies on the Subversion side, but
>> since the problem first arose for me on TortoiseSVN, I wanted to run it
>> by the experts here. Thanks for any insight.
> That's not true. Your blog post clearly mentions that you tried twice
> on the svn list without success. Now you're trying here.
No. :(
Let me be clear: there are two separate problems. One problem I had in
2007/2008, and it had exclusively to do with SVN+WebDav. I raised it
twice on the Subversion list, but got no response. So I created a
workaround! The workaround, which is a completely separate issue, only
showed up yesterday; I'm raising it here for the first time ever. I cite
the article only because it explains the background of why I was
creating this workaround to begin with, and goes into depth about
exactly what encoding scheme I am using in this workaround that's now
causing this new problem.
> ... Your problems and questions are not with TSVN but with the
> svn library.
Yes, you're probably right. I've now raised this problem on the
Subversion list separately. Sorry to have bothered you with it.
Garret
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2909160
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-16 16:07:23 CET