git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Albert Zeyer <albzey@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: Git, Mac OS X and German special characters
Date: Mon, 03 Oct 2011 21:48:39 +0200	[thread overview]
Message-ID: <4E8A1197.4050708@web.de> (raw)
In-Reply-To: <CAO1Q+jf=RO=sE90-mQdi+=fUWH1RLM+JTubSgSVGC5uDyhU+2A@mail.gmail.com>

The patch has probably not been applied, because it is not a god one.
I have been working on a better version,
but that is not 100% ready to be released.

I can post it in a couple of days,
(and yes, it does a NFD->NFC conversion in readdir() )
/Torsten
On 10/01/2011 02:44 PM, Albert Zeyer wrote:
> Hi,
>
> There are problems on MacOSX with different UTF8 encodings of
> filenames. A unicode string has multiple ways to be represented as
> UTF8 and Git treats them as different filenames. This is the actual
> bug. It should treat them all as the same filename. In some cases (as
> on MacOSX), the underlying operating system may use a normalized UTF8
> representation in some sort, i.e. change the actual UTF8 filename
> representation.
>
> Similar problems also exists in SVN, for example. This was reported
> [here](http://subversion.tigris.org/issues/show_bug.cgi?id=2464).
> There you can find also lengthy discussions about the topic. And also
> [here](http://svn.apache.org/repos/asf/subversion/trunk/notes/unicode-composition-for-filenames).
>
> This was already reported for Git earlier and there is also a patch
> for Git [here](http://lists-archives.org/git/719832-git-mac-os-x-and-german-special-characters.html).
>
> I wonder about the state of this. This hasn't been applied yet. Why?
>
> Regards,
> Albert
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-10-03 19:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-01 12:44 Git, Mac OS X and German special characters Albert Zeyer
2011-10-01 13:39 ` Andreas Ericsson
     [not found]   ` <CAO1Q+jeLEp2ReNc9eOFoJxdGq6oRE3b+O=JvMNU0Kqx_eAX=7w@mail.gmail.com>
2011-10-01 14:24     ` Andreas Ericsson
2011-10-01 19:47       ` Andreas Krey
2011-10-01 22:02         ` Michael Witten
2011-10-01 23:14           ` Jakub Narebski
2011-10-01 23:26             ` Michael Witten
2011-10-01 23:48           ` Albert Zeyer
2011-10-03 19:48 ` Torsten Bögershausen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-20  7:26 Matthias Moeller
2010-05-20  8:34 ` Ævar Arnfjörð Bjarmason
2010-05-20  8:50   ` Michael J Gruber
2010-05-20  8:57     ` demerphq
2010-05-20  9:02     ` Torsten Bögershausen
2010-05-20  9:15       ` Michael J Gruber
     [not found]         ` <4BF5294E.7060206@web.de>
2010-05-20 14:29           ` Michael J Gruber
2010-05-20 15:30         ` Jay Soffian
2010-05-20 15:50       ` Jay Soffian
2010-05-20 18:22         ` Jay Soffian
2010-05-20  9:16     ` Matthias Moeller
2010-05-20 10:38     ` Thomas Singer
2010-05-20  8:55   ` demerphq

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=4E8A1197.4050708@web.de \
    --to=tboegi@web.de \
    --cc=albzey@googlemail.com \
    --cc=git@vger.kernel.org \
    /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).