On Mon, Jul 18, 2011 at 23:50, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Ivan notes on IRC that this fixes issues with non-ASCII lock tokens.
> (At least, he reports errors in 'svn ls -v' over http://; but for me
> 'ls' and 'info' work fine over svn://.)
>
> Are lock tokens even permitted to be non-ASCII?
> (both backends generate ASCII-only lock tokens (in the same manner))
>
> If they are, are they required to be in UTF-8? Or can they be, say,
> arbitrary octet strings?
>
I didn't find explicit specification for lock token encoding, but it
handled everywhere as normal utf-8 string.

That's why I decided to implement minimum patch just to decide lock
token returned from hook output to utf-8 string.