3bc42@fidonet.org>
From: alexander koryagin
Hi, Ardith Hinton!
I read your message from 29.04.2013 23:42
about Is it readable? (1).
ak> All your examples with extended characters are skipped because I
ak> have problem sending back my answer.
AH> Understood. I can't help noticing, however, that in your experiment
AH> with DOS test symbols you were able to use the very same
AH> characters. I simply copied the numbers you had used & got exactly
AH> the same results. The following line is one which I quoted from
AH> your original message:
ak>>> N: 130 (Hex: 82) ‚
AH>> e acute
Small amounts of non-standard chars is OK. But in general, the
Russian NNTP server, I used to use, is checking every message so to find
out its charset. When it is clear that there are a lot of chars that
don't belong to KOI8-r charset (when you write many French words with
marks, for instance) server decides that this letter is not in KOI-8 as
it should be, and it refuses to process it. That's why I can't resend
your French lines back to you.
But anyway we can read/write French messages to one another if I use
a European NNTP server with European charset. For instance, when I read
the echo via Paul Quinn NNTP server quinnspost.dyndns.org I can see all
French words in your message perfectly well.
ak>> Using UTF-8 you can print words from all languages in one message.
ak>> But you must have software which supports UTF-8.
AH> So I gather. It's all very well for those who are starting out from
AH> scratch, and it may indeed be the wave of the future. But I don't
AH> expect "Joe Bloggs", who has had a DOS box running flawlessly in
AH> the basement for the past twenty years, to feel inspired by what
AH> for him could be an extreme makeover... regardless of how many
AH> other people believe his system is hopelessly outdated.
What about e-mail? Do you still use a mailer dated 20 years ago? If
you use for instance Mozilla things can be easier (you can use it to
read/write to Fidonet/Usenet. But the matter is not only in client
programs. All NNTP servers must support UTF-8, but it is not the case.
AH> Seems to me you can use N 32-255, when necessary, in such a way
AH> that everybody in Z1 & Z3 who responded to your test understood
AH> what you meant even if the colours were reversed or they couldn't
AH> duplicate what they saw. But it may be too much work sometimes for
AH> what you get out of it. I can see Cyrillic characters if I switch
AH> message editors. If only I'd known, when Dallas & were beta testing
AH> timEd... timEd doesn't give us the option of using your alphabet.
AH> The best alternative we've found so far doesn't allow me to quote
AH> something in Russian & then ask beginner-level questions in
AH> English, unless perhaps there's a toggle I don't know about which
AH> allows me to change horses in mid-stream. I often see Russians
AH> doing that, however. Ahh! Okay... so how would you do it?
First, in MSDOS, at your computer, you have to install russification
driver. Try keyrus v5.2, for instance, from
http://www.softpanorama.org/People/Gurtyak/index.shtml
You will get the toggle between Latin and Russian charset - the key
"Right Shift". It is the default value, can be changed, but the
documentation is in Russian. But Right Shift is not a bad choice, I
checked it. Your text message, in a MSDOS charset, will be received by
one of Russian servers and converted into KOI-8r. I read Russian words
if your write them. When I write message with Russian letters in KO8-r
it will be converted into 8 bit MSDOS char set and you will receive it
in such a form. Run keyrus.com after your system starts and you will be
able to see Russian symbols and type them.
Bye, Ardith!
Alexander Koryagin
fido7.english-tutor 2013
--- ifmail v.2.15dev5.4
* Origin: NPO RUSnet InterNetNews site (2:5020/400)
|
