From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22209 invoked by alias); 13 May 2015 20:20:14 -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: 20208 Received: (qmail 4451 invoked from network); 13 May 2015 20:20:12 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=AaWdAMUe574YxahUi+nkwmkh2T4BIi5Yvteis/Cc1js=; b=YDs605NCSOL66Eagbgb7g/Xn6EHdxmIFcHO3xn+AY9G5Y+87+TuFZRCtC/zg6xYxsX R/72S3pEosw+4oGyqOaVd87JuHCWVFD5LHIW8JkSmgBJcVU1QPN2Z18dzDjsN7Z5zut7 ZXKsdLU/6enBWvHmuAxYgwOOL45knENC9cFnDnPtPkAR1OLvfXJ+OdhihHIWh1Z/Q47V GyJ9q4mYeEXQMIa2kd88AsiTTTWHna+qBGHPlqZ+TzGg955A1rAwCAEZO5cQzOkhi7Sw Fm2iKhq3OdCToR5mBPgmwRpGv1iFIhUKk7cMTPfick8tyd3G1gS1HvUdqGlkKe8tnbni 66XQ== X-Gm-Message-State: ALoCoQmKhCl2wV2IeQ2Br5rEu4pr+owVM1p4P3jhUPMsqZJhKCK39w6ondePgcGQGVs/va0xHHno X-Received: by 10.60.101.195 with SMTP id fi3mr555873oeb.65.1431548410658; Wed, 13 May 2015 13:20:10 -0700 (PDT) From: Bart Schaefer Message-Id: <150513132007.ZM28402@torch.brasslantern.com> Date: Wed, 13 May 2015 13:20:07 -0700 In-Reply-To: <20150513182942.GB4834@lorien.comfychair.org> Comments: In reply to Danek Duvall "Re: zsh doesn't understand some multibyte characters" (May 13, 11:29am) References: <20150513161411.GA4834@lorien.comfychair.org> <150513104350.ZM28203@torch.brasslantern.com> <20150513182942.GB4834@lorien.comfychair.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: zsh doesn't understand some multibyte characters MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 13, 11:29am, Danek Duvall wrote: } } I'm less sure what to do about __STDC_ISO_10646__. I see that most of the } places it's checked you're also checking for __APPLE__, but not all of them } (and I'm not sure why that would be). } } I can talk to our globalization folks who might know why this isn't } defined, or what it should be set to, or whatever, and file a bug if } necessary. You've hit the limit of my knowledge on this point, I'm afraid. Someone else will have to chime in about __STDC_ISO_10646__.