TIP: Click on subject to list as thread! ANSI
echo: tuxpower
to: Maurice Kinal
from: August Abolins
date: 2024-12-08 18:32:00
subject: quoting..

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)

SOURCE: echomail via QWK@pharcyde.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.