Re: Proposal: Improved locking implementation for fsfs

kfogel@collab.net wrote:

When translating self-representations you need to ensure injectivity.

> Specifically, for certain common non-ASCII characters
> (e.g., most of those representable in ISO-8859-*), we could use an
> encoding that reads more intuitively to a human:
>
> foo/bör/baz.c ==> foo/bor/baz.c
>
> or
>
> foo/bör/baz.c ==> foo/boer/baz.c
>
> This would make the lock tree more debuggable in common cases.

Here, both "foo/bör" and "foo/boer" would translate to the same lock-path.

Basically transformed self-representation needs some escape mechanism no
matter how you twist and turn it.

This is a built-in problem of variation A.

-- 
Helge
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org