From: Jan Hudec <bulb@ucw.cz>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
David Kastrup <dak@gnu.org>,
git@vger.kernel.org
Subject: Re: Stupid quoting...
Date: Sun, 24 Jun 2007 18:25:59 +0200 [thread overview]
Message-ID: <20070624162559.GC6979@efreet.light.src> (raw)
In-Reply-To: <200706241314.46238.robin.rosenberg.lists@dewire.com>
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
On Sun, Jun 24, 2007 at 13:14:45 +0200, Robin Rosenberg wrote:
> söndag 24 juni 2007 skrev Jan Hudec:
> > IMHO it should be the default even for email format. Most projects that use
> > non-ascii filenames probably have all members using same locale. And for
> > such group, it will just work. Also usually the file names, content and
> > commit messages will usually be in the same (though project-specific)
> > encoding, so if charset in content-type is set to that, people with
> different
> > locale able to represent the same characters will still see the names
> > correctly. For other people, the MUA will probably print some escape anyway
> > (it will not screw up the terminal -- it usually knows what it can safely
> > pass to it).
>
> I can't talk about "most" here, only local conditions, i.e. northern Europe
> where both the legacy ISO encodings are very common with a steady increase in
> UTF-8 usage, in the Linux community. People using OSS in windows almost
> exclusively get the windows-1252 (for most practical purposes the same as
> ISO-8859-1).
>
> Even a *very* small set of random people you will wind up with people having
> different locales.
A small set of *random* people will likely have different locales. But
a project that would use non-ascii filenames would probably use some
particular language and thus be run by people that all speak that language --
which means they are not random at all and probably will use the same locale.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-24 16:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 11:30 Stupid quoting David Kastrup
2007-06-13 12:06 ` Alex Riesen
2007-06-13 12:21 ` Johannes Schindelin
[not found] ` <86ejkgvxmb.fsf@lola.quinscape.zz>
2007-06-14 0:51 ` Johannes Schindelin
2007-06-14 6:12 ` David Kastrup
2007-06-14 7:06 ` Alex Riesen
[not found] ` <86hcpb6lr6.fsf@lola.quinscape.zz>
2007-06-14 8:51 ` Alex Riesen
2007-06-14 1:06 ` Steven Grimm
2007-06-14 1:12 ` Johannes Schindelin
2007-06-14 1:19 ` Steven Grimm
2007-06-14 1:34 ` Johannes Schindelin
2007-06-14 8:49 ` Junio C Hamano
2007-06-16 21:03 ` Jakub Narebski
2007-06-18 8:00 ` David Kastrup
2007-06-18 16:19 ` Jeff King
2007-06-19 1:00 ` Johannes Schindelin
2007-06-19 7:44 ` David Kastrup
2007-06-19 9:50 ` Johannes Schindelin
2007-06-19 20:53 ` Olivier Galibert
[not found] ` <86645kutow.fsf@lola.quinscape.zz>
2007-06-20 2:19 ` Johannes Schindelin
2007-06-20 6:19 ` Junio C Hamano
2007-06-20 7:49 ` David Kastrup
2007-06-20 8:40 ` Jakub Narebski
2007-06-20 8:59 ` David Kastrup
2007-06-24 6:50 ` Jan Hudec
2007-06-24 11:14 ` Robin Rosenberg
2007-06-24 11:47 ` Junio C Hamano
2007-06-24 11:58 ` David Kastrup
2007-06-24 12:19 ` Junio C Hamano
2007-06-24 12:41 ` Jeff King
2007-06-24 16:25 ` Jan Hudec [this message]
2007-06-24 19:39 ` Robin Rosenberg
2007-06-24 19:47 ` David Kastrup
2007-06-24 20:17 ` Robin Rosenberg
2007-06-24 20:25 ` David Kastrup
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=20070624162559.GC6979@efreet.light.src \
--to=bulb@ucw.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg.lists@dewire.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).