From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ports from GPL
Date: Mon, 20 Mar 2006 22:00:01 +0200 [thread overview]
Message-ID: <200603202000.k2KK01Xu006954@skeeve.com> (raw)
In-Reply-To: <20060320021808.91DE411FC1@dexter-peak.quanstro.net>
In article <20060320021808.91DE411FC1@dexter-peak.quanstro.net> you write:
>the gnu awk folks are doing a pretty good job, given their constraints.
Thanks! I try, I really do.
>i have not read the sed code (for a while, anyway), but i could imagine
>that it may have the same character set problems as newer versions of gnu grep.
>gnu grep calls mbtowc for each input character, even when not required.
>
>have you tried your test with LC_LANG=C?
Make that LC_ALL=C and you'll be on track. (FWIW, the CVS grep is much
better than the released version; they've been working on this problem.)
And yes, the locale stuff is a *N*I*G*H*T*M*A*R*E*. Much of the heavy
lifting was done by others for the dfa and regex code, but I've done
my share to get it working too, and I must admit it's often a PITA.
Almost always the differences in behavior from LC_ALL=C to LC_ALL=xxx.UTF-8
are due to the locale definitions, not to gawk's handling of UTF
characters. That all happens in the (GNU) library, below the level
where I can do anything about it.
OTOH, when I get fan mail from people in China and other such places
who are able to *get their work done* using gawk, it makes things
much more worthwhile.
And, to completely change the subject, if anyone on this list wants to
hire a telecommuter who would LOVE to finally make the jump to Plan 9
without looking back, please drop me a line...
Arnold
--
Aharon (Arnold) Robbins --- Pioneer Consulting Ltd. arnold AT skeeve DOT com
P.O. Box 354 Home Phone: +972 8 979-0381 Fax: +1 206 350 8765
Nof Ayalon Cell Phone: +972 50 729-7545
D.N. Shimshon 99785 ISRAEL
next prev parent reply other threads:[~2006-03-20 20:00 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 14:11 erik quanstrom
2006-03-17 14:22 ` Brantley Coile
2006-03-17 15:40 ` Ronald G Minnich
2006-03-18 0:39 ` geoff
2006-03-18 0:59 ` erik quanstrom
2006-03-18 1:16 ` Lyndon Nerenberg
2006-03-18 1:18 ` George Michaelson
2006-03-19 14:43 ` David Leimbach
2006-03-20 2:18 ` erik quanstrom
2006-03-20 3:39 ` uriel
2006-03-20 11:50 ` erik quanstrom
2006-03-20 20:00 ` Aharon Robbins [this message]
2006-03-21 2:41 ` erik quanstrom
2006-03-20 19:50 ` Aharon Robbins
2006-03-20 19:59 ` George Michaelson
2006-03-21 23:43 ` Jack Johnson
-- strict thread matches above, loose matches on Subject: below --
2006-03-21 1:56 erik quanstrom
2006-03-21 3:43 ` dmr
2006-03-18 19:01 erik quanstrom
2006-03-18 14:14 erik quanstrom
2006-03-18 18:47 ` Skip Tavakkolian
2006-03-18 14:03 erik quanstrom
2006-03-18 2:03 dmr
2006-03-18 6:12 ` Bruce Ellis
2006-03-18 6:24 ` Tim Wiess
2006-03-18 6:36 ` Bruce Ellis
2006-03-18 13:31 ` Brantley Coile
2006-03-18 13:30 ` Brantley Coile
2006-03-18 16:28 ` George Michaelson
2006-03-18 23:13 ` Brantley Coile
2006-03-19 1:03 ` geoff
2006-03-17 16:17 erik quanstrom
2006-03-17 15:25 erik quanstrom
2006-03-17 15:21 Mike Haertel
2006-03-17 15:12 erik quanstrom
2006-03-16 8:11 Fernan Bolando
2006-03-16 13:03 ` Anthony Sorace
2006-03-16 16:50 ` Jack Johnson
2006-03-17 1:05 ` erik quanstrom
2006-03-17 11:33 ` Brantley Coile
2006-03-17 12:03 ` Axel Belinfante
2006-03-17 15:39 ` Ronald G Minnich
2006-03-20 3:44 ` Dave Eckhardt
2006-03-20 3:50 ` Skip Tavakkolian
2006-03-20 4:11 ` Russ Cox
2006-03-20 8:13 ` Charles Forsyth
2006-03-24 5:29 ` ems
2006-03-24 7:49 ` Bruce Ellis
2006-03-24 17:14 ` Ronald G Minnich
2006-03-24 17:34 ` erik quanstrom
2006-03-24 18:11 ` Wes Kussmaul
2006-03-24 18:09 ` Ronald G Minnich
2006-03-24 18:26 ` Wes Kussmaul
2006-03-26 9:14 ` ems
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=200603202000.k2KK01Xu006954@skeeve.com \
--to=arnold@skeeve.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).