From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc/branch too] Texinfo problems
Date: Tue, 31 Jul 2001 10:24:00 -0000 [thread overview]
Message-ID: <20010731102425.A8177@nevyn.them.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1010731113947.1042E-100000@is>
On Tue, Jul 31, 2001 at 11:40:18AM +0300, Eli Zaretskii wrote:
>
> On Mon, 30 Jul 2001, Daniel Jacobowitz wrote:
>
> > While building Debian gdb packages, I ran into two problems. One is, I
> > think, a problem in Debian's tools rather than gdb; the line:
> >
> > @dircategory Programming & development tools.
> >
> > gets munged.
>
> How does it get munged?
Through stupid perl mistakes :) & in a regex is special, and someone
isn't quoting properly. & gets replaced by #SECTION#. It's not gdb's
fault, but Debian's.
> > I assume & is a legal character here?
>
> The Texinfo manual doesn't say anything about characters that are
> invalid in @dircategory, and I don't see anything in makeinfo's code
> which would treat & specially, except maybe under --html.
>
> > In any case, Debian happens to use Development
>
> I don't understand that: what ``Development'' did you refer to here?
As opposed to Programming & Development. By default our info tools
pick the section out of the file, but I need to override it in my hat
as Debian packager in order to put it in the right place.
In other words, none of the above is a problem with GDB.
> > install-info --quiet --section 'Programming #SECTION# development tools.'
> > 'Programming #SECTION# development tools.' /usr/share/info/gdbint.info
> > install-info: warning, ignoring confusing INFO-DIR-ENTRY in file.
> >
> > I think the patch below is correct. OK to commit, trunk and branch?
>
> Yes, thanks.
OK, committing.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2001-07-31 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 12:06 Daniel Jacobowitz
2001-07-31 1:39 ` Eli Zaretskii
2001-07-31 10:24 ` Daniel Jacobowitz [this message]
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=20010731102425.A8177@nevyn.them.org \
--to=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/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