Subj : unicode/cp437 door
To   : All
From : bugz
Date : Wed Mar 31 2021 11:25 pm

Hello,

I've been working on writing my own door and door library, but I've run into some interesting issues with ENiGMA.  In my library, I try to detect if utf8/unicode or cp437 is active, and adjust my output accordingly.

The problem (I think) is ENiGMA wants to help.  Under linux, using stdio, you have to choose utf8 or cp437.  Selecting cp437, I can only detect cp437 and never unicode -- probably because ENiGMA is encoding/translating in the background for me.  If I select utf8, then cp437 gets Mojibaked.

I thought maybe if I could setup a "raw" mode that wasn't translated I'd have better luck, but doesn't seem like it.  Here's what I tried.

In core/door.js, I tried doing something like this:

     doorDataHandler(data) {
       if ('raw' === this.encoding) {
         this.client.term.write(data);
       } else {        
         this.client.term.write(decode(data, this.encoding));
       }
     }

But it still seemed like it's getting mojibaked.  Is this where the doors get encoded?  Is there somewhere else that encoding is going on?

Thanks for reading and take care,

bugz


--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 14.16.0)
 * Origin: BZ&BZ BBS (21:4/110)

.