On 1/16/2012 10:09 AM, Stefan Küng wrote:
>
>
> the test is done in libsvn_subr\properties.c, function svn_prop_name_is_valid():
>
> svn_boolean_t
> svn_prop_name_is_valid(const char *prop_name) ...
That's enlightening. So my take away from this is:
* Subversion's "official" code requires property names to be a
(alpha/colon/underscore) character followed by any number of
(alpha/number/minus/dot/colon/underscore) characters.
* This code prevents UTF-8-encoded property names.
* This requirement doesn't seem to be documented anywhere except
within the source code, so it's no surprise that other clients
(including the official "SVN+DAV" client) implement it differently.
As UTF-8-encoded property names are stored just fine by other clients
(and even read properly by TortoiseSVN and everything else), this
limitation seems arbitrary. (It's also a shame---I thought the world had
moved beyond ASCII and embraced UTF-8/Unicode years ago.)
If I knew that it would help anything, I would gladly volunteer to
update the documentation, update the source code, or whatever else it
would take to get this restriction removed. However, since in my
experience the Subversion users list doesn't even bother responding to
issues like this, I would probably be wasting my time---I doubt anyone
would even discuss it. I suppose I'll just continue to use SVNKit until
this eventually breaks, then I'll just be forced to write my own
versioning system. :(
Stefan, thank you very much for your time in helping me get to the
bottom of this---disappointing though the answer may be.
Best,
Garret
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2909200
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-16 19:45:53 CET