-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message <[EMAIL PROTECTED]">mid:[EMAIL PROTECTED]>, Joseph N. [JN] wrote: ... JN> Okay, Okay, except:
:-)) Are we being too persistent? JN> I think it is bad form, both in terms of style and meaning, to JN> have a signature *below* quotations when those quotes fall at the JN> bottom and are not interspersed with fresh comments. I agree here. If you quote your material at the end, then I tend to read the quotation only if I'm really forced to. Even if I don't understand the context, I'll just move on unless it's really important. The signature just after your input does tell me that there's no need to look any further for text you typed and that all that's left is just quoted material. On usenet some used to mercifully do this. Nothing is worse than scrolling to eternity to find only a signature at the end. However, the whole thing is just bad form except for the most special of circumstances. One such situation is tech support. Complete quotations are important to the tech staff who can easily peruse the history and have on record the whole tech support incident in a single message, i.e., the last message sent or received. That's the only time that I do quote the entire original message. I'm sure there are other similar circumstances but a discussion list is, emphatically, not one of them. :-) JN> So, if the newest message looked like: JN> <quote> JN> <response> JN> <quote> JN> <response> JN> then it would make sense to have a sig at the bottom of the whole JN> thing. But if the message looks like: JN> <response> JN> ________________________________________________________ JN> Current Ver: 1.60q You quoted the list footers. Your method got you there. A nested type reply would prevent this. It would immediately be tacky to start your response below the list footers. - -- -=Allie C Martin=- List Moderator | TB! v1.60q | Windows XP Pro PGP/GPG Public Key: mailto:[EMAIL PROTECTED]?Subject=2B0717E2 _________________________________________________________________ -----BEGIN PGP SIGNATURE----- iD8DBQE9AhemV8nrYCsHF+IRAsJDAKC71hXczDzffBItFPVc1d0gsmz3KACeIA7c R6N/64O/uXEBaL9jxcObqNk= =luV/ -----END PGP SIGNATURE----- ________________________________________________________ Current Ver: 1.60q FAQ : http://faq.thebat.dutaint.com Unsubscribe: mailto:[EMAIL PROTECTED] Archives : http://tbudl.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] TBTech List: mailto:[EMAIL PROTECTED] Bug Reports: https://bt.ritlabs.com
