All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "Jeff King" <peff@peff.net>,
	"Ævar Arnfjörð" <avarab@gmail.com>
Subject: Re: [PATCH 00/22] Refactor to accept NUL in commit messages
Date: Mon, 24 Oct 2011 13:09:19 +0200	[thread overview]
Message-ID: <87wrbu4peo.fsf@gmail.com> (raw)
In-Reply-To: <CACsJy8AsfQnS3L1fabzB-z7BdH=jvB=XNnmP2RZu0qp7C1uGYQ@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Mon, 24 Oct 2011 16:10:08 +1100")

On Mon, 24 Oct 2011 07:10:08 +0200
Nguyen Thai Ngoc Duy wrote:

> This is argument for the sake of argument because I don't use utf-16
> and do not care much. UTF-16 can have more code points and some may
> prefer utf-16 to utf-8.

I suspect this is really tangential to this thread, but I can't make
much sense of that last sentence -- if you meant that UTF-16 is somehow
more apt at encoding Unicode code points than UTF-8, then that's not the
case. Both can represent all Unicode characters. If anything, things are
_more_, not less complicated in UTF-16, which apart from the NUL and
endianness complications has to jump through the "surrogate pairs" hoop
for code points bigger than U+FFFF (so you'll actually find many apps
with buggy UTF-16 implementation which break for those code points,
unlike when using UTF-8).

-- 
Štěpán

  reply	other threads:[~2011-10-24 11:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1319277881-4128-1-git-send-email-pclouds@gmail.com>
2011-10-22 19:09 ` [PATCH 00/22] Refactor to accept NUL in commit messages Jeff King
2011-10-23 10:44   ` Robin Rosenberg
2011-10-23 16:09     ` Jeff King
2011-10-22 22:47 ` Junio C Hamano
2011-10-23  1:24   ` Nguyen Thai Ngoc Duy
2011-10-23  5:51     ` Junio C Hamano
2011-10-23  6:37       ` Nguyen Thai Ngoc Duy
2011-10-23  9:46         ` Junio C Hamano
2011-10-23 10:17           ` Nguyen Thai Ngoc Duy
2011-10-23 16:07           ` Jeff King
2011-10-23 20:16             ` Junio C Hamano
2011-10-24  4:40               ` Junio C Hamano
2011-10-24  5:10                 ` Nguyen Thai Ngoc Duy
2011-10-24 11:09                   ` Štěpán Němec [this message]
2011-10-24 22:45                 ` Jeff King
2011-10-25 10:16                   ` Štěpán Němec
2011-10-25 14:07                   ` Junio C Hamano
2011-10-27 18:13                     ` Jeff King
2011-10-27 18:47                       ` Junio C Hamano
2011-10-27 18:52                         ` Jeff King
2011-10-27 19:14                           ` Junio C Hamano
2011-10-27 23:44                             ` Jeff King
2011-10-28  0:03                               ` Junio C Hamano
2011-10-28  0:19                                 ` Jeff King
2011-10-28  1:40                               ` Miles Bader
2011-10-28  4:07                                 ` Junio C Hamano

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=87wrbu4peo.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.