> Am 02.02.2012 08:37, schrieb Ignacio González (Eliop):
>> What I was really surprised is to see that the filenames flowing through the
>> communication channel is not normalised (well, that is just speculation,
>> am I wrong?). Is there a way to force the clients to convert the names
>> to same canonical form (e.g., UTF-8) and back to the resident filesystem
>> convention again?
> This is exactly what is done, what makes you think otherwise? Generally, as
> Stefan suggested, please don't tell us your interpretation of what you saw without
> first telling us what you saw, because that makes it impossible to distinguish
> between a fault in what happened and a fault in your interpretation.
You are completely right, Ulrich. Proceeding carefully (and not at
late night) helped
me see that the second problem (checking out an 'accented' file in Linux) was a
no-problem. My apologies.
The first problem, though (being unable to use an 'accented' filename
in a hook script
called from an Apache module), is still a problem. Stefan has already
pointed me in
the right direction, although I'm afraid I don't have the resources to
workaround he suggested any time soon.
I have asked for help in CollabNet forums regarding the workaround
Thanks to everyone.
Received on 2012-02-03 13:42:08 CET