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).

- terminals with widths > 132 columns (e.g. quote section separator)
- terminals that don't support CP437 (ex-ASCII) - use console.print()
- terminals that send 0x7f for the backspace key (when at the end of the line
  treat DEL the same as backspace)

--<boundary>--

Without this change, some attachment (e.g. from gmail) would not be correctly
decoded because gmail would not insert any blank lines between the end of the
nested multipart/alternative part and the beginning of the attachment part:
--000000000000d75a0f058779bbb2--
--000000000000d75a12058779bbb4
Content-Type: image/jpeg;
	name="29571163_1640947089321419_3376478908098884084_n.jpg"
Content-Disposition: attachment;
	filename="29571163_1640947089321419_3376478908098884084_n.jpg"
Content-Transfer-Encoding: base64

It looks (from RFC2046) like boundary delimeters should actually be:
"\r\n--<boundary>", but I'll look into that later.

Added configurable options for the message score colors for the message list: msgListScoreColor, msgListToUserScoreColor, msgListFromUserScoreColor, and msgListScoreHighlightColor.  Incremented version to 1.20.

the user's your-scan config (&S using the default shell) even when
"Display subjects only" was confirmed. Previously, when only subjects were
shown, all subs were scanned regardless of user config.
Bug reported by John Hiemenz, thanks!

Version 1.19: If the terminal size is wide enough (at least 86 characters), the overall vote scores for the messages  is now displayed in the message list.  Also, fixed a bug introduced in the previous version where the vote scores were no longer being displayed when reading a message.  It's no longer using MsgBase.get_index() and uses get_all_msg_headers(), as before, since that's what is required for message tallies to be included in the message headers.

- DELAY:nn (delay nn 10ths of a second)
- POS:nn (move cursor to position nn, not sure if nn is 0 or 1-based)
- CLREOL (same as CLR2EOL)
- YESCHAR (the character/key for "Yes", from text.dat YNQP string)
- NOCHAR (the character/key for "No', from text.dat YNQP string)

and for good measure:
- QUITCHAR (the character/key for "Quit") - not supported by PCBoard