Hello All,

while coding zen phonebook I found something I'm kind of unable to solve easily. I imported the csv from google. And I was able to import it to
sqlite. And then when I query sqlite in Linux terminal it displays the UTF-8 characters just right. But how would I let this happen in Mystic BBS? So far Netrunner doesn't have UTF-8 support. And I think SyncTerm doesn't neither.
But Mystic BBS itself does support UTF-8 is that right? I also tried fTelnet. Just an quick and dirty check to change the font to UTF8. But didn't really succeeded displaying the fonts. So my question is.

Is it doable to display UTF8 using Mystic BBS?

Thanks in advance

Shinobi

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: INFOLINKA BBS (21:1/153)

Hello All,

while coding zen phonebook I found something I'm kind of unable to
solve easily. I imported the csv from google. And I was able to
import it to sqlite. And then when I query sqlite in Linux terminal
it displays the UTF-8 characters just right. But how would I let this happen in Mystic BBS? So far Netrunner doesn't have UTF-8 support.
And I think SyncTerm doesn't neither. But Mystic BBS itself does
support UTF-8 is that right? I also tried fTelnet. Just an quick and
dirty check to change the font to UTF8. But didn't really succeeded displaying the fonts. So my question is.

Is it doable to display UTF8 using Mystic BBS?

Thanks in advance

PuTTY is the most complete for stuff like that. I just did a fresh Win64 install to double check and found and it defaults to UTF-8. I have to
manually change it to CP437.

This can be configured by the individual connection.

I don't understand why you would want to though. Not for something
accessible by the public. If it were something just for you I could see
that. We have machines that I use PuTTY to connect to and program the
control boards and motor timing through a terminal connection that I use
UTF-8 for that connection, but I'd never do it for something the public
will access.

--- MagickaBBS v0.10alpha (Linux/armv7l)
* Origin: A Tiny slice o pi (21:1/130.4)

I don't understand why you would want to though. Not for something accessible by the public. If it were something just for you I could see that. We have machines that I use PuTTY to connect to and program the control boards and motor timing through a terminal connection that I use UTF-8 for that connection, but I'd never do it for something the public will access.

Well... the reason is I'm from Bohemia, Prague. That means English is fine.
But once I'd like to display anything in Czech here comes the trouble. I
didn't open the BBS to telnet nor ssh. But it is accessible via fTelnet. If
I'd be able to configure fTelnet client on the server web server... then victory is mine. And I'd possibly could offer the BBS in my first language.

Regards

Shinobi

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: INFOLINKA BBS (21:1/153)

UTF-8 characters just right. But how would I let this happen in Mystic BBS? So far Netrunner doesn't have UTF-8 support. And I think SyncTerm doesn't neither. But Mystic BBS itself does support UTF-8 is that right?

You'd probably have to use Putty if you want to use UTF8. The reason those terminals don't do UTF8 is because they are specifically made to emulate DOS character sets which only have 256 characters.

In contrast UTF8 has 1.1 million characters. If you feel like drawing a font for NetRunner that has all of the 1.1 million characters I'll try to add that in but chances are we'll both be dead before it gets finished ;)

Is it doable to display UTF8 using Mystic BBS?

Its just characters so you can display anything you want since you're pulling it from your SQL database.

--- Mystic BBS v1.12 A39 2018/04/16 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

You'd probably have to use Putty if you want to use UTF8. The reason those terminals don't do UTF8 is because they are specifically made to emulate DOS character sets which only have 256 characters.

I understand this clearly. What it complicates it on my side is that on Linux there is not any implementation of PuTTy. Or rather is. I have to explore that.

In contrast UTF8 has 1.1 million characters. If you feel like drawing a font for NetRunner that has all of the 1.1 million characters I'll try
to add that in but chances are we'll both be dead before it gets
finished ;)

I get it. So far what was my first thought is to convert any existing font.
But that should be pain I guess. So far there exists some UTF-8 fonts. So
that brings me back. If that would be possible to reuse existing one. I don't really understand on how the NetRunner implements the characters rendering.
But I guess it's not simple one. What language is it written in? C++

