From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: bash-4.4.12-3
Date: Sat, 28 Jan 2017 20:28:00 -0000 [thread overview]
Message-ID: <588cfec4.ae1d9d0a.76683.7c48@mx.google.com> (raw)
In-Reply-To: <announce.88ae2fe1-9528-9665-709e-93aad8d7e32c@redhat.com>
On Fri, 27 Jan 2017 13:23:53, "Eric Blake (cygwin)" wrote:
> A new release of bash, 4.4.12-3, has been uploaded and will soon reach a
> mirror near you.
Bash printf cannot handle any Unicode blocks starting with "Private Use Area"
(U+E000 - U+F8FF). Note I will be skipping the surrogate blocks[1] (U+D800 -
U+DFFF) for this post, as /bin/printf does not support them either[2]:
$ bash -c 'printf \\uD7FF' | od -tcx1
0000000 355 237 277
ed 9f bf
$ bash -c 'printf \\uE000' | od -tcx1
0000000 355 237 270 355 260 200
ed 9f b8 ed b0 80
$ /bin/printf '\uD7FF' | od -tcx1
0000000 355 237 277
ed 9f bf
$ /bin/printf '\uE000' | od -tcx1
0000000 356 200 200
ee 80 80
Tested with these environments:
cygwin-20170119 bash-4.4.12
cygwin-20170119 bash-4.4.11
cygwin-20170119 bash-4.4.5
cygwin-20170119 bash-4.3.48
cygwin-2.6.1 bash-4.4.12
cygwin-2.6.1 bash-4.4.11
cygwin-2.6.1 bash-4.4.5
cygwin-2.6.1 bash-4.3.48
cygwin-2.6.0 bash-4.4.12
cygwin-2.6.0 bash-4.4.11
cygwin-2.6.0 bash-4.4.5
cygwin-2.6.0 bash-4.3.48
This appears to be Cygwin specific: I tested also on Debian 8.7.1 without issue.
[1] http://wikipedia.org/wiki/Universal_Character_Set_characters#Surrogates
[2] http://lists.gnu.org/archive/html/bug-coreutils/2008-05/msg00068
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-01-28 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 19:44 Eric Blake (cygwin)
2017-01-28 20:28 ` Steven Penny [this message]
2017-01-28 20:44 ` Steven Penny
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=588cfec4.ae1d9d0a.76683.7c48@mx.google.com \
--to=svnpenn@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).