anybody have a NON HI-ASCII language file for mystic???

trying to login via older computers, I have found that mystic does not
support plain ASCII very well - all the boxes around things like oneliners, changing areas all are messed up

I have been editing the language file and changing the effected prompts, but its very time consuming.

Thanks,

Michael2

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Mike's Mansion - fluxcap.dynv6.net:2323 (21:2/145)

On 10/11/18, michael2 said the following...

anybody have a NON HI-ASCII language file for mystic???

trying to login via older computers, I have found that mystic does not support plain ASCII very well - all the boxes around things like oneliners, changing areas all are messed up

I have been editing the language file and changing the effected prompts, but its very time consuming.

Yes, it's time consuming. The ASCII theme I used is from:
/mystic/files/fsx_mutl/xq-ascii_theme.zip
It doesn't effect the prompts, nothing does that easily. A font could but
would need to be on both sides of the connection. so editing the prompts for the theme/language in question is the best way I know. I've also found that setting the BBS to 40 columns also doesn't effect the prompts, they are still 80 column in that case. All the prompts have to be changed. It's also not
just the prompts, the templates and help files need to be edited as well. It will take time, but it's the only way I know. To get 40 column setup (for
c64) I've been making all new menus as well - it seems the only way to do it. You can see the work in progress at bcw142.zapto.org:2323 or 2322 (ssh),
that's my AlphaTest system I try things like this out. There is an ASCII theme and c64 theme. Mystic only uses two font versions: CP437 and UTF-8. In UTF-8 mode normal Windows10/Linux/Mac UTF-8 (current normal font) picks the characters used for CP437 so it will look the same. That is heavily effected by the fonts and other things. On that BBS you have to pick what you want, if you pick wrong /G at the main menu drops you so you can try different settings.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 10/11/18, michael2 said the following...

anybody have a NON HI-ASCII language file for mystic???

trying to login via older computers, I have found that mystic does not support plain ASCII very well - all the boxes around things like oneliners, changing areas all are messed up

The language file itself doesn't do it! Someone did an ASCII theme, but it doesn't effect prompts, nothing other than prompt editing will I think. I've been editing my c64 theme here (AlphaTest bcw142.zapto.org port 2323 or 2322) since the c64 doesn't use ANSI graphics, but has it's own. Also setting 40 columns doesn't work either nor using 2 columns for menus, they are still defaulting to 80 columns. I have re-write each menu to force 40 columns. I could be missing something, but it's the only way I found to work. Fonts and language files aren't the same, and prompts aren't part of language files.
A font that used the same 128 ASCII characters for both 0-127 & 128-256 would force ASCII, but would still look odd and the prompts would need to be redone anyway. So changing the prompts are the only way I've found that will work.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 10/11/18, michael2 said the following...

anybody have a NON HI-ASCII language file for mystic???

The one I used was from /mystic/files/fsx_mutl/xq-ascii_theme.zip
That doesn't effect the prompts as I stated before, but it is a good starting point.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

Re: Re: Mystic Language File
By: bcw142 to michael2 on Thu Oct 11 2018 06:40 pm


I don't know if I am misunderstanding you here but there is why to create 40/80 column screens. When I was updating my Commodore BBS back in the day to satisfy ANSI users I used to use a pseudo type of menu system. In other words the first characters start off at column 2, then the 2nd column would start at column 42, thus making the screen for a 40 column user look 40 columns and it would look 80 columns for 80 column users.. If I misunderstood what you are trying to do I apologize..
--- SBBSecho 3.06-Win32
* Origin: The Wrong Number Family Of BBS' - Wrong Number IV (21:4/131.1)

On 10/14/18, Bucko said the following...

Re: Re: Mystic Language File
By: bcw142 to michael2 on Thu Oct 11 2018 06:40 pm

I don't know if I am misunderstanding you here but there is why to
create 40/80 column screens. When I was updating my Commodore BBS back
in the day to satisfy ANSI users I used to use a pseudo type of menu system. In other words the first characters start off at column 2, then the 2nd column would start at column 42, thus making the screen for a 40 column user look 40 columns and it would look 80 columns for 80 column users.. If I misunderstood what you are trying to do I apologize..

the Language file, contains loads & loads of HI-ASCII characters, that look really bad on older computers.
as far as the menus go, yes you could do something like that, if you want
none of your menus automatic

Michael2

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Mike's Mansion - fluxcap.dynv6.net:2323 (21:2/145)

On 10/14/18, Bucko said the following...

Re: Re: Mystic Language File
By: bcw142 to michael2 on Thu Oct 11 2018 06:40 pm

I don't know if I am misunderstanding you here but there is why to
create 40/80 column screens. When I was updating my Commodore BBS back
in the day to satisfy ANSI users I used to use a pseudo type of menu system. In other words the first characters start off at column 2, then the 2nd column would start at column 42, thus making the screen for a 40 column user look 40 columns and it would look 80 columns for 80 column users.. If I misunderstood what you are trying to do I apologize..

You have the right idea, not sure how to get Mystic to do that, but right
now my c64 is using ANSI to make it look c64 like. I need to setup something
to test it with though. I'm using text files like mm.asc in ctext to make a menu that looks right and works. I didn't find any way with the normal menu setup, so used basic ANSI text files (with color codes, not positioning). That's on my AlphaTest at bcw142.zapto.org:2323.
H

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 10/15/18, michael2 said the following...

the Language file, contains loads & loads of HI-ASCII characters, that look really bad on older computers.
as far as the menus go, yes you could do something like that, if you want none of your menus automatic

I gotcha now..

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)