From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6712 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: suggestion Date: Mon, 28 Jan 2002 13:01:20 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <5.1.0.14.1.20020128125638.02af7e60@server-1> References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Trace: main.gmane.org 1035397227 13051 80.91.224.250 (23 Oct 2002 18:20:27 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:20:27 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Patrick Gundlach In-Reply-To: <200201281059.g0SAxRf26692@sol.cs.uni-dortmund.de> Xref: main.gmane.org gmane.comp.tex.context:6712 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6712 At 11:59 AM 1/28/2002 +0100, Patrick Gundlach wrote: >More important is to "rate" the questions: > >1) is it a question to wich the answer can be found in the >manual? Then there is already a documentation for it and we do >not need to answer it again. > >2) is it a question that has not yet been documented? Say for >example "how can I draw a line below the headline?". (I actually >do not know if this is in the manual). In this case, we (Hans :-> >) should see this as an opportunity to add a few lines to the >manual, so the next time this questions will not be asked again. > >3) a questions that is related to the installation. For example >the texhash or mktexlsr thing. Or the cont-sys.ori/cont-sys.tex >stuff. I think these are worth being documented in some extra >document. or some flow chart or if-then thing; people tend to oversee such things when reading a manual >4) bug reports. We do not need to collect them, since one hour >later 96% of them are already fixed. Just search the archive if >you have some trouble. -) >5) Questions regarding fonts/encodings. Yuck. I have no clue what to do >with them. There is really something that has to be done. I know >that there is are docs. But there are a many questions on the >list concerning this subject. this is also related to "if it can be done then people will use it" or if you see otehr users use it ... ; this is therefore also a combined user effort: providing examples >6) request for improvements. They are probably documented in >Hans' privat todo list... I there a need to collect them? I >think yes. right, i wonder if we can use bugzilla for this (tobias is looking into that for (real big) bugs) >7) Questions like "How can this feature xyz (just think of gb's >indefinate long page that got cut off after each chapter) be >achieved? These questions are often very esoteric. But imho they >are worth being collected. right, which makes me wonder why gb is so silent, he must have run out of feature requests >So what is my conclusion? Ignore some questions, improve the >documentation where necessary, collect some stuff for an extra >doc. We do not need an faq. not a faq in the traditional sense; we may need a way to organize examples made by users (based on q/a's) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- fall-back web server: www.pragma-pod.nl -------------------------------------------------------------------------