Hi,
On 2005.12.07., at 3:19, Stuart Celarier wrote:
> Consider this. U+0391 (Α) is a capital Greek alpha, which in
> virtually every font is visually indistinguishable from A the
> English letter A. Here's a simple HTML document, save it, load it in a
> browser, and see for yourself:
>
> <HTML><BODY>AΑ</BODY></HTML>
>
> These are distinct code points, hence different characters, even if
> similar or identical glyphs are used. I don't get how this becomes a
> Windows (or any other operating system-specific) problem. If the
> letter
> 'O' and numeral '0' are visually indistinct on my computer, in
> whatever
> font I happen to use, should the file system prevent me from using one
> of these characters? I don't think so.
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! These charactes
have to have the same meaning (that's why OSX converts them to a
canonical form). The mentioned characters does not have the same
meaning (greek alpha vs. A and 0 vs O).
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). this
requires some kind of stringprep.
Regards,
Balázs Szabó (dLux)
-- -- - - - -- -
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 7 08:51:13 2005