From: Castor Fu <castor@drizzle.Stanford.EDU>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: UTF tools
Date: Thu, 7 Apr 1994 21:06:55 -0400 [thread overview]
Message-ID: <199404080106.SAA18926@hassle.Stanford.EDU> (raw)
Anyone have the equivalent of enscript for UTF? I've
been commenting my code using the unicode character set,
and I've got the urge to print it. . . .
I don't really need a full character set, but something which could
handle the math ones would be nice. . .
-castor
reply other threads:[~1994-04-08 1:08 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=199404080106.SAA18926@hassle.Stanford.EDU \
--to=castor@drizzle.stanford.edu \
--cc=sam-fans@hawkwind.utcs.toronto.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).