From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16750 invoked by alias); 7 Feb 2007 18:37:05 -0000 Received: (qmail 16739 invoked by uid 22791); 7 Feb 2007 18:37:05 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 07 Feb 2007 18:37:00 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1HErf6-0003t0-Sn; Wed, 07 Feb 2007 13:36:56 -0500 Date: Wed, 07 Feb 2007 18:37:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: XML XInclude support Message-ID: <20070207183656.GA14189@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , gdb-patches@sourceware.org References: <20070129213229.GA17422@nevyn.them.org> <20070206130330.GB31162@nevyn.them.org> <20070129213229.GA17422@nevyn.them.org> <20070206124910.GA31162@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-02/txt/msg00061.txt.bz2 On Wed, Feb 07, 2007 at 08:15:59PM +0200, Eli Zaretskii wrote: > "d:" is wrong because when you use it to construct a file name, you > will get "d:/bar", which is generally not in the same directory as > "d:foo". > > What you need is to produce "d:." from "d:foo", not "d:". Thank you for explaining! I've added this, and some notes so that I can remember why. On Wed, Feb 07, 2007 at 08:20:13PM +0200, Eli Zaretskii wrote: > > 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 > @end ifnotinfo Thanks - I'll use that. > 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? For this case, I've added xi:include too, since that's reasonable with or without the brackets. But in general, no, I wouldn't. Especially not since "reg" and "architecture" are very ambiguous index entries, but "" and "" are quite clear. So I didn't add a matching @cindex reg. -- Daniel Jacobowitz CodeSourcery