1. Forum
  2. FidoNet
  3. WILDCAT! SUPPORT

  • Pipe Color Code Translation

    From Robert Wolfe@1:116/17 to All on Sun Feb 3 12:35:20 2019
    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?"

    ... Robert Wolfe <robert.wolfe@winserver.org>, Sysop, Omicron Theta BBS
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: Omicron Theta (1:116/17)
  • From Rob Swindell@1:103/705 to Robert Wolfe on Sun Feb 3 15:10:43 2019
    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.

    digital man

    Synchronet "Real Fact" #23:
    The third ever Synchronet BBS was The Beast's Domain (sysop: King Drafus). Norco, CA WX: 51.4øF, 95.0% humidity, 1 mph NNW wind, 0.39 inches rain/24hrs --- SBBSecho 3.06-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Robert Wolfe@1:116/17 to Rob Swindell on Sun Feb 3 19:23:16 2019

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

    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.

    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 <robert.wolfe@winserver.org>, Sysop, Omicron Theta BBS
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: Omicron Theta (1:116/17)