- hot spots are clickable screen areas (e.g. in menus and prompts) that   generate key-strokes
- commands may be from 1 to 127 ASCII-characters in length
- currently using the X10 mouse reporting mode, may change
- all mnemonics strings (~Example) are automatically hot-spots
- The new ~ @-code defines a hot spot
- Any screen-clear operation clears all hot spots
- sbbs now tracks the current screen (cursor position) row
- eliminated the old "tos" (top-of-screen) boolean (row == 0 indicates "tos")
- created an sbbs_t::ungetstr() method
- keep track if in pause (hit a key) prompt, for special mouse behavior

new JS console object:
- row property
- tos property is now read-only (and deprecated)
- new methods:
  add_hotspot()
  clear_hotspots()
  scroll_hotspots()

redrwstr() gets some UTF8 touch-ups as part of this commit. <shrug>

Don't suppress the display of the "from network address" just because there's
an '@' in the "from name" - some Internet email (e.g. SPAM) "From" names
include '@'s to try and follow the reader. <sigh>

wrapper for utf8_normalize_str() and utf8_replace_chars with the proper
arguments.
This will fix *a* problem with UTF-8 message not being converted to CP437 in
QWK packets correctly (we were just normalizing, not fully converting).
Also got rid of the defunct DLLCALL usage str_util.c

characters in message headers and body text will be converted to CP437.
Also include a new field in HEADERS.DAT: utf8 = true/false to indicate that
the message headers and body text contain UTF-8 encoding (not CP437).

would reuse the same buffer where the message subject (list of filenames)
was stored causing havok. Reported by Alterego (ALTERANT).

can't use it as an argument to sprintf(str, ...)
Also, use getfname()... more.

- bstrlen() moved to sbbs_t, accepts an option pmode argument so it can account
  for UTF-8 encoded strings correctly
- JS console.strlen() now accepts an optional pmode argument (e.g. P_UTF8)
- Renamed sbbs_t::utf8_to_cp437 to sbbs_t::print_utf8_as_cp437
- Create/use msghdr_hfield() to perform UTF-8->CP437 conversions as needed for
  printing/copying UTF-8 encoded message header fields.
- Defined XTRN_UTF8 misc setting flag. If a message editor does *not* have this
  flag, it is assumed to *not* support UTF-8. Will likely use this for UTF-8
  doors as some point too (none known to exist, yet).

show_msghdr()

flag in the message header.
When displaying message header fields containing UTF-8 using show_msghdr()
with text.dat string or with msghdr.asc and @-codes, do the "dance" to be sure
it's displayed correctly depending on the user's terminal (UTF-8 or not).

to putmg() when displaying messages in the sub on the terminal server.
E.g. to disable word-wrap for *all* messages displayed in a sub, set P_WORDWRAP
in sub_t.n_pmode.

support in putmsg/printfile, etc. on per-use basis.
Add per-sub-board P-mode flags (so "Extra Attribute Codes" can be disabled
on a per-sub-board basis).

with ZWNBSP/BOM UTF-8 sequence) and messages (with the "CHRS: UTF-8"
FTN control paragra or MIME "charset=utf-8" parts).
Not all UNICODE codepoints are supported (obviously).
Tested with various files from ftp://columbia.edu/kermit/charsets/
(e.g. test.utf8, utf8-boxes.txt)

to a text/html part of a multi-part MIME encoded message if no text/plain part
exists.
Changed smbmsg_t.charset to smbmsg_t.text_charset.
Added smbmsg_t.text_subtype (e.g. "plain" or "html").
Fixed issue with parsing parsed plain-text when the charset was the last
element of the MIME-part header.
MIMEDecodedPlainTextFmt text.dat line now includes the text sub-type arg

as well as the auxattr "Attach" when either FILEATTACH or MIMEATTACH is set
(requires an updated MsgAttr line in text.dat).

Expanded codes will not *not* go beyond the terminal column width (minus 1).
If you need the old/wrap behavior, add a "-W" modifier to your @-code.
If a length value is specified with -W, it is ignored.

- MSG_TO, MSG_FROM, MSG_SUBJECT now reflect the header values passed
  to sbbs_t::show_msghdr(), JS bbs.show_msg_header() and not necessarily the
  actual stored (e.g. MIME-encoded) header values.

New codes:
- MSG_CC - reflect a message's CC list, if it has one
- DATETIMEZONE - combines DATETIME and TIMEZONE in one string

used to display a CC list, when applicable.

show_msghdr(), over-riding the values from the passed smbmsg_t. This is useful
for, say, displaying MIME-decoded values rather than the MIME-encoded versions
of the header fields that you often find in email today.

Renamed MIMEDecodedPlainText to MIMEDecodedPlainTextFmt
(since it is now a printf-style format string).
No special handling of non US-ASCII (e.g. UTF-8) characters... yet.

