Hey deon

I'm wondering if your CHRS kludges are correct on the clearing houz
replys.

1) I noticed that one had ASCII 1 but had high ASCII in it, I think that
should be CP437 2

2) I noticed in a reply to an enigma test it had UTF-8 4 as a chars
kludge but I think it might be CP437 2 again?

I'm attempting to implement UTF-8 conversion to CP437 in talisman, I may
have something wrong, but the UTF-8 version shows ??? where it should be
box chars, but when I don't have the UTF-8 conversion it displays
correctly.

I thought maybe you're just matching the CHRS kludge of the test message instead of what the message actually is? It's not a big problem if that's
what you're doing, just trying to work things out on my end, and if I've
done something wrong myself.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.33-dev (Windows/x64)
* Origin: The Grinning Cat - telnet://gcat.talismanbbs.com:11823 (21:1/151)

Re: Clearing Houz CHRS
By: apam to deon on Mon Nov 22 2021 04:24 pm

Howdy,

I'm wondering if your CHRS kludges are correct on the clearing houz replys.

I thought maybe you're just matching the CHRS kludge of the test message instead of what the message actually is? It's not a big
problem if that's what you're doing, just trying to work things out on my end, and if I've done something wrong myself.

Yeah, you are right.

CHRS's kludge is on my to-do list to improve. So at the moment, if the original message has a CHRS kludge, I'm using it verbatim (assuming it is correct from the sender, which sometimes it doesnt appear to be). And if there is no CHRS kludge, I'm inserting CP437 2 (knowing that my response does include some high ascii chars.

I'm attempting to implement UTF-8 conversion to CP437 in talisman, I may have something wrong, but the UTF-8 version shows ??? where it should be
box chars, but when I don't have the UTF-8 conversion it displays
correctly.

Yeah, I think I understand your issue - I use iterm2 to access my BBS (Synchronet), which most times displays correctly, unless the source test message advertises UTF8 4, to which the response from clrghouz is garbled (synchronet not converting the message to my UTF8 terminal when it needs it). (I see a similar issue when viewing the message with Syncterm.)


...ëîåï
--- SBBSecho 3.14-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

I thought maybe you're just matching the CHRS kludge of the test

message instead of what the message actually is? It's not a big

problem if that's what you're doing, just trying to work things out

on my end, and if I've done something wrong myself.

Yeah, you are right.

Thanks deon, that helps :)

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.33-dev (Windows/x64)
* Origin: The Grinning Cat - telnet://gcat.talismanbbs.com:11823 (21:1/151)