From: daniel@electricrain.com (Dan Sully)
Subject: [sup-talk] Unicode
Date: Wed, 25 Jul 2007 12:00:24 -0700 [thread overview]
Message-ID: <1185389999-sup-7964@zap.electricrain.com> (raw)
In-Reply-To: <1185388707-sup-1409@south>
> If you cat out a utf-8 file, does the terminal display the right thing?
> If so, I would think that would work for Sup... at least under my
> current mental model where ncurses doesn't do anything except put out
> raw bytes which the terminal interprets.
Yep, it displays the right thing. I'll try and get you more data.
--
-D
--
<dsully> please describe web 2.0 to me in 2 sentences or less.
<jwb> you make all the content. they keep all the revenue.
prev parent reply other threads:[~2007-07-25 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 15:34 Dan Sully
2007-07-25 17:42 ` William Morgan
2007-07-25 17:54 ` Dan Sully
2007-07-25 18:50 ` William Morgan
2007-07-25 19:00 ` Dan Sully [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=1185389999-sup-7964@zap.electricrain.com \
--to=daniel@electricrain.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