Re: @ SCOS Message Format ?

Richard Heathfield <rjh@cpax.org.uk> wrote:

On 24/02/2025 18:08, Rich wrote:

Richard Heathfield <rjh@cpax.org.uk> wrote:

>
Given this input:
>
[long input snipped]

 

$md5sum charset.txt
d5c6d06587dbac07fed831293ff0580d  charset.txt
$ md5sum charset.scos2
87ea4967605a5ba4d69ff6cf0fb541f5  charset.scos2
>
Anyone get anything different?

 
Mouse copy/paste from Tin running inside a Urxvt terminal results in
identical md5's to yours above:
 
   $ md5sum *
   d5c6d06587dbac07fed831293ff0580d  charset.txt
   87ea4967605a5ba4d69ff6cf0fb541f5  charset.scos2

 
Thanks for that. So it is beginning to look like a fair lot of
noise over not very much.

I'd say if one is using a newsreader that /does/ perform such
"transformations" -- and one is unaware such is happening, that for
those "ones" it is more than noise.  In fact, with Tin, if one
surrounds words/strings with stars or forward slashes, Tin attempts to
highlight those, and IIRC it hides the stars/slashes, so depending on
just what character sequence is output, I might have had a different
md5 from mouse copy/paste.

I.e. the word bold below should end up bold in Tin but without stars:

*bold*

And the word italics below should be in italics (if my terminal 'did'
italics, that is):

/italics/

I suspect if you send back a reply with a 'starred' or 'slashed' word,
I won't see the stars or the slashes.  But this is a lower likelyhood
accidental pattern vs 2^2.