console.msghdr_top_of_screen):
a hack to let scripts know whether the most-recently displayed message header
was displayed on the top of the terminal screen (or not). This allows us to
show avatars at the top of the screen when the header is up there, rather than
relevative to the bottom of the header (the pos can vary, depending on stuff).

download_file_attachments() and expose via new JS "bbs" method. Currently
this only reall works for the mail base.

- bbs.show_msg()
- bbs.show_msg_header()
Re-worked the JS bbs.netmail() implementation
sbbs::show_msg(), show_msghdr(), msgtotxt() now take an smb_t* argument
(don't use the pseudo-global 'smb' in these functions any longer)
sbbs_t::putmsg() and JS console.putmsg() now accept an optional orig_columns
argument to specify the original column width of a text for intelligent
re-word-wrapping (e.g. as taken from a message header field). Previously, the
original-column value was hard-coded to 80 columns (technically, 79).
sbbs_t::show_msghdr() no longer sends a CRLF if the cursor is already at the
top-of-screen (TOS).
sbbs_t::show_msg() now uses the stored "columns" msg header fields to pass to
putmsg() to intelligently re-word-wrap message bodies for display.
sbbs_t::show_msg() and msgtotxt() return bool now instead of void.
JS MsgBase.get_all_msg_headers() now supports an optional "expand_fields"
argument (defaults to true). I contemplated just getting rid of the (few)
expanding header fields (more like default-value-header fields, like 'id'), but
decided against it, at least for now.
JS MsgBase.put_msg_header(), the "number_or_offset" argument is optional and
not needed if a header object argument is provided. Make this clear in this JS
docs for this method

Note:
I sat on this commit for a while because I noticed occasional errors like this:
    Node 1 <Digital Man> !ERROR 2 (No such file or directory) (WinError 0) in
    readmsgs.cpp line 217 (sbbs_t::loadposts) locking
    "path/to/sub" access=-100 info=smb_locksmbhdr msgbase not open
started cropping up after introducing these changes and which I never
root-caused. But after a clean-build and waiting a week, I haven't seen it
again, so hopefully it was just a incomplete rebuild issue and not a new bug.

menu() if it does (exist) and doing something else if it doesn't.

message header.

users) and adjusting scan ptrs by date or set to "Last msg" while online:
- speed (on my system, reduced from 12 to < 2 seconds)
  This involved 2 enhancements: check msgbase index file timestamp (fast)
  before opening any files. When opening the msgbase, just open the index
  file (no other msgbase files) - required new smblib function: smb_open_index.
- fixed off-by-one when setting by date (when setting the new-scan ptr to
  Jan-1-2018, you want that first message posted on/after Jan-1-2018 to be
  found as "new", not the first message posted *after* that date.
- re-added the fixmsgptrs() call in putmsgptrs(), inadvertently removed
  in the .ixb -> .ini ptr storage update in rev 1.192 of userdat.c.

  MsgHdrBodySeparator
This is display between the msg header text.dat lines and the message body
(previously, just hard-coded to a blank line).
This enables us to now execute showmsgavatar.js much faster than loading
msghdr.asc file, and using it to execute showmsghdr.js.
So... if you're upgrading to this build, you can get rid of msghdr.asc and
get a message viewing performance boost. The results should look the same
(but the message header will display immediately, with no discernable delay).

line (CRLF) after the header and before the message body. If you want a blank
line, it must be in the msghdr.asc file. This change is to be consistent with
the behavior in v3.16.

- if the sysop had text/menu/<filename>.bak (for example), the optoinal menu
  would attempt to load, resulting in an error ("<filename>.asc not found")
- if the sysop specified menu_file or menu_dir (e.g. via Baja), the existing
  checks for optional menu file existance would not work

When displaying message body text, skip all initial ocurrences of CR or LF
(rather than all initial white-space). Some people use white-space for
centering or justifying blocks of text and we don't want to mess up the
presentation of their messages.

- VoteInThisPollNow
- MIMEDecodedPlainText

trailing white-space.

Server via the new 'V' command from the Reading Mail prompt allows you to
toggle between all mail (including SPAM, the default), SPAM only, or HAM only.
Also added a new '/' (search text) command from the reading mail prompts.
Mail imported before the mailsrvr added support (recently) for the MSG_SPAM
attribute flag will not be counted/filtered as SPAM.
SBBSecho will have a commit (next) to support the new loadmail() usage, it
will not compile until then.

Introduced a better progress indicator (similar to poll results), using the
backfill() method. 2 new attr.cfg fields allow the progress indicator colors to
be configured separately from poll results (though they default to the same
white on magenta). This new progress indicator is used when loading msg ptrs
and scanning for votes. I will be using it while performing other searches
(e.g. file libraries/dirs) as well.

by Bill McGarrity: new bug.