1. Forum
  2. AgoraNet
  3. AGN TST

  • Translations in WWIVTOSS.

    From WEATHERMAN@46:1/263 to All on Wed Jul 1 21:32:47 2015

    I spent some time working on trying to figure out the problem with the translation tables in WWIVTOSS. It seems like this doesn't have anything to do
    with the ANSI export/import, as it shouldn't be changing any characters by default.

    Maybe ANSI is just handled differently on each BBS. I saw the other ANSI post over here so not sure what is different.

    The translation table issue still has me stumped. It basically loads and IN/OUT character for all ASCII from decimal 33 up to 126. For whatever reason,
    the first (8) translations end up with NULLs (blank), then the next 15 show up fine, then next (8) NULL, then 15 show up, etc..etc..

    I have no idea why, as it is reading this from a regular .dat file as an unsigned char.

    Anyway, no big deal as I don't think it is needed anyway and wouldn't have an effect on this.

    - Mark
      
    --- WWIVToss v.1.51
    * Origin: http://www.weather-station.org * Bel Air, MD -USA (46:1/263.0)
  • From Mercyful Fate@46:1/140 to WEATHERMAN on Thu Jul 2 04:33:14 2015
    $ WEATHERMAN was quoted saying . . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    I spent some time working on trying to figure out the problem with the translation tables in WWIVTOSS. It seems like this doesn't have anything
    to do with the ANSI export/import, as it shouldn't be changing any
    characters by default.

    Maybe ANSI is just handled differently on each BBS. I saw the other ANSI post over here so not sure what is different.

    The translation table issue still has me stumped. It basically loads and IN/OUT character for all ASCII from decimal 33 up to 126. For whatever reason, the first (8) translations end up with NULLs (blank), then the
    next 15 show up fine, then next (8) NULL, then 15 show up, etc..etc..

    I have no idea why, as it is reading this from a regular .dat file as an unsigned char.

    Anyway, no big deal as I don't think it is needed anyway and wouldn't have
    an effect on this.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Well 33-126 would just be normal ASCII so thats not even hitting ESC (27) or Extended Ascii 127-255 for 8-bit block drawing characters. What excatly needs translating or is WWIV toss doing?

    |07M|11er|03cy|07ful Fate |08(|15hTc|08)|07

    --- Enthral BBS v.635 (PI/2 Linux armv7l)
    * Origin: haunting The chapel >>--> htc.zapto.org <--<< (46:1/140)
  • From WEATHERMAN@46:1/263 to Mercyful Fate on Thu Jul 2 15:26:20 2015


    Well 33-126 would just be normal ASCII so thats not even hitting ESC (27) or Extended Ascii 127-255 for 8-bit block drawing characters. What
    excatly needs translating or is WWIV toss doing?

    Yes.. That is why once I saw the code for the translation table in WWIVTOSS knew it had nothing to do with the ANSI messages.

    Honestly I'm not really sure what the translation table was meant to do. You can basically make it replace characters with other characters, but have no idea why you would want to do that. So, I just kept that part of the code commented out.

    I do have WWIVTOSS set to pass High/Extended ASCII - so it should send it without touching the content.

    I just sent another ANSI from another source to see if that displays any different.

    - Mark

    --- WWIVToss v.1.51
    * Origin: http://www.weather-station.org * Bel Air, MD -USA (46:1/263.0)