From: rob@plan9.research.att.com
To: <sam-fans@hawkwind.utcs.toronto.edu>
Date: Fri, 18 Mar 1994 12:02:17 -0500 [thread overview]
Message-ID: <94Mar18.120256est.24181@hawkwind.utcs.toronto.edu> (raw)
the "4.1" naming convention is new to me.
as for russian, the posted sam sources support the unicode character
set as encoded by the plan 9 UTF byte-stream encoding, now called
UTF-8 by ISO. the russian poster probably has his own character
set and encoding. to support them, it should be sufficient to modify the
encoding/decoding routines at the periphery; the system will handle
the rest. sam has been used like this in greece since 1986, long before
unicode. the core of the editor doesn't care about the character set
as long as values 0-127 are ASCII. now for our russian friend, that
might not be true, in which case he has a problem. i'd suggest converting
to unicode and UTF - why not be able to edit english AND russian
with the same editor?
-rob
next reply other threads:[~1994-03-18 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-18 17:02 rob [this message]
1994-03-19 5:49 ` Nickolay Saukh
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=94Mar18.120256est.24181@hawkwind.utcs.toronto.edu \
--to=rob@plan9.research.att.com \
--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).