git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Constantine Plotnikov <constantine.plotnikov@gmail.com>
To: git@vger.kernel.org
Subject: Q: description of file name encoding approach used by git
Date: Wed, 11 Feb 2009 14:56:24 +0300	[thread overview]
Message-ID: <85647ef50902110356l19870259t9de22fd8827ac144@mail.gmail.com> (raw)

I'm interested if there is some document that specifies the approach
of encoding non-ASCII file names used by the git and related issues.
I'm particularly interested in cross-platform issues, since I'm
writing plugin for cross-platform tool.

My understanding based on previous discussions of the issue is that
GIT saves file names as bytes in the tree objects without specifying
actual encoding used. And there will be problem if different clients
use different system encoding.

The list of issues known to me is:
1. All Linux and Unix machines that use the same git repository should
use the same encoding (ru_RU.KOI-8 and ru_RU.UTF-8 are not
compatible).
2. On windows UTF-8 codepage should be specified for msys git in order
to force it using UTF-8 if any cross-platform support is wanted. (I do
not known about cygwin git).
3. As I understand, there is an unresolved problem with Mac OSX HFS+
case insensitive file system due to file name normalization.
4. Git log seems to ignore encoding specified on the command line when
printing file names (for example in case of --name-status).

Are these issues still open?
Are there other issues?

Regards,
Constantine

             reply	other threads:[~2009-02-11 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 11:56 Constantine Plotnikov [this message]
2009-02-11 16:08 ` Q: description of file name encoding approach used by git 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=85647ef50902110356l19870259t9de22fd8827ac144@mail.gmail.com \
    --to=constantine.plotnikov@gmail.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).