From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: printf %s in UTF-8 is not POSIX-compliant
Date: Tue, 04 Mar 2008 09:40:07 +0000 [thread overview]
Message-ID: <200803040940.m249e7DC012517@news01.csr.com> (raw)
In-Reply-To: <20080304012917.GA15833@prunille.vinc17.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Vincent Lefevre wrote:
> Under UTF-8 locales:
>
> vin:~> zsh-beta -f
> vin% emulate sh
> vin% printf ".%2s.\n" é
> . é.
> vin% /usr/bin/printf ".%2s.\n" é
> .é.
> vin%
>
> As you can see, the zsh printf builtin doesn't behave like the
> coreutils printf, and this is zsh which is wrong. Indeed, the
> precision is the number of bytes, not the number of characters.
That seems to me useless. I can understand in C that a string is a
low-level entity consisting of a set of bytes, but I don't see why a
shell should force the user to count the size of a multibyte character
in the particular locale.
You can fix it by unsetting the MULTIBYTE option.
printf() { emulate -L zsh; unsetopt multibyte; builtin printf "$@" }
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
next prev parent reply other threads:[~2008-03-04 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 1:29 Vincent Lefevre
2008-03-04 1:37 ` Vincent Lefevre
2008-03-04 9:40 ` Peter Stephenson [this message]
2008-03-05 0:27 ` Vincent Lefevre
2008-03-05 1:34 ` Bart Schaefer
2008-03-06 1:27 ` Vincent Lefevre
2008-03-05 10:41 ` Peter Stephenson
2008-03-06 1:39 ` Vincent Lefevre
2008-03-06 9:46 ` Peter Stephenson
2008-03-06 17:09 ` Bart Schaefer
2008-03-06 17:45 ` Peter Stephenson
2008-03-07 2:29 ` Bart Schaefer
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803040940.m249e7DC012517@news01.csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.vuxu.org/mirror/zsh/
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).