| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Peter Eisentraut *EXTERN*" <peter_e(at)gmx(dot)net>, "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-06-01 07:31:36 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C2067E84CF@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Peter Eisentrautwrote:
>>>> 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)
>
> 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.
I have and I encountered the same problem.
I didn't bother to report it because my machine and openjade are quite old:
The machine is Red Hat Enterprise Linux ES release 3 (Taroon Update 9),
and docbook.dcl is from the docbook-dtds-1.0-17.2 RPM.
Maybe that really only affects quite old versions, but I think it wouldn't
hurt to shorten the tag in question to avoid the problem.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-06-01 16:55:21 | Re: [HACKERS] DOCS: SGML identifier may not exceed 44 characters |
| Previous Message | Brendan Jurd | 2011-06-01 01:05:39 | Re: [HACKERS] DOCS: SGML identifier may not exceed 44 characters |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-06-01 08:43:41 | Re: Getting a bug tracker for the Postgres project |
| Previous Message | Alexander Korotkov | 2011-06-01 07:20:04 | Re: pgsql: Protect GIST logic that assumes penalty values can't be negative |