27 Mar 20 10:45, you wrote to me:

 ml>> what you posted above is what i'm calling 4.5D since it is a mixture of
4D
 ml>> and 5D...

 Oli>> What you call 4.5D is what I know as 5D from the 1990s. IIRC Squish and
 Oli>> Binkleyterm use the hex extension for all outbound dirs that are not the
 Oli>> default outbound.

 ml> even when using full 5D? i think you're remembering 3D/4D in which all BSO
 ml> directories have the same base name...

I'm pretty sure I used 5D with Squish and BinkleyTerm in the last millennium,
because I already knew how it works when I installed Squish last year. I also
was surprised that many tossers (hpt, fmail, ...) still don't support 5D
outbound.

 Oli>> The example I posted was a quote from FTS-5005
 Oli>> http://ftsc.org/docs/fts-5005.003

 ml> it is possible the document is wrong or doesn't explain things clearly...

I think it's very clearly explained and I also doubt the document is wrong.

 Oli>> Which tossers do support 5D.nohex binkD style outbound?

 ml> i'm not sure, at this point, and don't have the means to test like i used
to
 ml> have... i just know that the main difference between 3D/4D and 5D is the
 ml> outbounds for other FTNs have different base names from the main FTN
domain...
 ml> in that case, they do properly have the zone HEX on the additional
directories
 ml> beside the main one /for that domain/ as opposed to doing that for *all*
 ml> directories except the main outbound... again, that's my understanding
even
 ml> though there are numerous tossers used today that are doing it
differently...

This is a quote from the BinkleyTerm 2.40 DOC (from 1990):

"Note that outbound areas for domains other than your own will ALWAYS have a
zone extension."

BinkleyTerm is doing it exactly as it is documented by the FTSC.

There is a longer chapter at the end of the BinkleTerm documentation about 5D
outbounds:
http://www.retroarchive.org/cdrom/nightowl-005/001A/BEXE_240/BINK_240.DOC



--- GoldED+/LNX 1.1.5-b20180707