Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Problems with non-ascii filenames
- X-seq: zsh-workers 26653
- From: Andrey Borzenkov <arvidjaar@xxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Problems with non-ascii filenames
- Date: Sun, 1 Mar 2009 11:05:47 +0300
- 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=
- In-reply-to: <20090301021516.GZ4629@xxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <19e566510902280137s3bb02510te650364cb03145a9@xxxxxxxxxxxxxx> <19e566510902281428r5d70c182l720b99527ecc1d9d@xxxxxxxxxxxxxx> <20090301021516.GZ4629@xxxxxxxxxxxxxxxxxxx>
On 1 ÐÐÑÑÐ 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
first place. Zsh is using whatever character set and encoding underlying
operating system happens to use.
I do not say it is not doable, just that this is not how it is
implemented right now.
Attachment:
signature.asc
Description: This is a digitally signed message part.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author