>Subversion uses UTF-8 internally to store all filenames. So, now the problem
>1. how do I get these two chars in Mac OS X
>2. how do I tell Subversion about it
>In general, this is a task solved by so-called locales. Typing 'locale' at the
>console might give you a hint, other than that you need to do something OS X
>specific. It's possible that a simple 'export LC_CTYPE=utf8' already does the
>job. However, I'm mostly guessing - I have never used these charactersets let
>alone on a Mac.
I am in luck :-) simple 'export LC_CTYPE=utf-8 is work, In fact, utf-8
and MacRoman are very similar:
The default font encoding in Mac OS X is MacRoman. The default font
encoding on some other platforms is ISO-Latin-1 or WinLatin-1. These are
subsets of UTF-8 which means that files or filenames can be turned into
UTF-8 by just turning a byte into a char. Programs that assume this
behavior cause problems in Mac OS X.
The simplest way to work around this problem is to specify a font
encoding explicitly rather than assuming one.
If you do not specify a font encoding explicitly, recognize that:
In the conversion from Unicode to MacRoman you may lose information.
Filenames are not stored on disk in the default font encoding, but
in UTF-8. Usually this isn’t a problem, since most files are
handled in Java as |java.io.File|s, though it is good to be aware of.
Although filenames are stored on disk as UTF-8, they are stored
decomposed. This means certain characters, like e-acute (é) are
store as two characters, “e”, followed by “´” (acute accent). The
default HFS+ filesystem of Mac OS X enforces this behavior. SMB
enforces composed Unicode characters. UFS and NFS do not specify
whether filenames are stored composed or decomposed, so they can
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jun 23 18:58:24 2005