... more aligned with a sub-board's internal code help text.

This is an experimental feature that's been in the code for quite a while without any supporting help/docs (there was the original commit message, I'm sure). I'm not sure how much value this feature is without providing automatic access to the *files* within the sub-directories, but there you have it.

Per FMail.txt:
Area name
          This is the name of the conference. It can be up to 50
          characters long. This name is often referred to as the
          area tag.

I did not locate a FidoNet spec to contradict that and support a 35 character maximum area tag length. I think Mystic also has a 50 character area tag limit. So 50 character area tags are fine I guess.

So up to 50 characters are now supported in SBBSecho and SCFG for area tags (for message and file echoes). The exception is the (new to 3.19) optional area tag stored in msgs.cnf/file.cnf is limited to 40 characters due to reserved space limitations. If you need a tag stored per sub (most sysops do not) and it needs to be longer than 40 chars, use the newsgroup name instead (limited to 63 chars).

Changed at the request of Keyop via IRC.

According to  Lupine Furmen (FURFOL):
It says in the help that the field is used for both the Newsgroup name AND the
Fido Echo-tag.

These really should be 2 different fields.

Now, the echo/area tag is usually configured in the area file (areas.bbs) and so does not need to match *any* string configured in SCFG. But since an area file *can* be generated from SCFG (Export Areas option) and its possible to use SBBSecho withOUT an area file at all, then it's possible someone would like to have their FidoNet-style area tags configured different from any other strings related to a sub-board (e.g. newsgroup name) - why? I'm not clear, but there it is: another string that  a sysop can set (or not).

Since I'd recently added an area tag field per directory for use by hatchit.js, this does create some logical symmetry. And there were enough free bytes per-sub in the msgs.cnf, so why not.

This won't impact Synchronet as it has a separate signal handling
thread, but we still need to behave properly for processes that
don't.  I'm also saying that ENOMEM does not indicate a disconnection,
though it may be better to pretend it was disconnected...

... as pointed out by Nelgin. You can toggle more than one sub-board/directory's "template" option to "Yes". But only the first such sub/dir is actually the template, so only indicate the first such sub with a splat ('*').

Let UIFC do the truncation as necessary to fit windows/forms, when applicable.
Thanks for jc and nelgin for pointing this out via IRC.

when there is no "template directory" selected/configured.

(not delete) from the end of the sorted list of files (normally, 0).

in load_cfg.c for displaying the path. If you previously had a "parent dir"
configured for a library but did *not* have one or more "Transfer File Paths"
configured for directories within that library, the default location of your
files has now moved! Either clear-out the "Parent Directory" setting or move
your files where SBBS will now expect them to be. Sorry about that.

use mixed or upper-case for their Transfer File Paths.

directory's file transfer path, the array index usage here could cause a
crash or just garbage to be displayed.

Path" or "Directory File Path".

internal code suffixes or grp/lib internal code prefixes.
More strcpy->SAFECOPY and sprintf -> SAFEPRINTF replacements.
More use of uifcYesNoOpts.

Wrap all read_*_cfg() and write_*_cfg() calls with simple functions that
display popup messages that the Reading or Writing is being performed.
There was already copy/pasta everywhere for the Reading ... cnf files, but
nothing for writing.

"short name" (e.g. derived from the "AREA tag" from FILEGATE.ZXX) is the same
as a pre-existing dir, just over-write that dir - don't create a new one.

conditions) - e.g. if a malloc or realloc failed, then some other allocated
memory would be leaked.

auto-generated file transfer path (no transfer path specified), in
square brackets.

index (the sub/dir constructor wasn't setting the initial subnum/dirnum
property).

- Must set the dirnum property so the initial sort doesn't re-order the
  imported dirs (changing them from the list file order)
- Make sure all the required strings have some text even if the import file is
  in the wrong format or corrupt

* Include the Directory Index in the Advanced Options menu, for debugging
* Allow the Directory settings menu to expand beyond 60 chars wide
* Display the implied/auto-generated Transfer File Path

(change for *nix).

brackets to make it more clear that it's an implied (not real) value.

  Automatically detect child sub-directories and make them available as virtual
  directories for users to download from - only useful via FTP currently.
* Implemented Sorting options for Message Groups and File Libraries:
  Sub-boards within groups and directories within library can now be
  automatically sorted based on the sysop's chosen sort field (long name, short
  name, or internal code)
  - Required that sub-boards are now stored/saved in msgs.cnf based on groups
  - Required QWKnet hub sub-board reference dynamic renumbering
* Implemented "Template" toggle option for sub-boards and file directories:
  A sub-board or directory marked as "template" will be used for newly created
  (or imported) subs/dirs for that group/lib. Clone Options via SCFG will now
  use the "template" item as the source of the cloned settings, if available.
* New "Impport Conferences..." option for QWKnet hubs to import subs (or just
  conference numbers) from a QWK control.dat file.
* New command-line options:
  -import=<filename> - import a message Area List file
  -g<name> - specify a target message group for imported area list
* All paste operations are now "Paste-Insert" (not over-write), as sysops would
  expect.
* Unified several of the duplicate (or nearly duplicate) help text strings.
* Over-hauled new group/sub/library/directory creation logic
* Display number of sub-boards in groups and directories in libraries
* Fixed a lot of help text typos and conversion issues

and when pasted, all the child subs/dirs/xtrns will be pasted with it.
If however, you cut a group/lib/section and then exit SCFG, you'll lose all the
children subs/dir/xtrns that were on the "clipboard" along with the parent.

Copy - F5, Ctrl-C, Ctrl-Insert
Cut - Shift-Del, Ctrl-X
Paste Over - F6, Ctrl-V
Paste Insert - Shift-Insert

(currently only via FTP) - simiilar to the global FTP option: DIR_FILES.
I intend to extend this option to the terminal server as well.

file area listings: Since these file don't contain paths, the paths are blank
(which is normal and expected), but a recent change treated directories with
the same path (even if blank) as the same directory and over-write. Now, only
non-blank paths are compared to see if the directory is a duplicate and should
be overwritten.

Also changed references to FILEBONE.NA to FILEGATE.ZXX since that appears to
be the currently distributed filename. Update help text to reflect this too.

Also display a popup error if attempting to import a non-existant filename.

1. Randomize the last 3 characters of the internal code to generate a unique
   internal code.
2. Attempt to skip sub-directory names when generating long/short names from
   imported path, if no sub-dirs are in the path, then just right-justify the
   truncated path - trying to generate meaninful long/short names from long
   paths.
3. Do not allow duplicate paths to be imported into the same library.
4. Skip (do not import) directory entries that are > 63 chars in length.
5. Stop importing if/when total dirs >= MAX_DIRS (65534).

1. added option to import empty sub-directories (previously empty subdirs were
    always ignored).
2. attempt to generate a unique internal code when the auto-generated internal
    code (based on the characters in path) is not unique.
3. display "Scannnig Directories..." popup since this can take a while
    (especially on network drives and especially recurisvely).

Note: if you're importing lots of deeply nested subdirs, it's likely that a
unique internal code can't be generated (from the path) for all subdirs.
A randomly generated internal code might be an option if this is really
a problem for any sysops.

Also updated the brace style of this .c file, finally.

While "fixing" compiler warnings, a bug was introduced that would cause an
infinite loop while inserting File Libraries. This is possibly the same
problem reported by KK4QBN.

Done.

systems to find them.

code is generated from the sysop-supplied name, don't truncate at the first
space character (concatenate words instead) - making much nicer internal codes
by default (e.g. "FAT FISH" becomes "FATFISH" instead of "FAT").