From: Alan Watson <alan@oldp.nmsu.edu>
To: sam-fans@hawkwind.utcs.toronto.edu, wilyfans@jli.com
Subject: UTF support for mailx
Date: Thu, 11 Jul 1996 12:37:33 -0400 [thread overview]
Message-ID: <9607111637.AA15151@oldp.nmsu.edu> (raw)
I've hacked together support for UTF in mailx. It does the things you
might expect: converting to and from 7-bit MIME encodings and the
ISO-8859-X character sets where appropriate. See
http://charon.nmsu.edu/~awatson/utf-mailx/
I've been using it for a few months now, so it should be fairly
stable. If you find bugs, though, please let me know.
Alan
reply other threads:[~1996-07-11 16:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9607111637.AA15151@oldp.nmsu.edu \
--to=alan@oldp.nmsu.edu \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
--cc=wilyfans@jli.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;
as well as URLs for NNTP newsgroup(s).