From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-47539-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 8973 invoked by alias); 7 Feb 2007 18:20:27 -0000
Received: (qmail 8964 invoked by uid 22791); 7 Feb 2007 18:20:26 -0000
X-Spam-Check-By: sourceware.org
Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (213.8.233.22)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 07 Feb 2007 18:20:18 +0000
Received: from HOME-C4E4A596F7 (IGLD-80-230-70-73.inter.net.il [80.230.70.73]) 	by nitzan.inter.net.il (MOS 3.7.3a-GA) 	with ESMTP id FZS93014 (AUTH halo1); 	Wed, 7 Feb 2007 20:20:09 +0200 (IST)
Date: Wed, 07 Feb 2007 18:20:00 -0000
Message-Id: <umz3pu8wy.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
CC: gdb-patches@sourceware.org
In-reply-to: <20070206130330.GB31162@nevyn.them.org> (message from Daniel 	Jacobowitz on Tue, 6 Feb 2007 08:03:30 -0500)
Subject: Re: XML XInclude support
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <20070129213229.GA17422@nevyn.them.org> <usldo1jdf.fsf@gnu.org> <20070206130330.GB31162@nevyn.them.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2007-02/txt/msg00059.txt.bz2

> 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?