Re: [HACKERS] DOCS: SGML identifier may not exceed 44 characters

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Browne <cbbrowne(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] DOCS: SGML identifier may not exceed 44 characters
Date: 2011-05-31 20:36:10
Message-ID: 1306874170.20912.6.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On tis, 2011-05-31 at 12:13 -0400, Tom Lane wrote:
> Christopher Browne <cbbrowne(at)gmail(dot)com> writes:
> > On Tue, May 31, 2011 at 3:22 PM, Alvaro Herrera
> > <alvherre(at)commandprompt(dot)com> wrote:
> >> Excerpts from Brendan Jurd's message of mar may 31 02:17:22 -0400 2011:
> >>> openjade:information_schema.sgml:828:60:Q: length of name token must
> >>> not exceed NAMELEN (44)
>
> >> Odd. I tried it here and it doesn't fail -- same openjade version.
> >> Maybe mine is patched.
>
> > It's not likely an issue of how OpenJade was compiled; there has been
> > a limitation in how SGML parsing was configured. If you poke around
> > in /usr/share/sgml, you should find some configuration indicating
> > NAMELEN was set to 44.
>
> On a Fedora 13 machine:
>
> $ grep -r NAMELEN /usr/share/sgml/
> /usr/share/sgml/openjade-1.3.2/style-sheet.dtd: ArcQuant CDATA #FIXED "NAMELEN 64"
> /usr/share/sgml/docbook/sgml-dtd-3.0-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/sgml-dtd-3.0-1.0-50.fc13/cals-tbl.dtd: NOTE: This set of declarations assumes a NAMELEN of 32 as is used in
> /usr/share/sgml/docbook/sgml-dtd-4.4-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/dsssl-stylesheets/dtds/dbdsssl/dbdsssl.dtd: ArcQuant CDATA #FIXED "NAMELEN 64"
> /usr/share/sgml/docbook/dsssl-stylesheets/dtds/decls/docbook.dcl: NAMELEN 44
> /usr/share/sgml/docbook/sgml-dtd-3.1-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/sgml-dtd-3.1-1.0-50.fc13/cals-tbl.dtd: NOTE: This set of declarations assumes a NAMELEN of 32 as is used in
> /usr/share/sgml/docbook/sgml-dtd-4.1-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/sgml-dtd-4.1-1.0-50.fc13/cals-tbl.dtd: NOTE: This set of declarations assumes a NAMELEN of 32 as is used in
> /usr/share/sgml/docbook/sgml-dtd-4.2-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/sgml-dtd-4.5-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/dsssl-stylesheets-1.79/dtds/dbdsssl/dbdsssl.dtd: ArcQuant CDATA #FIXED "NAMELEN 64"
> /usr/share/sgml/docbook/dsssl-stylesheets-1.79/dtds/decls/docbook.dcl: NAMELEN 44
> /usr/share/sgml/docbook/sgml-dtd-4.3-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/sgml-dtd-4.0-1.0-50.fc13/docbook.dcl: NAMELEN 256
> /usr/share/sgml/docbook/sgml-dtd-4.0-1.0-50.fc13/cals-tbl.dtd: NOTE: This set of declarations assumes a NAMELEN of 32 as is used in
> /usr/share/sgml/html.dcl: NAMELEN 72 -- somewhat arbitrary; taken from
>
> It's hard to tell from this exactly which value is active in what
> contexts, but it does look like 44 is relevant in some. FWIW,
> I don't see the reported failure on this machine ...

It looks like the original DocBook distribution has a limit of 44, but
someone patched it to 256 on your installation.

But it seems like no one else has seen this problem yet, so it's quite
suspicious, since surely people have built the documentation in the last
few months.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Andrew Dunstan 2011-05-31 21:21:58 Re: [HACKERS] DOCS: SGML identifier may not exceed 44 characters
Previous Message Peter Eisentraut 2011-05-31 20:25:17 Re: non-ASCII characters in SGML documentation (and elsewhere)

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2011-05-31 21:05:20 Re: Please test peer (socket ident) auth on *BSD
Previous Message Dimitri Fontaine 2011-05-31 20:11:35 Re: Getting a bug tracker for the Postgres project