From: "İsmail Dönmez" <ismail@namtrac.org>
To: "Peter Stephenson" <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: Multibyte test fails on MacOSX Leopard
Date: Wed, 27 Feb 2008 23:12:02 +0200 [thread overview]
Message-ID: <19e566510802271312k42ab6505m605ed2967305f014@mail.gmail.com> (raw)
In-Reply-To: <20080227193741.6bff30b7@pws-pc>
Hi,
On Wed, Feb 27, 2008 at 9:37 PM, Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
> On Wed, 27 Feb 2008 10:34:56 +0000
> Peter Stephenson <pws@csr.com> wrote:
> > We might be able to compare the output of "sort", I suppose, but that does
> > rely on sort being internationalized. It's probably a reasonable bet if
> > we've got this far.
>
> Let's see what happens.
>
> Index: Test/D07multibyte.ztst
> ===================================================================
> RCS file: /cvsroot/zsh/zsh/Test/D07multibyte.ztst,v
> retrieving revision 1.22
> diff -u -r1.22 D07multibyte.ztst
> --- Test/D07multibyte.ztst 17 Dec 2007 17:11:29 -0000 1.22
> +++ Test/D07multibyte.ztst 27 Feb 2008 19:37:37 -0000
> @@ -322,10 +322,16 @@
> # We ask for case-insensitive sorting here (and supply upper case
> # characters) so that we exercise the logic in the shell that lowers the
> # case of the string for case-insensitive sorting.
> - print -oi HAH HUH HEH HÉH HÈH
> +# As all letters are upper case, however, sort should produce the same order.
> + print -loi HAH HUH HEH HÉH HÈH >zshsort.txt
> + print -l HAH HUH HEH HÉH HÈH | sort >sortsort.txt
> + print Diff output should be empty
> + diff zshsort.txt sortsort.txt
> + print Sort in C locale
>
> (LC_ALL=C; print -oi HAH HUH HEH HÉH HÈH)
> 0:Multibyte characters in print sorting
> ->HAH HEH HÉH HÈH HUH
> +>Diff output should be empty
> +>Sort in C locale
>
> >HAH HEH HUH HÈH HÉH
>
> # These are control characters in Unicode, so don't show up.
>
Gives another error now :
./D07multibyte.ztst: starting.
Testing multibyte with locale en_US.UTF-8
*** /tmp/zsh.ztst.out.2929 2008-02-27 23:10:23.000000000 +0200
--- /tmp/zsh.ztst.tout.2929 2008-02-27 23:10:23.000000000 +0200
***************
*** 4,12 ****
ngs20.txt
ngs100.txt
ngs200.txt
- ngs100.txt
- ngs10.txt
ngs1.txt
! ngs200.txt
! ngs20.txt
ngs2.txt
--- 4,12 ----
ngs20.txt
ngs100.txt
ngs200.txt
ngs1.txt
! ngs10.txt
! ngs100.txt
ngs2.txt
+ ngs20.txt
+ ngs200.txt
Test ./D07multibyte.ztst failed: output differs from expected as shown
above for:
touch ngs1.txt ngs2.txt ngs10.txt ngs20.txt ngs100.txt ngs200.txt
setopt numericglobsort
print -l ngs*
unsetopt numericglobsort
print -l ngs*
Was testing: NUMERIC_GLOB_SORT option in UTF-8 locale
Thanks,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again
prev parent reply other threads:[~2008-02-27 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 21:00 İsmail Dönmez
2008-02-27 10:34 ` Peter Stephenson
2008-02-27 19:37 ` Peter Stephenson
2008-02-27 21:12 ` İsmail Dönmez [this message]
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=19e566510802271312k42ab6505m605ed2967305f014@mail.gmail.com \
--to=ismail@namtrac.org \
--cc=p.w.stephenson@ntlworld.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).