Great work on NetRunner, BTW. It is my favorite terminal. So far I didn't get SyncTem in full-screen. And NetRunner renders just very well. I really like
the font aliasing on bigger screens.

Its just characters so you can display anything you want since you're pulling it from your SQL database.

From my experiments there is no trouble with Mystic BBS. I switched the BBS
to UTF-8 and it just sends the characters in diacritics correctly. Now the trouble is on the client side.

Thanks for Your reply & best wishes

Shinobi

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: INFOLINKA BBS (21:1/153)

Re: Re: Mystic BBS in UTF-8
By: shinobi to g00r00 on Wed Apr 18 2018 07:13 am

Great work on NetRunner, BTW. It is my favorite terminal. So far I didn't get SyncTem in full-screen. And NetRunner renders just very well. I really like the font aliasing on bigger screens.

In Syncterm you can use different video output modes. It's in the program settings on the bottom right of the main screen.

I use SDL Overlay fullscreen for that old time look 'n feel.. :) That only works if your on the desktop. You may need to close and open Syncterm
again after setting that.

But Yeah, NetRunner is excellent as well.. :)

Ttyl :-),
Al


... Brain: the apparatus with which we think we think
--- SBBSecho 3.04-Linux
* Origin: The Rusty MailBox - Penticton, BC trmb.synchro.net (21:4/106)

I understand this clearly. What it complicates it on my side is that on Linux there is not any implementation of PuTTy. Or rather is. I have to explore that.

Putty has a Linux version. But if you're in Linux you can also just use linux command line Telnet if your shell runs in UTF8.

As far as Mystic... the install programs "quizzes you" to find out if you're UTF8 native or not. All of Mystic can run in UTF8 in Linux for both SysOp and user, but there are some "open/unfinished issues"... Mystic will not properly support input of and saving of UTF8 in message bases. Thats the #1 major issue regarding UTF8 at this point.

I get it. So far what was my first thought is to convert any existing font. But that should be pain I guess. So far there exists some UTF-8 fonts. So that brings me back. If that would be possible to reuse
existing one. I don't really understand on how the NetRunner implements the characters rendering. But I guess it's not simple one. What language is it written in? C++

NetRunner and Mystic are both written in Free Pascal. NetRunner renders its own Amiga or PC-based characters and can "upscale" them which is why you get that added clarity you cannot get in SyncTerm. It does not load fonts.

I don't know that there are fonts that support the full UTF8 (1 million+ characters) but there are some that may have 20 to 50 thousand of the most common. Technically if they're bit-mapped fonts I could make NetRunner load them.

NetRunner gives you that emulated DOS or Amiga experience that can look 100% accurate and pretty clear even on a 4K display (which is unique to NetRunner) and can freely scale and change size without crashing other other video-based applications like SyncTerm does.

Mystic's NodeSpy gives you the text-based telnet/ssh/rlogin client that can do UTF8 (in Linux/Pi/OSX. Windows is another story because it doesn't support UTF8... I need to convert to UTF16 which I haven't written code for yet).

--- Mystic BBS v1.12 A39 2018/04/18 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Putty has a Linux version. But if you're in Linux you can also just use linux command line Telnet if your shell runs in UTF8.

That's what I found. I was able to display results from python querying
sqlite database correctly. In the shell. Using telnet.

As far as Mystic... the install programs "quizzes you" to find out if you're UTF8 native or not. All of Mystic can run in UTF8 in Linux for
both SysOp and user, but there are some "open/unfinished issues"... Mystic will not properly support input of and saving of UTF8 in message bases. Thats the #1 major issue regarding UTF8 at this point.

Good to know. At first I wanted to test the message base post using accented characters. But I wasn't really able to write them at first.

NetRunner and Mystic are both written in Free Pascal. NetRunner renders its own Amiga or PC-based characters and can "upscale" them which is why you get that added clarity you cannot get in SyncTerm. It does not load fonts.

That's a neat feature. In the fact that's the reason in my case using it. As
Al wrote it is possible to get full-screen in SyncTerm. But for now I prefer the clear fonts in NetRunner.

