Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<0e4b01c1453a$a788baa0$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Charles Wilson" <cwilson AT ece DOT gatech DOT edu>,
	"David Starks-Browning" <starksb AT ebi DOT ac DOT uk>
Cc:	<cygwin AT cygwin DOT com>
References:	<u1xt7fqf DOT fsf AT blue DOT sea DOT net> <3BAE6B03 DOT 6080801 AT ece DOT gatech DOT edu> <4235-Mon24Sep2001101512+0100-starksb AT ebi DOT ac DOT uk> <3BAF5B9B DOT 1030408 AT ece DOT gatech DOT edu>
Subject:	Re: FAQ URLs (Was: Where are instructions for contributing package to cygwin?)
Date:	Tue, 25 Sep 2001 06:51:15 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MIMEOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	24 Sep 2001 20:59:09.0457 (UTC) FILETIME=[C17B8810:01C1453B]

With docbook, you can choose to have the created file nodes named after
the chapter/section (actually the title of the chunk element). If you
assign id's to the linked to nodes then the # references can become
static as well IIRC. (ie http://www.cygwin.com/faq/faq#using_ntsec.)

Rob

----- Original Message -----
From: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
To: "David Starks-Browning" <starksb AT ebi DOT ac DOT uk>
Cc: <cygwin AT cygwin DOT com>
Sent: Tuesday, September 25, 2001 2:13 AM
Subject: Re: FAQ URLs (Was: Where are instructions for contributing
package to cygwin?)


> David Starks-Browning wrote:
>
> > On Sunday 23 Sep 01, Charles Wilson writes:
> >
> >>4. As far as the mechanics of getting a package prepared and
uploaded,
> >>that's kinda in flux right now; partly because we're in the
processes of
> >>vetting the new setup...but for some pointers, take a look here:
> >>
> >>http://www.cygwin.com/faq/faq.html#SEC83
> >>
> >
> > Until such time as I can figure out how to avoid it, it's better not
> > to refer to FAQ entries this way.  These change over time as the FAQ
> > gets updated.  It's perhaps a bit more work, but instead say
something
> > like:
> >
> > FAQ entry "How do I contribute a package?"
> >
> > It has the added benefit of forcing people to read the TOC, which
> > might prove educational itself.
>
>
> Will do.  BTW, many FAQs address this issue as follows:
>
> 1) number questions in small groups -- e.g "FAQ_2_1_4", "FAQ_2_1_5",
> etc, according to the TOC structure.  (e.g. Chapter 2, Section 1, FAQ
4
> or 5). Don't number all FAQs sequentially. (e.g. 001 to 094 spanning 7
> chapters and 21 sections)
>
> 2) When adding new FAQs, always add at the end of a section
>
> 3) When adding new sections, always insert at the end of a chapter
>
> 4) New chapters always go at the end of the document
>
> 5) When removing a FAQ, leave a placeholder:
>
> FAQ 2.1.2:
>    This entry intentionally left blank.
>
> That way, old FAQ references never change.  The sed tutorial/faq works
> this way.
>
> --Chuck
>
>
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -