On Thu, Jan 22, 2004 at 01:34:33PM -0600, Jonathan Scott Duff wrote:
: On Thu, Jan 22, 2004 at 11:25:41AM -0800, Larry Wall wrote:
: > Me?  I handle it by making it an adverb on the base operator.  :-)
: 
: Does that mean it should get the colon?  :)

Only if all adverbs in English end in -ly.

Of course, my name ends -ly in Japan--I had to learn to answer to "Rally"
when I was there.  So maybe I still get the colon...  :-)

: > I don't think that ?X? means "Do whatever the mathematicians want X
: > to do."  Unicode operators have to be good for something, after all.
: > 
: > So perhaps its best to call ? and ? "distribution modifiers" or
: > some such.
: 
: Could someone put the non-unicode variants up there so those of us
: with unicode-ignorant MUAs can know what exactly we're talking about?

Those are just the German/French quotes that look like >> and <<.

: Or alternatively (and certainly better), could someone clue me on how
: to make mutt unicode-aware?

Modern versions of mutt are already unicode aware--that's what I'm using.
Make sure .muttrc has

    set charset="utf-8"
    set editor="vim"            (or any editor that can handle utf-8)
    set send_charset="us-ascii:iso-8859-1:utf-8"

The main thing is you have to make sure your xterm (or equivalent)
unicode aware.  This starts a (reversed video) unicode terminal on
my machine:

LANG=en_US.UTF-8 xterm \
    -fg white -bg black \
    -u8 \
    -fn '-Misc-Fixed-Medium-R-Normal--18-120-100-100-C-90-ISO10646-1'

I'm also using gnome-terminal 2.4.0.1, which knows how to do utf-8
if you tell it in the preferences.

Of course, this is all from the latest Fedora Core, so your software
might not be so up-to-date.  And other folks might prefer something
other than en_US.  It's the .UTF-8 that's the important part though.
I run some windows in ja_JP.UTF-8.  And, actually, my send_charset is

    set send_charset="us-ascii:iso-8859-1:iso-2022-jp:utf-8"

because I have Japanese friends who prefer iso-2022-jp because they
don't know how to read utf-8 yet.

Larry

Reply via email to