I don't know that there are fonts that support the full UTF8 (1 million+ characters) but there are some that may have 20 to 50 thousand of the
most common. Technically if they're bit-mapped fonts I could make NetRunner load them.

Well... after all I went path that I display CP852. And fTelnet serves it
very well for this purpose. I mean for any external users. For my own
purposes I would be satisfied with English. But when I want to attract some more local users then accented characters display would come handy.

Mystic's NodeSpy gives you the text-based telnet/ssh/rlogin client that can do UTF8 (in Linux/Pi/OSX. Windows is another story because it
doesn't support UTF8... I need to convert to UTF16 which I haven't
written code for yet).

From my own feelings I guess most of the BBS runs in English. At least the Mystic One. What was interesting was a BBS that ran in Traditional Chinese. That was impressive. But I cannot read the characters. Regarding Windows. It would be a huge amount of work to do so. And this is where Linux in my
opinion differs. I'm unsure. But UTF-16 is something I've not seen so far in the configurations of Linux Terminal etc. So good luck with that. My guess is... at least for now.. there are not many users demanding it.

I'll stick to experiments with UTF-8 and CP852 is sure thing for me.

Thanks for explanation and nice talking to You

Best regards

Shinobi

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: INFOLINKA BBS (21:1/153)

I don't understand why you would want to though. Not for somethi accessible by the public. If it were something just for you I co that. We have machines that I use PuTTY to connect to and progra control boards and motor timing through a terminal connection tha UTF-8 for that connection, but I'd never do it for something the
will access.

Well... the reason is I'm from Bohemia, Prague. That means English is
fine. But once I'd like to display anything in Czech here comes the trouble. I didn't open the BBS to telnet nor ssh. But it is
accessible via fTelnet. If I'd be able to configure fTelnet client on
the server web server... then victory is mine. And I'd possibly could
offer the BBS in my first language.

Ah. I tend to forget that there's more world out there than my own
little world. :) Seriously, Check out PuTTY for the client side. It may
be what you're looking for. It translates all sorts of oddities that
you're common clients usually don't.

--- MagickaBBS v0.10alpha (Linux/armv7l)
* Origin: A Tiny slice o pi (21:1/130.4)

I understand this clearly. What it complicates it on my side is that
on Linux there is not any implementation of PuTTy. Or rather is. I
have to explore that.

A little confused on that one. It looks like there's a Unix source, so
should work if compiled on your OS. See Package files....

https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html


--- MagickaBBS v0.10alpha (Linux/armv7l)
* Origin: A Tiny slice o pi (21:1/130.4)

A little confused on that one. It looks like there's a Unix source, so should work if compiled on your OS. See Package files....

https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

Thanks so much. I'll take a look. However my client is Ubuntu. And it seems PuTTy is installable from default repository out of the box.

Best regards

Shinobi

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: INFOLINKA BBS (21:1/153)

On 04/17/18, shinobi said the following...

that. We have machines that I use PuTTY to connect to and program th control boards and motor timing through a terminal connection that I UTF-8 for that connection, but I'd never do it for something the publ will access.

Putty is common on Linux as well Ubuntu 16.04 64 bit shows:
p putty - Telnet/SSH client for X
p putty:i386 - Telnet/SSH client for X
p putty-doc - PuTTY HTML documentation
p putty-tools - command-line tools for SSH, SCP, and SFTP
p putty-tools:i386 - command-line tools for SSH, SCP, and SFTP

so 'sudo apt-get install putty' will install it for X

--- Mystic BBS v1.12 A39 2018/04/16 (Linux/64)
* Origin: Workpoint (21:1/145.3)

g00r00 wrote to shinobi <=-

I understand this clearly. What it complicates it on my side is that on Linux there is not any implementation of PuTTy. Or rather is. I have to explore that.

Putty has a Linux version. But if you're in Linux you can also just
use linux command line Telnet if your shell runs in UTF8.

Or "ssh". :-) And yes, modern distributions should default to UTF-8.


... People who live in stone houses shouldn't throw glasses.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)