From: Thomas Singer <thomas.singer@syntevo.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: Git, Mac OS X and German special characters
Date: Thu, 20 May 2010 12:38:43 +0200 [thread overview]
Message-ID: <4BF51133.6040504@syntevo.com> (raw)
In-Reply-To: <4BF4F7D7.60002@drmicha.warpmail.net>
On 20.05.2010 10:50, Michael J Gruber wrote:
> There seems to be no way to reliably detect which one HFS+ uses.
IIRC, HFS+ always stores and reports the file names with decomposed UTF-8,
even if the file is created using composed UTF-8. IMHO, Git should
standardize on the file and text encoding (e.g. commit messages) used in the
repository, so such problems can't occur. SVN has standardized on "UTF-8" in
the repository, but had/s similar problems on OS X with the decomposed
characters:
http://subversion.tigris.org/issues/show_bug.cgi?id=2464
Tom
next prev parent reply other threads:[~2010-05-20 10:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 7:26 Git, Mac OS X and German special characters 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 [this message]
2010-05-20 8:55 ` demerphq
-- strict thread matches above, loose matches on Subject: below --
2011-10-01 12:44 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
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=4BF51133.6040504@syntevo.com \
--to=thomas.singer@syntevo.com \
--cc=git@drmicha.warpmail.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.