Subj : Re: can i talk about my recently aquired amiga?
To   : slacker
From : hyjinx
Date : Fri Jul 04 2025 04:56 pm

 sl> > 204beers, and I appreciate you for
 sl> > enabling UTF8 so that mTelnet
 sl> > works, there are a few other
 sl> 
 sl> I always referred to mTelnet as the one that comes with mTCP:
 sl> 
 sl> https://www.brutman.com/mTCP/mTCP_Telnet.html
 sl> 
 sl> That one always worked fine for me on my DOS computer with regular old CP4
 sl> 
 sl> I'm now thinking maybe I've been referring to it by the wrong name this wh
 sl> time as I don't believe the Brutman one does UTF8 at all... oops! :)
 sl> 
When I say mTelnet, I'm referring to mTCP Telnet. I don't know of any other mTelnet.

In the most recent of updates, Michael Brutman changed from CP437 to UTF8 by default. You have to compile from source and change the default to CP437 if you don't want that behaviour, I believe. What you end up getting, is better compatability with most other telnettable things, for example, if you telnet into a Linux box, things that are UTF8 generally 'just work'. In one of the resources (I forget which), there is a CP437 to UTF8 translation. You need to set that as DOS environment variable, but essentially, when your ye-olde DOS computer sees a UTF8 char, it maps it to a CP437 char, so that life carries on as normal. If it really can't convert the char, you see some ANSI symbol (I forget which one).

So, yes, Brutman is going all-in on UTF8 from Jan 2025.

Cheers,
Al


hyjinx // Alistair Ross
Author of 'Back to the BBS' Documentary: https://bit.ly/3tRINeL (YouTube)
alsgeeklab.com

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: bbs.alsgeeklab.com:2323 (21:1/126)

.