Subj : Re: unicode/cp437 door
To   : NuSkooler
From : bugz
Date : Sun Apr 04 2021 06:49 pm

-=> NuSkooler wrote to bugz <=-

 Nu> Sounds like you already found a work around via ACS, but you were on
 Nu> the right track here.

I guessed right.  :D   I amaze myself sometimes...  

 Nu> When the external process is spawned we disable all encoding so
 Nu> everything is "raw" between ENiG and the process. The handler you have
 Nu> above takes that raw |data| and decodes it based on the specified
 Nu> encoding -- on the way out back to the client's term it has to be
 Nu> re-encoded to whatever their term specified.

Actually, I have a problem with the normal process, also.  My card door game 
is trying to use CP437 0x03, 0x04, 0x05, 0x06 (hearts, diamonds, spades, 
clubs).  But I'm thinking that "iconv" (or whatever is doing the encoding) 
ignores these as control codes.  [RATS!]

 Nu> e.g. PID -> UTF-8 -> Decode to JS/Unicode -> Encode CP437 -> Terminal

^ This here doesn't like the "control codes" symbols. 

 Nu> This is used successfully in a lot of setups, so I'd have to have more
 Nu> details as to why it's not working for you I guess -- assuming the work
 Nu> around isn't too much of of a PITA/you want to muck with it more :)

The "raw" workaround above failed on CP437 to CP437 output.  It was mojibaked
/garbled up.  Like when you edit ANSI files/high ascii with vim, it "fixes" 
the broken utf-8 it sees.   

Yes, there are ways to make vim work right ...   

  vim --cmd "set encoding=Latin1" WELCOME.ANS 

Am I missing something further along in the terminal output part to get 
"raw"?  I think I'll probably stick to the ACS fix until I see what happens
with the door running on other BBS software.

I don't think there's many BBSes that handle unicode, and unicode is weird.
And fewer (if any?) doors that are crazy enough to try unicode.  I just 
happened to be crazy enough to try writing a CP437/unicode door.

They don't call it unipain without a reason!  

And I'm not sure how other BBS systems handle these cases.  That's for
testing out another day.  I don't think I'd even be trying unicode
support with them.

I think you've got a great way of dealing with unicode/CP437.  Thanks
for reading and the feedback.

Take care,
bugz

.... You must know your limits to break through them.

--- MultiMail/Linux v0.52
                                                  

--- Talisman v0.16-dev (Linux/x86_64)
 * Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

.