From: Thomas Singer <thomas.singer@syntevo.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: OS X and umlauts in file names
Date: Mon, 23 Nov 2009 19:10:54 +0100 [thread overview]
Message-ID: <4B0AD02E.1040408@syntevo.com> (raw)
In-Reply-To: <200911231845.04325.trast@student.ethz.ch>
Hi Thomas,
Thanks for the feed-back. I know the problem from SVN, too, but I had the
hope, that Git was smarter than SVN for this topic. IIRC, one could get SVN
working "somehow" with umlauts on OS X by setting some environment variable.
Unfortunately, I don't remember the details any more.
Basically, getting it "somehow" to work on OS X is just one minor step. IMHO
Git should standardize on file names in the repository and do the
platform-specific conversion independent of any locale setting, if needed.
Then and only then it would be possible to get the same characters out of
the repository, no matter whether the file was added or checked out on OS X,
Linux or Windows.
At the moment we've got a problem report regarding our SmartGit GUI client:
the user says, on command line it[1] works (German OS X) but not with
SmartGit, for me it doesn't even work on the command line (English OS X). As
you may know, Java uses characters for file names, the Java runtime
internally converts from the platform-specific byte-representation on disk
to characters. I can't simply tunnel the file name as byte array to the
invoked Git command - I simply don't know how to transform the characters of
the file name to a representation the Git command line client will
understand[2].
Tom
[1] e.g. to stage or commit files with umlauts in the file name
[2] executing an external command in Java also "only" works with strings
(aka characters), not with byte sequences
Thomas Rast wrote:
> Thomas Singer wrote:
>> I'm on an English OS X 10.6.2 and I created a sample file with umlauts in
>> its name (Überlänge.txt). When I try to stage the file in the terminal, I
>> can't complete the file name by typing the Ü and hitting the tab key, but I
>> can complete it by typing an U and hitting the tab key. Unfortunately, after
>> executing
>>
>> git stage Überlänge.txt
>
> This is because of OS X's unicode normalisation. Try any of the
> many threads on the topic, e.g.,
>
> http://thread.gmane.org/gmane.comp.version-control.git/70688
>
> The short version is that this Ü is in fact decomposed into an
> U-umlaut duo.
>
> Considering that this leads to endless fun[*] not just with git, and
> that we German speakers have an easy way out (Ueberlaenge), I can only
> suggest that you avoid umlauts wherever possible to preserve
> the sanity of your users.
>
>
> [*] I once had an SVN repo with two different directories both called
> Übungen. Took me a while to figure out what was going on.
>
next prev parent reply other threads:[~2009-11-23 18:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 16:37 OS X and umlauts in file names Thomas Singer
2009-11-23 17:45 ` Thomas Rast
2009-11-23 18:10 ` Thomas Singer [this message]
2009-11-23 18:23 ` Johannes Schindelin
2009-11-23 20:31 ` Thomas Singer
2009-11-23 23:31 ` Jakub Narebski
2009-11-23 18:29 ` Martin Langhoff
2009-11-23 20:26 ` Daniel Barkalow
2009-11-25 8:50 ` Thomas Singer
2009-11-25 9:51 ` B Smith-Mannschott
2009-11-25 10:07 ` Martin Langhoff
2009-11-25 10:19 ` Martin Langhoff
2009-11-25 22:43 ` Andreas Schwab
2009-11-26 8:28 ` Thomas Singer
2009-11-26 17:27 ` Jay Soffian
2009-11-27 10:01 ` Thomas Singer
2009-11-27 10:20 ` Thomas Singer
2009-11-27 10:56 ` Martin Langhoff
2009-11-27 18:35 ` Thomas Singer
2009-11-26 17:23 ` Jay Soffian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B0AD02E.1040408@syntevo.com \
--to=thomas.singer@syntevo.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).