Removed the X-Comment-To header field (is this file being used for NNTP?).
Added an 'unfold' boolean argument (defaults to true). If false, don't unfold
the header fields.

Removed extra space from LongLineContinuationPrefix (when used, there's
usually already a space following the cond line-break).
Removed the cond-line break from the AutoMsgHdr.

Decodes those funky strings you see in message (e.g. email) headers:
=?ISO-8859-1?Q?a?= =?ISO-8859-1?Q?b?=
=?UTF-8?B?UmVtaW5kZXI6IFdlc3Rlcm4gUml2ZXJzaWRlIENvdW50eSBDb21tdW5pdHkg?=

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.

- mime_version (from the message header, if MIME)
- content_type (from the messgae header, if MIME)
- charset (from the plain-text MIME portion content-type header field)

content-type "charset" parameter value and store in the (new) smbmsg_t.charset.
This is a heap-allocated copy of the text from the message body, so it must be
freed in smb_freemsgmem(). When NULL, the charset can be assumed to be
US-ASCII.

(when set to Yes).

The default is off (no stripping). Previously, Soft-CRs were always stripped,
but this behavior is now seen as an anachronism as CP437 char 141 is an
important non-English laguage character and used as such in FidoNet msgs.

in switch

nicely when displaying at various terminal widths.

attempt to resolve infinite recursion bug -- would love to know what word was attempted so I can recreate the issue -- anyone?

Should fix error reported by pfortran on fsxnet.

For QuickBBS editors, the default will be the same as previous behavior: to
convert Soft-CRs to Hard-CRs (CRLFs).
For non-QuickBBS editors, the default will be to treat Soft-CRs as any other
valid printable character in the text ("Retain").
A 3rd option is available to strip Soft-CRs completely from the generated
message text.

For QuickBBS editors, the default will be the same as previous behavior: to
convert Soft-CRs to Hard-CRs (CRLFs).
For non-QuickBBS editors, the default will be to treat Soft-CRs as any other
valid printable character in the text ("Retain").
A 3rd option is available to strip Soft-CRs completely from the generated
message text.

when the user is using the internal msg editor (useron_xedit == 0) and
replying to a message.

Refer to the dubious get_msg_body() feature of dot-stuffing as that
("dot-stuffing") and not "rfc822-encoding" - because it isn't.
dot-stuffing is a requirment of SMTP (RFC*821) and NNTP, not RFC822 (oops).

- to_list
- cc_list
- replyto_list

Always enclose the 'From' name in quotes.
Don't force a reply-to field if subnum is undefined.

- to_list (RFC822TO, previosuly unavailable via JS)
- cc_list
- replyto_list (RFC822REPLYTO, previously unavailable via JS)

Added RFC822FROM to the "field_list" array (previously unavailable via JS).
Removed SMB_CARBONCOPY from the "field_list" (now duplicated in cc_list).

headers

pointer - apparently this has never actually been used before.

- to_list
- cc_list
- replyto_list

These are all comma-separated lists of names/addresses, RFC-822 style
(so quotes and angle-brackets and all that jazz preserved/included)

Document the [newuser] avatar_file and avatar_offset options.

Rename the 'send_newuser_welcome' option to just 'send_welcome' (match wiki)
(let's not repeat ourselves repeatedly) - but leave a backwards compatibility
hack at least for now.

 - HitYourBackspaceKey
 - CharacterReceivedFmt
 - InvalidBackspaceKeyFmt
 - SwapDeleteKeyQ
 - PetTermDetected

New text.dat strings:
 - HitYourBackspaceKey
 - CharacterReceivedFmt
 - InvalidBackspaceKeyFmt
 - SwapDeleteKeyQ
 - PetTermDetected

Fix up some message header field lengths.

Fix up some message header field lengths.

will be sending 0x7f (DEL) when the backspace key is struck: SWAP_DELETE
For example, xterm sends 0x7f when backspace and hit and an ANSI escape
sequence when the DEL key is hit.

I don't yet have a way to *enable* this setting.

Also, allow the user's setting of NO_EXASCII to take effect even when
auto-terminal type detection is used (yes, the user's terminal can support
ANSI and *not* CP437).