MSGID: 2:221/1.58@fidonet 1b3fd81d
REPLY: 1:153/7001 67560475
PID: OpenXP/5.0.58 (Win32)
CHRS: ASCII 1
TZUTC: -0500
Hello Maurice!

 MK> 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.


 MK> As for the threading codes, I am assuming you are referring to
 MK> 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.


 MK> ..but will not work if a proper MSGID doesn't exist in the
 MK> MSG one is REPLYing to.  Also quotes can exist in posts
 MK> 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)
SEEN-BY: 1/19 16/0 19/37 105/81 106/201 123/130 128/187 142/104 153/7715
SEEN-BY: 203/0 218/700 221/1 6 226/30 227/114 229/110 114 206 300
SEEN-BY: 229/317 400 426 428 664 700 705 240/5832 266/512 280/464
SEEN-BY: 280/5003 5006 282/1038 291/111 301/1 320/119 219 319 2119
SEEN-BY: 322/757 762 342/200 396/45 423/81 460/58 633/280 712/848
SEEN-BY: 902/26 5075/35
PATH: 221/1 320/219 229/426