X-RFC-Mime: 1.0   
   REPLYADDR: ozznixon@gmail.com   
   MSGID: 1:1/123.0 5CC4043D   
   REPLY: 1:153/7001.2989 5cc2262d   
   PID: ExchangeBBS NNTP Server v3.1/Linux64   
   TID: ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta 4.09)   
   On 2019-04-25 21:27:09 +0000, Maurice Kinal -> Ozz Nixon said:   
      
   >    
   > Dec     CP437   CP850   CP855   CP866   
   >    
   > Let me know what you think of the idea and I am sure we could come up with a   
   > better map if it matters.  Bottom line is that you could come up with a   
   > "bottom line" in 8 bit codes that will be the same for the above codepages   
   and   
   > potentially more.   
      
   The challenge is, how common is it for the end user to know their CodePage?   
      
   I am always looking for ways to auto-detect... for example, I send 3 3    
   byte UTF codes at the start of my BBSes - send ANSI 6n, if I get 10;1 I    
   know NOT UTF, if I get 4;1, I know UTF.   
      
   Right now, 10;1 I assume CP437 output. And 4;1 goes through my CP437 ->    
   UTF8 map - built into my socket layer.   
      
   Now yes, the effort you did, has been "absorbed" into my mappings ...    
   just wonder if there is a way to detect their Terminal CodePage. I know    
   there are a few other ANSI inqueries - terminal, and height/width.    
   However, I rely on the TELNET IAC inqueries right now for terminal,    
   height and width. (which won't work on Dial-up.. and I have been asked    
   to keep Dial-up in the next release).   
      
      
   --    
   .. Ozz Nixon   
   ... Author ExchangeBBS (suite)   
   .... Since 1983 BBS Developer   
      
   --- ExchangeBBS NNTP Server v3.1/Linux64   
    * Origin:  (1:1/123)   
   SEEN-BY: 15/2 18/200 123/1970 226/17 229/107 123 354 426 452 1014   
   SEEN-BY: 240/5832 249/206 317 400 280/464 317/3 322/757 342/200 393/68   
   SEEN-BY: 633/280   
   PATH: 1/123 229/426