REPLY: 2:221/1.58@fidonet 1b3fd81d
MSGID: 1:153/7001 6757b90d
CHRS: UTF-8 4
Hey August!

> The problem with that ftsc proposal is that it doesn't define
> what a "line" is.

Back then the default terminal was 80 characters wide.  That was true for GUI
terminals as well.  Thus when that document was written I believe everyone and
their dog was assuming a line was 79 characters with the null character in the
80th position.  I seem to recall teletype machines being 72 characters, which
could explain why some strings - subject() being a good example - are limited
to 72 (71 plus null) characters.  As far as I am personally concerned, I vote
for unlimited (unbounded) line lengths which is covered in http:
/ftsc.org/docs/fts-0001.016.

> I may be mistaken but I believe the QWK messages do not have
> MSGIDs produced at the source.

QWK messages aren't FTN MSGs.  As we speak, my vim can do modified MSG format
(packed MSG without the binary header garbage) but not QWK, or Bluewave.  It
does email along with mutt's assistance.

Life is good,
Maurice

-o   -o    o-  -o
 (\   (\  /)    (\
 ^^   ^^  ^^    ^^
... Lot sceal mid lyswe, list mid gedefum.
    Cunning goes with corruption, craft with what is right.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
 * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
SEEN-BY: 10/0 1 103/705 105/81 106/201 124/5016 128/187 134/100 153/135
SEEN-BY: 153/143 148 151 757 7001 7715 154/10 30 203/0 214/22 218/0
SEEN-BY: 218/1 601 700 840 850 860 880 940 221/0 6 226/30 227/114
SEEN-BY: 229/110 114 206 300 317 400 426 428 664 700 705 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 282/1038 291/111 292/8125 301/1
SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 460/58 467/888
SEEN-BY: 633/280 712/848 770/1 902/26 3634/12 5020/400 5075/35
PATH: 153/7001 757 280/464 103/705 218/700 229/426