From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: StGit and charsets
Date: Mon, 4 Aug 2008 11:21:31 -0400 [thread overview]
Message-ID: <9e4733910808040821t492b74fcq7c2178690c0a6831@mail.gmail.com> (raw)
In-Reply-To: <20080804153146.GF12232@diana.vm.bytemark.co.uk>
On 8/4/08, Karl Hasselström <kha@treskal.com> wrote:
> On 2008-08-04 10:21:20 -0400, Jon Smirl wrote:
> > I don't work much with international charsets. If someone is using
> > something like Russian or Finish locally, is the metadata in the
> > patch converted to UTF8 before exporting or sending it as mail?
>
>
> I think what happens is that it's assumed to be utf8. No one has
> complained that their non-utf8 locale doesn't work, but my guess is
> that's because those people just haven't tried StGit yet.
This might be worth testing for Asian locales. If Asian locales make
it through ok everything else probably will too.
I don't know enough about Unicode to decode the mangled names, I
suspect they are still in the local charset and haven't been UTF8
converted. Of course the name mangling may be coming from other
tools. There is no way to tell.
This problem happens in other ways in the kernel. There is a file in
the DRM code where two people's names have been inserted in different
charsets. If I set my editor to display one right the other is always
wrong. checkpatch probably needs to make sure that patches are
completely valid UTF8.
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2008-08-04 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 14:21 StGit and charsets Jon Smirl
2008-08-04 15:31 ` Karl Hasselström
2008-08-04 15:21 ` Jon Smirl [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=9e4733910808040821t492b74fcq7c2178690c0a6831@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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).