A sysop who tested the Win32 snapshot door on a BBS reported that the
"output appears to be UTF-8 instead of CP-437." On a CP437 terminal, that >means the box-drawing and block characters render as garbage (mojibake).
The observation is correct. Immortal Barons emits UTF-8 on the wire, and there >is no output-side character-set layer.
Subject: charset question for Immortal Barons
I saw there was a lively AI/vibe-coding discussion on Dove-Net. :) I'm vibe-coding a clone of Barren Realms Elite, and hit a snag, and looking for human feedback regarding this charset issue:
https://github.com/andy5995/immortal-barons/issues/18
Excerpt:
A sysop who tested the Win32 snapshot door on a BBS reported that the >"output appears to be UTF-8 instead of CP-437." On a CP437 terminal, that >means the box-drawing and block characters render as garbage (mojibake).
The observation is correct. Immortal Barons emits UTF-8 on the wire, and there >is no output-side character-set layer.
I've been testing locally in my terminal (on Manjaro Linux in XFCE terminal), and set up a Mystic BBS locally, telnetted in and opened it as a door, with no trouble.
I'd appreciate it if anyone could provide me with definitive feedback about the
design.
Digital Man wrote to Andy Alt <=-
Traditional BBS terminals (including even modern ones like SyncTERM, Netrunner, etc.) do not (yet) support UTF-8 - just CP437. And
Synchronet assumes all doors, by default, output CP437. So you need to convert your output character set to CP437. It's not a "design" so much
as an implementation detail. --
digital man (rob)
Digital Man wrote to Andy Alt <=-
Re: charset question for Immortal Barons
By: Andy Alt to All on Wed Jul 08 2026 08:45 pm
Subject: charset question for Immortal Barons
I'd appreciate it if anyone could provide me with definitive feedback about the
design.
Traditional BBS terminals (including even modern ones like SyncTERM, Netrunner, etc.) do not (yet) support UTF-8 - just CP437. And
Synchronet assumes all doors, by default, output CP437. So you need to convert your output character set to CP437. It's not a "design" so much
as an implementation detail. --
digital man (rob)
Subject: Re: charset question for Immortal Barons
Digital Man wrote to Andy Alt <=-
Traditional BBS terminals (including even modern ones like SyncTERM, Netrunner, etc.) do not (yet) support UTF-8 - just CP437. And Synchronet assumes all doors, by default, output CP437. So you need to convert your output character set to CP437. It's not a "design" so much as an implementation detail. --
digital man (rob)
Thanks! That pretty much confirms things. Regarding sbbs, has there ever been a
discussion about configuring a door to use the charset the user has enabled (or
what's been auto-detected) in their settings?
On a loosely related topic, I've been working on modemu2k, and for testing, I use it with minicom. On Vertrauen (and other boards), cp437 is auto-detected, but I get odd characters (mostly '?'s) at some of the ANSI screens. When I tried minicom's '-R CP437' option, the characters were correct, but some of the
block chars weren't positioned properly (at the main menu, for example), and the prompt appeared in the lower-right corner of the menu, buried in the border. Other sbbs boards I've tried recently have an option where I can manually change to UTF-8, and that always gives me the correct output when using minicom. On Vert, I've changed to US-ASCII (I didn't see a utf-8 option).
I've used syncterm (telnet/ssh client) a little and so far never have to change
any settings on vert or in syncterm for proper operation.
Digital Man wrote to Andy Alt <=-
But other than some recent experiments I've been working on, I know of
no doors that actually handle the charset conversions themselves.
Subject: Re: Immortal Barons (BRE Clone)
Digital Man wrote to Andy Alt <=-
But other than some recent experiments I've been working on, I know of no doors that actually handle the charset conversions themselves.
Immortal Barons does now.
https://andy5995.github.io/immortal-barons/charset/
How do you suppose the BBS software is going to add the -utf8 or -cp437 option on the command-line when invoking the door, only for UTF-8
callers? --
On 09 Jul 2026, Digital Man said the following...
How do you suppose the BBS software is going to add the -utf8 or -cp437 option on the command-line when invoking the door, only for UTF-8 callers? --
mystic can accept:
door.exe -%C
and it'll replace %C with "UTF8" or "CP437"
what can Synch do? run some javascript and check the ACS for UTF8 or CP437? print an error to the user if it's neither?
seems like the sysop will figure it out somehow.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 104 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 03:30:28 |
| Calls: | 8,697 |
| Calls today: | 1 |
| Files: | 9,527 |
| D/L today: |
2,031 files (790M bytes) |
| Messages: | 418,408 |
| Posted today: | 3 |