From: Jacob Keller <jacob.keller@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Ax Da <discussion@gmx.net>,
Git mailing list <git@vger.kernel.org>
Subject: Re: git has issues with international characters in branch names
Date: Sun, 5 May 2019 21:32:41 -0700 [thread overview]
Message-ID: <CA+P7+xraNUBN_UjN+fL0vfTEzpHmNYUj5f=YLUF9etxo79zEPw@mail.gmail.com> (raw)
In-Reply-To: <20190505181444.GA7458@genre.crustytoothpaste.net>
On Sun, May 5, 2019 at 11:16 AM brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>
> On Sun, May 05, 2019 at 12:27:31PM +0200, Ax Da wrote:
> > The documentation doesn't seem to be clear about which characters are allowed as branch names.
> >
> > We have been using umlauts and apostrophes in our branch names, and both are having issues:
> >
> > - apostrophe:
> > git removes the apostrophes from the branch name when creating/pushing a branch.
> > In our TFS server repository we're having the same branch name twice: Once with apostrophes,
> > and once without. And I don't seem to be able to delete the one without apostrophes.
> >
> > - umlauts:
> > The umlauts are not correctly interpreted when SMB is used. "gemäss" becomes "gem<C3><A4>ss".
> > (See images attached.)
>
> I don't think Git itself has a problem with Unicode. I literally just
> the other day created a branch with a Unicode apostrophe and pushed it
> to GitHub successfully using macOS. It is possible that TFS doesn't like
> them; that depends on the hosting solution you use. If you're seeing
> problems with TFS, I'd reach out to Microsoft for assistance.
>
> It looks also like the Git CMD interface isn't rendering them properly.
> I would try using Git Bash instead, and if that doesn't work, please
> report that to Git for Windows. The folks there will have a better idea
> about the portability issue that's occurring; I expect there's a wart
> there somewhere between UTF-8 and UTF-16. It may also be that SMB is not
> a good choice for sharing repositories if you require
> internationalization, or you may need to change the character set your
> SMB server uses.
In my experience, the regular command prompt will have significant
troubles displaying UTF-8 characters.
I had better luck in Git Bash, but I don't recall if I had to do
something for it.
Thanks,
Jake
>
> You may also, depending on which version of Windows you are using, have
> better luck at the command line with Windows Subsystem for Linux.
> --
> brian m. carlson: Houston, Texas, US
> OpenPGP: https://keybase.io/bk2204
prev parent reply other threads:[~2019-05-06 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 10:27 git has issues with international characters in branch names Ax Da
2019-05-05 18:14 ` brian m. carlson
2019-05-06 4:32 ` Jacob Keller [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+P7+xraNUBN_UjN+fL0vfTEzpHmNYUj5f=YLUF9etxo79zEPw@mail.gmail.com' \
--to=jacob.keller@gmail.com \
--cc=discussion@gmx.net \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).