On Dec 5, 2005, at 16:22, Balázs Szabó (dLux) wrote:
> I really can't believe this thing can happen: why subversion uses
> unicode filenames if it cannot handle such a common thing as a Mac
> OS X default filesystem. I understand that OSX is a weird Unix in
> many aspects, but man, many people use this.
>
> Please someone just tell me what the heck I can do with this
> problem: is it solvable easily? Is there any patch I can apply? Or
> just forget using accents in the filenames? Or I am doing something
> wrong and it works file for everyone else?
Unfortunately I don't know the answer to your question. I also use
Mac OS X with Subversion, but I use it to manage web sites. In a web
page URL, what charset should be used to encode non-ASCII characters?
I'm not aware of any RFC which answers that question. Therefore to
avoid unpredictable behavior, I restrict myself to ASCII filenames.
This is easy for me to do since I primarily speaks English, but I
certainly acknowledge that Hungarian and other languages have a much
tougher time with that restriction, and I agree that Subversion
should be handling non-ASCII filenames correctly. I don't know what
the problem is in your situation, but the previous suggestion that
Subversion isn't running stringprep when it should certainly sounds
possible to me. If that is the case, then a Subversion programmer
will probably have to evaluate all places where Subversion uses UTF-8
data and see whether stringprep is being used and if not whether it
should be used at that point.
If you could provide a step-by-step reproduction recipe for the
problem, I could try to reproduce it, as I have access to both Mac OS
X and Linux machines.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 6 07:58:41 2005