Martin Tomes wrote:
> Simon Large wrote:
>
>> Hi folks,
>>
>> 1. Martin, maybe you could add an optional section to your pre-commit
>> hook which restricts the character set allowed in filenames to ones
>> you *know* how to case fold, pure ASCII in the limiting case. eg. the
>> subversion project has committers from all over the world, but
>> filenames are always ASCII (and log messages in english). It is up to
>> the hook installer to decide what character set should be used for
>> their repository.
>
>
> I am not sure that this has any benfit, the script will behave correctly
> for ASCII file names without any changes. As check-case-insensitive.py
> is my first Python program I am not a great expert in how Python handles
> Unicode, but the research I did suggests that it will case fold
> according to the Unicode rules and so I am pretty sure that it will
> survive real world use.
I am not suggesting that there is any problem with your script. I was
suggesting that it might also prevent committing of files which contain
characters outside (say) the ASCII range, because case-folding is then
client-dependent (there was a reference earlier in the thread to Windows
OS version variations in how case is handled for unicode). But maybe
it's a sledgehammer to crack a nut ;-)
> At the end of the day the hook script's goal is to prevent files being
> created on the server which cannot be checked out on the client. I
> would be very interested in any examples where it fails to enforce this.
> From my reading of
> http://blogs.msdn.com/michkap/archive/2005/01/16/353873.aspx I think it
> might be possible in obscure cases. I am afraid I don't know exactly
> what he means by the bogus lower case Georgian mapping!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 25 15:22:41 2005