git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: StGit and charsets

From
Karl Hasselström <kha@treskal.com>
Date
Aug 4, 2008, 15:31 UTC
Message-ID
<20080804153146.GF12232@diana.vm.bytemark.co.uk>
In-Reply-To
<9e4733910808040721n6c47908o9d8fabd8f16293c1@mail.gmail.com>
On 2008-08-04 10:21:20 -0400, Jon Smirl wrote:
> Do you have tests in place to handle the names and comments in
> patches being in different charsets?

There are some tests in t1800 and t1900 that use non-ascii names. Might be others, but a quick grep didn't find them.

> 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.

> Comments should be in English, but people's names may need UTF8.

Mine does, for example. I started my StGit career by making sure it could send out patches that didn't mangle my name. (That's a while ago, though, so my memory's getting a bit rusty.)

> And what about email addresses, does DNS allow Unicode names now?
I think it's up to each TLD whether they want to allow it. See e.g.
  http://en.wikipedia.org/wiki/Internationalized_domain_name
-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Jon SmirlNext: Jon Smirl
Message 2 of 3 in “StGit and charsets”
  1. Jon SmirlAug 4, 2008
  2. Karl HasselströmAug 4, 2008
  3. Jon SmirlAug 4, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.