We don't need the carriage returns and they cause Git warnings:
warning: in the working copy of 'src/sbbs3/text.h', CRLF will be replaced by LF the next time Git touches it

Fixes issue #670

New method: bbs.load_user_text() to load/reload user's language file. The
user's select language file (if there is one) is automatically loaded upon
logon to the terminal server, but if the user changes their language
(e.g. via user_settings.js), we needed a way to force re-load of the language
text. This is the way.

bbs.text() now accepts an optional second (bool) argument that if true, will
return a string from the default language strings (in text.dat), and not a
string from any alternate language files (ctrl/text.*.ini) that might've been
loaded. This allows user_settings.js to always get the name of the default
language string (LANG), e.g. "English".

The CTX constructor arguments weren't documented

Some blind beautification via HTML tags

Also clarify (or try to clarify) that the maxlen argument is required if you
want to specify any kmode flags.

Ragnarok (DOCKSUD) would like to use lang_COUNTRY for their language files
as  "I use es_AR and is exactly not same to es_ES"

It's trivial to extend the length more if there's a desire to do that.
That's a nice thing about the new (in v3.20) user.tab file format.

Fix issue #667

I'm not sure why these warnings just started popping up (maybe the inclusion
of string in sbbs.h), but it only seems to happen in debug builds and the
possible truncation is intentional.

C++ Builder6 doesn't have unordered_map, so only #include those std C++
headers if/where we actually need them.

Whoohoo, I'm a reel STL programmerz n0w!

error: ISO C++ forbids comparison between pointer and integer

Uses the new ctrl/text.??.ini files (just a few words translated so far).
Adds the new "lang" user property (to user.tab and JS User class).
The language code is the 2-3 char (e.g. ISO 639-1) abbreviation of a language.
A "blank" language property value (the default), just means to use the
ctrl/text.dat contents.
User-selected alternate language file is loaded upon logon and in the
built-in/hard-coded user default settings menu.
More on the user default settings menu:
- AutoLogin via IP option ('I') to make room for new (I) Language option.
- The cold-keys menu option was removed to make room for Language option
  (via text.dat change to UserDefaultsHotKey)
- Any options disabled via blank text.dat strings will no longer result in
  supported command keys (that could accidentally be struck with hidden
  consequences/effect)
- The user_settings.js will need similar treatment

text/menu/<lang>/* is where alternate language menu files should be stored

New UserDefaultsLanguage text.dat string (inserted before new PasswordChar
string).

This fixes the issue with the ContinueQ setting in ctrl/text.??.ini when
attempting to use one of them to replace text.dat strings with localized text.

In a fresh install, neither of these files would exist, and that's normal,
so getstats() should just return true in that case (with the stats struct
zeroed-out).

Fixes error during login to a new install reported by Zoltán Gábor on
Facebook.

... in the linked node listing

In attempt to address the "Error 11" (EAGAIN) error theat Nelgin sees when
configuring some longer modem init strings on Linux.

This is just a single retry (after a yield) after any modem command char
send failure (for any reason), including the terminating carriage-return.

See issue #662 to details.

For waveOutOpen and friend functions

.. so it can be loaded in the same solution as the conio project

to differentiate it from the non-SDL version of the conio property sheet

e.g. src/sbbs3/scfg/scfg.vcxproj

Running SBBSCTRL on Windows 11 with a 4K monitor looked horrible.
The default font sizes varied widely - I'm not sure why this wasn't
apparent before now. And the default font ("MS Sans Serif") is no longer
included in modern Windows versions, so when choosing a Log font, the
pre-selected font was just blank. So change use of "MS Sans Serif"
everywhere to "Microsoft Sans Serif" which appears to have been around since
Win95 and be the preferred alternative. I would consider Segoe, but that
wasn't introduced into Windows until Vista and I'm not sure (yet) what
troubles that might introduce. I'll experiment with a WinXP VM maybe
and find out.

Also:
For log message styles (e.g. colorization) based on log level, don't apply
a different font (Name) or size. This just looks terrible when this is done
and I don't think any sysops want that. Keep each log window using the same
font face (name) and size, just allow the color and style (e.g. bold, italics)
to change based on log severity.

This does increase the confusion with the Properties->Customize->Log Fonts
as the "Change Font" dialog still allows the sysop to select/change a font
face and size, they're just not saved/used. I coudln't find a way to remove
or disable these from the displayed TFontDialog form.

Win32 GDI mode is also native, so let's be more specific.

Apparently this was non-intuitive to sysops. <shrug>

This is version installed with MSVC 2022

to find VsMSBuildCmd.bat

This means you can't use MSVS 2019 with this build.bat any longer.

sbbs_t::mnemonics() now supports @-codes immediately following the tilde
(e.g. ~@Yes@) to use the first character of a dynamically-replaced
(e.g. localized/translated) text string as a command key.
Fixed issue in sbbs_t::mnemonics if multiple @-codes were specified in the
string, but no space characters (just noticed this bug while reviewing).

Created: sbbs_t::expand_atcodes() - used by sbbs_t::mnemonics(), exposed in
JS as bbs.expand_atcodes().

bbs.text and system.text now have properties: each text string ID is the
property name and the text index number (1-based) is the property value -
enabling fast text string lookup without load/require text.js

Constified sbbs_t::atcode() and attrstr() - not too painful

Deprecated YNQP text.dat string in favor of (the first character of)
  "Yes" and "No" text strings and new strings: "Quit", and "PasswordChar"

Other text.dat changes: ListKey->List, AllKey->Unused853
More new text.dat strings: Which, Next, Previous, Language, LANG
Deprecate the "AllKey" text string
Create/use sbbs_t::all_key() - first character of "All" text string

New JS console properties that present common (possibly localized) command
keys: yes_key, no_key, quit_key, all_key, list_key, next_key, prev_key

This could use more cleanup (e.g. instances of "MSGERR:") and in the summary
report there are still mentions of "message" after scanning a file base.

for those that want to use cryptic numbers rather than human-readable names.

There are other ways to generate forced-upper case expanded @-codes, if that's
what you want.

Fewer duplicates in text.dat make localization, translation to other languages
easier.