[ANSIART]
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 :)
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.
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.
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.
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?
causes problems for Mystic systems. <shrugs>Shrugs
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>
[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
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).
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')
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,044 |
Nodes: | 15 (1 / 14) |
Uptime: | 00:28:23 |
Calls: | 500,299 |
Calls today: | 17 |
Files: | 95,203 |
D/L today: |
2,561 files (611M bytes) |
Messages: | 465,280 |
Posted today: | 13 |