RE: Encoding problems in subversion under Mac OS X (HFS+)

Balázs wrote:
>I don't think we are talking about the same problem. We are not
talking about the same (or similar) glyphs, we are talking about the
same characters: one character with the same encoding. UTF-8 allows
the same character to be encoded with different code!

Perhaps Paul has overstated his case. Repeating the passage that I quoted:

Paul wrote:
>One might argue this is a Windows bug -- it shouldn't allow two names
that
>produce the same pixels on the screen but have different encoding --
>and that no doubt is why OS X doesn't.

Balázs continued:
>What I suggest is having a config option to at least allow OSX users
to use SVN with its full glory (I mean accented filenames).

I agree that Subversion (ideally) should work equally well on all platforms and with all languages. Having multiple Unicode representations for a single text element is not limited to accents on (Latin-based) characters, for example see [1]. I bring this up in hopes that any solution be general enough to apply to all languages.

In the interim, could you use a pre-commit hook, similar in concept to check-case-insensitive.pl, to either prevent conflicting Unicode representations or make them canonical? I'm a novice when it comes to using Subversion hooks, so I don't know the extent to which this could fix the problem or ease your pain.

Cheers,
Stuart

Stuart Celarier | Corillian Corporation

[1] http://developer.apple.com/documentation/Carbon/Conceptual/ProgWithTECM/tecmgr_concepts/chapter_2_section_7.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 7 12:21:06 2005