From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: XML XInclude support
Date: Wed, 07 Feb 2007 18:37:00 -0000 [thread overview]
Message-ID: <20070207183656.GA14189@nevyn.them.org> (raw)
In-Reply-To: <umz3pu8wy.fsf@gnu.org> <uodo5u940.fsf@gnu.org>
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 <xi:include>
> @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 "<reg>" and "<architecture>" are quite clear. So I didn't
add a matching @cindex reg.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-07 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 21:32 Daniel Jacobowitz
2007-01-31 18:33 ` Daniel Jacobowitz
2007-02-02 18:53 ` Eli Zaretskii
2007-02-06 12:49 ` Daniel Jacobowitz
2007-02-07 18:16 ` Eli Zaretskii
2007-02-07 18:37 ` Daniel Jacobowitz [this message]
2007-02-07 18:45 ` Daniel Jacobowitz
2007-02-07 22:49 ` Daniel Jacobowitz
2007-02-08 13:06 ` Mark Kettenis
2007-02-08 13:14 ` Daniel Jacobowitz
2007-02-08 16:15 ` Mark Kettenis
2007-02-08 13:57 ` Daniel Jacobowitz
2007-02-06 13:03 ` Daniel Jacobowitz
2007-02-07 18:20 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070207183656.GA14189@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox