From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13647 invoked from network); 22 Oct 2001 11:32:45 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 22 Oct 2001 11:32:45 -0000 Received: (qmail 3435 invoked by alias); 22 Oct 2001 11:32:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16107 Received: (qmail 3418 invoked from network); 22 Oct 2001 11:32:37 -0000 Date: Mon, 22 Oct 2001 07:32:31 -0400 From: Clint Adams To: Borsenkow Andrej Cc: "'Geoff Wing'" , "'Zsh Hackers'" Subject: Re: multibyte backwarddeletechar Message-ID: <20011022073231.B31806@dman.com> References: <20011022105702.A4297@primenet.com.au> <000001c15ab9$489f8cf0$21c9ca95@mow.siemens.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000001c15ab9$489f8cf0$21c9ca95@mow.siemens.ru>; from Andrej.Borsenkow@mow.siemens.ru on Mon, Oct 22, 2001 at 09:20:37AM +0400 > implementation. Using wchar looks portable but the immediate problem is > that conventional str* functions stop working. Using UTF-8 is appealing Since there are wide equivalents for most str* functions, that's not too severe a problem. I did try once to replace shingetline with something that called a shingetwline (using wide equivalents) then ran it through wcstombs() to return the char * that was wanted. It didn't function properly; probably something I don't understand about wide characters.