So, passed the following idea along to Santronics this afternoon re:pipe color codes:
"I was wondering if you would consider pipe color codes to @-code translation on
import in PXECHO/PXMAIL? There are lots of Mystic boards on the networks these days and a lot of their users post using their software native pipe codes for color. I was wondering if, when importing messages, PXMAIL/ECHO could check for
"Mystic BBS" in the @TID line in the message header and translate the color pipe
codes properly before putting them into the message database?"
Re: Pipe Color Code Translation
By: Robert Wolfe to All on Sun Feb 03 2019 12:35 pm
So, passed the following idea along to Santronics this afternoon re:pipe
color codes:
"I was wondering if you would consider pipe color codes to @-code
translation on
import in PXECHO/PXMAIL? There are lots of Mystic boards on the networks
these days and a lot of their users post using their software native pipe
codes for color. I was wondering if, when importing messages,
PXMAIL/ECHO
could check for
"Mystic BBS" in the @TID line in the message header and translate the
color
pipe
codes properly before putting them into the message database?"
That seems like a weird place to do the translation (in the tosser).
What if you have a network of Mystic systems with a Wildcat! hub? Would the Wildcat! hub have to convert all colors codes back to pipe-codes before sending to the Mystic nodes? And what if some of the nodes
weren't running Mystic? The hub would have to know what software was in use at all times for each node to convert color codes correctly. Seems like a mess to me.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 253:42:53 |
Calls: | 500,267 |
Calls today: | 5 |
Files: | 95,201 |
D/L today: |
311 files (217M bytes) |
Messages: | 464,714 |