Not tested on Windows.

I don't expect anything actually uses this...

This is so gross... outputting any character depends on every
character above it, so it must be checked every time.  If the state
was ste up differently, this could be avoided, but it's not, so it
can't.

For v2, I'm going to want to store some per-line data in a separate
struct so I can track this.

(these options follow the password by one or more spaces)

I implemented these based on AreaFix v1.10 User's Guide, at Ragnarok's
suggestion/request. I didn't test them, so looking forward to getting some
test results.

The -L and -Q options are functionally identically to the %LIST and %QUERY
AreaManager commands, while -R ads a little efficiency by combining +areatag
(add) and %RESCAN <areatag> requests in a single command.

Apparently AreaFix and other area managers assume password never have spaces
in them, so they can support additional arguments following the password in
the AreaFix request.

This change also now disallows setting AreaManager passwords with spaces in
them.

I don't yet support any of the additional AreaFix request options (e.g. -L,
-R, -Q), but am considering it.

A bunch of sprintf() -> snprintf() conversions are included in this commit
(better string buffer security, probably eliminate a Coverity issue or two).

This build rule needed to be defined *after* objects.mk and rules.mk are
included.

Changing "stuff" on a line will now propogate to the right
appropriately.

Next up is double-height characters... hopefully.

Basic Prestel support based on the "Prestel Terminal Specification"
Issue 2 by the Post Office.

Known issues:
Modifying an existing line does not update the row after it.
Double height is not supported.
Keyboard mapping kinda sucks (looking at you #/Return).
Concealed is always shown.
Remote programming sequences aren't supported.

There appears to be something wrong with the End of the Line title
and menu screens, but maybe nelgin did them wrong.

Supporting the deletion of ranges of lines (e.g. 10-20 rather than one line
at a time) was a big ommission for a long time.

... if you're deleting more than one string, this is much more efficient.

Note we do some pointer compares (in strListFastRemove) *after* we've freed
them in strListFastDelete(). I don't suspect this to be an issue, but it does
seem suspect.

... integer sign extension at fault here.

Also, add examples to Numeric vs. Verbal short date selection dialog.
Update some related help text.

For cases where we want to the verbal short date output, regardless of sysop
preference/configuration.

to not overwrite help "screen" borders

This allows us to use dstrtounix() for MM/DD/YY dates regardless of the system
configuration (sysop/locale preference).

This fixes issue with QWK route.dat file and door.sys (expiration date)
parsing where the date is/has-to-be in MM/DD/YY format, always.

RIPtel reset to the font configured by the user, not the current
font.  Do the same here.

It appears v3 kept the font through a RIP_RESET_WINDOWS command

Fix new date editing bug in user editor: we must use the numeric format
for dates when creating strings to be edited.

No need to use time32_t for this.

"01/00/00" would get parsed/converted back to Jan-1-2000 (usually), which is
usually not what we want.

If telnet binary mode is enabled (the new default), and a CR and LF
come in on separate recv() calls, the RIP parser would stop at the
CR, and pass the LF back to the ANSI parser.

Ah, dura-bbs.net, always pushing the limits.

We want to not expand tilde to attributes when there are any attribute codes
in the mnemonics string. The existene of a non-attribute ctrl-a code should
not have prevented the tilde expansion.

Fix for issue #805 reported by Nelgin (thank you)

RIP XOR operation had issues with polylines, boxes, etc. where the
same pixel could be written more than once, resulting in it being
toggled back to the original state.

Also, there were some memory leaks of temporary struct ciolib_pixel
variables.  This is now fixed as well.

Although we've added (in SBBS v3.20) configurable numeric date input/display
formats for the system, the output was still ambiguous for users (e.g.
NN/NN/NN which could be interpretted a number of ways), so I've added an option
to choose "verbal" short date formats to be displayed where possible instead.
The same value separate from the numeric format (whatever the sysop chose) is
used in the verbal date output, but since month name abbreviations are 3
characters, only one separator is used (to keep the output length fixed at 8
characters).

The new "Verbal" short date display format is choosable in the SCFG wizard and
via SCFG->System->Short Date Format.

Both selecting scrollback from the online menu, and viewing the last
scrollback from the main menu were impacted.

Currently, this is a slower way to look-up a text.dat string, but requires no
load/require of text.js and allows for a shorter syntax to get a text.dat
string, i.e. bbs.text("Quit") instead of bbs.text(bbs.text.Quit);

Although the bbs.text() ID lookup is cached, it's only marginally faster than
system.text() ID lookup, which is not cached and about 1/3 the speed of the
other methods of index to string lookup (in the MSVC-Windows build).

... with Servers->Terminal Server->Login Requirements

Updated help text: F5->Ctrl-C, no need to hand-update sbbs.ini when adding
or removing nodes (any more).

- Attempt to suppress go aheads in both directions.
- Attempt to set binary mode in both directions
- Request the remote echos

These express the assumptions that SyncTERM always makes, so it's
a good idea to tell the remote this.  For systems that don't like
this, there is the Raw "protocol".