From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-26653-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 12467 invoked from network); 1 Mar 2009 08:06:06 -0000
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.5
Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88)
  by ns1.primenet.com.au with SMTP; 1 Mar 2009 08:06:06 -0000
Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts)
Received: (qmail 9525 invoked from network); 1 Mar 2009 08:06:02 -0000
Received: from sunsite.dk (130.225.247.90)
  by a.mx.sunsite.dk with SMTP; 1 Mar 2009 08:06:02 -0000
Received: (qmail 17059 invoked by alias); 1 Mar 2009 08:05:58 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 26653
Received: (qmail 17045 invoked from network); 1 Mar 2009 08:05:58 -0000
Received: from bifrost.dotsrc.org (130.225.254.106)
  by sunsite.dk with SMTP; 1 Mar 2009 08:05:58 -0000
Received: from mail-fx0-f171.google.com (mail-fx0-f171.google.com [209.85.220.171])
	by bifrost.dotsrc.org (Postfix) with ESMTP id 7DC368058F82
	for <zsh-workers@sunsite.dk>; Sun,  1 Mar 2009 09:05:55 +0100 (CET)
Received: by fxm19 with SMTP id 19so1602251fxm.45
        for <zsh-workers@sunsite.dk>; Sun, 01 Mar 2009 00:05:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:from:to:subject:date
         :user-agent:references:in-reply-to:mime-version:content-type
         :content-transfer-encoding:message-id;
        bh=XZDl+vSdfB3EvCnQX0i/7kt4L+nWOrvNOMkdXnxBL6E=;
        b=MFKFQBZO8WtGg7n22Ik55T1qqDD6XfCr1ND0QfgioY/pjbkCkKPE3fkH8Ozq0h40j7
         Dab0I0FXsTXn2kjzr1CpvmYyDMEmst/phn2Jby9HahoG4uVT/Pwg5IN2eGyWWVpoN6eP
         8XULAH57UHD77hHFJ4Zrrjn3ndSzWoSCTQAsU=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:subject:date:user-agent:references:in-reply-to:mime-version
         :content-type:content-transfer-encoding:message-id;
        b=Z3L5Jw3VuIYMtBz5wUG/xGOmMVOo4YJWAI25bCZpmlb+gxcAaxnkR9CKSgk04Dahfb
         VjSrJd9D7btr1zdXib4LFLitsLZCMDroYV0RLIHbIqzy0dwxZlWReK5Zzc9Mr6pKVP3D
         iARx+I4SYdA2vwKKBvFIff+KssmHFHEMAcCGU=
Received: by 10.86.51.10 with SMTP id y10mr4480007fgy.51.1235894754535;
        Sun, 01 Mar 2009 00:05:54 -0800 (PST)
Received: from cooker.localnet (ppp91-77-249-132.pppoe.mtu-net.ru [91.77.249.132])
        by mx.google.com with ESMTPS id d4sm5304191fga.55.2009.03.01.00.05.52
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Sun, 01 Mar 2009 00:05:53 -0800 (PST)
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: Problems with non-ascii filenames
Date: Sun, 1 Mar 2009 11:05:47 +0300
User-Agent: KMail/1.11.0 (Linux/2.6.29-rc6-1avb; KDE/4.2.1; i686; ; )
References: <19e566510902280137s3bb02510te650364cb03145a9@mail.gmail.com> <19e566510902281428r5d70c182l720b99527ecc1d9d@mail.gmail.com> <20090301021516.GZ4629@prunille.vinc17.org>
In-Reply-To: <20090301021516.GZ4629@prunille.vinc17.org>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1431498.TgoyE3k9ZA";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200903011105.48867.arvidjaar@gmail.com>
X-Virus-Scanned: ClamAV 0.92.1/9058/Sun Mar  1 05:12:39 2009 on bifrost
X-Virus-Status: Clean

--nextPart1431498.TgoyE3k9ZA
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 1 =D0=BC=D0=B0=D1=80=D1=82=D0=B0 2009 05:15:16 Vincent Lefevre wrote:
>
> Normalization insensitivity is not implemented in zsh.

This is not applicable to zsh because zsh does not use UNICODE in the=20
first place. Zsh is using whatever character set and encoding underlying=20
operating system happens to use.

I do not say it is not doable, just that this is not how it is=20
implemented right now.


--nextPart1431498.TgoyE3k9ZA
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkmqQdwACgkQR6LMutpd94xm1QCgycBSZemXh5C2VhvRFi4O820S
L+wAn3r7pllbT2a3WLJgjLRfcI0EgwYT
=MVf3
-----END PGP SIGNATURE-----

--nextPart1431498.TgoyE3k9ZA--