Lists Home |
Date Index |
- From: Peter Murray-Rust <firstname.lastname@example.org>
- To: email@example.com
- Date: Fri, 24 Apr 1998 16:43:18
At 09:33 24/04/98 -0400, Siping Liu wrote:
>I posted this question yestoday and yet to get any reply. Here it goes again.
>you know the answer please help.
Reposting questions to XML-DEV isn't going to help get answers quickly, I
am afraid, and will annoy some people who might otherwise have replied.
[Despite the rapidity of Web-based processes, a day isn't a very long time
All postings to this list are made voluntarily. People do this because
they think they can help. There are lots of reasons why they may not reply
to your question, such as:
- they don't know the answer (that's why I haven't replied, and I suspect
most others haven't).
- they are not sure how to answer it (this may also be a factor)
- their boss doesn't approve of them spending time on the Internet.
- their partner/kids don't approve either.
- they haven't had any sleep for the last 2 days...
If it helps you, people often don't reply to my questions either. This is
probably because the Qs are too simple; been suggested/asked before; the Qs
are too profound for the XML experts; I don't make them simple to
understand; they think I'm crazy, etc. and they have
bosses/kids/partners/cash_flow_crises, etc. You have to learn to live with
it. Try again in 2 months?
The percentage of postings on XML-DEV which receive useful replies is very
high and we are all very grateful to everyone who takes time to reply. It
often costs them time/social_life, etc.
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)