Re: Logon Screens
  By: mark lewis to Nightfox on Mon Jun 03 2019 05:05 pm

 >
 >  On 2019 Jun 03 09:17:38, you wrote to me:
 >
 >  Hu>>> Oh..No.. I don't. I figured if my term is ansi I would just need
 >  Hu>>> logon1.ans. I'll try adding logon1.asc
 >
 >  ML>> might be better to go with *.msg format since it can contain color
 >  ML>> codes which will be transmitted or not as the remote end needs...
 >
 >  Ni> Same with .asc..  .asc files can contain Synchronet color codes, which
 >  Ni> will be converted to ANSI or left out, depending on the user's
 >  Ni> terminal capabilities.
 >
 > interesting... wonder what msg brings to the table? i guess i need to do
 > some more reading...

Documented here: http://wiki.synchro.net/custom:menu_files

Mainly, if you want separate menu files for terminals that support
extended-ASCII (CP437) and those that do not, then you can have both .msg and
.asc (the .asc being for ASCII-only users) - otherwise, they're the same.

One advantage to .msg is that PabloDraw recognizes it as a Synchronet (Ctrl-A)
format file automatically - so if you use PabloDraw, they're definitely more
convenient.

                                            digital man

Synchronet/BBS Terminology Definition #72:
TCP = Transmission Control Protocol
Norco, CA WX: 75.3°F, 56.0% humidity, 5 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.07-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)