public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Andreas Seltenreich <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Texinfo docs/target
Date: Tue, 3 Oct 2006 17:13:24 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Patch applied. Thanks.
---------------------------------------------------------------------------
Andreas Seltenreich wrote:
> Peter Eisentraut <[email protected]> writes:
>
> > Andreas Seltenreich wrote:
> >> Now I'm wondering, if it'd be worth fixing the index and some minor
> >> encoding deficiencies (e.g. medium-length dashes end up as
> >> "[mdash]"), and adding Autoconf support in order to make it a proper
> >> target.
> >
> > We probably won't ship it with the default distribution, but I don't see
> > any harm in at least providing build support for it initially.
>
> The index seems to work with more recent versions of DB2X, and the
> apparent encoding problems turned out to be an overlook in the
> postgres.xml target.
>
> I had to run makeinfo with the --no-validate option, mostly because
> the info design doesn't allow duplicate node names. However, it
> doesn't seem to impair navigation besides addressing nodes by name,
> and since most of the duplicate names are nodes like "Changes" in the
> release notes section, I don't think it will be more of a nuisance
> than being unable to look up Pi in the index...
>
> I figured adding autoconf support for db2x/info wouldn't be very wise
> as long as the experimental postgres.xml target the new rules depend
> on doesn't have any either.
>
> Patch attached.
>
> regards,
> andreas
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
--
Bruce Momjian [email protected]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Texinfo docs/target
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox