On Friday, 24 Feb 2017 5:42 PM -0500, Ed Cryer wrote:
> μῶλυ δέ μιν καλέουσι θεοί, χαλεπὸν δέ τ' ὀρύσσειν
> ἀνδράσι γε θνητοῖσι· θεοὶ δέ τε πάντα δύνανται.
> (Odyssey 10)
> The gods call it "moly", but it's difficult for mortal men to dig up.
> The gods, however, can do anything.
Looking at Ed's post, I see in the headers these lines:
Date: Fri, 24 Feb 2017 22:42:25 +0000
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 24 Feb 2017 22:41:51 -0000 (UTC)
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
Thunderbird/45.5.0
-----
On Saturday, 25 Feb 2017 5:35 PM -0500, Ned Latham wrote:
>>
>> ????????? ???? ?????? ???????????????? ????????,
>> ??????????????? ???? ??' ?????????????????
>> ??????????????? ???? ??????????????????? ?????????
>> ???? ???? ?????????? ????????????????.
>> (Odyssey 10)
>> The gods call it "moly", but it's difficult for mortal men to dig up.
>> The gods, however, can do anything.
>
> Er ... what *is* that string of question amrks?
From *his* headers I see:
User-Agent: slrn/1.0.1 (Linux)
Date: Sat, 25 Feb 2017 22:35:07 GMT
Note that unlike Ed's post, there is no indication of encoding.
-----
On Saturday, 25 Feb 2017 5:59 PM -0500, John W Kennedy wrote:
> The original passage in Greek. It‘s in UTF-8
Yes.
> and correctly labeled as
> such, so you probably need a more modern newsreader.
Hold on there, *I'm* using slrn, and *I* don't have a problem!
-----
On Sunday, 26 Feb 2017 9:25 PM -0500, John W Kennedy wrote:
>
> UTF-8 is normally end-to-end ASCII-transparent, unless there’s actually
> a 7-bit stage in there. I can read Ed’s original message just fine.
As can I (using slrn).
-----
On Monday, 27 Feb 2017 2:01 AM -0500, Ned Latham wrote:
> No RFC, huh? That means that even 8-bit ASCII is unsafe.
There is no such thing as "8-bit ASCII".
-----
On Monday, 27 Feb 2017 6:59 AM -0500, Ed Cryer wrote:
> You use slrn/1.0.1 (Linux)
> Version 1.0.3 was released October 23rd, 2016, but I doubt it'll solve
> your problem. The source of that appears to be in s-lang2;
>
http://www.slrn.org/docs/slrn-FAQ-1.html#ss1.6
I don't think so. The long-delayed support for Unicode in slrn (or
rather the slang library that it uses ) was IIRC fixed in version 1.0.
Admittedly, I'm using slrn 1.0.3, rather than Ned's slrn 1.0.1, but I
seriously don't think that's the problem.
-----
On Monday, 27 Feb 2017 8:14 AM -0500, Ned Latham wrote:
> Never did like slang. Would have been better to redo (n)curses
> and leave the scripting to python or ruby or some such.
As far as I know, the only justification for slang is that it's used by
slrn. But, I *really* like slrn.
-----
No thank you. "slrn" works just fine for me, and it's a real newsreader
(which I don't think Thunderbird really is).
-----
On Monday, 27 Feb 2017 5:48 PM -0500, Ned Latham wrote:
> Absolutely not. I want easy access to my archive. Thunderbird hides
> everything and overlays it with garbage. Kind of like Google did
> with the public archive.
No argument there.
-----
On Monday, 27 Feb 2017 11:04 AM -0500, John W Kennedy wrote:
> I have no idea whether there is an RFC, but, in this day and age, 7-bit
> text processing, except, perhaps, at a 7-bit end point, is barbarous.
>
> And we haven’t established that this is the case, anyway. From all the
> information I possess, the problem can still be entirely on your end.
I rather expect it is.
Looking at one of my own previous posts (using slrn), I notice the
following in my headers:
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
User-Agent: slrn/1.0.2 (FreeBSD)
Could the difference between Ned's experience and mine be the editor we use?
I specify Emacs in my ~/.slrnrc file:
set editor_command "emacs +%d %s"
Don't know, but I *don't* think that slrn is the culprit here.
--
Will