Re: cyclists attack auto driver

On Thu, 15 Aug 2024 15:20:07 -0500, AMuzi <am@yellowjersey.org> wrote:

On 8/15/2024 3:12 PM, Jeff Liebermann wrote:

On Thu, 15 Aug 2024 12:10:47 -0500, AMuzi <am@yellowjersey.org> wrote:
 

On 8/15/2024 11:57 AM, Jeff Liebermann wrote:

On Thu, 15 Aug 2024 12:38:35 -0400, Catrike Ryder
<Soloman@old.bikers.org> wrote:
>

On Thu, 15 Aug 2024 11:03:42 -0500, AMuzi <am@yellowjersey.org> wrote:

Usenet changed my ALT-259 heart into a question mark.

>
Usenet messages are all 7 bit characters.  Most (not all) of the alt
characters are 8 bit, which are replaced by a question mark
>

I know how to use acii characters in computer code, but I've never
done it in regular text.

>
See:
<https://www.alt-codes.net/how_to_use_alt_codes/>
<https://www.alt-codes.net>
When I cut-n-paste these 8 bit characters from a document into a text
editor or word processor, it appears correctly.  However, when I
pasted them into a newsreader (Forte Agent), it sometimes appears
correctly on my screen, but when I read the message as posted, it
produces a question mark or black square.
>
Try some of the other hearts and see what happens:
>
Heart alt-codes:
<https://www.alt-codes.net/heart_alt_code.php>
>
>

>
Thanks.
Here's an ALT-3
>
?

 
It shows as a single question mark.  If you want, I can sniff the NNTP
traffic with Wireshark, between my computah and my service provider
and see what is actually sent to my ISP.  If it's a question mark,
then the change is being made in whatever program you're using for
reading Usenet news.  If it's something else, the change might happen
at the ISP (although I doubt it).

Not motivated enough to track it down.

Good, because I'm loafing today.  I sold my Craftsman drill press,
which involved tearing it apart, carrying the heavy pieces down 32(?)
stairs and loading everything into a friends pickup.  We delivered it
yesterday.  I'm still tired and taking the day off to recover:
<https://photos.app.goo.gl/6vN9aQHE1osJv3uh6>

I know a few common extended-character codes which are
enough for document processors (Word) and text (Notepad).
>
Haven't had a problem with those in Thunderbird emails, only
usenet, and I don't need to memorize a duplicate set.

It's not going to be fixed in Usenet, no matter what software is used.
Looking at your header in your last message, I see:

Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla Thunderbird

Although your Thunderbird supports 8 bit Unicode characters as UTF-8,
the encoding for file transfer (NNTP) is only 7 bit.  So, my guess(tm)
is that Thunderbird is converting or truncating everything you send to
7 bit characters.

For comparison, my message header looks like this:

Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: ForteAgent/8.00.32.1272

It's similar to yours except that Forte Agent doesn't support 8 bit
Unicode characters, just ASCII. 

I hope this helps.
--
Jeff Liebermann                 jeffl@cruzio.com
PO Box 272      http://www.LearnByDestroying.com
Ben Lomond CA 95005-0272
Skype: JeffLiebermann      AE6KS    831-336-2558