From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "José Fonseca" <j_r_fonseca@yahoo.co.uk>
Cc: git@vger.kernel.org
Subject: Re: [EGIT] UTF-8 in author names in history views read as ISO-8859-1
Date: Thu, 27 Sep 2007 20:59:32 +0200 [thread overview]
Message-ID: <200709272059.32934.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <200709272053.41795.robin.rosenberg.lists@dewire.com>
torsdag 27 september 2007 skrev Robin Rosenberg:
> Encoding is largeley neglected. Actually conversions are made because one
> has to, but there is no consistency there. Git mostly neglect encodings and
> so does anything that attempt to be compatible with it. I have some patches
> towards improvement. A problem is that conversion to or from UTF-8 and back
> are not reversible, especially when the input is invalid for the conversion. This
> *will* happen when dealing with git repos that contain non-ascii comments or
> file names.
A confession. The only thing we do cater for is the encoding header in commits.
-- robin
prev parent reply other threads:[~2007-09-27 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 22:04 [EGIT] UTF-8 in author names in history views read as ISO-8859-1 José Fonseca
2007-09-27 18:53 ` Robin Rosenberg
2007-09-27 18:59 ` Robin Rosenberg [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709272059.32934.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=j_r_fonseca@yahoo.co.uk \
/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).