Subj : Re: Problem with filenames containing spaces
To   : Andrew Leary
From : James Coyle
Date : Thu Jan 20 2022 11:03 am

 AL> I would have to test further to populate the list of mailers that
 AL> require  setting the WrongEscape option (as it's labeled in the mbcico
 AL> code.)

I haven't finished fully testing it, but here is what I came up with as an automated way to use the \## mode based on Oli's suggestion to check the VER frame:

If the VER frame contains any of "Internet Rex", "Argus" or "Mystic/1.12" then use the \## escape method.  I think that will cover any compatibility issues, but I still need to test against the final version of IREX to confirm without any doubt it needs \##.

In terms of Mystic anyone can just search for "Mystic" and use that as a trigger for \## too since Mystic does support both like MBSE/BinkD does.

 AL> If you ever need clarification on anything related to the FTSC, please
 AL> don't  hesitate to netmail me.

Thank you I appreciate that!

Likewise if you ever hear of or encounter anything that seems out of place that Mystic is doing please let me know so I can get it fixed up.  Its at a pretty good place these days although there were growing pains getting there (as should probably be expected with one person developing 3 mailers, net/echo/tic tossers, and BBS software all at once lol).

.... My reality check just bounced

--- Mystic BBS v1.12 A48 2022/01/19 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.