git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Peter Krefting <peter@softwolves.pp.se>
Cc: Johannes Sixt <j.sixt@viscovery.net>, git@vger.kernel.org
Subject: Re: [RFC PATCH] Windows: Assume all file names to be UTF-8 encoded.
Date: Mon, 2 Mar 2009 22:21:09 +0100	[thread overview]
Message-ID: <200903022221.10254.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0903022146510.20047@perkele.intern.softwolves.pp.se>

måndag 02 mars 2009 21:52:41 skrev Peter Krefting <peter@softwolves.pp.se>:
> Robin Rosenberg:
> 
> > I'd be almost happy with a solution that works when people are interacting 
> > using the subset that is convertible between the character sets in use.
> 
> You mean like the "invariant" character set? :-) Using Unicode internally 
> (in whatever encoding) is nice, the problem is when you have to interact 
> with the world around you.

Not sure what that is. I mean that in a local nordic, setting people can use iso-8859-1|15/windows-1252/UTF-8 for their needs be means of converting the characters as-needed without loss, with very few practial restrictions. 

For a larger setting that won't do, but then the need is typically less since people tend to use ASCII only, or you jump to all unicode.

Just because I use UTF-8 doesn't mean I use start using more characters in practice.

-- robin

  reply	other threads:[~2009-03-02 21:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  8:47 [RFC PATCH] Windows: Assume all file names to be UTF-8 encoded Peter Krefting
2009-03-02 10:30 ` Johannes Sixt
2009-03-02 10:46   ` Peter Krefting
2009-03-02 10:56     ` Johannes Schindelin
2009-03-02 12:03       ` Peter Krefting
     [not found]         ` <a2633edd0903020512u5682e9am203f0faccd0acf6a@mail.gmail.com>
2009-03-02 13:57           ` Peter Krefting
2009-03-02 14:29             ` Thomas Rast
2009-03-02 20:41               ` Peter Krefting
2009-03-03  7:56                 ` Lars Noschinski
2009-03-03 11:54                   ` Peter Krefting
2009-03-03 16:29                     ` Lars Noschinski
2009-03-03 20:59                       ` Robin Rosenberg
2009-03-03  9:47                 ` Dmitry Potapov
2009-03-03 11:48                   ` Peter Krefting
2009-03-03 17:13                     ` Dmitry Potapov
2009-03-04 10:51                       ` Peter Krefting
2009-03-04 14:18                         ` Dmitry Potapov
2009-03-02 12:34     ` Johannes Sixt
2009-03-02 13:12       ` Peter Krefting
2009-03-02 19:58         ` Robin Rosenberg
2009-03-02 20:52           ` Peter Krefting
2009-03-02 21:21             ` Robin Rosenberg [this message]
2009-03-03  5:51               ` Peter Krefting
2009-03-03  9:43 ` Dmitry Potapov
2009-03-03 11:56   ` Peter Krefting
2009-03-07 10:38 ` Robin Rosenberg
  -- strict thread matches above, loose matches on Subject: below --
2009-03-03 18:25 John Dlugosz
2009-03-04 10:53 ` Peter Krefting
2009-03-04 19:34   ` John Dlugosz
2009-03-03 19:36 John Dlugosz
2009-03-03 20:39 John Dlugosz
2009-03-03 21:02 ` Dmitry Potapov
2009-03-03 21:56   ` John Dlugosz

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=200903022221.10254.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=peter@softwolves.pp.se \
    /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).