[Oberon] Complex ETHO mailArchive problem.

[easlab-absa]

Using LEO to compose this 'log' while extracting info. from
the relevant linux files, I see that:
on  Dec 1 2007 I used
curl -o ObnMailLst \
https://lists.inf.ethz.ch/pipermail/oberon/2005/004110.html

This would/should have fetched 
  https://lists.inf.ethz.ch/pipermail/oberon/2005/004110.html
 to the file: ObnMailLst

[https is a curse. I don't think ETHO handles it ?]

Embedded in this file linux : mc <plain ascii editor> sees:
AsciiCoder.DecodeFiles % js.TextPopups.Mod ~ 
52J0_o1YJIa;M9jK7kLMYC;<A HREF="https://mailman.inf.ethz.

Since the original name of the file is 004110.html
I'll make a copy with that name and use a 'standard browser',
opera to view it. I see:--
AW: [Oberon] USB Open Host Controller Driver, AosUsbOhci.Mod. 
sedlacek sedlacek at swissonline.ch 
Tue Jul 19 17:06:53 CEST 2005
...
Fax: +41 (81) 860 06 62 

AsciiCoder.DecodeFiles % js.TextPopups.Mod ~ 

52J0_o1YJIa;M9jK7kLMYC;kM9jK732 at
0;@F?Q>dgbfg:W3d1dX\=\dI0bdg>feFFb<07j
...
NB in `opera`the string:
     kM9jK732 at 0
is a hotLink,   and there are many more, all with the format
<string> <space> "at" <space> <string>

For some reason opera decodes the view of these hotLinks.
Other hotlinks on the page/file look normal.
OK, hotlinks need a view: field and a URL: field, and this
corrupted file has got only spurious URL-fields.

That's another reason why I HATE M$loth, for their wizard
mentality and deceptively transforming the bytes, and breaking
ASCII by introducing their own non-standard substitutes for the
existing apostophe & back-quote. So that when M$ users write
"can't", it looks like garbage.

But now, for a 3rd opinion, via:
  EditTools.OpenUnix /home/crg/Inet/wget.curl/ObnMailLst 
ETHO, will show the actual bytes, which are:-
Fax: +41 (81) 860 06 62

AsciiCoder.DecodeFiles % js.TextPopups.Mod ~

52J0_o1YJIa;M9jK7kLMYC;<A
HREF="https://mailman.inf.ethz.ch/mailman/listinfo/oberon">kM9jK732 at
0</A>;@F?`<A
HREF="https://mailman.inf.ethz.ch/mailman/listinfo/oberon">kS at
S</A>`Q&gt;dgbfg:W3d1dX\=\dI0bdg&gt;feFFb&lt;07j
=============
That's one line starting with "52J0" which the emailing may 'break'.

At what stage between sedlacek's ETHO and mine was his ASCII
corrupted [transformed for a better experience]?

Thanks,

== Chris Glur.