Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    JAMNNTPD    |    Support for the JAMNNTPD software client    |    2,630 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 283 of 2,630    |
|    mark lewis to Scott Street    |
|    xlat bug?    |
|    30 Jun 12 17:31:35    |
       SS> On 6/29/2012 5:16 PM, mark lewis -> Scott Street wrote:              > SS> On my end, in UTF-8: Γòú (3-byte char: 0xE2 0x95 0xA3 )              thanks for this as it definitely demonstrates my previous "multiple       translations ad nausm" point that i was trying to make... now your three       characters (0xe2 0x95 0xa3) have been translated to 6 characters (0xCE 0x93       0xC3 0xB2 0xC3 0xBA) and if you quote the above line back to me again, it'll       have each one of those 6 also translated which will then result in 12       characters ;)              > yes, those are the three characters seen in CP437... now, the question       > is, will they be translated back to UTF-8 individually when you read       > this message or will you see only the one character i originally sent       > that is now already translated to UTF-8? it/they will show up twice in       > this post... my quoted first line above and then your line starting "On       > my end"...               SS> Because of "@CHRS: IBMPC 2", my system didn't send it to my client        SS> as UTF-8, but instead did a CP437 to UTF-8 translate. I see it as        SS> three seperate characters. (an upside-down L, an o with a back        SS> tick, and a u with a forward tick.)              yup :)               SS> AND - because of the 8-bittedness(tm) of those characters, this        SS> message will post as UTF-8.              yup! :)              )\/(ark               * Origin: (1:3634/12)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca