From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25443 invoked by alias); 2 Jul 2013 01:11:37 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17847 Received: (qmail 4834 invoked from network); 2 Jul 2013 01:11:32 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 Received-SPF: neutral (ns1.primenet.com.au: 66.111.4.25 is neither permitted nor denied by SPF record at _netblocks3.google.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=from:to:subject:date:message-id :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=smtpout; bh=2pWepHWxAEf3IP+eWtRHKn GswK4=; b=qN7ENBV+QEAyr+gUeEA1d9HjiUDzK4Lr6V7Z3Nudl7e1KPneJySl8I ez6hlatUbZwyRv7MoCtNxnRIPjhpNARjFVXHHm+ynSnHQriN22fSvbZRZ5HVQRPp hp4tEvLebyJ3jmb8BsRlKQMlX2k2OP7f7Mr5XGSMiVlRVdVtpFzog= X-Sasl-enc: HzZaxQk5J6ZTqGhQe8KUzIl+FV3G7K2UT6FG3G1sdfeX 1372727484 From: "TJ Luoma" To: "Zsh-Users List" Subject: Re: input foo, output '[F|f][O|o][O|o]'? Date: Mon, 01 Jul 2013 21:11:13 -0400 Message-ID: In-Reply-To: References: <8B5FCBBB-DF52-43E1-8924-AAE08263D76F@goldweb.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.5.4r3323) On 1 Jul 2013, at 20:38, Kurtis Rader wrote: > In short, for any reasonable regex implementation there is no need to > resort to something as clumsy  as what you propose. You would certainly be correct in the vast majority of cases. However, I happen to be dealing with one of the small percentages of exceptions, as the AddDescription implementation in Apache does not have a 'reasonable regex' implementation for this, as far as I have been able to tell. > Keep in mind to that for anything other than ASCII this is impossible, > for all practical purposes, to implement correctly using the strategy > you had in mind. Yup. But these are filenames on a web server and will only be ASCII. Thanks again TjL