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.
<Z39C> That problem is already fixed.--- SBBSecho 3.24-Linux
<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! ;-)
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.
Sysop: | fluid |
---|---|
Location: | wickliffe, ohio |
Users: | 4 |
Nodes: | 10 (0 / 10) |
Uptime: | 86:35:31 |
Calls: | 52 |
Files: | 15,838 |
Messages: | 53,747 |