From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] awk, not utf aware...
Date: Wed, 27 Feb 2008 10:54:27 -0500 [thread overview]
Message-ID: <39d22acfc53470335fdb74156c738feb@plan9.bell-labs.com> (raw)
In-Reply-To: <599f06db0802262336n7e418f22p1a94e2cfbb564069@mail.gmail.com>
> There is split and other functions,
> for example:
>
> toupper("aí")
> gives
> Aí
>
> My guess is that there are many more little (or not) corners where it
> doesn't work.
Yes, and then there is locale: does [a-z] include ij when you run it
in Holland (it should)? Does it include á, è, ô in France (it should)?
Does it include ø, å in Norway (it should not)? And what happens when
you evaluate "è" < "o" (it depends)?
Fixing awk is much harder than anyone things. I had a chat about it with
Brian Kernighan and he says he's been thinking about fixing awk for a
long time, but that it really is a hard problem.
Sape
next prev parent reply other threads:[~2008-02-27 15:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 12:18 Gorka Guardiola
2008-02-26 13:16 ` Martin Neubauer
2008-02-26 14:54 ` Gorka Guardiola
2008-02-26 20:24 ` erik quanstrom
2008-02-26 21:08 ` geoff
2008-02-26 21:21 ` Pietro Gagliardi
2008-02-26 21:24 ` erik quanstrom
2008-02-26 21:32 ` Steven Vormwald
2008-02-26 21:40 ` Pietro Gagliardi
2008-02-26 21:42 ` Pietro Gagliardi
2008-02-26 23:59 ` Steven Vormwald
2008-02-27 2:38 ` Joel C. Salomon
2008-02-29 17:00 ` Douglas A. Gwyn
2008-02-26 21:34 ` erik quanstrom
2008-02-27 7:36 ` Gorka Guardiola
2008-02-27 15:54 ` Sape Mullender [this message]
2008-02-27 20:01 ` Uriel
2008-02-28 19:06 ` [9fans] localization, unicode, regexps (was: awk, not utf aware...) Tristan Plumb
2008-02-28 15:10 ` [9fans] awk, not utf aware erik quanstrom
2008-03-03 23:48 ` Jack Johnson
2008-03-04 0:13 ` erik quanstrom
2008-02-27 9:57 erik quanstrom
2008-02-28 18:54 Aharon Robbins
2008-02-28 21:48 ` Uriel
2008-02-28 22:08 ` erik quanstrom
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=39d22acfc53470335fdb74156c738feb@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.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).