using the version to determine what's supported (and isn't).

to have the NO_EXASCII (plain-ASCII only) set if the logged in without a
successful auto-terminal-type detection.
And with sbbs_t::term_supports(), we don't need useron.misc to reflect the
auto-detected-terminal-type any longer.

expanded.

the "darkgray" background issue when using xterm.
Apparently if the foreground attribute has the high intensity attribute set
and a CRLF or a clear-screen sequence is sent, the new (blank) lines (normally,
black) will have the high intensity *background* attribute set (or it just
looks that way). I don't understand why... yet.

 hex escape sequence out of range

clear-screen (CLS) in logon.cpp.
Use of the new ELLIPSIS @-code.

This prevents any auto [Hit a Key] prompt just because we printed the
"Logging on to <bbs> as <user> ..." line.

where the comment was only on the first line.
This only cropped up in the text.h output when the *last* line was a multi-line
(continued) string.

don't move the cursor position.

string: LoggingOn
This was the *first* possible cause of an auto-pause ([Hit a key] prompt)
during successful SSH logins.
The new text string is just "Logging on to @bbs@ as @alias@ @ellipsis@"
- if you want a screen clear here or to display a text file, you can do so by
  modifying this line.

U+ code now supports <code-hex>:<text> syntax so that multiple chars (a string)
may be specified as a fallback for non-UTF-8 terminals.
The U+<code>/<char> syntax was changed to U+<code>,<char>
New symbolic @-codes that send the right Unicode code point to UTF-8 terminals
or a string to others:
- ELLIPSIS
- COPYRIGHT
- SOUNDCOPY
- TRADEMARK
- DEGREE_C
- DEGREE_F

string (multiple) CP437 fallback chars, for when a single CP437 char won't
suffice.

Fix error in CP437 0x96 (small U with circumflex) translation to UNICODE
(typo: 0x00FB not 0x00F8).

Fixed one typo (LATIN_LATIN).

Extract the term size method used by SSH and pty into a function, and remove
the need to change the video mode.

always uses font zero now.

things.

This allows full control over the display, and avoids font mangling.

a struct vmem_cell.

This allows modifying a savescreen() rather than needing to vmem_gettext()
stuff, but also change things without hacking up the pixels array yourself.

Also, the vmem is an array of struct vmem_cell.

problems loading font data in SyncTERM over Telnet.

<Deuce> Easiest fix would be to have outbuf_append adjust outlen to be "long enough" if doubling isn't.
<Deuce>         /* Not enough room, double the size. */
<Deuce>         *outlen *= 2;
<Deuce>         if(*outp - *outbuf + len >= *outlen)
<Deuce>                 *outlen = *outp - *outbuf + len + 1
<Deuce> So yeah, blindly doubling won't work for utf-8.
<Deuce> Because a line will have more bytes than the number of characters in a line.

cvstat.

Per RFC-5198:
   2.  In Net-ASCII, CR MUST NOT appear except when immediately followed
       by either NUL or LF, with the latter (CR LF) designating the "new
       line" function.  Today and as specified above, CR should
       generally appear only when followed by LF.  Because page layout
       is better done in other ways, because NUL has a special
       interpretation in some programming languages, and to avoid other
       types of confusion, CR NUL should preferably be avoided as
       specified above.

It's not worth breaking all connections for some broken telnet servers.
Especially since we do not explicitly want CR behaviour which is the only
place it's allowed.

Per RFC-854:
   the sequence "CR NUL" must be used where a carriage return alone is
   actually desired;

It's quite possible that these "telnet servers" are actually raw socket
servers and should use raw sockets rather than telnet.

Note that conn_pty does not support PETSCII or ATASCII as the terminal
type since it sets TERMCAP, and I don't have a termcap entry for either of
those.

rather than no char, when calculating word lengths. We needed that 'continue'
here.

on cterm.