From: "Nikolai Weibull" <now@bitwi.se>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: more sorting: multibyte case-insensitivity
Date: Mon, 22 Jan 2007 18:22:00 +0100 [thread overview]
Message-ID: <dbfc82860701220922k2d199579t6728f2a519f15f83@mail.gmail.com> (raw)
In-Reply-To: <070122075835.ZM10252@torch.brasslantern.com>
On 1/22/07, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 22, 2:23pm, Peter Stephenson wrote:
> } This extends the new sort code to handle lowering of case properly with
> } multibyte characters.
> I'm beginning to worry that we're piling up some pretty severe performance
> penalties with this stuff.
I'll trade almost any amount of performance for proper handling of
multibyte characters.
nikolai
prev parent reply other threads:[~2007-01-22 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 14:23 Peter Stephenson
2007-01-22 15:58 ` Bart Schaefer
2007-01-22 16:06 ` Peter Stephenson
2007-01-22 17:22 ` Nikolai Weibull [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=dbfc82860701220922k2d199579t6728f2a519f15f83@mail.gmail.com \
--to=now@bitwi.se \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).