open https://gitlab.synchro.net/main/sbbs/-/issues/920

Not sure if this is a you thing or a Digital Man thing. Looks like more encoding issues.

{width=769 height=472}

You can see this in the new MOSCOWTIMES group.

Thanks.
--- SBBSecho 3.24-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hi Nigel,

On 2025-05-01 01:52:15, you wrote to GitLab issue in main/sbbs:

open https://gitlab.synchro.net/main/sbbs/-/issues/920

Not sure if this is a you thing or a Digital Man thing. Looks like more encoding issues.

![image](https://gitlab.synchro.net/main/sbbs/uploads/d6e37686ab0a3765526934ad
224fa171/image.png){width=769 height=472}

You can see this in the new MOSCOWTIMES group.

I don't think it's a Synchronet issue.

The originating system for the messages in the MOSCOWTIMES area had an issue where the message contained a 'CHRS: CP850 2' kludge, but the message and subject text could contain utf-8 characters. That was fixed yesterday. So new messages shouldn't have this problem.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

https://gitlab.synchro.net/main/sbbs/-/issues/920#note_7172

Z39C said (in IRC) that the issue was the message wasn't posted properly:

<Z39C> That problem is already fixed.
<Nightfox> Z39C: It is? I'm the author of DDMsgReader, and I haven't done any work on that issue yet
<Nightfox> Or was the message just messed up somehow?
<Z39C> Yes, the message had utf-8 chars but the chrs kludge said cp850... <Z39C> The originating system fixed that in his RSS to fido script.
<Nightfox> ah.. Yeah, DDMsgReader should be handling UTF-8 already. If it didn't know there was UTF-8, maybe that's why they weren't displayed properly, I'd guess
<Dan_C> Yes, the kludge inserted by the originating system was wrong, and now corrected
<Z39C> Well, the kludge is still the same but he converts the text from utf-8 to cp850 now before posting! ;-)
--- SBBSecho 3.24-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/920#note_7172

Z39C said (in IRC) that the issue was the message wasn't posted properly:

<Z39C> That problem is already fixed.
<Nightfox> Z39C: It is? I'm the author of DDMsgReader, and I haven't done any work on that issue yet
<Nightfox> Or was the message just messed up somehow?
<Z39C> Yes, the message had utf-8 chars but the chrs kludge said cp850... <Z39C> The originating system fixed that in his RSS to fido script. <Nightfox> ah.. Yeah, DDMsgReader should be handling UTF-8 already. If it didn't know there was UTF-8, maybe that's why they weren't displayed properly, I'd guess
<Dan_C> Yes, the kludge inserted by the originating system was wrong, and now corrected
<Z39C> Well, the kludge is still the same but he converts the text from utf-8 to cp850 now before posting! ;-)

--- SBBSecho 3.24-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: DDMsgReader: MOSCOWTIMES not displaying correctly
By: Wilfred van Velzen to Nigel Reed on Thu May 01 2025 10:56:10

I don't think it's a Synchronet issue.

The originating system for the messages in the MOSCOWTIMES area had an issue where the message contained a 'CHRS: CP850 2' kludge, but the message and subject text could contain utf-8 characters. That was fixed yesterday. So new messages shouldn't have this problem.

Good information. Thank you.

---
■ Synchronet ■ End Of The Line BBS - endofthelinebbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/920
--- SBBSecho 3.24-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)