Date:	Thu, 6 Feb 2003 13:30:23 +0200 (EET)
From:	Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
Sender:	peuha AT sirppi DOT helsinki DOT fi
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Add @tindex for types in docs [PATCH]
In-Reply-To:	<2561-Wed05Feb2003174006+0200-eliz@is.elta.co.il>
Message-ID:	<Pine.OSF.4.51.0302061313110.25275@sirppi.helsinki.fi>
References:	<E18fmrW-0000gG-00 AT phekda DOT freeserve DOT co DOT uk>
	<Pine DOT OSF DOT 4 DOT 51 DOT 0302041153300 DOT 10610 AT sirppi DOT helsinki DOT fi>
	<3E3FDCB5 DOT D2875A7E AT phekda DOT freeserve DOT co DOT uk> <Pine DOT OSF DOT 4 DOT 51 DOT 0302051322280 DOT 1814 AT sirppi DOT helsinki DOT fi>
	<2561-Wed05Feb2003174006+0200-eliz AT is DOT elta DOT co DOT il>
MIME-Version:	1.0
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

On Wed, 5 Feb 2003, Eli Zaretskii wrote:

> Sorry, I don't understand: what does @mkdoc refer to here?  You need
> to realize that in the Texinfo context, the `@' character is loaded
> with a meaning...

I realize that, but the .txh files are only read by mkdoc, and mkdoc
already uses @node with syntax that is far from that of Texinfo, and
@portability and @port-note which have no Texinfo equivalents.  So using
another @-construct to tell mkdoc how to handle the node wouldn't be any
more problematic with Texinfo.

-- 
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/

- Raw text -