Subj : TIC files
To   : Deon George
From : Andrew Leary
Date : Mon Sep 17 2018 02:46 am

Hello Deon!

17 Sep 18 00:03, you wrote to me:

 DG> So this was bugging me - so I made a quick workaround.

I am testing a fix for this problem now.  I also am allowing it to handle 
incoming .TICs with long filenames (over 8 characters for the filename 
portion.)  Mystic creates these when hatching a file with a long filename.

 DG> I know if the standard is that a tic file needs to be 12 chars in
 DG> length (I think it would be good if it was - but I'm not sure that
 DG> that is the standard), then it would be good if on a node by node (or
 DG> global config?) that you can "override" the standard. "Allow Non
 DG> Standard TIC [YES|NO]"

The intention when the standard was written was to specify a DOS compatible 
8.3 filename for .TIC files.  At the time, all known implementations did it 
that way.

 DG> What do you think?

I don't see the need to enable or disable this on a per-node basis.  Since 
MBSE will never create these non-compliant .TIC files, it just needs to handle 
them properly when receiving them.

Andrew

--- GoldED+/LNX 1.1.5-b20170303
 * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

.