Hello Nick!

The '> ' prefix is definitely more universal, not only for
FTN, but newsgroups and email as well. However, initials
don't bother me much if they're there or not, as I don't
usually look at them, and normally don't quote past the
first level anyways.

Personally, I like the following method of quoting..

The '> ' prefix is definitely more universal, not only for

FTN, but newsgroups and email as well. However, initials
don't bother me much if they're there or not, as I don't
usually look at them, and normally don't quote past the
first level anyways. <NB

IOW, just put a quoted block between two quotes. One at that
beginning, and one at the end of the block.

Or.. even something simpler without the initials..

The '> ' prefix is definitely more universal, not only for

FTN, but newsgroups and email as well. However, initials
don't bother me much if they're there or not, as I don't
usually look at them, and normally don't quote past the
first level anyways. <<

--
../|ug

--- OpenXP 5.0.58
* Origin: (2:221/1.58)

Hello Maurice!

Why not just ONE prefix (initials or no initials) at the
beginning..

The '> ' prefix is definitely more universal, not only for FTN, but newsgroups and email as well.

Agreed. I think it would be the best way to handle this all things considered. I will definetly adjust accordingly from here on in. As for the trailing spaces I am inclined to keep them where they exist but getting rid of them is of no real concern. If I discover something that indicates differently I'll let you know.

Why do we really need repeated initals on each line anyway?

--
../|ug

--- OpenXP 5.0.58
* Origin: (2:221/1.58)

Hey August!

Why not just ONE prefix (initials or no initials) at the
beginning..

It could.

Why do we really need repeated initals on each line anyway?

It makes it easier to distinguish a quote from the rest of the MSG.

For the record, I'd rather not quote at all but if we're going to do it then keeping true to the words quoted and having them distiguishable from the rest of the MSG is a nice touch. The above looks good from this angle.

Life is good,
Maurice

-o -o -o o-
(\ (\ (\ /)
^^ ^^ ^^ ^^
... Eþel byþ oferleof æghwylcum men.
Home is very dear to every man.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice!

Why do we really need repeated initals on each line anyway?

It makes it easier to distinguish a quote from the rest of the MSG.

Yes.. the initals help as a reminder who's voice that was.

For the record, I'd rather not quote at all but if we're going to do it then keeping true to the words quoted and having them distiguishable from the rest of the MSG is a nice touch. The above looks good from this angle.

You mean just rely on the threading codes?

--
../|ug

--- OpenXP 5.0.58
* Origin: (2:221/1.58)

Hey August!

I wasn't referring to just the quote initials when commenting on distinguishing quotes from the rest of the MSG. Instead to the entire quoting prefix whether or not there are initials, spaces, etc. within the prefix. According to http://ftsc.org/docs/fsc-0032.001;

Newly quoted text should be preceeded by the a single space,
a greater than symbol ('>') and another space.

Other than tacking on the prefix ' > ' the above quote is an exact replica of the original text. This differs slightly from what Nick last posted where the prefix omitted the leading space, '> '. Either way works for me but am noting that mutt (email agent with vim as default editor) uses the '> ' quote prefix which appears to be the norm in traditional email applications.

As for the threading codes, I am assuming you are referring to MSGID/REPLY, which in the case of this REPLY, will work but will not work if a proper MSGID doesn't exist in the MSG one is REPLYing to. Also quotes can exist in posts that aren't a REPLY.

Life is good,
Maurice

o- -o -o -o
/) (\ (\ (\
^^ ^^ ^^ ^^
... Ðonne se heretoga wacað þonne bið eall se here swiðe gehindred.
When the general weakens, the whole army is greatly hindered.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice!

I wasn't referring to just the quote initials when commenting on distinguishing quotes from the rest of the MSG. Instead to the entire quoting prefix whether or not there are initials, spaces, etc. within the prefix. According to http://ftsc.org/docs/fsc-0032.001;

The problem with that ftsc proposal is that it doesn't define
what a "line" is. Is it like I just used it in my above quote?
Or.. is "line" 30-40 characaters, or something?

Newly quoted text should be preceeded by the a single space, a greater than symbol ('>') and another space.

Well.. my quoted parts above follow that rule.

As for the threading codes, I am assuming you are referring to MSGID/REPLY, which in the case of this REPLY, will work..

Yes.. that is what I meant. The official terms escaped me at
the time of writing.

..but will not work if a proper MSGID doesn't exist in the
MSG one is REPLYing to. Also quotes can exist in posts
that aren't a REPLY.

Ah.. then some intelligence could be built into the quoting
system to prompt for quoting or not. If a MSGID is present in
the original, then offer quoting as an option. If no MSGID is
present, then proceed with a quoting method.

I may be mistaken but I believe the QWK messages do not have
MSGIDs produced at the source.
--
../|ug

--- OpenXP 5.0.58
* Origin: (2:221/1.58)

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)