The message 200510141901.18754.runlevelten@gmail.com from Ten runlevelten@gmail.com contains these words:
On Friday 14 October 2005 01:12, Anthony Anson wrote:
The message 200510140035.41757.runlevelten@gmail.com
from Ten runlevelten@gmail.com contains these words:
Sorry, Ten, your mail is almost unreadable.
On reading that back, I see what you mean. Haha.
I don't think you do...
Still, you were warned - rapid, unconnected and tangential thoughts are=3D20 characteristic of stream of consciousness..
It's not the thoughts, it's the format.
Ahhhh, (*sound of penny dropping*) _now_ I see what you mean, honest. :)
Having been in deep hack for around 4 hours non-stop immediately prior, I=3D20 fired off that mail in a few seconds.
Don't make excuses for the mail software - it's making a pig's ear of formatting the text, especially ends of lines=20
On this note, I suspect that this may be your email client not correctly=20 reading the message as quoted-printable.
It tells me:
Attachment 1: ,text/plain --nextPart1856573.UnSRygy2nE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
This may be as a matter of choice of course (many people consider qp icky),= =20
Indeed I do, but ZIMACS renders properly-formatted qp
but I suspect it's more likely to be related to your client not doing MIME= =20 properly, as evidenced by the empty content-type header etc.
I usually trim unnecessary detail in the reply. I could have sent the full header too...
Speaking of which..
andnon-standard characters.
Your client not giving proper information on what your message contains, is= a=20 reason others reading your mails may see squares and stuff when you use=20 non-standard characters - which is what I see and probably what you see=20 quoted back :)
I only use plain ASCII
You may want to fix/report that behaviour, which could be considered broken.
Anyway, I don't want to stick my neck out and say kmail's doing it right an= d=20 your client's doing it wrong, because I'll want to check that, but your=20 client is doing _some_ stuff wrong which relates to at least one of the=20 problems. :)=20
I'll forward your emu to our Development Guru...
However, if it's your client that just refuses to read qp, blaming qp for t= hat=20 is equivalent to blaming JPEG for vanilla versions of links being plain-tex= t.
We accept we won't see the images if we use something that won't show them = to=20 us...
Like I said, I will check because Kmail's weirdness with quoted-printablene= ss=20 when you quote it (ie: showing the =3D and =3D20 signs in the quote) makes = me=20 suspicious.
If you could send me back a copy of my email as it arrived at your end, I'd= be=20 grateful, thanks :)
Consider it sent - and Cc'd to the developer of ZIMACS. I'll relay his views.
It isn't a critique of linguistics, it's a lament for the absence of plain ASCII
=2E..now this, I can appreciate. I shall try to be mindful of this, though = go=20 easy on me if I forget some time. It would still be multipart, mind you,=20 because of the gpg signature :)
I suspect I'm not the only one to find the qp borked.
I can't help=3D20 wondering - did you ever test that ram?
No. I think the URL may have disappeared up the SCSI with the earlier incarnation of ZIMACS - but if it didn't, I shall be visiting it, ta.
Go on, you know you want to. :)
You may be right.
If I am, could I have it in writing? My other half won't believe it happene= d=20 otherwise :D
Later,
IKWYM - but I think you have it in writing already, yhough it's only in plain ASCII. I could do you a certificate in a blackletter font though and send it as an attachment, but you'll have to d without the seal and the ribbon as they won't go through the modem.
Ten
Ten-Ten