Subj : Re: Setup check..
To   : Alan Ianson
From : Nicholas Boel
Date : Wed Sep 07 2016 16:45:29

Hello Alan,

On 07 Sep 16 13:39, Alan Ianson wrote to Michiel van der Vlist:

 >> It doesn't look good on my screen because it is not encoded in
 >> UTF-8 but in CP437 instead. You still need to do some tinkering to
 >> get your system UTF-8 compatible...

 AI> I still use CP437 here because the BBS software I use seems to depend
 AI> on it. I have used a UTF-8 terminal at times just to see how it goes.
 AI> I know that MBSE and Mystic can output in UTF-8 but they both still
 AI> use CP437 or maybe LATIN-1 internaly as far as I know.

Have you tried switching the CP437/UTF-8 option in Mystic's configuration at all? I don't recall how far along that was.

 AI> I need to figure out what keywords I need for golded to use UTF-8
 AI> properly and then I'll try it again. I suppose I will still have
 AI> trouble with Bj”rn's name on my keyboard though.

You can translate a bunch of tables TO UTF-8, but not back. Then again, if you're posting in UTF-8 why would you want to break it back down to something less widely used, so instead, I force my export to UTF-8 and created a blank conversion table called utf8_utf8.chs. This is only to get Golded to send out the proper CHRS kludge (as noted in this message).

 AI> I'm not sure how the BBS would handle posts if I was to run it from a
 AI> UTF-8 console. Maybe I should try and see what happens.

I doubt you'd break anything. Mystic actually has a UTF-8 setting, but I seem to recall it only handling some characters, while trying to keep ANSI compatibility.

 AI> Is anyone running their BBS from a UTF-8 console? Is that doable or
 AI> are there problems?

I run Synchronet as a daemon, and always have a UTF-8 console without any problems. But I'm not sure if that's what you mean or not.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20160827
 * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

.