From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1042 invoked by alias); 28 Nov 2002 18:31:17 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 1021 invoked from network); 28 Nov 2002 18:31:15 -0000 Received: from unknown (HELO myware.akkadia.org) (24.221.190.179) by sources.redhat.com with SMTP; 28 Nov 2002 18:31:15 -0000 Received: from redhat.com (myware.akkadia.org [192.168.7.70]) (authenticated bits=0) by myware.akkadia.org (8.12.5/8.12.5) with ESMTP id gASIVOYA019786; Thu, 28 Nov 2002 10:31:25 -0800 Message-ID: <3DE660FC.6030403@redhat.com> Date: Thu, 28 Nov 2002 10:31:00 -0000 From: Ulrich Drepper User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andreas Schwab CC: libc-hacker@sources.redhat.com Subject: Re: fnmatch and invalid multibyte characters References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00073.txt.bz2 Andreas Schwab wrote: > When fnmatch detects an invalid multibyte character it should fall back to > single byte matching, so that "*" has a chance to match such a string. And why is this better or more correct? Is there existing practice? -- --------------. ,-. 444 Castro Street Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA Red Hat `--' drepper at redhat.com `---------------------------