Texinfo docs/target

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.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Peter Eisentraut <peter_e@gmx.net> 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

Your patch has been added to the PostgreSQL unapplied patches list at:

http://momjian.postgresql.org/cgi-bin/pgpatches

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.

---------------------------------------------------------------------------

Andreas Seltenreich wrote:

Peter Eisentraut <peter_e@gmx.net> 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 bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Patch applied. Thanks.

---------------------------------------------------------------------------

Andreas Seltenreich wrote:

Peter Eisentraut <peter_e@gmx.net> 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 bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Bruce Momjian writes:

Patch applied. Thanks.

Here's a small update to pass the basename of the target as a
stylesheet parameter. This makes the resulting info file work
properly when compressed or split. It also prevents Debian's
"install-info" script from choking.

Thanks,
andreas

Andreas Seltenreich wrote:

Bruce Momjian writes:

Patch applied. Thanks.

Here's a small update to pass the basename of the target as a
stylesheet parameter. This makes the resulting info file work
properly when compressed or split. It also prevents Debian's
"install-info" script from choking.

Applied. Thanks.

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +