[top posting fixed]
xm****@yahoo.c om wrote:
<snip>I am trying to hide my JavaScript source. ...
<snip>
"StanD" <St**********@m ail.forum4desig ners.com> wrote in message
news:St******** **@mail.forum4d esigners.com...
JavaScript is a client side script, ...
<snip>
Pleas do not top-post to comp.lang.javas cript. The group FAQ outlines
acceptable posting style in section 2.3 paragraph 5 and references the
applicable standard.
Your posting software appears to exhibiting faulty behaviour in its
handling of the "References " header in your postings. It has sent (split
across lines at the location of spaces to avoid uncontrolled wrapping):-
References: <4a************ **************@ posting.google. com>
<c0************ *******@news.de mon.co.uk>
<40************ *********@news. xs4all.nl>
<Ao************ ********@comcas t.com>
But:-
| RFC 1036 Standard for USENET Messages December 1987
|
|
| 2.2.5. References
|
| This field lists the Message-ID's of any messages prompting the
| submission of this message. It is required for all follow-up
| messages, and forbidden when a new subject is raised.
| Implementations should provide a follow-up command, which allows a
| user to post a follow-up message. This command should generate a
| "Subject" line which is the same as the original message, except
| that if the original subject does not begin with "Re:" or "re:", the
| four characters "Re:" are inserted before the subject. If there is
| no "References " line on the original header, the "References " line
| should contain the Message-ID of the original message (including the
| angle brackets). If the original message does have a "References "
| line, the follow-up message should have a "References " line
| containing the text of the original "References " line, a blank, and
| the Message-ID of the original message.
|
| The purpose of the "References " header is to allow messages to be
| grouped into conversations by the user interface program. This
| allows conversations within a newsgroup to be kept together, and
| potentially users might shut off entire conversations without
| unsubscribing to a newsgroup. User interfaces need not make use of
| this header, but all automatically generated follow-ups should
| generate the "References " line for the benefit of systems that do
| use it, and manually generated follow-ups (e.g., typed in well after
| the original message has been printed by the machine) should be
| encouraged to include them as well.
|
| It is permissible to not include the entire previous "References "
| line if it is too long. An attempt should be made to include a
| reasonable number of backwards references.
- would require that the References header of a message that appears,
from the quoted material and its attribution, to be intended as a
response to the OP should carry the header:-
References: <4a************ **************@ posting.google. com>
And if intended to be a response to any of the other contributors to
date would be only the References header from that "original message"
(singular) followed with a space and the message ID of that message.
While the header that you sent contains the message IDs of all of the
contributions to the thread to date and will probably give most
newsreader software the impression that it is Randy that you are
responding to (or just confuse it). It is important for newsreader
software to be able to accurately represent which messages are replying
to which other messages and they need meaningful References headers in
order to be able to do that. Hence the clearly specified format and
contents of that header and the fact that it is required in messages
that represent responses.
If you are going to post to Usenet, in addition to making yourself
familiar with the conventions of the groups that you are posting to, it
would be a very good idea to be using software that does not violate
such an important aspect of the applicable standard.
Richard.
