From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 32424 invoked from network); 15 Dec 2022 02:05:22 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 15 Dec 2022 02:05:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20210803; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:Message-ID:Date:Content-ID: Content-Type:MIME-Version:Subject:To:References:From:In-reply-to:Reply-To:Cc: Content-Transfer-Encoding:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=yMlWZlX569lx/C1xkM2EblcFxJyVuFDksJnJk+N1k7U=; b=qtlyRq6mz+OW/OLuFqwwea/7lB H2YJi/HEJ2YNT3qDae23I3G0KxqPMQ+9iRKcUPB6soS4qKkqpKNEz0Gd00vSOt7bfDHdlzfco4GJc k6pu+A6Tm5NcD71922BYXRyMkZM9QK5aBSTb/AWYQiVehO5P58dLU2yTHlDCKSI/7rBmY+2kta5by 5d48bfobW+mGJkEh098G/oO1PmNel316Z+n4lqBbVFwtD+wlb0o0QyjdJXBXQbqJpxWzn6I3dgpx7 xFDUCQ67fArLil03Jk8bNA2iUIJJPOeEorLey1h106RW+z++zzm7No6s1OY3XBF76EEvPVF0H/Lb5 6Lu9lj3A==; Received: by zero.zsh.org with local id 1p5dcg-0003hq-CI; Thu, 15 Dec 2022 02:05:22 +0000 Received: by zero.zsh.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) id 1p5dZ0-0003KQ-Lr; Thu, 15 Dec 2022 02:01:34 +0000 Received: from [192.168.178.21] (helo=hydra) by mail.kiddle.eu with esmtp(Exim 4.95) (envelope-from ) id 1p5dYz-000ETM-Ln for zsh-workers@zsh.org; Thu, 15 Dec 2022 03:01:33 +0100 In-reply-to: <20221210090626.mkv7bxeqnap6awah@chazelas.org> From: Oliver Kiddle References: <20221209154225.2z3lbtf422ypnmjx@chazelas.org> <99492-1670616302.663548@1brw.o7tP.wgJL> <20221210090626.mkv7bxeqnap6awah@chazelas.org> To: Zsh hackers list Subject: Re: read -d $'\200' doesn't work with set +o multibyte (and [PATCH]) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <55634.1671069693.1@hydra> Date: Thu, 15 Dec 2022 03:01:33 +0100 Message-ID: <55635-1671069693.668786@bPS-.5Kzj.qxen> X-Seq: 51216 Archived-At: X-Loop: zsh-workers@zsh.org Errors-To: zsh-workers-owner@zsh.org Precedence: list Precedence: bulk Sender: zsh-workers-request@zsh.org X-no-archive: yes List-Id: List-Help: , List-Subscribe: , List-Unsubscribe: , List-Post: List-Owner: List-Archive: On 10 Dec, Stephane Chazelas wrote: > Is a requirement on the *application*, not the implementation. > That is, it only specifies what's meant to happen when the input > doesn't contain NULs. > > So I think we're good here. Ok, good. I'm afraid I'm not very good at interpreting the specific language used in those standards. > I'm susbscribed to both austin-group-l and zsh-workers but don't > follow them very closely. I try to mention things relevant to > zsh here when I spot them on austin-group-l and I try to argue > there about things that would conflict with the zsh way for no > good reason. Thanks for passing such things on. I did subscribe some time ago but time is limited and it didn't spark joy so I unsubscribed. I still have a login for the site at least. > GB18030 and BIG5/BIG5-HKSCS may still be relevant. They don't > work on Shift state like Shift-JIS, but many of their characters > have bytes <= 0x7f, and zsh doesn't really work with them for > that reason. Thanks for the answer. Oliver