git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Singer <thomas.singer@syntevo.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Jay Soffian <jaysoffian@gmail.com>,
	Daniel Barkalow <barkalow@iabervon.org>,
	git@vger.kernel.org
Subject: Re: OS X and umlauts in file names
Date: Fri, 27 Nov 2009 19:35:50 +0100	[thread overview]
Message-ID: <4B101C06.1030300@syntevo.com> (raw)
In-Reply-To: <46a038f90911270256w57487e6cq9bda8b98a5384799@mail.gmail.com>

Martin Langhoff wrote:
> have you tried calling git-update-index --add
> --stdin -z? Your original email stated

No, we don't do such a massive change immediately before a release.

>> we've got a problem report regarding our SmartGit GUI client
> 
> so it sounds like you are building a porcelain. In that case, the
> sanest approach is to invoke git-update-index and write to its stdin.

We will try this out after release.

For those who are interested: I've got it working on OS X and Git was not
the problem, but Java. A longer time ago directory.list() or
directory.listFiles() returned the file names with decomposed characters (as
they are stored on OS X hard disk). Now (don't know which Java update
introduced this change) these methods return file names with composed
characters, so I had to decompose them before handing them to the git
executable call.

Nevertheless, the cross-platform-problem remains: if you add files with
umlauts in their names on non-OS X, you will not be able to use them on OS X.

-- 
Tom

  reply	other threads:[~2009-11-27 18:34 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
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 [this message]
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=4B101C06.1030300@syntevo.com \
    --to=thomas.singer@syntevo.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.com \
    --cc=martin.langhoff@gmail.com \
    /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).