views:

1214

answers:

5

I'm interested in trying out distributed version control systems. git sounds promising, but I saw a note somewhere for the Windows port of git that says "don't use non-ASCII filenames". I can't find that now, but there is this link. It's put me off git for now, but I don't know if the other options are any better.

Support for non-ASCII filenames is essential for my Japanese company. I'm looking for one that internally stores filenames as Unicode, not a platform-dependent encoding which would cause endless grief. So:

  1. What DVCS support Unicode filenames?
  2. In both Windows and Linux?
  3. Ideally, with the possibility to transfer repositories between Windows and Linux machines with minimal issues?
+5  A: 

See issue 80 in the same repository. There is a recent (mar/apr) discussion on the Git Mailing list (e.g. 1, 2) where the Git maintainer Junio Hamano asks some questions regarding this. I don't have it right here. By joining the thread in a constructive manner you might help in resolving the issue.

In the Java implementation JGit, we always use UTF-8 when we create textual metadata and filenames. That is the only way, but there are some things to consider.

robinr
+2  A: 

Bazaar VCS works with unicode filenames internally. And it has very good support for unicode both on Linux and Windows.

bialix
There is a page on their site about Bazaar's Unicode support: http://bazaar-vcs.org/UnicodeSupport
Austin
That page is more developers spec, than user doc, and it's a bit out of date.
bialix
I did some basic tests of Bazaar on Windows, and confirmed it could add and merge files even if they had filename characters outside the current system code page. Good stuff. I'll try the repository on a Linux box later and see if it can branch it correctly.
Craig McQueen
I did some further tests of Bazaar on Windows, and discovered that while the command line works fine, the GUI fails at committing changes to a file with filename characters outside the current system code page.
Craig McQueen
What the name of GUI?
bialix
Craig, thank you for comment. This is actually problem of all Python-based programs. I've filed the bug about unicode characters outside current system code page in the command line: https://bugs.launchpad.net/bzr/+bug/375934. It will be fixed shortly.
bialix
So I discovered about Python and the Windows command line. See my question about it: http://stackoverflow.com/questions/846850/how-to-read-unicode-characters-from-command-line-arguments-in-python-on-windows
Craig McQueen
Thanks, Craig. I've already implemented similar solution for bzr. It will be released as bzr 1.16 or later, IIUC.
bialix
+2  A: 

Mercurial

On Linux, I think Mercurial just encodes in whatever is the system's encoding (correct me if I'm wrong). So best to set Linux up for UTF-8 for cross-platform compatibility. This is the default for many modern distributions.

On Windows, Mercurial (due to Python's byte string handling) uses the system code page. This just about guarantees bad cross-platform interoperation for non-ASCII characters.

fixutf8 Extension for Windows

There is an externally-created Mercurial extension called fixutf8 for Windows which properly handles all Unicode characters (even those outside the current code page) and encodes the filenames as UTF-8 in the Mercurial repository. It thus enables interoperation with Linux as long as Linux is using the UTF-8 encoding. I tried enabling it on my Windows set-up last week, and had a couple of problems with installation. Since then, one problem has been fixed. Now the only issue is that the binary Mercurial distributions are built with Python 2.4, while fixutf8 requires Mercurial to be built with Python 2.5 or higher to load fixutf8. I expect this will be resolved in the near future.

Craig McQueen
When I've looked at the Mercurial code I did not find any unicode support for filenames.
bialix
I maintain the fixutf8 extension and use it daily with a binary build of HG. File a bug http://bitbucket.org/stefanrusek/hg-fixutf8/ and I will gladly take a look.
Stefan Rusek
Thanks Stefan. I've heavily edited this answer now that I've successfully installed fixutf8 and found that it works well. I was held back by a bug that you've fixed in the last few days.
Craig McQueen
I've had a [problem with the `fixutf8` extension](http://bitbucket.org/stefanrusek/hg-fixutf8/issue/24/error-using-rename-command) recently. That problem seems to be fixed by a [fork of `fixutf8`](http://bitbucket.org/tinyfish/hg-fixutf8).
Craig McQueen
+1  A: 

The msysgit project is busy fixing UTF-8 support for Git on Windows. It might be fixed in the next release.

Johan: if they do fix it, come back and update your post. I'm sure someone will find it useful.
quark
Till know (9/2010) it's not fixed!
niels
A: 

According to this page: Bazaar, Codendi, CVSNT, Monotone, Perforce, Rational Team Concert, Subversion, Surround SCM, Synergy. But there are lots of 'Unknowns' on that page.

Benjol