Date: Sun, 21 Jan 2001 19:06:12 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
Message-Id: <2950-Sun21Jan2001190611+0200-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC: djgpp-workers AT delorie DOT com
In-reply-to: <3A6B08A1.D3F04FDE@phekda.freeserve.co.uk> (message from Richard
	Dawe on Sun, 21 Jan 2001 16:04:49 +0000)
Subject: Re: Describe @portability in develop.txi [Was: Re: mkdoc patch, take 2]
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000711100538 DOT 19180B-100000 AT is> <396B6BB3 DOT 49C1F993 AT phekda DOT freeserve DOT co DOT uk> <3A6B08A1 DOT D3F04FDE AT phekda DOT freeserve DOT co DOT uk>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Sun, 21 Jan 2001 16:04:49 +0000
> From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
> 
> I have written a section for src/docs/kb/develop.txi to describe the use
> of @portability and @port-note.

Thanks!

>   @item
> + Under the subheading @samp{Portability}, @samp{@@portability} should be
> + used to indicate whether a feature is specified in the ANSI C and POSIX
> + standards.  For example:

It might be better to use @acronym for ANSI and POSIX.  It's not a
requirement, though; it's up to you.  (Personally, I think @acronym
looks much better in print.)

> + @samp{@@portability} and @samp{@@port-note} are DJGPP-specific extensions
> + of texinfo (@pxref{Top, , texinfo})

This cross-reference won't work.  You need a 4-argument form of
@pxref, not a 3-argument form.  See the Texinfo manual, under @xref.

> + to build the C library documentation (@pxref{Top, , libc}). 

Same here.