Subj : RE: Pipe Color Code Translation
To   : Rob Swindell
From : Robert Wolfe
Date : Sun Feb 03 2019 07:23 pm


On Feb 03, 2019 03:18pm, Rob Swindell wrote to Robert Wolfe:

RS>   Re: Pipe Color Code Translation
RS>   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?"

RS> That seems like a weird place to do the translation (in the tosser).
RS> What if you have a network of Mystic systems with a Wildcat! hub? Would
RS> the Wildcat! hub have to convert all colors codes back to pipe-codes
RS> before sending to the Mystic nodes? And what if some of the nodes
RS> weren't running Mystic? The hub would have to know what software was in
RS> use at all times for each node to convert color codes correctly. Seems
RS> like a mess to me.

Well, it was just an idea.  :)  I know that it does the same thing for PCBoard
@-codes.  But, again, just an idea, just a starting point.  Nothing else.

... Robert Wolfe <[email protected]>, Sysop, Omicron Theta BBS
--- Platinum Xpress/Win/WINServer v7.0
* Origin: Omicron Theta (1:116/17)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.