vidparam structure itself.

HEADERS.DAT.

FIDOCHARSET, no longer FIDOCTRL.

FIDOCHARSET
Export CHRS: control line with value determined by sub-board settings (e.g.
ASCII only) and the contents of the message (UTF-8 or CP437).
Import "NOTE:" control line values into the SMB_EDITOR hfield and export
from SMB_EDITOR -> NOTE:.
Increment SBBSecho version to 3.08.

And remove the "CHRS: " portion of the FIDO_CHARSET_UTF8 definition as we're
now storing these values in their own SMB hfields (FIDOCHARSET), not FIDOCTRL.

FIDOCHARSET
with its own smbmsg_t convenience pointer: ftn_charset.
this allows greater control over when/how this header field is exported.
Constify smb_msg_is_utf8().
Note that the "Editor" hfield type should hold any FTN "NOTE" control line
values (where msg editor details/version are normally propagated over FidoNet).

Replacement for Baja TEXT_FILE_SECTION and JS bbs.text_sec() functions.
Ported from src/sbbs3/text_sec.cpp

You run it from a Baja module with: exec_bin text_sec

This is a work-alike port of one of the oldest/cruftiest bits of C code in
Synchronet with no improvements in look or usability.
1. I want to eventually start deleting all the redundant C/C++ code in sbbs,
   so that's one reason why I've been creating these *_sec.js modules, and
2. I think this "section" of the BBS could use some significant improvement
   and didn't want to do any of that in C/C++ - this is clearly a JavaScript
   task. But I wanted to start with the identical functionality and improve
   from there.

(e.g. for UTF-8 Fido or QWK netmail messages sent over SMTP or POP3).

instead of "charset=IBM437", when appropriate.

instead of "charset=IBM437", when appropriate.

FAQ.

When set to true, enables group read permissions on the ssl.cert file
(using the new file_chmod() global function).

- "ECHO" (useful for testing @-codes)
- "EVAL" (useful for testing JavaScript expressions)

"TYPE" and "CAT" are now aliases for "LIST" (display a text file)

Return an inverted question mark for unsupported codepoints.

I've been sitting on this uncomitted changed for a while, likely needed for
BinkIt outbox support (oops).

- Boolean: is_utf8
In the case of multi-part MIME messages, this may not be populated
accurately until the message body is read with the get_msg_body() method.

CP437 would've made a bit more sense here, but we're HTML entity-encoding those
chars where needed.

JS scripts using system.temp_dir to store files get a sensible value (and not
the hard-coded default of just "temp").
This should fix the creation of ctrl/tempftelnet.url files.

- Export all FIDOCTRL (other FTN kludge lines) to the QWK HEADERS.DAT file.
  These should already be imported if they exist, but were never added during
  export, so untested/new behavior. The control paragraph (kludge line) of
  specific interest here is the "CHRS" (charset) kludge we need for UTF-8.

- Don't use the QWK "newline" character (0xE3) when the message is UTF-8.
  Use bare-LF's instead. This is pretty untested at this point as I will need
  another QWKnet board to post or receive UTF-8 encoded messages to test,
  getting the code into CVS is the first step. At least for now, there's no
  opt-in/out for this behavior. If your BBS has UTF-8 encoded messages, some
  QWK nodes or offline readers may have trouble with packets which include
  those messages. Or they may work fine (but likely display garbage CP437
  chars in-place of the proper Unicode codepoint glyph).

- The beginning of UTF-8 input support in getstr() - which needs more work,
  particularly around character and word deletion and insertion.
- The internal message editor now supports UTF-8 messages and kind of somewhat
  supports inputting UTF-8 characters in message text.

New put/print text flag: P_AUTO_UTF8 which can auto-detect UTF8 strings and
do the "right thing" for the user's terminal. New associated sbbs_t method:
auto_utf8() which automatically sets P_UTF8 for any stirng that begins with
a UTF-8 BOM (ZWNBSP). Else, if the P_AUTO_UTF8 mode flag is set, then
it checks to see if the string contains invalid US-ASCII chars but valid UTF-8
sequences and then sets P_UTF8 accordingly. Used by putmsg() and bputs().

There's a new permuation of bprintf() which accepts a mode argument
(i.e. for P_UTF8) and passes it on to the new mode-capable bputs().

Since sockwrap.h #Includes winsock2.h, let's #include it before any other
header files (e.g. genwrap.h)

Since sockwrap.h #Includes winsock2.h, let's #include it before any other
header files (e.g. genwrap.h)

InterlockedCompareExchange() expects a long*, not a uint32_t*.