[ANSIART]
@PAUSE@
@POFF@
`[?7h`[255D`[0;1mPLAY...

`[7C`[33m~ ~ `[35m~~~~ `[31m~ ~ `[36m~ ~ `[32m~~~~ `[34m~~~~ `[33m~`[A `[41C~~~~ `[35m~~~~ `[31m~~~~ `[36m~~~~ `[32m~~~~ `[34m~~~~ `[37m~
`[7C`[33m~ ~ `[35m~ ~ `[31m~~ ~ `[36m~~~ `[32m~ `[34m~`[9C`[33m~ `[A `[46C`[35m~ ~ `[31m~ ~ `[36m~ ~ `[32m~ `[34m~ ~ `[37m~
`[7C`[33m~~~~~ `[35m~~~~ `[31m~~~~ `[36m~~ `[32m~~~ `[34m~~~`[7C`[33m~ `[A `[44C `[35m~~~~ `[31m~~~~ `[36m~ ~ `[32m~~~ `[34m~~~~ `[37m~
`[9C`[33m~ `[35m~ ~ `[31m~ ~~ `[36m~~~ `[32m~ `[34m~`[9C`[33m~ `[A `[46C`[35m~ ~~ `[31m~ ~ `[36m~ ~ `[32m~ `[34m~ ~~ `[37m~
`[9C`[33m~ `[35m~ ~ `[31m~ ~ `[36m~ ~ `[32m~~~~ `[34m~~~~`[6C`[33m~ `[A `[45C `[35m~ ~ `[31m~ ~ `[36m~~~~ `[32m~~~~ `[34m~ ~ `[37m~

`[24C`[32mWhere only the `[33mTOUGH `[32mSurvive!

`[22C`[37mNow with `[33mFOUR `[37mdifferent versions!
`[33mn/P `[0m(Original 1994 ver) * `[1;33mn/M `[0m(no missles patch) *`[A `[53C `[1;33mn/E `[0m(no Earth patch)
`[26C`[1;33m1000 `[0m(1000 sector patch)
`[10CCourtesy of `[1mthe `[32mYankee Trader Strategy Guide `[37mhomepage: `[23Chttp://www.starfit.com/yt.html

`[11C`[31mFight the Xanor! Challenge local Xanor-killer `[37mZharous`[A `[65C`[31m!

`[25C`[33mAll at Moe's Tavern BBS!
`[20Cmoetiki.ddns.net:27 * 1+502-875-8938 `[0m`[255D
@PAUSE@

* SLMR 2.1a * "Mmmmmmmm.....doughnuts."

---
þ BgNet 1.0á12 ÷ FSX * Moe's Tavern * 1-502-875-8938 * moetiki.ddns.net:27
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

[ANSIART]

Hey, not sure what you intended to share here but none of the ansi codes came through so the post looked like gibberish :)

--- Mystic BBS v1.12 A48 2022/07/11 (Linux/64)
* Origin: m O N T E R E Y b B S . c O M (21:4/173)

esc wrote to MIKE POWELL <=-

[ANSIART]

Hey, not sure what you intended to share here but none of the ansi
codes came through so the post looked like gibberish :)

The screen showed up and displays here in ANSI color. Maybe it is on your
end? It is also in the wrong area, so maybe your system is set to
(rightfully) not "do ANSI" for this area.


... How do you tell when you're out of invisible ink?
--- MultiMail/DOS
* Origin: possumso.fsxnet.nz * SSH:2122/telnet:24/ftelnet:80 (21:4/134)

On 13 Nov 2022, Blue White said the following...

esc wrote to MIKE POWELL <=-

[ANSIART]

Hey, not sure what you intended to share here but none of the ansi codes came through so the post looked like gibberish :)

The screen showed up and displays here in ANSI color. Maybe it is on
your end? It is also in the wrong area, so maybe your system is set to (rightfully) not "do ANSI" for this area.

So it's everyone else problem if your display doesn't render correctly?

ogg
Sysop, Altair IV BBS
altairiv.ddns.com:2323

--- Mystic BBS v1.12 A48 2022/07/15 (Windows/64)
* Origin: Altair IV BBS (21:2/147)

Hey, not sure what you intended to share here but none of the ansi codes came through so the post looked like gibberish :)

The screen showed up and displays here in ANSI color. Maybe it is on
your end? It is also in the wrong area, so maybe your system is set to (rightfully) not "do ANSI" for this area.

It didn't render correctly for me either. Using Mystic, and checked that this message area was set to allow ANSI ? So not sure what the factor is on who see's the ANSI and who doesn't. I do see ANSI in other posts across the message bases just fine.


Insomnia City BBS SysOp
Kalamazoo, MI USA
bbs.farcasternet.org Telnet 23, SSH 2222

... THE fIRST sTEP iS tO tAKE oFF tHE cAPS lOCK

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Insomnia City BBS - Kalamazoo, MI (21:1/156)

Hey, not sure what you intended to share here but none of the ansi codes came through so the post looked like gibberish :)

The screen showed up and displays here in ANSI color. Maybe it is on
your end? It is also in the wrong area, so maybe your system is set to (rightfully) not "do ANSI" for this area.

FWIW also came through as gibberish here as well.

---
Ganiman
bbs.madetoraid.com:[2323/2222]

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Made to Raid BBS (21:3/174)

ogg wrote to Blue White <=-

On 13 Nov 2022, Blue White said the following...

esc wrote to MIKE POWELL <=-

[ANSIART]

Hey, not sure what you intended to share here but none of the ansi codes came through so the post looked like gibberish :)

The screen showed up and displays here in ANSI color. Maybe it is on
your end? It is also in the wrong area, so maybe your system is set to (rightfully) not "do ANSI" for this area.

So it's everyone else problem if your display doesn't render correctly?

The screen shows up on *this BBS*, having transfered from the BBS it posted
on, though the Net 4 hub, and then to *this BBS*. *This BBS* is not the
one it was posted from, and *This BBS* does not run the same software that
BBS does.

So, yes, that would lead me to believe it is not my problem. :)

One trend I do notice is that all the sysops who say it came through bad
are running Mystic, so maybe there is something about the screen that
causes problems for Mystic systems. <shrugs>


... Tell me, is something eluding you, Sunshine?
--- MultiMail/DOS
* Origin: possumso.fsxnet.nz * SSH:2122/telnet:24/ftelnet:80 (21:4/134)

causes problems for Mystic systems. <shrugs>

Shrugs

ogg
Sysop, Altair IV BBS
altairiv.ddns.com:2323

... If you can't make it good, make it LOOK good. -Bill Gates.

--- Mystic BBS v1.12 A48 2022/07/15 (Windows/64)
* Origin: Altair IV BBS (21:2/147)

*** Quoting Blue White from a message to ogg ***

One trend I do notice is that all the sysops who say it came through
bad are running Mystic, so maybe there is something about the screen
that causes problems for Mystic systems. <shrugs>

It didn't render correctly either on my Telegard system. Here's how it
looks on this end:

https://ibb.co/MsBzL43

Most ANSI BBS ads are displayed fine here, but this one didn't. It's almost
as if the ANSI escape character was replaced with a `


Jay

... RAM DISK is NOT an installation procedure!

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms | tg.nrbbs.net | 289-424-5180 (21:3/110.1)

Re: Re: [ansi] Visit Moe's Tavern
By: deon to Digital Man on Mon Nov 28 2022 03:26 pm

I would like to know more about the history of what/why these messages happen and I'll happily reconsider adding support back into Synchronet (perhaps just convert such messages upon import to actual ANSI sequences).

Does that you can revert it now, now that you know why it was there?

(Just askin')

I could, but I still don't know:
1. what software is sending ANSI-encoded messages in this way (GT Power?) - and why?
2. should the \xFA[ encoding also be supported (in addition to `[) - and if so, why?
--
digital man (rob)

This Is Spinal Tap quote #38:
Artie Fufkin: I'm not asking, I'm telling with this. Kick my ass.
Norco, CA WX: 60.9øF, 63.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Re: Re: [ansi] Visit Moe's Tavern
By: esc to MIKE POWELL on Sat Nov 12 2022 03:30 pm

[ANSIART]

Hey, not sure what you intended to share here but none of the ansi codes came through so the post looked like gibberish :)

Well, not really gibberish, just the ASCII ESC characters (27) have been replaced with backtick (ASCII 96) characters.

I once had code in Synchronet to convert messages such as this one into ANSI upon display. 2 years ago, I removed that support with this commit:
https://gitlab.synchro.net/main/sbbs/-/commit/f26b296b

and the message:
Removed the conversion of `[ and \xFA[ to \x1b[ in putmsg(). This unexplained output translation has been supported since at least v2.xx and I have no recollection of exactly why it was added. If I recall correctly, some BBS software at some point in time sent ANSI-encoded messages into message networks by translating the ESC (\x1b) character in the ANSI sequences to either ` or \xFA in the process. This "feature" seems like it would still work, but it's completely undocumented and I have no idea why it was added (and seriously doubt anyone relies on this behavior), so I'm removing it. If anyone misses this feature, I'll happily add it back, but I'm skeptical that'll happen.

I would like to know more about the history of what/why these messages happen and I'll happily reconsider adding support back into Synchronet (perhaps just convert such messages upon import to actual ANSI sequences).
--
digital man (rob)

Sling Blade quote #13:
Karl: He lives inside of his own heart. That's an awful big place to live in. Norco, CA WX: 70.7øF, 28.0% humidity, 2 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Re: Re: [ansi] Visit Moe's Tavern
By: Digital Man to esc on Sun Nov 27 2022 01:00 pm

Hey DM,

Well, not really gibberish, just the ASCII ESC characters (27) have been replaced with backtick (ASCII 96) characters.

I once had code in Synchronet to convert messages such as this one into ANSI upon display. 2 years ago, I removed that support with this commit: https://gitlab.synchro.net/main/sbbs/-/commit/f26b296b

Removed the conversion of `[ and \xFA[ to \x1b[ in putmsg(). This unexplained output translation has been supported since at least v2.xx and I have no recollection of exactly why it was added. If I recall correctly,

I would like to know more about the history of what/why these messages happen and I'll happily reconsider adding support back into Synchronet (perhaps just convert such messages upon import to actual ANSI sequences).

Does that you can revert it now, now that you know why it was there?

(Just askin')


...ëîåï
--- SBBSecho 3.15-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)