Re: Let's discuss about unicode compositions for filenames!

On Mon, Jan 30, 2012 at 8:10 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Tue, Jan 31, 2012 at 01:42:21AM +0900, Hiroaki Nakamura wrote:
>> 2012/1/30 Stefan Sperling <stsp_at_elego.de>:

[ ... ]

> And mixing various unicode forms works fine today if the filesystem
> used by the client supports this. The use case Neels contrived, where
> developers want to test their code with unicode filenames in various
> NFD/NFC forms, and check those test files into Subversion, should still
> be supported.

Indeed.

Though this means that unconditional NFC (or whatever) normalization
in the working copy database is not an option, since it precludes
representing multiple forms at the same time in the wc. Except maybe
dependent on the (filesystem of the) client platform.

Of course, if a repository needs to support also checkouts to OSX/HFS+
clients, it should be configured to disallow multiple (conflicting)
forms to enter the repository. This can be done with a pre-commit
hook, similar to case-insensitive.py [1], which does the same for
case-clashing files.

(BTW, case-insensitive.py works by comparing incoming adds with the
list of directory entries of the corresponding directory within the
txn (comparing their normalized forms))

-- 
Johan
[1] http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/case-insensitive.py