"Far Canal" <me@privacy.net> wrote in message
news:MPG.1cc73b076f6dda3298cfaa@news.readfreenews. net...
> <Vanguard> wrote
>
>
>> Is the problem that Forte actually forcibly prepends a space
>> character
>> before the leading quote character? Or did you redefine the quoting
>> sequence to add a space before the quote character? OE won't do it
>> but
>> I thought Forte would compress the quoting to eliminate unnecessary
>> and
>> space-wasting spaces between the quote characters. So when you
>> replied
>> to a reply, the leading double indention would look like ">>" instead
>> of
>> "> >", triple indention would look like ">>>" instead of "> > >", and
>> so
>> forth. Since your prior post with double indention looks like " > >"
>> then it looks like YOU reconfigured Forte to deliberately change the
>> quote character from ">" to " >" (i.e., you change it from one
>> character
>> to a 2-character string).
>>
>>
>
> http://www.netmeister.org/news/learn2quote3.html
>
> 3.1 Which character should I use to mark the quoted text?
> Use the "Greater-Than" character (">"). This character is
> recognized as a quotationmark by almost every newsreader and is
> mentioned in the netiquette as such for technical reasons (Son-
> Of-RFC 1036 and successors).


In RFC 1036, it discusses the various headers and transfer mechanisms
but I saw nothing about how to handle inclusion of original content in a
reply (i.e., quoting).

Articles, like the one above at the link, are not standards, nor is this
one even really a synopsis of netiquette that has become a de facto
standard. The Net is rife with articles on what conventions are used
regarding quoting, like
http://members.fortunecity.com/nnqweb/nquote.html (and note question &
answer #11). Since such conventions may change over time, an NNTP
client that has been abandoned or been stagnant won't keep pace with the
changes or its code maintained to correct bugs or alter behavior to
conform. Gravity got abandoned quite awhile ago but looks like it got
picked up by enthusiasts and is now at
http://sourceforge.net/projects/mpgravity/. Did you get it from there?
They have forums (http://sourceforge.net/forum/?group_id=95245) where
you might want to ask why Gravity cannot ignore contiguous whitespace
characters before the quote character; however, there are so few posts
there that you probably won't get a response. You could post a bug
report to see what, if any, response you get from the developers. You
might also want to ask over in the alt.usenet.offline-reader and
alt.usenet.offline-reader groups.

In trying to find something that shows standardization or a
representation of a de facto standard, RFC 3676 was the closest that I
could find despite that its context is primarily for use with MIME
encoding (although there may be no MIME parts within the body of the
message since the content type and formatting can be specified globally
by headers). The fact that NNTP clients let users select which
character to use for quoting or even specify a string of characters
reflects the fact that there is no substantive standard available that
dictates exactly how quoting is always to be performed.

While there is the common netiquette regarding many Usenet conventions
(which are not themselves defined standards by a recognized authority),
Jay decided to be non-conventional. That's like some posters that
change the quote character to "|" or ":" instead of ">". While most of
would prefer to compress the quote indents to eliminate spaces, Jay (or
Forte) choose to add more space.

--
__________________________________________________ __________
** Post your replies to the newsgroup - Share with others **
For e-mail Reply: remove "DELETE", add "~VN56~" to Subject.
__________________________________________________ __________