On 30.01.2012 21:00, Johan Corveleyn wrote:
> 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.
Are you seriously proposing that we /support/ such broken, hackish
nonsense? How do you expect users to tell the difference between file
names that look identical on the character level, but are not on the
code point level?
Supporting such hacks would only be a source of bug reports. I don't see
this as a desirable feature.
And as for doing the server-side checks in pre-commit hooks ... i guess
you could write a whole libsvn_repos implementation merely as a set of
pre-commit hooks, but who would want to? Hooks aren't intended for
implementing core functionality..
-- Brane
Received on 2012-01-30 21:10:00 CET