Hi there!
On 25 Mar 00, at 21:31, Istv�n Szendr� wrote
about "Re[2]: Okay, who wants to test this":
> AVK> But wait, I've found a bug in that script today: it won't work
> AVK> against *your* messages (i.e. when the From: name contains 8bit, in either
> AVK> QP or base64 form).
> BY the way, is this allowed or am I guilty in violating RFCs?
It _is_ allowed, it's just that _I_ don't like it. Anyhow, in many existing MUAs
users just won't be able to read your name properly. For example, in Pegasus
with Russian font setup your surname looks exactly this way: Szendrx. And I
wouldn't like my own name to be displayed God knows how;-) Therefore I use
a Latin-transliterated form for From: address. In fact, my name looks
differently, it's ��������� ����̣�;-))
> AVK> The corrected script is attached to this one.
> It isn't :-(((
Well, it definitely is, don't forget that I received my message back, too;-) I
mean, from the list;-))
> AVK> BTW, if somebody wants a script that would scan a _directory_ for
> AVK> NNNNN.msg files and autorename these in any meaningful way, judging by
> AVK> the headers, you're welcome to ask for it <sigh>;-)
> <Asking abjectly and covering his face in shame>
Okay, when I have time;-)
> One more thing: your message used the Cyrillic code page. Now whatever
> I do in this response, it won't change to Central European.
This is a feuture of TB, and _I_ like it. Reconsider: I'm using Russian in my
message to you, hence the message goes out in KOI8-R encoding. TB makes
it's best to display it properly on your end, then you open the reply. _If_ TB
were to use _your_ codepage in reply, it would definitely need to switch the
fontscript, too, since otherwise you wouldn't be able to see your _own_ highbit
characters. But then, you won't be able to see _my_ Russian text properly,
too, since there are no Russian characters in the central European font script.
That's why TB assumes that since you're willing to reply to a message in
Russian, you _can_ read (and possibly even write;-)) Russian, and therefore
it preserves the charset used in my original message (and the font script,
accordingly). OTOH you always can override this by explicitely changing the
encoding _after_ you open the reply (rightclicking the status line).
BTW, this your message came in CE encoding, so I assume that you
managed to do what you wanted to already;-)
--
SY, Alex
(St.Petersburg, Russia)
http://mph.phys.spbu.ru/~akiselev
---
Thought for the day:
Everything in excess! To enjoy the flavor of life, take big
bites. Moderation is for monks.
---
PGP public keys on keyservers:
0xA2194BF9 (RSA); 0x214135A2 (DH/DSS)
fingerprints:
F222 4AEF EC9F 5FA6 7515 910A 2429 9CB1 (RSA)
A677 81C9 48CF 16D1 B589 9D33 E7D5 675F 2141 35A2 (DH/DSS)
---
--
--------------------------------------------------------------
View the TBBETA archive at http://tbbeta.thebat.dutaint.com
To send a message to the list moderation team double-click HERE:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBBETA, double-click HERE:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
