help / color / mirror / code / Atom feed
From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: Test ./E03posix.ztst was expected to fail, but passed.
Date: Wed, 23 Mar 2022 16:14:46 +0900	[thread overview]
Message-ID: <E516EDC9-32C2-4C23-9064-76298D3CA85D@kba.biglobe.ne.jp> (raw)
In-Reply-To: <CAH+w=7baJiXR1MJy00VfeHDymzK7q-xXQXL1TbeeJ0RAW1dV9A@mail.gmail.com>

> 2022/03/23 6:04, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Mon, Mar 21, 2022 at 8:33 PM Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>> [2] Why is the test marked "expected to fail"?
> POSIX printf counts bytes regardless of locale, zsh printf counts
> characters in multibyte locales.

>> What does 'F:This is considered a bugfix in zsh' mean?

> Specifically in this instance, we consider it a POSIX bug that '%s'
> always counts byte positions and that zsh has fixed this when it
> counts character positions.

Thanks for the explanation.

If the 'expected to fail' test exists for reminding us that we are
(intentionally?) contradicting with POSIX, the test need be run under
UTF-8 locale (in D07multibyte.ztst), with

>< Stéphane>      # single ' ' before 'S'

as the POSIX-conforming output. Am I right?

  parent reply	other threads:[~2022-03-23  7:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 16:33 Vincent Lefevre
2022-03-15 16:53 ` Mikael Magnusson
2022-03-16 15:30   ` Jun. T
2022-03-22  3:32     ` Jun T
2022-03-22 13:03       ` Vincent Lefevre
2022-03-22 21:04       ` Bart Schaefer
2022-03-23  2:26         ` Vincent Lefevre
2022-03-23 10:38           ` Stephane Chazelas
2022-03-23 16:17             ` Vincent Lefevre
2022-03-23  7:14         ` Jun T [this message]
2022-03-29  9:10           ` Jun T
2022-03-29  9:00     ` Jun T

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E516EDC9-32C2-4C23-9064-76298D3CA85D@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).