Hello Mark,
> However, expecting TB to ignore cut marks would be asking the
> developers to violate RFC-2646 in much the same way that Microsoft's
> developers did with OE.
I may have missed it but I haven't seen where RFC-2646 says that cut
marks and text below have to be ignored when quoting. All I have seen (I
browsed quite quickly over the full text of the RFC) is:
,----- [ 4.3. Usenet Signature Convention ]
| There is a convention in Usenet news of using "-- " as the separator
| line between the body and the signature of a message. When generating a
| Format=Flowed message containing a Usenet-style separator before the
| signature, the separator line is sent as-is. This is a special case; an
| (optionally quoted) line consisting of DASH DASH SP is not considered
| flowed.
`-----
All it says is that the separator line is sent as is, with the space at
the end. And it also says "optionally quoted". Which, to me, means that
I should be able to quote it if I wish.
On the other hand, it seems that item '4.5.- Quoting' establishes the
"standard" of the ">" prefix for quoted text, and it says:
,----- [ ]
| ... the canonical quote indicator (or quote mark) is one or more close
| angle bracket (">") characters. Lines which start with the quote
| indicator are considered quoted. The number of ">" characters at the
| start of the line specifies the quote depth.
`-----
Great! Why does TB allow to include initials and even full names before
the ">" quote prefix? Aren't the developers then _violating_ the same
RFC? Also, if TB allows me to change the quote prefix to any character I
want by using the %QUOTESTYLE macro, are they violating the RFC? No, I
don't think so.
--
Best regards,
Miguel A. Urech (El Escorial - Spain)
Using The Bat! v2.01.3
Winamp OFF:
________________________________________________
Current version is 2.01.3 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
