469,648 Members | 1,564 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,648 developers. It's quick & easy.

FAQ Topic - What do I have to do before posting to clj?

-----------------------------------------------------------------------
FAQ Topic - What do I have to do before posting to clj?
-----------------------------------------------------------------------

Before posting to clj, you should thoroughly read this document.
You should also check the resources mentioned in section 3 and
the Quick Answers in section 4. Read FYI28/RFC1855

http://www.ietf.org/rfc/rfc1855.txt

,on Usenet and

http://www.jibbering.com/faq/faq_notes/clj_posts.html

Also you should read all appropriate posts to the clj newsgroup
for several days. Most questions come up at least once every
other day and people can get annoyed of answering them
repeatedly.

Please state your question as clearly and concisely as possible,
as this will make it far easier for the other readers of the
group to understand your problems and suggest possible solutions.
Use the Subject: of your post to indicate the type of problem
you have, but include the question in the body as well. 'Help!'
or 'I hate Netscape!' are not nearly as useful to contributors
who do not read every post as 'parseInt("09")!=9'.

Has the same question already been posted that day? - if it has
wait to see if the answers to that solve your problem.

Include the script you have been working on (or URL) - indicate
the problem spots and/or previous attempts. Try to limit the
length of your post by removing extraneous page elements, but
avoid removing script unless you are sure it is not an issue. If
the script is long though, please do not post the full script
and just provide a link. As a guide more than 500 lines for a
post is not normally a good idea in any circumstances. A
mention of which platforms and browsers are used or are giving
problems is also necessary.

Post in plain-text only. Do not post using HTML. If you have to
include your script, paste it in to your post in plain-text. Do
not uuencode it or attach it using MIME. There is good reason for
this request: many newsreaders do not read HTML or MIME, and this
limits the number of people who could help you. Test posts belong
in test newsgroups (they have "test" in their names).

When replying to a message on the group quote the minimum of the
preceding messages that is sufficient to provide context for
the reply but trim the remainder, and add your comments below the
pertinent section of quoted material, as per FYI28/RFC1855 (never
top post).

If posting through groups.google.com don't use the "Reply" link
at the bottom of the article, instead use "Show Options" at the
top of the article and than click the "Reply" option exposed
there. This automatically includes the quote of the preceding
message to be edited down as described above.

Don't ask, or at least expect, to be emailed individually. Some
individuals run scams for the purpose of collecting active email
addresses and many won't risk being victimized. If you have
circumstances that won't allow you to read clj for the
follow-up, explain what they are and ask to be CC'ed a copy. You
also might try

http://groups.google.com/

to read replies.

Don't expect to be able to e-mail contributors to the group
privately. E-mail addresses are often obscured, fictional or
unmonitored span sinks (this is an increasingly normal (and
even unofficially recommended) practice as open e-mail
addresses in news articles will be both the target of spam
and used as fake sender's addresses in spam to third parties).

Don't take flames too seriously, and don't start a thread
complaining about rude or flippant responses. There is already
enough noise in clj. Keep a sense of humour while posting and
reading and everything will be a lot more enjoyable.

Remember that it is _not_ the _job_ of posters
here to help you. The majority of regular posters here do so
_voluntarily_ in their free time. They have good days
and bad days just like everyone else.

clj is a technical group: the posting of job adverts and
commercial adverts are not welcome. Job postings should go to
an appropriate regional jobs group. Announcements of products
of particular relevance to javascript are welcome, but not
more often than once per major release, and then post a short
link to the product's webpage.
===
Postings such as this are automatically sent once a day. Their
goal is to answer repeated questions, and to offer the content to
the community for continuous evaluation/improvement. The complete
comp.lang.javascript FAQ is at http://www.jibbering.com/faq/.
The FAQ workers are a group of volunteers.

Nov 26 '06 #1
3 1577
FAQ server wrote on 27 nov 2006 in comp.lang.javascript:
-----------------------------------------------------------------------
FAQ Topic - What do I have to do before posting to clj?
-----------------------------------------------------------------------

Before posting to clj, you should thoroughly read this document.
You should also check the resources mentioned in section 3 and
the Quick Answers in section 4. Read FYI28/RFC1855

http://www.ietf.org/rfc/rfc1855.txt

,on Usenet and
I object to the comma!
>
http://www.jibbering.com/faq/faq_notes/clj_posts.html


--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)
Nov 27 '06 #2
Evertjan. said the following on 11/27/2006 3:04 AM:
FAQ server wrote on 27 nov 2006 in comp.lang.javascript:
>-----------------------------------------------------------------------
FAQ Topic - What do I have to do before posting to clj?
-----------------------------------------------------------------------

Before posting to clj, you should thoroughly read this document.
You should also check the resources mentioned in section 3 and
the Quick Answers in section 4. Read FYI28/RFC1855

http://www.ietf.org/rfc/rfc1855.txt

,on Usenet and

I object to the comma!
It is removed from my local index.xml and will get removed from the
Draft FAQ next upload.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 27 '06 #3
In comp.lang.javascript message
<Xn********************@194.109.133.242>, Mon, 27 Nov 2006 08:04:00,
Evertjan. <ex**************@interxnl.netwrote:
>FAQ server wrote on 27 nov 2006 in comp.lang.javascript:
>-----------------------------------------------------------------------
FAQ Topic - What do I have to do before posting to clj?
-----------------------------------------------------------------------

Before posting to clj, you should thoroughly read this document.
You should also check the resources mentioned in section 3 and
the Quick Answers in section 4. Read FYI28/RFC1855

http://www.ietf.org/rfc/rfc1855.txt

,on Usenet and

I object to the comma!

Further "literary" errors can readily be found, by careful inspection or
by Word, AISB.

That section, including its Subject, needs totally re-planning and
re-writing, including the provision of paragraph numbers.

If the average user's default font is like mine, it would be well to
minimise use of colons & semicolons in plain text using that font.

"Don't" should not start a paragraph. I see no grammatical objection,
bur it is semantically oppressive. In each of the three cases where it
is currently present, exchanging the first and second sentences would be
an immediate improvement - though not necessarily best.

One should be positive - for example, compare -

(A) Please do not post copyrighted material to clj without
permission from the copyright holder.

(B) Copyright material should be posted to News only with the
permission of the copyright holder.

"Don't expect to be able to e-mail contributors to the group privately.
E-mail addresses are often obscured, fictional or unmonitored spam sinks
(this is an increasingly normal (and even unofficially recommended)
practice as open e-mail addresses in news articles will be both the
target of spam and used as fake sender's addresses in spam to third
parties)." --- it's not our FAQ's job to explain munging --->

"False E-mail addresses are often given, and contributors may not want
E-mail interaction, so do not presume that you may E-mail contributors."

--
(c) John Stockton, Surrey, UK. REPLYyyww merlyn demon co uk Turnpike 6.05.
Web <URL:http://www.uwasa.fi/~ts/http/tsfaq.html-Timo Salmi: Usenet Q&A.
Web <URL:http://www.merlyn.demon.co.uk/news-use.htm: about usage of News.
No Encoding. Quotes precede replies. Snip well. Write clearly. Mail no News.
Nov 27 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

18 posts views Thread by Ben Hanson | last post: by
33 posts views Thread by Chris Croughton | last post: by
1 post views Thread by Oleg Subachev | last post: by
11 posts views Thread by Harris Kosmidhs | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.