This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: XML XInclude support
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 07 Feb 2007 20:20:13 +0200
- Subject: Re: XML XInclude support
- References: <20070129213229.GA17422@nevyn.them.org> <usldo1jdf.fsf@gnu.org> <20070206130330.GB31162@nevyn.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Tue, 6 Feb 2007 08:03:30 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org
>
> I wanted to index this as:
>
> @subsection Inclusion
> +@cindex target descriptions, inclusion
> +@cindex XInclude
> +@cindex <xi:include>
>
> That doesn't work in info, because the info browser tries to interpret
> the colon.
Yes, colons shouldn't appear in index entries (see the Texinfo
manual).
> But the colon is a syntactic element here, and this is what
> I would look for. Plus it works in the PDF, or in print. What do you
> think - should I leave the somewhat broken @cindex, since it's more
> useful than not?
I think you can condition it on the output format, like so:
@ifnotinfo
@cindex <xi:include>
@end ifnotinfo
Btw, isn't it better to use "@cindex xi:include", without the
brackets? If I were looking for this, I'd probably omitted the
brackets; wouldn't you?